You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Sylwester Lachiewicz (Jira)" <ji...@apache.org> on 2021/02/02 20:56:00 UTC
[jira] [Assigned] (MASSEMBLY-907) Dependencies are not included
when run with mvn install
[ https://issues.apache.org/jira/browse/MASSEMBLY-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylwester Lachiewicz reassigned MASSEMBLY-907:
----------------------------------------------
Assignee: (was: Karl Heinz Marbaise)
> 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: 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.4#803005)