[
https://issues.apache.org/jira/browse/MASFRES-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742047#comment-13742047
]
Maysam Yabandeh commented on MASFRES-8:
---------------------------------------
Thanks [~denn...@apache.org].
| First, when you say "assembly descriptor", which assembly descriptor do you
mean? Is it the apache-source-release-assembly-descriptor?
By assembly descriptor, I was referring to src.xml in the following pom.xml
file.
{code}
<project>
[...]
<build>
[...]
<plugins>
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.4</version>
<configuration>
<descriptors>
<descriptor>src/main/assembly/src.xml</descriptor>
</descriptors>
</configuration>
[...]
</project>
{code}
src.xml itself is not by default packaged in the final jar file. Having src.xml
in the jar file, one can disassemble the jar file and reassemble it with an
updated src.xml that excludes the common dependencies.
| Second, it sounds to me like you want to change the current configuration for
the JAR Plugin in org.apache:apache parent POM. It that correct?
I am not sure if it is possible to instruct pom.xml to package src.xml in the
final jar file. But anyway I was hoping that maven could that by default
without needing extra configuration from the user. As it was discussed in
HADOOP-9639, large companies are serving many internal users and variety of
applications, and needing to update all the related configuration files raises
some management issues.
> Include assembly descriptor in the produced jar file
> ----------------------------------------------------
>
> Key: MASFRES-8
> URL: https://issues.apache.org/jira/browse/MASFRES-8
> Project: Apache Maven Resource Bundles
> Issue Type: Wish
> Reporter: Maysam Yabandeh
> Priority: Minor
>
> Many assembly descriptors conservatively include many jar dependencies in the
> final jar file, resulting into fat jar problem. If the assembly descriptor
> file was included by default, each framework could disassemble the fat jar on
> demand and reassemble it having the known, available jar files excluded.
> Issues like hadoop-9639 can benefit from this feature.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
