[
http://jira.codehaus.org/browse/MASSEMBLY-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165658#action_165658
]
Luke Nezda commented on MASSEMBLY-196:
--------------------------------------
I second Martin's comment, if you copy-paste the example from
http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/using-repositories.html,
it doesn't produce the output it indicates it should. Primary element that is
missing from the resulting repository seems to be the project artifact itself.
If you add an apropos explicit {{<dependencySet>}} for this artifact, it
doesn't copy it (e.g., the jar) along side the metadata (pom, sha1, md5), but
rather to the base dir, so it doesn't result in a valid repository. I tried to
run the integration test ({{mvn integration-test}} right?), but I don't follow
the setup well enough to verify my own expectations of it. I'm willing to help
fix the documentation and/or code and/or provide a test case. I'm using Maven
2.0.9, maven-assembly-plugin 2.2-beta-3. Results definitely "improved" from
beta1 to beta3, but still doesn't seem quite right.
> use of repository assembly is no longer working
> -----------------------------------------------
>
> Key: MASSEMBLY-196
> URL: http://jira.codehaus.org/browse/MASSEMBLY-196
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Reporter: Brett Porter
> Assignee: John Casey
> Fix For: 2.2-beta-3
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> I have the following that works in 2.1:
> <repositories>
> <repository>
> <outputDirectory>repository/releases</outputDirectory>
> <includeMetadata>true</includeMetadata>
> <groupVersionAlignments>
> <groupVersionAlignment>
> <id>org.apache.maven</id>
> <version>2.0.5</version>
> <excludes>
> <exclude>maven-plugin-surrogate-parent</exclude>
> <exclude>maven-archetype</exclude>
> <exclude>maven-archetype-core</exclude>
> <exclude>maven-archiver</exclude>
> <exclude>maven-parent</exclude>
> <exclude>maven-jxr</exclude>
> <exclude>maven-plugin-tools-java</exclude>
> <exclude>maven-plugin-tools-beanshell</exclude>
> <exclude>maven-plugin-tools-api</exclude>
> <exclude>maven-plugin-tools</exclude>
> </excludes>
> </groupVersionAlignment>
> </groupVersionAlignments>
> </repository>
> </repositories>
> However, in 2.2-beta-1 it results in an empty directory being created in the
> assembly instead of copying the repository contents.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
