FYI, the benefits of using the maven-remote-resources-plugin IIRC is that these NOTICE and LICENSE files are also included in the javadoc and source jars generated by maven (which is a bit of a pain if you don't use it afaik).
On Dec 17, 2007 9:45 AM, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > Maven does provide support for these files. > The correct way is to use the maven-remote-resources-plugin and use the > apache resource set for example. > Unfortunately, this is incompatible with bundles because the BND tool > won't include these easily > > > On Dec 17, 2007 9:38 AM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: > > > To have correct releases we need to have the LICENSE and NOTICE file in > > each and every distribution. For source distributions these need to be > > in the root directory, for jars they should be in the META-INF dir. > > > > Now, as maven does not provide any support in this area, we currently > > have two sets of these files in our modules: on in the root directory of > > the module and one stored under src/main/resources/META-INF. > > Keeping duplicate information is of course not the best thing :) > > > > I think we could solve this easily by adding the folling resource > > definiton to our parent pom. This definition will require to have > > LICENSE and NOTICE in the root directory of the project and it will copy > > it during the build to the META-INF/ directory in the jar. > > > > Here is the snippet which we have to add to the <build> section: > > <resources> > > <resource> > > <directory>src/main/resources</directory> > > </resource> > > <resource> > > <directory>.</directory> > > <targetPath>META-INF</targetPath> > > <includes> > > <include>LICENSE</include> > > <include>NOTICE</include> > > </includes> > > </resource> > > </resources> > > > > I did some tests and at least these worked for me. > > > > WDYT? > > Carsten > > > > -- > > Carsten Ziegeler > > [EMAIL PROTECTED] > > > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
