| Summary: | Composite task doesn't check <add> elements directly | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Andrew Niefer <aniefer> | ||||
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | pascal, pwebster | ||||
| Version: | 3.4.2 | Keywords: | polish | ||||
| Target Milestone: | 3.7 M1 | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Created attachment 172540 [details]
patch
fixed with attached patch Do we want to port that to 3.6.1? We could release this to 3.6.1. It is really a polish item. |
The composite repository ant task reuses the RepositoryList class to specify children repositories. The repository list allows specifing a nested list of repos which is supported by the composite task, but it also can just be a repository itself instead of being a list, this is not supported by the task. This is the difference between using <p2.composite.repository location="file:/parent"> <add location="child"/> </p2.composite.repository> and <p2.composite.repository location="file:/parent"> <add> <repository location="child"/> </add> </p2.composite.repository>