You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brian (JIRA)" <ji...@apache.org> on 2019/06/10 20:52:00 UTC
[jira] [Updated] (MASSEMBLY-916) When using mulitple Spring
dependencies, the files from META-INF (from the Spring jars) overwrite each
other in an executable jar-with-dependencies.
[ https://issues.apache.org/jira/browse/MASSEMBLY-916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian updated MASSEMBLY-916:
----------------------------
Description:
When using multiple Spring jars with the assembly plugin the spring.schemas file is not correctly populated and will only include the xsd file mapping for one jar file.
This appears to be the same issue as MASSEMBLY-360, which was fixed in 2.2, but is happening again in version 3.1.1. It looks like it is only 3.1.1 that is a problem since I confirmed that the correct behaviour happens in 3.1.0.
This can go unnoticed since it is often only an issue when the xsd file urls cannot be accessed, like on an environment with no internet access. I have attached our spring.schemas files for the same project, but built using versions 3.1.0 and 3.1.1 of the assembly plugin to illustrate the difference in output.
was:
When using multiple Spring jars with the assembly plugin the spring.schemas file is not correctly populated and will only include the xsd file mapping for one jar file.
This appears to be the same issue as MASSEMBLY-360, which was fixed in 2.2, but is happening again in version 3.1.1. It looks like it is only 3.1.1 that is a problem since I confirmed that the correct behaviour happens in 3.1.0.
This can go unnoticed since it is often only an issue when the xsd file urls cannot be accessed, like on an environment with no internet access.
> When using mulitple Spring dependencies, the files from META-INF (from the Spring jars) overwrite each other in an executable jar-with-dependencies.
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-916
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-916
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Affects Versions: 3.1.1
> Reporter: Brian
> Priority: Major
>
> When using multiple Spring jars with the assembly plugin the spring.schemas file is not correctly populated and will only include the xsd file mapping for one jar file.
> This appears to be the same issue as MASSEMBLY-360, which was fixed in 2.2, but is happening again in version 3.1.1. It looks like it is only 3.1.1 that is a problem since I confirmed that the correct behaviour happens in 3.1.0.
> This can go unnoticed since it is often only an issue when the xsd file urls cannot be accessed, like on an environment with no internet access. I have attached our spring.schemas files for the same project, but built using versions 3.1.0 and 3.1.1 of the assembly plugin to illustrate the difference in output.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)