You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Carlos Martins (JIRA)" <ji...@codehaus.org> on 2011/09/29 15:58:17 UTC
[jira] Created: (MASSEMBLY-577) dependencySet inside
moduleSet/binaries picks up dependencies of other dependencySets
dependencySet inside moduleSet/binaries picks up dependencies of other dependencySets
-------------------------------------------------------------------------------------
Key: MASSEMBLY-577
URL: https://jira.codehaus.org/browse/MASSEMBLY-577
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2.1
Environment: JDK 1.6_27, maven 3.0.2, Eclipse Indigo
Reporter: Carlos Martins
Attachments: moduleset-issue.zip
Inside moduleset-issue.zip is a maven project (including eclipse indigo project files)
The project has three modules: module-a, module-b and assembler. The assembler module used the assembly plugin with a descriptor.
You can reproduce the issue by executing "mvn package" for the assembler module and then observing the file moduleset-issue/assebler/target/assembler-0.0.1-SNAPSHOT-bin.zip.
The objective of the descriptor was to create a zip file with two directories: Directory A would include module-a and its dependencies and directory B would contain module-b and its dependencies.
What happens is: both directories have all the dependencies.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MASSEMBLY-577) dependencySet inside moduleSet/binaries
picks up dependencies of other dependencySets
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MASSEMBLY-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MASSEMBLY-577:
--------------------------------------
Component/s: moduleSet
> dependencySet inside moduleSet/binaries picks up dependencies of other dependencySets
> -------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-577
> URL: https://jira.codehaus.org/browse/MASSEMBLY-577
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Components: moduleSet
> Affects Versions: 2.2.1
> Environment: JDK 1.6_27, maven 3.0.2, Eclipse Indigo
> Reporter: Carlos Martins
> Attachments: moduleset-issue.zip, multiproject-modulset-issue.zip
>
>
> Inside moduleset-issue.zip is a maven project (including eclipse indigo project files)
> The project has three modules: module-a, module-b and assembler. The assembler module used the assembly plugin with a descriptor.
> You can reproduce the issue by executing "mvn package" for the assembler module and then observing the file moduleset-issue/assebler/target/assembler-0.0.1-SNAPSHOT-bin.zip.
> The objective of the descriptor was to create a zip file with two directories: Directory A would include module-a and its dependencies and directory B would contain module-b and its dependencies.
> What happens is: both directories have all the dependencies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MASSEMBLY-577) dependencySet inside moduleSet/binaries
picks up dependencies of other dependencySets
Posted by "Ronald Sigmund (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MASSEMBLY-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ronald Sigmund updated MASSEMBLY-577:
-------------------------------------
Attachment: multiproject-modulset-issue.zip
in the zip is a multiproject with the following structure:
* maven-assembly-test (root)
** modul-client (dependecy maven-monitor)
** modul-server (dependency maven-default-skin)
** distribution (the assembly-modul)
*** target/
**** distribution-0.0.1-SNAPSHOT-all/
{color:red}client/lib/maven-default-skin-1.0.jar{color}
client/lib/maven-monitor-2.2.0.jar
client/lib/modul-client.jar
server/lib/maven-default-skin-1.0.jar
{color:red}server/lib/maven-monitor-2.2.0.jar{color}
server/lib/modul-server.jar
**** distribution-0.0.1-SNAPSHOT-client/
client/lib/maven-monitor-2.2.0.jar
client/lib/modul-client.jar
**** distribution-0.0.1-SNAPSHOT-server/
server/lib/maven-default-skin-1.0.jar
server/lib/modul-server.jar
The wrong files are red.
When you run {{mvn}} the build will be failed. Because the last step is checking the generated directories with a enforcer-rule.
> dependencySet inside moduleSet/binaries picks up dependencies of other dependencySets
> -------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-577
> URL: https://jira.codehaus.org/browse/MASSEMBLY-577
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2.1
> Environment: JDK 1.6_27, maven 3.0.2, Eclipse Indigo
> Reporter: Carlos Martins
> Attachments: moduleset-issue.zip, multiproject-modulset-issue.zip
>
>
> Inside moduleset-issue.zip is a maven project (including eclipse indigo project files)
> The project has three modules: module-a, module-b and assembler. The assembler module used the assembly plugin with a descriptor.
> You can reproduce the issue by executing "mvn package" for the assembler module and then observing the file moduleset-issue/assebler/target/assembler-0.0.1-SNAPSHOT-bin.zip.
> The objective of the descriptor was to create a zip file with two directories: Directory A would include module-a and its dependencies and directory B would contain module-b and its dependencies.
> What happens is: both directories have all the dependencies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MASSEMBLY-577) dependencySet inside
moduleSet/binaries picks up dependencies of other dependencySets
Posted by "Filipe Dias (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MASSEMBLY-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283188#comment-283188 ]
Filipe Dias commented on MASSEMBLY-577:
---------------------------------------
I'm experiencing the same problem.
> dependencySet inside moduleSet/binaries picks up dependencies of other dependencySets
> -------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-577
> URL: https://jira.codehaus.org/browse/MASSEMBLY-577
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2.1
> Environment: JDK 1.6_27, maven 3.0.2, Eclipse Indigo
> Reporter: Carlos Martins
> Attachments: moduleset-issue.zip
>
>
> Inside moduleset-issue.zip is a maven project (including eclipse indigo project files)
> The project has three modules: module-a, module-b and assembler. The assembler module used the assembly plugin with a descriptor.
> You can reproduce the issue by executing "mvn package" for the assembler module and then observing the file moduleset-issue/assebler/target/assembler-0.0.1-SNAPSHOT-bin.zip.
> The objective of the descriptor was to create a zip file with two directories: Directory A would include module-a and its dependencies and directory B would contain module-b and its dependencies.
> What happens is: both directories have all the dependencies.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira