[jira] [Commented] (MASFRES-8) Include assembly descriptor in the produced jar file
[ https://issues.apache.org/jira/browse/MASFRES-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13746729#comment-13746729 ] Dennis Lundberg commented on MASFRES-8: --- I'm not sure what kind of configuration you have in place in your project, but Maven does not build a JAR with source code or dependencies by default. That is done through various plugins other than the JAR Plugin, using some configuration. 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
[jira] [Commented] (MASFRES-8) Include assembly descriptor in the produced jar file
[ https://issues.apache.org/jira/browse/MASFRES-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742036#comment-13742036 ] Dennis Lundberg commented on MASFRES-8: --- I not sure I understand what it is you want. First, when you say assembly descriptor, which assembly descriptor do you mean? Is it the apache-source-release-assembly-descriptor? 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? 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
[jira] [Commented] (MASFRES-8) Include assembly descriptor in the produced jar file
[
https://issues.apache.org/jira/browse/MASFRES-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
artifactIdmaven-assembly-plugin/artifactId
version2.4/version
configuration
descriptors
descriptorsrc/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
[jira] [Commented] (MASFRES-8) Include assembly descriptor in the produced jar file
[ https://issues.apache.org/jira/browse/MASFRES-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742102#comment-13742102 ] Dennis Lundberg commented on MASFRES-8: --- Thanks for explaining. The descriptor you are referring to is local to the project you are building. So it has nothing to do with the ASF shared descriptor that this JIRA project is for. That had me confused at first. Since the naming of the the descriptor is entirely up to the project, including it can't be a default behavior in Maven. Not all projects have a descriptor. One solution to your problem is to add a bit of configuration in your POM. You need to add directory of the descriptor as a resource in the build section. See this URL for more info: http://maven.apache.org/plugins/maven-resources-plugin/examples/resource-directory.html 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
[jira] [Commented] (MASFRES-8) Include assembly descriptor in the produced jar file
[ https://issues.apache.org/jira/browse/MASFRES-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742133#comment-13742133 ] Maysam Yabandeh commented on MASFRES-8: --- Thanks for the clear answer [~denn...@apache.org]. I now understand that solution I was pursuing is not feasible. But, let me explain the original problem and the valuable feature that it seems to be missing from maven. The jar that maven builds includes (a) project source code, (b) project resources, and (c) project dependencies. There are many cases in practice that the framework that receives a fat jar file, wishes to *reassemble* the jar file, excluding certain dependencies from it. This is however not currently possible since the packed information in the jar is not sufficient to tell which classes originate from the project source code and which originate from the dependencies. There are some workarounds like setting the dependencies to be assembled unpacked (as a jar file inside the final jar file). Then it would be easy to reassemble the jar file and exclude certain dependencies. But, I created this wish jira to express the need for a standard approach to this. If maven assembly plugin could also pack the dependency information in a standard way, this feature will be feasible. 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
