[ODLPARENT-15] features-parent should handle repository versions Created: 16/Jun/15 Updated: 24/Jan/18 Resolved: 28/Aug/15 |
|
| Status: | Resolved |
| Project: | odlparent |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Robert Varga | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 3761 |
| Priority: | Highest |
| Description |
|
features-parent template version substitution works on artifact versions, but not for features. That means we need to retain a property, which cannot be exported from upstream artifacts pom. We want to eradicate version properties, so we really need this feature to make inter-project versioning based solely on a single 'project' version. The project version bears no relationship to the artifact versions actually produced by that project. |
| Comments |
| Comment by Robert Varga [ 16/Jun/15 ] |
|
This blocks build system evolution. |
| Comment by Robert Varga [ 23/Jun/15 ] |
|
Specifically, we need to handle the repository version in this sort of declaration: <features name="openflowplugin-li-${project.version}" xmlns="http://karaf.apache.org/xmlns/features/v1.2.0" Note these should map to artifacts pulled into the project. |
| Comment by Robert Varga [ 29/Jun/15 ] |