maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Commented: (MASSEMBLY-291) attach the resulting assembly not working as expected
Date Fri, 21 Mar 2008 18:29:46 GMT


Benjamin Bentmann commented on MASSEMBLY-291:

bq. <appendAssemblyId>false</appendAssemblyId>
This setting causes the Assembly plugin to set the generated assembly as the file of the project's
main artifact instead of attaching it as a separate artifact. This fails for a project with
packaging "pom" because the Install plugin does not expect that.

The same logic caused MASSEMBLY-301.

> attach the resulting assembly not working as expected
> -----------------------------------------------------
>                 Key: MASSEMBLY-291
>                 URL:
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-2
>         Environment: Maven version: 2.0.8
> Java version: 1.5.0_14
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>            Reporter: Vlad Skarzhevskyy
>         Attachments:
> After changing to  2.2-beta-2 attach is not working in our project.
> This is configuration used:
> project:  <packaging>pom</packaging>
> maven-assembly-plugin:
>  <phase>package</phase>
>  <goals><goal>single</goal></goals>
> <configuration>
>                            <attach>true</attach>
>                            <appendAssemblyId>false</appendAssemblyId>
> ....
> The idea is to replace main artifact jar with created jar.  packaging pom  has been selected
base on example form the site. May be this is wrong but used to work in version 2.1.
> Full Project  here:
> PS
>  We also have second sources assembly in the same pom.xml  This assembly is installed
to local repository!

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message