| Summary: | kernel test bundlor template contains incorrect version range | ||
|---|---|---|---|
| Product: | [RT] Virgo | Reporter: | Glyn Normington <glyn.normington> |
| Component: | runtime | Assignee: | Chris Frost <eclipse> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | minor | ||
| Priority: | P3 | CC: | eclipse |
| Version: | unspecified | ||
| Target Milestone: | 3.0.0.M01 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 336029 | ||
| Bug Blocks: | |||
This was done as part of the work on Bug 336029, it was required to get an initial build through without breaking the build. Now the new versions have been rippled the changed templates in the kernel and also in web and apps have been put back to the correct ranges and pushed. |
The following: org.eclipse.virgo.util.*;version="${org.eclipse.virgo.util:[=.=.=, +1.+1)}", should of course be: org.eclipse.virgo.util.*;version="${org.eclipse.virgo.util:[=.=.=, +1)}", The incorrect range gives results like [2.2.0, 3.3.0) and [3.0.0, 4.1.0). (I noticed this while working on the framework hooks branch, but the fix clearly needs to go into master.)