[ 
https://issues.apache.org/jira/browse/MASFRES-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742133#comment-13742133
 ] 

Maysam Yabandeh commented on MASFRES-8:
---------------------------------------

Thanks for the clear answer [[email protected]]. 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

Reply via email to