maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject Re: Incorrect license metadata after inheriting org.apache:apache:6
Date Thu, 02 Jul 2009 18:16:27 GMT
These are added by the maven-remote-resources-plugin and you can  
customize the output using per-project velocity templates in src/main/ 
appended-resources/META-INF/ to add stuff to the basic LICENSE and  
NOTICE files. The plugin docs have more instructions.  I think I saw  
that someone figured out how to not include the DEPENDENCIES file but  
I don't know what they did.

david jencks

On Jul 2, 2009, at 4:13 AM, Jukka Zitting wrote:

> Hi,
> In Jackrabbit we recently upgraded to the org.apache:apache:6 parent
> POM to get the latest settings, but as a
> side-effect we started getting extra LICENSE, NOTICE, and DEPENDENCIES
> files in the META-INF directories of our jar artifacts.
> This would be nice if the included license metadata was correct, but
> unfortunately it is not at least in our case. For example, we have
> many components where we're including external code snippets with
> separate licenses or copyright notice requirements.
> We already include our own custom license metadata files in the jar
> artifacts and it's confusing to have the remote resources plugin add
> these extra files. To avoid this confusion, is there some way (apart
> from not using org.apache:apache:6) for us to either disable the
> inclusion of these extra files or customize the files to match our
> needs?
> BR,
> Jukka Zitting
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message