[
https://issues.apache.org/jira/browse/MASSEMBLY-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16801826#comment-16801826
]
Karl Heinz Marbaise commented on MASSEMBLY-907:
-----------------------------------------------
The simple issue is that you a relying on the defined order of modules in your
parent {{pom.xml}} which is defined as:
{code:xml}
<modules>
<module>common</module>
<module>services</module>
<module>assembly</module>
</modules>
{code}
But this is not reliable.
In your {{assembly}} you have to define dependencies to the modules you would
like have been packaged in your assembly. and that would make sure the order of
building is the one you expect..In consequence you have to add dependencies in
the {{pom.xml}} of the {{assembly}} module. The definition of the module set in
the assembly descriptor will not influence the build order of the reactor.
> 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)
