Eclipse Community Forums: Buckminster » Source bundle and roots

Help

Home

Home » Archived » Buckminster » Source bundle and roots

Show: Today's Messages :: Show Polls :: Message Navigator

Source bundle and roots [message #384841]

Wed, 15 April 2009 12:32

Thomas Hallgren

Messages: 3240
Registered: July 2009

Senior Member

I'm going to change the source generation so that Buckminster looks at the build.properties file property:

src.additionalRoots

instead of the:

src.includes

when generating the 'roots' declaration included in the manifest. The src.includes will still be used to determine what
to include into the feature. If no src.additionalRoots is found, then the root will be set to ".".

Background:
The current generated source bundles doesn't function very well when they are imported into a workspace. This is because
the implementation mixes two ways of looking at the definitions.

Using the feature editor, you can specify what should be included in a "Source Build". This ends up in the as the
src.includes property in build.properties file and tells Buckminster what it is that should be copied to the source
bundle. Buckminster will also use this information to declare source 'roots' in the manifest. And this is where it gets
messed up. PDE assumes that source roots are to be placed beneath the source that is declared in the class path.
Consequently, the imported bundle ends up with a src/src folder and errors indicating unexpected package. Not good.

For more information about the src.includes and src.additionalRoots property, see:

http://help.eclipse.org/stable/index.jsp?topic=/org.eclipse. pde.doc.user/tasks/pde_individual_source.htm

Let me know if you see any problems or have any issues with this approach.

Regards,
Thomas Hallgren

Report message to a moderator

Re: Source bundle and roots [message #384850 is a reply to message #384841]

Fri, 17 April 2009 08:49

Achim Demelt

Messages: 160
Registered: July 2009

Senior Member

Hi Thomas,

Now that my source features appear in the update site ;-) I could verify the
problem. Your solution seems appropriate.

Regards,
Achim

Thomas Hallgren wrote:

> I'm going to change the source generation so that Buckminster looks at the
> build.properties file property:
>
> src.additionalRoots
>
> instead of the:
>
> src.includes
>
> when generating the 'roots' declaration included in the manifest. The
> src.includes will still be used to determine what to include into the
> feature. If no src.additionalRoots is found, then the root will be set to
> ".".
>
> Background:
> The current generated source bundles doesn't function very well when they
> are imported into a workspace. This is because the implementation mixes
> two ways of looking at the definitions.
>
> Using the feature editor, you can specify what should be included in a
> "Source Build". This ends up in the as the src.includes property in
> build.properties file and tells Buckminster what it is that should be
> copied to the source bundle. Buckminster will also use this information to
> declare source 'roots' in the manifest. And this is where it gets messed
> up. PDE assumes that source roots are to be placed beneath the source that
> is declared in the class path. Consequently, the imported bundle ends up
> with a src/src folder and errors indicating unexpected package. Not good.
>
> For more information about the src.includes and src.additionalRoots
> property, see:
>
>
http://help.eclipse.org/stable/index.jsp?topic=/org.eclipse. pde.doc.user/tasks/pde_individual_source.htm
>
> Let me know if you see any problems or have any issues with this approach.
>
> Regards,
> Thomas Hallgren

Report message to a moderator

Previous Topic:	Include source features in site
Next Topic:	Error parsing site stream

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Wed Apr 24 21:29:19 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter