You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org> on 2019/03/26 19:48:00 UTC

[jira] [Closed] (MASSEMBLY-907) Dependencies are not included when run with mvn install

     [ https://issues.apache.org/jira/browse/MASSEMBLY-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Heinz Marbaise closed MASSEMBLY-907.
-----------------------------------------
    Resolution: Not A Problem
      Assignee: Karl Heinz Marbaise

So first I would say this issue is not bug anymore ? If you have a different opinion please let me know...and give me more details.

Apart from that If you have an example project of that structure github or a like I can take a look...cause from my first feeling the usage of maven-resources-plugin and maven-assembly-plugin sounds a little bit wrong but I'm not sure cause I don't know the exact situation.  So now this has become a support question which should be continued on the users mailing list....

> Dependencies are not included when run with mvn install
> -------------------------------------------------------
>
>                 Key: MASSEMBLY-907
>                 URL: https://issues.apache.org/jira/browse/MASSEMBLY-907
>             Project: Maven Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 3.1.1
>            Reporter: Lau Bakman
>            Assignee: Karl Heinz Marbaise
>            Priority: Major
>         Attachments: assembly_deps.zip
>
>
> We have just updated to version 3.1.1 due to MASSEMBLY-873 and have stumbled upon a problem.
> Our project is structured similar to the attached project. When we build our project using "mvn clean package" the project is assembled correctly including dependencies. If we on the other hand build our project using "mvn clean install", only the top level jar files are assembled and all dependencies are missing.
> This worked in version 3.1.0.
> Is this by design? And if it is, is there a way to revert to the old behavior?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)