You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ken Cheng (JIRA)" <ji...@codehaus.org> on 2010/11/14 13:10:04 UTC
[jira] Created: (MNG-4897) Maven 3 : In Multi-Module project, one
module project can not depend on another
Maven 3 : In Multi-Module project, one module project can not depend on another
-------------------------------------------------------------------------------
Key: MNG-4897
URL: http://jira.codehaus.org/browse/MNG-4897
Project: Maven 2 & 3
Issue Type: Bug
Components: Apache or Maven Parent poms
Affects Versions: 3.0
Environment: Ubuntu 9.10
Jdk 1.6
Mavne 3.0
Reporter: Ken Cheng
Attachments: parent.zip
Hi All,
Right now I am upgrading my project from maven2 to maven3. My project is a
multiple-module project such as
- Parent ----> It's the parent project and it only contains a pom.xml
---- module-A ---> It is one child module
---- module-B ---> It is another child module at the same time it depends
on module-A
This project runs well with Maven2 but after I upgrade to Maven3, I can not
build module-B. The error message such like below
[ERROR] Failed to execute goal on project child2: Could not resolve
dependencies for project com.abc:child2:jar:1.0-SNAPSHOT: Could not find
artifact com.abc:child1:jar:3.8.1 in central (http://repo1.maven.org/maven2)
-> [Help 1]
By the way, It's very easy to reproduce this issue with the attached simple
java project. You can go to "Child2" project and run "mvn compile" to
reproduce the issue.
--
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: (MNG-4897) Maven 3 : In Multi-Module project, one
module project can not depend on another
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MNG-4897:
-----------------------------------
Component/s: (was: Apache or Maven Parent poms)
Dependencies
> Maven 3 : In Multi-Module project, one module project can not depend on another
> -------------------------------------------------------------------------------
>
> Key: MNG-4897
> URL: http://jira.codehaus.org/browse/MNG-4897
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 3.0
> Environment: Ubuntu 9.10
> Jdk 1.6
> Mavne 3.0
> Reporter: Ken Cheng
> Attachments: parent.zip
>
>
> Hi All,
> Right now I am upgrading my project from maven2 to maven3. My project is a
> multiple-module project such as
> - Parent ----> It's the parent project and it only contains a pom.xml
> ---- module-A ---> It is one child module
> ---- module-B ---> It is another child module at the same time it depends
> on module-A
> This project runs well with Maven2 but after I upgrade to Maven3, I can not
> build module-B. The error message such like below
> [ERROR] Failed to execute goal on project child2: Could not resolve
> dependencies for project com.abc:child2:jar:1.0-SNAPSHOT: Could not find
> artifact com.abc:child1:jar:3.8.1 in central (http://repo1.maven.org/maven2)
> -> [Help 1]
> By the way, It's very easy to reproduce this issue with the attached simple
> java project. You can go to "Child2" project and run "mvn compile" to
> reproduce the issue.
--
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-4897) Maven 3 : In Multi-Module project, one
module project can not depend on another
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-4897.
----------------------------------
Resolution: Cannot Reproduce
Assignee: Benjamin Bentmann
bq. By the way, It's very easy to reproduce this issue with the attached simple java project. You can go to "Child2" project and run "mvn compile" to reproduce the issue.
Unpacking your archive and running "mvn compile" on the {{child2}} module fails with both Maven 2.x and 3.0 due to an unresolvable dependency on {{com.abc:child1:jar:3.8.1}}. After manually fixing your example project to use the proper version 1.0-SNAPSHOT for the dependency, running "mvn compile" on child2 still fails with both Maven versions, which isn't suprising given that both {{child1}} and {{parent}} haven't been installed yet. So I run "mvn install" on the parent directory, cd back into {{child2}} and now "mvn compile" works, again with both Maven versions.
-> Whatever issue you face, it's not reproducible from the given project and instructions.
> Maven 3 : In Multi-Module project, one module project can not depend on another
> -------------------------------------------------------------------------------
>
> Key: MNG-4897
> URL: http://jira.codehaus.org/browse/MNG-4897
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 3.0
> Environment: Ubuntu 9.10
> Jdk 1.6
> Mavne 3.0
> Reporter: Ken Cheng
> Assignee: Benjamin Bentmann
> Attachments: parent.zip, parent.zip
>
>
> Hi All,
> Right now I am upgrading my project from maven2 to maven3. My project is a
> multiple-module project such as
> - Parent ----> It's the parent project and it only contains a pom.xml
> ---- module-A ---> It is one child module
> ---- module-B ---> It is another child module at the same time it depends
> on module-A
> This project runs well with Maven2 but after I upgrade to Maven3, I can not
> build module-B. The error message such like below
> [ERROR] Failed to execute goal on project child2: Could not resolve
> dependencies for project com.abc:child2:jar:1.0-SNAPSHOT: Could not find
> artifact com.abc:child1:jar:3.8.1 in central (http://repo1.maven.org/maven2)
> -> [Help 1]
> By the way, It's very easy to reproduce this issue with the attached simple
> java project. You can go to "Child2" project and run "mvn compile" to
> reproduce the issue.
--
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: (MNG-4897) Maven 3 : In Multi-Module project, one
module project can not depend on another
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MNG-4897:
-----------------------------------
Attachment: parent.zip
Fixed example project (proper dependency version for child2).
> Maven 3 : In Multi-Module project, one module project can not depend on another
> -------------------------------------------------------------------------------
>
> Key: MNG-4897
> URL: http://jira.codehaus.org/browse/MNG-4897
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 3.0
> Environment: Ubuntu 9.10
> Jdk 1.6
> Mavne 3.0
> Reporter: Ken Cheng
> Attachments: parent.zip, parent.zip
>
>
> Hi All,
> Right now I am upgrading my project from maven2 to maven3. My project is a
> multiple-module project such as
> - Parent ----> It's the parent project and it only contains a pom.xml
> ---- module-A ---> It is one child module
> ---- module-B ---> It is another child module at the same time it depends
> on module-A
> This project runs well with Maven2 but after I upgrade to Maven3, I can not
> build module-B. The error message such like below
> [ERROR] Failed to execute goal on project child2: Could not resolve
> dependencies for project com.abc:child2:jar:1.0-SNAPSHOT: Could not find
> artifact com.abc:child1:jar:3.8.1 in central (http://repo1.maven.org/maven2)
> -> [Help 1]
> By the way, It's very easy to reproduce this issue with the attached simple
> java project. You can go to "Child2" project and run "mvn compile" to
> reproduce the issue.
--
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