You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brian Fox (JIRA)" <ji...@codehaus.org> on 2008/03/08 02:55:28 UTC
[jira] Updated: (MNG-2398) attached artifacts (such as assemblies)
are not resolved in the workspace when running 'package' phase
[ http://jira.codehaus.org/browse/MNG-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox updated MNG-2398:
---------------------------
Fix Version/s: (was: Reviewed Pending Version Assignment)
2.0.11
> 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