[
https://jira.codehaus.org/browse/MASSEMBLY-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Ekushev updated MASSEMBLY-663:
----------------------------------------
Description:
Say I want to create an assembly that contains jars, sources and javadocs for
the module and all its dependencies.
Currently it works for jar dependencies only, but I cannot retrieve sources and
javadocs unless I mention them in the pom.
In the attached example module b depends on module a and I has to specify its
dependencies 3 times: as a jar, sources and javadoc.
The result I am trying to assembly is:
{noformat}
b-1.0
javadoc
a-1.0-javadoc.jar
b-1.0-javadoc.jar
lib
a-1.0.jar
b-1.0.jar
src
a-1.0-sources.jar
b-1.0-sources.jar
{noformat}
It would be convenient if I could mention the dependency only once. There can
be variants to make this happen:
* Add a flag (e.g. "useTransitiveProjectAttachments") to include all transitive
project attachments
* Add a classifier to add to dependencies (similar to "attachmentClassifier" in
moduleSet/binaries)
Please close this issue, if assembly-plugin is not suited for this purposes.
Required functionality can be achieved by using
dependency:copy-dependencies goal to download all dependencies - but it lacks
the outputFileNameMapping feature of the assembly plugin.
was:
Say I want to create an assembly that contains jars, sources and javadocs for
the module and all its dependencies.
Currently it works for jar dependencies only, but I cannot retrieve sources and
javadocs unless I mention them in the pom.
In the attached example module b depends on module a and I has to specify its
dependencies 3 times: as a jar, sources and javadoc.
The result I am trying to assembly is:
{pre}
b-1.0
javadoc
a-1.0-javadoc.jar
b-1.0-javadoc.jar
lib
a-1.0.jar
b-1.0.jar
src
a-1.0-sources.jar
b-1.0-sources.jar
{pre}
It would be convenient if I could mention the dependency only once. There can
be variants to make this happen:
* Add a flag (e.g. "useTransitiveProjectAttachments") to include all transitive
project attachments
* Add a classifier to add to dependencies (similar to "attachmentClassifier" in
moduleSet/binaries)
Please close this issue, if assembly-plugin is not suited for this purposes.
Required functionality can be achieved by using
dependency:copy-dependencies goal to download all dependencies - but it lacks
the outputFileNameMapping feature of the assembly plugin.
> Allow to include transitive dependency attachments
> --------------------------------------------------
>
> Key: MASSEMBLY-663
> URL: https://jira.codehaus.org/browse/MASSEMBLY-663
> Project: Maven Assembly Plugin
> Issue Type: Improvement
> Components: dependencySet
> Affects Versions: 2.4
> Reporter: Alexander Ekushev
> Priority: Minor
> Attachments: massembly-663.zip
>
>
> Say I want to create an assembly that contains jars, sources and javadocs for
> the module and all its dependencies.
> Currently it works for jar dependencies only, but I cannot retrieve sources
> and javadocs unless I mention them in the pom.
> In the attached example module b depends on module a and I has to specify its
> dependencies 3 times: as a jar, sources and javadoc.
> The result I am trying to assembly is:
> {noformat}
> b-1.0
> javadoc
> a-1.0-javadoc.jar
> b-1.0-javadoc.jar
> lib
> a-1.0.jar
> b-1.0.jar
> src
> a-1.0-sources.jar
> b-1.0-sources.jar
> {noformat}
> It would be convenient if I could mention the dependency only once. There can
> be variants to make this happen:
> * Add a flag (e.g. "useTransitiveProjectAttachments") to include all
> transitive project attachments
> * Add a classifier to add to dependencies (similar to "attachmentClassifier"
> in moduleSet/binaries)
> Please close this issue, if assembly-plugin is not suited for this purposes.
> Required functionality can be achieved by using
> dependency:copy-dependencies goal to download all dependencies - but it lacks
> the outputFileNameMapping feature of the assembly plugin.
--
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
