Re: [pde-dev] PDE Incubator "b3" project proposal

[Andrew Niefer <aniefer@xxxxxxxxxx>]

I will also be adding my name to this
project.

With the reminder that PDE/Build has
its own history of backwards compatibility to maintain, I think it would
be good discover what changes can be made to make it easier for other projects
to extend and take advantage of what is available in build.  Similarly,
I would like to look at places where PDE/Build can provide points so that
other bundles could contribute information to the build.  Target platforms
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=284480)
are a perfect example of this.

PDE/Build has never had much of an official
API beyond what it exposes to PDE/UI., it would be good to identify which
pieces are generally interesting and can be exposed to others.

-Andrew

From:	Ian Bull <irbull@xxxxxxxxxxxxxxxxx>
To:	"Eclipse PDE general developers list." <pde-dev@xxxxxxxxxxx>
Date:	07/28/2009 01:36 PM
Subject:	Re: [pde-dev] PDE Incubator "b3" project proposal
Sent by:	pde-dev-bounces@xxxxxxxxxxx

---

I am very excited about the b3 proposal and I would like
to join the project. I have knowledge of p2, modeling and I'm getting better
with PDE/Build ;).  I have been thinking about the Eclipse build story
for a while, and here are some random thoughts:

1. Eclipse has shown great leadership with respect to OSGi.  Eclipse
provides the reference implementation, arguably the most widely adopted
OSGi platform, an excellent provisioning system and some of the best tool
support for OSGi.  I see b3 as an opportunity for the Eclipse community
to design "the" build environment for OSGi.

2. Provide a consistent build model at all levels of abstraction. 
Whether your are building features, products, bundles or collections of
things, providing a consistent model is key.  Currently (with PDE/Build
-- please don't take this as a criticism) consistency among build types
is lacking.  Different scripts and properties are used to build "seemingly"
similar things. B3 provides an opportunity to review some of these inconsistencies
and look for areas of improvement.

3. Review our abstraction story.  Currently features (and in many
respects, products) are primarily a build / deployment time construct (they
have little use at run-time, and are seldom used during development time). 
B3 provides an opportunity to review this (and other build time abstractions). 
I'm not saying we should remove / rewrite the notation of features -- just
review their role.

4. Bring target management to build.  PDE has done an excellent job
of bringing target management to the developers, this same functionality
(and top-notch tooling) should be brought to the build infrastructure.

Cheers,
Ian

On Tue, Jul 28, 2009 at 7:47 AM, Chris Aniszczyk <zx@xxxxxxxxxxxxxxxxx>
wrote:
On Tue, Jul 28, 2009 at 4:57 AM, Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>
wrote:
The web interface for newsgroup does not allow for new
posts to be posted on eclipse.b3. Is this normal?

The newsgroup isn't created yet as this is just the draft of the project proposal. You can use this mailing list for comments now.

Cheers,

--
Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk

_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev




--
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev