[
https://issues.apache.org/jira/browse/MASFRES-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
