You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Vlad Skarzhevskyy (JIRA)" <ji...@codehaus.org> on 2008/03/05 19:56:28 UTC
[jira] Created: (MASSEMBLY-291) attach the resulting assembly not
working as expected
attach the resulting assembly not working as expected
-----------------------------------------------------
Key: MASSEMBLY-291
URL: http://jira.codehaus.org/browse/MASSEMBLY-291
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
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:
https://microemulator.svn.sourceforge.net/svnroot/microemulator/branches/microemulator_2_0_2/microemulator
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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MASSEMBLY-291) attach the resulting assembly not
working as expected
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127523 ]
John Casey commented on MASSEMBLY-291:
--------------------------------------
I've used 2.2-beta-2 specifically for this purpose in the past, so I'll have to investigate the differences between my configuration and yours...
> attach the resulting assembly not working as expected
> -----------------------------------------------------
>
> Key: MASSEMBLY-291
> URL: http://jira.codehaus.org/browse/MASSEMBLY-291
> 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
>
> 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:
> https://microemulator.svn.sourceforge.net/svnroot/microemulator/branches/microemulator_2_0_2/microemulator
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MASSEMBLY-291) attach the resulting assembly not
working as expected
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_128190 ]
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: http://jira.codehaus.org/browse/MASSEMBLY-291
> 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: test.zip
>
>
> 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:
> https://microemulator.svn.sourceforge.net/svnroot/microemulator/branches/microemulator_2_0_2/microemulator
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MASSEMBLY-291) attach the resulting assembly not
working as expected
Posted by "Daniel Spilker (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Spilker updated MASSEMBLY-291:
-------------------------------------
Attachment: test.zip
I stripped down my project to create a test case. It consists of two module where moduleB depends on moduleA. ModuleA is of type "pom" and creates a zip artifact which should be installed a the modules primary artifact. ModuleB should use this artifact to product an archive which contains additional files.
When using 2.2-beta-1 everything is fine:
{noformat}
C:\dspilker\test>mvn clean install
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Unnamed - com.coremedia:test:pom:1-SNAPSHOT
[INFO] Unnamed - com.coremedia.test:moduleA:pom:1-SNAPSHOT
[INFO] Unnamed - com.coremedia.test:moduleB:pom:1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] Building Unnamed - com.coremedia:test:pom:1-SNAPSHOT
[INFO] task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] [site:attach-descriptor]
[INFO] [install:install]
[INFO] Installing C:\dspilker\test\pom.xml to C:\Users\dspilker.QUASIMODO\.m2\repository\com\coremedia\test\1-SNAPSHOT\t
est-1-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[INFO] Building Unnamed - com.coremedia.test:moduleA:pom:1-SNAPSHOT
[INFO] task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory C:\dspilker\test\moduleA\target
[INFO] [site:attach-descriptor]
[INFO] [assembly:attached {execution: make-assembly}]
[INFO] Reading assembly descriptor: C:\dspilker\test\moduleA\src\main\assembly\zip.xml
[INFO] Building zip: C:\dspilker\test\moduleA\target\moduleA-1-SNAPSHOT.zip
[INFO] [install:install]
[INFO] Installing C:\dspilker\test\moduleA\pom.xml to C:\Users\dspilker.QUASIMODO\.m2\repository\com\coremedia\test\modu
leA\1-SNAPSHOT\moduleA-1-SNAPSHOT.pom
[INFO] Installing C:\dspilker\test\moduleA\target\moduleA-1-SNAPSHOT.zip to C:\Users\dspilker.QUASIMODO\.m2\repository\c
om\coremedia\test\moduleA\1-SNAPSHOT\moduleA-1-SNAPSHOT.zip
[INFO] ------------------------------------------------------------------------
[INFO] Building Unnamed - com.coremedia.test:moduleB:pom:1-SNAPSHOT
[INFO] task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory C:\dspilker\test\moduleB\target
[INFO] [site:attach-descriptor]
[INFO] [assembly:attached {execution: make-assembly}]
[INFO] Reading assembly descriptor: C:\dspilker\test\moduleB\src\main\assembly\zip.xml
[INFO] Processing DependencySet (output=/)
[INFO] Expanding: C:\dspilker\test\moduleA\target\moduleA-1-SNAPSHOT.zip into C:\Users\DSPILK~1.QUA\AppData\Local\Temp\a
rchived-file-set.18360180.tmp
[INFO] Building zip: C:\dspilker\test\moduleB\target\moduleB-1-SNAPSHOT.zip
[INFO] [install:install]
[INFO] Installing C:\dspilker\test\moduleB\pom.xml to C:\Users\dspilker.QUASIMODO\.m2\repository\com\coremedia\test\modu
leB\1-SNAPSHOT\moduleB-1-SNAPSHOT.pom
[INFO] Installing C:\dspilker\test\moduleB\target\moduleB-1-SNAPSHOT.zip to C:\Users\dspilker.QUASIMODO\.m2\repository\c
om\coremedia\test\moduleB\1-SNAPSHOT\moduleB-1-SNAPSHOT.zip
[INFO]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] ------------------------------------------------------------------------
[INFO] Unnamed - com.coremedia:test:pom:1-SNAPSHOT ........... SUCCESS [2.054s]
[INFO] Unnamed - com.coremedia.test:moduleA:pom:1-SNAPSHOT ... SUCCESS [0.771s]
[INFO] Unnamed - com.coremedia.test:moduleB:pom:1-SNAPSHOT ... SUCCESS [0.106s]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3 seconds
[INFO] Finished at: Tue Mar 18 11:05:25 CET 2008
[INFO] Final Memory: 10M/18M
[INFO] ------------------------------------------------------------------------
{noformat}
but with 2.2-beta-2 build fails:
{noformat}
C:\dspilker\test>mvn clean install
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Unnamed - com.coremedia:test:pom:1-SNAPSHOT
[INFO] Unnamed - com.coremedia.test:moduleA:pom:1-SNAPSHOT
[INFO] Unnamed - com.coremedia.test:moduleB:pom:1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] Building Unnamed - com.coremedia:test:pom:1-SNAPSHOT
[INFO] task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] [site:attach-descriptor]
[INFO] [install:install]
[INFO] Installing C:\dspilker\test\pom.xml to C:\Users\dspilker.QUASIMODO\.m2\repository\com\coremedia\test\1-SNAPSHOT\t
est-1-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[INFO] Building Unnamed - com.coremedia.test:moduleA:pom:1-SNAPSHOT
[INFO] task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory C:\dspilker\test\moduleA\target
[INFO] [site:attach-descriptor]
[INFO] [assembly:attached {execution: make-assembly}]
[INFO] Reading assembly descriptor: src/main/assembly/zip.xml
[INFO] Building zip: C:\dspilker\test\moduleA\target\moduleA-1-SNAPSHOT.zip
[WARNING] Configuration options: 'appendAssemblyId' is set to false, and 'classifier' is missing.
Instead of attaching the assembly file: C:\dspilker\test\moduleA\target\moduleA-1-SNAPSHOT.zip, it will become the file
for main project artifact.
NOTE: If multiple descriptors or descriptor-formats are provided for this project, the value of this file will be non-de
terministic!
[INFO] [install:install]
[INFO] Installing C:\dspilker\test\moduleA\pom.xml to C:\Users\dspilker.QUASIMODO\.m2\repository\com\coremedia\test\modu
leA\1-SNAPSHOT\moduleA-1-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[INFO] Building Unnamed - com.coremedia.test:moduleB:pom:1-SNAPSHOT
[INFO] task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory C:\dspilker\test\moduleB\target
[INFO] [site:attach-descriptor]
[INFO] [assembly:attached {execution: make-assembly}]
[INFO] Reading assembly descriptor: src/main/assembly/zip.xml
[INFO] Processing DependencySet (output=/)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to create assembly: Failed to resolve dependencies for project: com.coremedia.test:moduleB:pom:1-SNAPSHOT
Missing:
----------
1) com.coremedia.test:moduleA:zip:1-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=com.coremedia.test -DartifactId=moduleA -Dversion=1-SNAPSHOT -Dpackaging=zip -D
file=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=com.coremedia.test -DartifactId=moduleA -Dversion=1-SNAPSHOT -Dpackaging=zip -Dfi
le=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) com.coremedia.test:moduleB:pom:1-SNAPSHOT
2) com.coremedia.test:moduleA:zip:1-SNAPSHOT
----------
1 required artifact is missing.
for artifact:
com.coremedia.test:moduleB:pom:1-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3 seconds
[INFO] Finished at: Tue Mar 18 11:04:18 CET 2008
[INFO] Final Memory: 10M/19M
[INFO] ------------------------------------------------------------------------
{noformat}
Please contact me if you need further information.
> attach the resulting assembly not working as expected
> -----------------------------------------------------
>
> Key: MASSEMBLY-291
> URL: http://jira.codehaus.org/browse/MASSEMBLY-291
> 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: test.zip
>
>
> 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:
> https://microemulator.svn.sourceforge.net/svnroot/microemulator/branches/microemulator_2_0_2/microemulator
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MASSEMBLY-291) attach the resulting assembly not
working as expected
Posted by "Daniel Spilker (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127517 ]
Daniel Spilker commented on MASSEMBLY-291:
------------------------------------------
The same happens to me but I am using
<goals><goal>attached</goal></goals>
> attach the resulting assembly not working as expected
> -----------------------------------------------------
>
> Key: MASSEMBLY-291
> URL: http://jira.codehaus.org/browse/MASSEMBLY-291
> 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
>
> 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:
> https://microemulator.svn.sourceforge.net/svnroot/microemulator/branches/microemulator_2_0_2/microemulator
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MASSEMBLY-291) attach the resulting assembly not
working as expected
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MASSEMBLY-291.
--------------------------------
Assignee: John Casey
Resolution: Fixed
see: http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-assembly-plugin/src/it/projects/mojo-configuration/massembly-291 for an integration test verifying this is fixed.
> attach the resulting assembly not working as expected
> -----------------------------------------------------
>
> Key: MASSEMBLY-291
> URL: http://jira.codehaus.org/browse/MASSEMBLY-291
> 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
> Assignee: John Casey
> Fix For: 2.2-beta-3
>
> Attachments: test.zip
>
>
> 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:
> https://microemulator.svn.sourceforge.net/svnroot/microemulator/branches/microemulator_2_0_2/microemulator
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira