[ 
https://issues.apache.org/jira/browse/MASSEMBLY-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802504#comment-16802504
 ] 

Lau Bakman commented on MASSEMBLY-907:
--------------------------------------

I still believe it is a bug and it is very much a problem for us. We cannot use 
3.1.0 anymore due to MASSEMBLY-873 and we cannot upgrade to 3.1.1 because of a 
change in behavior.

Prior to 3.1.1 our project setup which is demonstrated in the attached 
assembly_deps worked flawlessly, assembling all jars and their dependencies. 
With 3.1.1 this is no longer the case. Something has broken (for us) when the 
plugin is executed as part of "mvn install"

My last comment yesterday concerned your question of why we use the "dir" 
format. We use the "dir" format to create a directory structure for building 
our installers. We cannot build the structure if the dependencies are not 
copied to the assembly output directory. The maven-resource-plugin is not 
relevant for this problem - it was part of my explanation for the "dir" format. 

> 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)

Reply via email to