[
https://issues.apache.org/jira/browse/MASSEMBLY-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16801896#comment-16801896
]
Lau Bakman commented on MASSEMBLY-907:
--------------------------------------
Thank you for your time on this issue. Just trying to understand what is
happening.
I am using a dir format because I am assembling an application that includes
native libraries as well. I use the assembly plugin (and later
maven-resources-plugin) to build a directory structure that I can take and use
directly for my installers.
For example:
module-services: Root folder for my services.
|- libs: Directory containing jar dependencies used by my services
|- win32: Directory containing Windows 32-bit native libraries
|- win64: Directory containing Windows 64-bit native libraries
|- linux32: Directory containing Linux 32-bit native libraries
|- linux64: Directory containing Linux 64-bit native libraries
| launcher.jar: Service launcher
| *-service.jar: A number of services loaded by the service launcher - these
may vary on the build and these are the ones I would like to avoid specifying
dependencies for.
My installer step will then grab the service files, libs directory and the
appropriate native directory from the module-services folder and create an
installer for the appropriate architecture.
I do not know if it is the right tool for the job, but maven-assembly-plugin
have been doing great until now. If you have any suggestions on how to do this
differently, I am open to new ideas.
As for the different combinations, the only thing I changed in my project when
discovering this problem was the version of maven-assembly-plugin.
> 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)