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

Karl Heinz Marbaise commented on MASSEMBLY-907:
-----------------------------------------------

This can be a coincidence based on using a different version of JDK a different 
version of Maven or different version of the assembly-plugin etc. or simply 
changed the order of modules in your pom file etc. which changed the order of 
the reactor. 

Furthermore I don't know why you are using the format: dir ...in your 
descriptor. 

And yes you have to do the dependencies to be sure the reactor is in the 
expected order...


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