[
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
