[
http://jira.codehaus.org/browse/MNG-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146053#action_146053
]
Piotr Oktaba commented on MNG-2398:
-----------------------------------
I have similar problem. During release goals 'clean verify' are called. When
one artifact depends on another attached artifact release fails due to
unsatisfied dependency. Workaround is to call goals 'clean install' from
maven-release-plugin.
However, maven should properly resolved that artifacts.
> attached artifacts (such as assemblies) are not resolved in the workspace
> when running 'package' phase
> ------------------------------------------------------------------------------------------------------
>
> Key: MNG-2398
> URL: http://jira.codehaus.org/browse/MNG-2398
> Project: Maven 2
> Issue Type: Bug
> Components: Reactor and workspace
> Affects Versions: 2.0.4
> Environment: Running of Mac OSX 10.4
> Reporter: Matt Brozowski
> Priority: Blocker
> Fix For: 2.0.11
>
> Attachments: attached-artifact-bug.tar.gz,
> maven-project-2.0.4-patch.txt
>
>
> I have attached a sample project.
> submoduleA creates an attached artifact (a tar.gz assembly) which submoduleB
> depends on.
> When running:
> mvn package
> The attached artifact cannot be resolved from the workspace but tries the
> repos instead, yet when running:
>
> This problems makes using attached artifacts very 'risky' because it could be
> running 'old' code.
--
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
