[
https://issues.apache.org/jira/browse/MASSEMBLY-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911189#comment-16911189
]
Mark Symons commented on MASSEMBLY-907:
---------------------------------------
Is there any progress on this?
Our teams ran into exactly the same problem after upgrading from 3.1.0 to
3.1.1. Like [~lbakman], we also have bouncy castle dependencies that necesitate
usage of 3.1.1 due to MASSEMBLY-873.
> 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: 310_install.log, 310_install_verbose.log,
> 311_install.log, 311_install_verbose.log, 311_package_verbose.log,
> 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
(v8.3.2#803003)
