You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Corneil du Plessis (JIRA)" <ji...@codehaus.org> on 2011/06/12 22:40:42 UTC
[jira] Commented: (MDEP-204) go-offline fails to resolve artifact
available in maven reactor
[ 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