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 2009/03/30 01:25:12 UTC
[jira] Created: (MDEP-204) go-offline fails to resolve artifact
available in maven reactor
go-offline fails to resolve artifact available in maven reactor
---------------------------------------------------------------
Key: MDEP-204
URL: http://jira.codehaus.org/browse/MDEP-204
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: go-offline
Affects Versions: 2.1, 2.0
Environment: maven 2.1.0
Reporter: Stevo Slavic
Assignee: Brian Fox
Attachments: mvn-dependency-go-offline-failing-example.zip
Attached is example project, for which IMO dependency:go-offline should be able to resolve all dependencies as they are only intermodule dependencies within same multimodule project which haven't been installed yet but are available in maven reactor so can be considered as resolvable in offline mode - instead dependency:go-offline fails to resolve these dependencies.
--
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: (MDEP-204) go-offline fails to resolve artifact
available in maven reactor
Posted by "Louis Lecaroz (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196458#action_196458 ]
Louis Lecaroz commented on MDEP-204:
------------------------------------
Having the same issue on a project in Maven 2.2.1.
I am also blocked on a maven deployment on some remote dev workstation due to this error.... developers needs to go offline with a big project containing some child modules having dependencies exactly like in this example attached in this issue to work offline & remotly & the go-offline fails with the same error.
I was able to reproduce this issue with the attached zip above also in 2.2.1
> go-offline fails to resolve artifact available in maven reactor
> ---------------------------------------------------------------
>
> Key: MDEP-204
> URL: http://jira.codehaus.org/browse/MDEP-204
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: go-offline
> Affects Versions: 2.0, 2.1
> Environment: maven 2.1.0
> Reporter: Stevo Slavic
> Assignee: Brian Fox
> Attachments: mvn-dependency-go-offline-failing-example.zip
>
>
> Attached is example project, for which IMO dependency:go-offline should be able to resolve all dependencies as they are only intermodule dependencies within same multimodule project which haven't been installed yet but are available in maven reactor so can be considered as resolvable in offline mode - instead dependency:go-offline fails to resolve these dependencies.
--
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: (MDEP-204) go-offline fails to resolve artifact
available in maven reactor
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198762#action_198762 ]
Brian Fox commented on MDEP-204:
--------------------------------
patches welcome ;-)
> go-offline fails to resolve artifact available in maven reactor
> ---------------------------------------------------------------
>
> Key: MDEP-204
> URL: http://jira.codehaus.org/browse/MDEP-204
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: go-offline
> Affects Versions: 2.0, 2.1
> Environment: maven 2.1.0
> Reporter: Stevo Slavic
> Assignee: Brian Fox
> Attachments: mvn-dependency-go-offline-failing-example.zip
>
>
> Attached is example project, for which IMO dependency:go-offline should be able to resolve all dependencies as they are only intermodule dependencies within same multimodule project which haven't been installed yet but are available in maven reactor so can be considered as resolvable in offline mode - instead dependency:go-offline fails to resolve these dependencies.
--
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: (MDEP-204) go-offline fails to resolve artifact
available in maven reactor
Posted by "Corneil du Plessis (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=270219#comment-270219 ]
Corneil du Plessis commented on MDEP-204:
-----------------------------------------
I'm amazed that this issue is still unresolved. Does no one use dependency:go-offline for multi-module projects?
> go-offline fails to resolve artifact available in maven reactor
> ---------------------------------------------------------------
>
> Key: MDEP-204
> URL: http://jira.codehaus.org/browse/MDEP-204
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: go-offline
> Affects Versions: 2.0, 2.1
> Environment: maven 2.1.0
> Reporter: Stevo Slavic
> Assignee: Brian Fox
> Attachments: mvn-dependency-go-offline-failing-example.zip
>
>
> Attached is example project, for which IMO dependency:go-offline should be able to resolve all dependencies as they are only intermodule dependencies within same multimodule project which haven't been installed yet but are available in maven reactor so can be considered as resolvable in offline mode - instead dependency:go-offline fails to resolve these dependencies.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDEP-204) go-offline fails to resolve artifact
available in maven reactor
Posted by "manuel aldana (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197374#action_197374 ]
manuel aldana commented on MDEP-204:
------------------------------------
The same for me here (maven 2.1.0), I think this is a severe issue. The only workaround to use dependency:resolve/tree etc. is to do a *mvn install* beforehand, so the modules are inside repository.
> go-offline fails to resolve artifact available in maven reactor
> ---------------------------------------------------------------
>
> Key: MDEP-204
> URL: http://jira.codehaus.org/browse/MDEP-204
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: go-offline
> Affects Versions: 2.0, 2.1
> Environment: maven 2.1.0
> Reporter: Stevo Slavic
> Assignee: Brian Fox
> Attachments: mvn-dependency-go-offline-failing-example.zip
>
>
> Attached is example project, for which IMO dependency:go-offline should be able to resolve all dependencies as they are only intermodule dependencies within same multimodule project which haven't been installed yet but are available in maven reactor so can be considered as resolvable in offline mode - instead dependency:go-offline fails to resolve these dependencies.
--
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: (MDEP-204) go-offline fails to resolve artifact
available in maven reactor
Posted by "jonathan gold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198747#action_198747 ]
jonathan gold commented on MDEP-204:
------------------------------------
I'd also like to request that the plugin be changed to be reactor aware. I have projects with intermodule dependencies, and it appears that the only way I can use the dependency:tree plugin is to first install my project into my local repo. Full context of the discussion is here: http://markmail.org/message/z2sya75pynr3ia2k?q=list:org%2Eapache%2Emaven%2Eusers
> go-offline fails to resolve artifact available in maven reactor
> ---------------------------------------------------------------
>
> Key: MDEP-204
> URL: http://jira.codehaus.org/browse/MDEP-204
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: go-offline
> Affects Versions: 2.0, 2.1
> Environment: maven 2.1.0
> Reporter: Stevo Slavic
> Assignee: Brian Fox
> Attachments: mvn-dependency-go-offline-failing-example.zip
>
>
> Attached is example project, for which IMO dependency:go-offline should be able to resolve all dependencies as they are only intermodule dependencies within same multimodule project which haven't been installed yet but are available in maven reactor so can be considered as resolvable in offline mode - instead dependency:go-offline fails to resolve these dependencies.
--
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