[MAGNOLIA-1414] build with maven 2.0.5 Created: 28/Feb/07 Updated: 23/Jan/13 Resolved: 28/Feb/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 3.0.1 |
| Fix Version/s: | 3.0.2, 3.1 M1 |
| Type: | Task | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Description |
|
Since maven 2.0.5 has a much more consistent dependencies resolution mechanism than previous versions, we should mandate its usage to avoid inconsistant builds (we've add trouble in the past controlling precisely which dependencies would end up in the final war artifact for instance) |
| Comments |
| Comment by Magnolia International [ 28/Feb/07 ] |
|
Right, well, as discussed here: The <prerequisites> feature was mostly intended for plugins to check their environment. Until a version of the maven-enforcer-plugin is available, our build will use geronimo's "tools-maven-plugin", which allows the build to break if a certain version of maven is not used (2.0.5+ in our case) |
| Comment by Magnolia International [ 28/Feb/07 ] |
|
commited to 3.0 branch and trunk |