Source bundle and roots [message #384841] |
Wed, 15 April 2009 12:32 |
|
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
|
|
|
|
Powered by
FUDForum. Page generated in 0.03508 seconds