Re: [pde-build-dev] Building the platform feature

[Andrew Niefer <aniefer@xxxxxxxxxx>]

Hi Thomas,

PDE.Build does not look at the project
descriptor files, so I would guess one reason that information isn't there
is simply that it isn't needed.  The features are there to drive the
build, and I don't expect people load them in the workspace that often.

Having features and plugins with the
same project name is not a problem in pde.build because they are fetched
to separate /features and /plugins directories.

-Andrew

Thomas Hallgren <thomas@xxxxxxx>
Sent by: pde-build-dev-bounces@xxxxxxxxxxx

10/25/2006 04:21 AM

Please respond to
"Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>

To	pde-build-dev@xxxxxxxxxxx
cc
Subject	[pde-build-dev] Building the platform feature

Hi,
As a step in making Buckminster more PDE-build compliant, I'm now trying
to build the whole org.eclipse.platform-feature feature and everything
that it depends on and not surprisingly :-), I run into some problems.

The first thing I noticed was that many (most?) of the features that I
find under the /cvsroot/eclipse have a stripped project descriptor 
files. The only element with content is the project name. I would have
expected the 'org.eclipse.pde.FeatureNature' nature element there and 
perhaps also a buildCommand for the 'org.eclipse.pde.FeatureBuilder'. 
I'm curious. Why you are leaving this out?

I've also noted that the project names are not unique. You have a 
feature project called 'org.eclipse.rcp' and a plugin with the exact 
same name. Consequently, I cannot materialize both of them without 
inventing a new name for one of them. What conventions do you use when
you do that?

Kind Regards,
Thomas Hallgren



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