[
http://jira.codehaus.org/browse/MASSEMBLY-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Albert Kurucz closed MASSEMBLY-410.
-----------------------------------
Resolution: Fixed
Assembly descriptor (configuration) file has the problem.
It was not a bug of the plugin.
> assembly is not attached
> ------------------------
>
> Key: MASSEMBLY-410
> URL: http://jira.codehaus.org/browse/MASSEMBLY-410
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Reporter: Albert Kurucz
>
> Please look at the POM of this project:
> http://svn.codehaus.org/jtstand/trunk/jtstand/jtstand-demo/
> It includes an assembly executed at "package" phase.
> It creates a zip file into "target/jtstand-demo-1.0-SNAPSHOT-distribution.zip"
> This zip file is the one, which I want the mvn deploy to send out to
> the codehaus repo, and not the
> "target/jtstand-demo-1.0-SNAPSHOT.jar" which is already packed into
> the distro file.
> Problem: Even if I have
> "
> <plugin>
> <artifactId>maven-assembly-plugin</artifactId>
> <configuration>
> <attach>true</attach>
> "
> The "mvn deploy" does not deploy the zip file made by the assembly plugin.
> How can I find out if the deploy plugin ignores a correctly attached zip
> file, or the assembly is not attaching?
--
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
