Bugzilla – Full Text Bug Listing
| Summary: | customTargets/Assembly project names | ||
|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Andrew Niefer <aniefer> |
| Component: | Build | Assignee: | pde-build-inbox <pde-build-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.7 | ||
| Target Milestone: | 3.7 M5 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
fixed by naming the projects "customTargets.template" and "customAssembly.template" |
Both the customTargets.xml and the customAssembly.xml template scripts have "Build specific targets and properties" as the project name. When using <import> to reuse and override these templates without having your own complete copy, the project name becomes a qualifier through which you can invoke targets from the import that you have overridden. There are two issues here: 1) This actually is a very awkward name if you want to reference the parent task: <property name="super" value="Build specific targets and properties" /> <import file="${eclipse.pdebuild.templates}/headless-build/customTargets.xml"/> <target name="getMapFiles" unless="skipMaps"> <antcall target="${super}.getMapFiles" /> </target 2) The two custom scripts have the same name which results in warnings if both are being used in this way: Duplicated project name in import. Project Build specific targets and properties defined first in .... This also prevents you from accessing the super's targets in both scripts. We should rename the templates so that they can be more easily consumed in this manner.