You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Albert Kurucz (JIRA)" <ji...@codehaus.org> on 2009/05/19 16:12:44 UTC

[jira] Commented: (MASSEMBLY-410) assembly is not attached

    [ http://jira.codehaus.org/browse/MASSEMBLY-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177130#action_177130 ] 

Albert Kurucz commented on MASSEMBLY-410:
-----------------------------------------

After further searching I have found out I probably need "ModuleBinaries" and "attachmentClassifier" to set.
If this is true, BUG report should be changed to documentation improvement request.

Can I get some help how to use "ModuleBinaries" and "attachmentClassifier" for my project?
This is the best what I have found:
http://www.sonatype.com/books/maven-book/reference/assemblies-sect-modulesets.html
but it does not say if it has to go to parent POM, module POM or to the assembly descriptor file.

I good example project with multiple modules which uses this packaging would help.
Can I have a link please?


> 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