![]() pdebuild.jar - pdebuildsrc/org/**/*.java If the plug-in contains additional libraries "foo/lib.jar", the source is expected to be in corresponding "foo/libsrc/" folders in the source bundles. This is the main case for most jarred plug-ins. The root of the plug-in maps to the root of the source bundle. Class file libraries are mapped to source locations in a predictable manner. In order for PDE/UI to properly access it, custom source should be place in proper location. This can be accomplished using customBuildCallbacks in the plug-in.Īs an extension to "src.zip in CVS" above this, custom content can always be included in the generated source bundle using the src.includes property and the custom callback. When building individual source bundles, this src.zip should be unzipped into the root of the source bundle. Some bundles (for example org.junit4, or ) have a src.zip in CVS that is included in the source bundle via the src.includes property. Or, bundles can explicitly specify in their own build.properties file that no source bundle should be generated for them: In this case, the bundles may be excluded by the feature as outlined above in generate.feature. This may occur with platform specific fragments that only contain a native library. By default a generated source feature does not have a bin.includes and will be excluded from the build.Įxample: The sdk.examples feature used to look like this in the feature.xmlĪnd in the feature's changes to the following in the feature.xml:Īnd this in the feature's in the feature.xml:Īnd in the feature's plug-ins may not require source bundles because they don't actually contain source. Or, the ugin property can be changed to a generate.feature property and the source feature included. When generating individual source bundle, features will need to include a *.source bundle for each plug-in along with a corresponding ugin property for each one. When generating individual source bundles, this changes to be based on a given ugin property was used by features to include source without having a source feature (even though behind the scenes an entire source feature was generated). This can be accomplished with the addition of arguments to the generate.feature ugin generates a source bundle based on a given feature. Some plug-ins that were included in the originating feature (ie doc plugins) may not have source and should be excluded from the generated source feature. ![]() This is useful for adding doc plug-ins to the source feature. Plug-ins that were included in the source feature via the syntax will not get corresponding source bundles. In the new way, the source feature will include a source bundle for each plug-in/fragment listed in the original feature. Before, the source feature would have included 1 source plugin + a source fragment for each platform being built. In a feature's build.properties file, the generate.feature property tells pde.build to generate a source = [, [, generating individual source bundles, this property remains as before, the difference will be noticed in the resulting source feature. However, generally, things are never that easy. If you are lucky, this is all that is required. ![]() This tells pde.build that you want to generate the new-style source bundles. In your build configuration's build.properties file, set the property ![]() 7 sourceTemplatePlugin vs sourceTemplateBundle. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |