[
https://issues.apache.org/jira/browse/MASSEMBLY-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16801867#comment-16801867
]
Lau Bakman commented on MASSEMBLY-907:
--------------------------------------
Interesting.
I have tried to add the dependency to the assembly pom and that does indeed
include the dependencies in the output, although the output is no longer
structured as I expect it to be. But that is a different matter for me to
figure out.
Just a few things:
* Reading the FAQ
([http://maven.apache.org/components/plugins/maven-assembly-plugin/faq.html#module-binaries]).
I do not get an error when building my original project. Everything seems to
work - except that the dependencies are missing from my output.
* I am curious as to why this has worked for us since we started using
maven-assembly-plugin in 2014 and only just stopped working with version 3.1.1
and also why only when executed using "mvn install" and not "mvn package".
We have a configuration where we want to package all jar files with similar
artifact id's, like the "spike.services.*" example. Having to maintain an
additional dependency list is something that we would like to avoid if possible.
> 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)
