You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stevo Slavic (JIRA)" <ji...@codehaus.org> on 2008/08/13 15:04:28 UTC
[jira] Created: (MNG-3706) Multi-module project with intermodule
dependencies fails to package
Multi-module project with intermodule dependencies fails to package
-------------------------------------------------------------------
Key: MNG-3706
URL: http://jira.codehaus.org/browse/MNG-3706
Project: Maven 2
Issue Type: Bug
Components: Reactor and workspace
Affects Versions: 2.0.9
Reporter: Stevo Slavic
Say we have a maven project with following module structure:
mainproject (packaging: pom)
module 1 (packaging: jar)
module 2 (packaging: pom)
module 2.1 (packing: jar, depends on module 1)
module 2.2 (packagin: jar, depends on module 2.1)
module 3 (packaging: pom)
module 3.1 (packaing: jar, depends on module 1)
module 3.2 (packaging: jar, depends on module 2.2)
If using command line one issues "mvn clean package" on a main project a build error gets reported that while building module 3.1 maven "failed to resolve artifact", reporting module 1 as missing. If using command line one issues "mvn clean install", again on a main project, a similar build error gets reported but now while building module 3.2 maven failed to resolve artifact, reporting as missing module 3.1 and module 2.2.
Before issuing either of the commands I've cleaned up local repository from all of these modules artifacts, expecting that maven will resolve dependencies between modules while building them without using local or remote repositories.
--
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: (MNG-3706) Multi-module project with intermodule
dependencies fails to package
Posted by "Stevo Slavic (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144925#action_144925 ]
Stevo Slavic commented on MNG-3706:
-----------------------------------
One important note, all the modules are snapshots, same version. I wanted, but couldn't set version information just in mainproject pom, and have all others (or at least some modules) reuse it, so now I have to go through all the pom's and set version manually to same value. Using "parent.version" works only in simplest cases, and using separate property didn't work also. But, anyway, that's another issue.
> Multi-module project with intermodule dependencies fails to package
> -------------------------------------------------------------------
>
> Key: MNG-3706
> URL: http://jira.codehaus.org/browse/MNG-3706
> Project: Maven 2
> Issue Type: Bug
> Components: Reactor and workspace
> Affects Versions: 2.0.9
> Reporter: Stevo Slavic
>
> Say we have a maven project with following module structure:
> mainproject (packaging: pom)
> module 1 (packaging: jar)
> module 2 (packaging: pom)
> module 2.1 (packing: jar, depends on module 1)
> module 2.2 (packagin: jar, depends on module 2.1)
> module 3 (packaging: pom)
> module 3.1 (packaing: jar, depends on module 1)
> module 3.2 (packaging: jar, depends on module 2.2)
> If using command line one issues "mvn clean package" on a main project a build error gets reported that while building module 3.1 maven "failed to resolve artifact", reporting module 1 as missing. If using command line one issues "mvn clean install", again on a main project, a similar build error gets reported but now while building module 3.2 maven failed to resolve artifact, reporting as missing module 3.1 and module 2.2.
> Before issuing either of the commands I've cleaned up local repository from all of these modules artifacts, expecting that maven will resolve dependencies between modules while building them without using local or remote repositories.
--
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: (MNG-3706) Multi-module project with intermodule
dependencies fails to package
Posted by "Stevo Slavic (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stevo Slavic closed MNG-3706.
-----------------------------
Resolution: Not A Bug
Issue was in wrong use of maven assembly plugin where instead of "attached" goal, "assembly" goal was used, breaking multimodule project build.
> Multi-module project with intermodule dependencies fails to package
> -------------------------------------------------------------------
>
> Key: MNG-3706
> URL: http://jira.codehaus.org/browse/MNG-3706
> Project: Maven 2
> Issue Type: Bug
> Components: Reactor and workspace
> Affects Versions: 2.0.9
> Reporter: Stevo Slavic
>
> Say we have a maven project with following module structure:
> mainproject (packaging: pom)
> module 1 (packaging: jar)
> module 2 (packaging: pom)
> module 2.1 (packing: jar, depends on module 1)
> module 2.2 (packagin: jar, depends on module 2.1)
> module 3 (packaging: pom)
> module 3.1 (packaing: jar, depends on module 1)
> module 3.2 (packaging: jar, depends on module 2.2)
> If using command line one issues "mvn clean package" on a main project a build error gets reported that while building module 3.1 maven "failed to resolve artifact", reporting module 1 as missing. If using command line one issues "mvn clean install", again on a main project, a similar build error gets reported but now while building module 3.2 maven failed to resolve artifact, reporting as missing module 3.1 and module 2.2.
> Before issuing either of the commands I've cleaned up local repository from all of these modules artifacts, expecting that maven will resolve dependencies between modules while building them without using local or remote repositories.
--
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