[MAGNOLIA-1439] Magnolia build to create a war builds using older release jars Created: 27/Mar/07 Updated: 08/Sep/08 Resolved: 08/Sep/08 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 3.0.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | David Smith | Assignee: | Magnolia International |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Sun Java 1.5.0_10, Maven 2.0.5 |
||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
Magnolia subproject in the 3.0.x branch builds a war using older 3.0.2 jars rather than the 3.0.x-SNAPSHOT jars just built in the local subprojects. It seems rather counter-intuitive to go through the process of building a .war file from branch that doesn't actually use the branch jar files. Dependencies in the magnolia subproject pom.xml should use the snapshot jars built by the other subprojects. |
| Comments |
| Comment by Magnolia International [ 08/Sep/08 ] |
|
Please reopen if this occurs again, but I believe both the 3.0 and the 3.5 branch are fine. We had a whole load of issues with the release plugin prior to 3.5, but the branch and the pom you mention seem ok now. |