[ 
http://jira.codehaus.org/browse/MASSEMBLY-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106604
 ] 

Daniel Siegmann commented on MASSEMBLY-125:
-------------------------------------------

I have found the lack of such support to be a severe deficiency. I have an 
assembly descriptor which combines some (but not all) of the dependencies into 
one jar. However, I need to be able to deliver an analogous source jar.

It is possible to work around this (with dependency:copy and some ant 
scripting), but it doesn't work very well.

I suggest an enhancement be made to the dependencySet includes section so a 
classifier may be explicitly specified. This will provide flexibility to work 
not only for sources, but also for other types of jars (such as javadoc).

I would be happy to provide an example, if desired.

> add mojo for creating a source bundle
> -------------------------------------
>
>                 Key: MASSEMBLY-125
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-125
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: New Feature
>            Reporter: Ovidio Mallo
>             Fix For: 2.2-beta-2
>
>
> I think it would be nice to have some mojo "source:jar-with-dependencies" or 
> something similar which not only includes the artifact's sources into the JAR 
> but also those of its transitive dependencies. This would e.g. allow to 
> create a source bundle for an assembly created with Maven.
> As a concrete example, the "Maven 2.x Plugin for Eclipse" project, which is 
> no Maven but a simple PDE project, uses the MavenEmbedder assembly. There, it 
> would be very handy to also have such a source bundle to attach to the 
> assembly JAR file inside Eclipse for developing and especially for debugging.
> Would there maybe be any interest (beside my single use case :-)) in such a 
> feature? If so, I would eventually give it a try myself if I find the time...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to