[
http://jira.codehaus.org/browse/MASSEMBLY-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138939#action_138939
]
Daniel Kulp commented on MASSEMBLY-330:
---------------------------------------
You might be able to do this today by configuring the remote-resource plugin to
run twice with separate configurations. The latest remote-resources provides
an optional "scope" to use. Thus, you can run it once with "runtime" scope and
another with "test" scope and have it output to separate places. The
src/bin assemblies would grab the appropriate output.
> LICENSE/NOTICE modification/generation based on included dependencies
> ---------------------------------------------------------------------
>
> Key: MASSEMBLY-330
> URL: http://jira.codehaus.org/browse/MASSEMBLY-330
> Project: Maven 2.x Assembly Plugin
> Issue Type: New Feature
> Affects Versions: 2.2-beta-2
> Reporter: Stefano Bagnara
>
> I create jar, javadoc-jar and sources-jar using maven jar plugin.
> The maven remote resources plugin together with the
> apache-jar-resource-bundle allow me to have a good LICENSE/NOTICE file for
> that jars.
> The problem is that I also have a src\assemble\src.xml and
> src\assemble\bin.xml files to create a sources + compile/test/runtime
> dependencies (all of them) zip file and a binary + runtime dependencies zip
> file.
> Assembly plugin make a grea job in allowing me using this for the binary
> dependencies:
> dependencySets>
> <dependencySet>
> <outputDirectory>/lib/</outputDirectory>
> <scope>runtime</scope>
> </dependencySet>
> </dependencySets>
> For the src distribution I instead copy files manually not using the
> dependencies (because I need them in the same structure I already have), and
> this is another issue, but let's fix one issue at a time.
> currently I put a LICENSE/NOTICE files in the zips by adding this:
> <fileSet>
> <directory>target/maven-shared-archive-resources/META-INF/</directory>
> <outputDirectory>/</outputDirectory>
> <includes>
> <include>NOTICE</include>
> <include>LICENSE</include>
> </includes>
> </fileSet>
> But they are now wrong for a binary distribution including the runtime
> dependencies.
> It would be cool to have the assembly plugin automatically manage this (I
> don't even know how) by altering (or interacting with the remote resources
> plugin) to add snippets related to the included dependencies.
--
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
