Introduce a parameter to define the scopes of the libraries to be included in
the NOTICE licensing.
---------------------------------------------------------------------------------------------------
Key: MRRESOURCES-23
URL: http://jira.codehaus.org/browse/MRRESOURCES-23
Project: Maven 2.x Remote Resources Plugin
Issue Type: Improvement
Affects Versions: 1.0-alpha-5
Reporter: Stefano Bagnara
Priority: Minor
I use the assembly plugin to create the following artifacts:
1) a source package including the whole source tree (including ALL the
dependencies: also test dep).
2) a binary jar only package
3) a binary + runtime dependencies package
I currently include the NOTICE/LICENSE by adding
{code}
<fileSet>
<directory>target/maven-shared-archive-resources/META-INF/</directory>
<outputDirectory>/</outputDirectory>
<includes>
<include>NOTICE</include>
<include>LICENSE</include>
</includes>
</fileSet>
{code}
it would be cool if the remote resource plugin could "better" collaborate with
the assembly plugin by including a correct NOTICE depending on assembled
depenendencies, but for basic usage it would be enough to have a parameter to
define what is the scope of the dependencies to be listed.
E.g: in my jar only distribution I don't need to make a list of runtime
depenendecies (I don't include them), in the binary package I only need to
include the runtime dependencies, in the complete-source distribution I need to
include test/compile/runtime dependencies disclaimers.
--
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
