[BUILD-47] Investigate why maven-remote-resources-plugin is not used for pom artifacts Created: 01/Nov/10 Updated: 20/Nov/10 Resolved: 20/Nov/10 |
|
| Status: | Closed |
| Project: | Build |
| Component/s: | Poms |
| Affects Version/s: | None |
| Fix Version/s: | POMs 18 |
| Type: | Bug | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Description |
|
We have a couple of modules where a simple bundle is used (stk, newsletter, ldap), and where we have to set the packaging to jar, which is inherently wrong: it creates an "empty" jar artifacts (which is attached to the build and thus uploaded to repositories). If we set those modules to packaging:pom, the assembly still works but is missing the .TXT files from our remote resources. Additionally, we might want to use runOnlyAtExecutionRoot, to investigate. Also check why our parent pom also uses the "bundle" goal. http://maven.apache.org/plugins/maven-remote-resources-plugin/usage.html |
| Comments |
| Comment by Magnolia International [ 20/Nov/10 ] |
|