You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Benedict (JIRA)" <ji...@codehaus.org> on 2014/07/02 15:45:16 UTC
[jira] (MNG-2181) Problem with reactor when using attached goal
[ https://jira.codehaus.org/browse/MNG-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Benedict updated MNG-2181:
-------------------------------
Fix Version/s: (was: Issues to be reviewed for 3.x)
> Problem with reactor when using attached goal
> ---------------------------------------------
>
> Key: MNG-2181
> URL: https://jira.codehaus.org/browse/MNG-2181
> Project: Maven
> Issue Type: Bug
> Components: Reactor and workspace
> Reporter: Vincent Massol
> Attachments: log.txt
>
>
> Here's my project dir structure:
> {noformat}
> trunk/
> |_ core/
> |_ api/
> |_ (several projects here)
> |_ uberjar/ (assembly project)
> |_ samples
> |_ testdata
> |_ empty-jar
> |_ (...)
> {noformat}
> If I build the trunk/core/ubjerjar project alone it works fine. Note: I have attached the "attached" goal to the verify phase so the assembly can be created when calling "mvn install".
> If I build the project from the trunk by typing "mvn install", the uberjar/ project fails saying that the empty-jar artifact cannot be found in the local repository. That's normal it cannot be found because there are no dependencies on it in the core/ branch and it hasn't been built yet when the uberjar project executes. Of course there are no dependencies to it in the uberjar project.
> It seems there's something fishy happening in the assembly plugin implementation... :-)
> Thanks
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)