August 2010 - Maven-license-plugin-users - mailman.cloud.codelutin.com

Re: [Maven-license-plugin-users] Maven-license-plugin-users Digest, Vol 6, Issue 3
by Petrica Grama Aug. 31, 2010

Aug. 31, 2010

Hello, < What was your point by saying : "...I wonder if it's possible to provide such a functionality with the Maven License Plug-in." > I've needed the exclusion functionality for the project I work for, so I've checkout the sources from your SVN and modified them to accommodate my needs ( the modifications are in the patch I've sent some days ago). However, having some modified sources on my repository will pose problems of synchronization with the evolutions/corrections that are done on the genuine License plugin. So I was just wondering if adding some exclusion filters could get on the list of evolutions that will be done on Maven License plugin (you already answered on that question with yes and that's great). This way, the moment this functionality will be available, I will give up the plugin I've modified and use the official one. Thank you again, Petrica On Mon, Aug 30, 2010 at 1:00 PM, < maven-license-plugin-users-request(a)list.nuiton.org> wrote: > Send Maven-license-plugin-users mailing list submissions to > maven-license-plugin-users(a)list.nuiton.org > > To subscribe or unsubscribe via the World Wide Web, visit > > http://list.nuiton.org/cgi-bin/mailman/listinfo/maven-license-plugin-users > > or, via email, send a message with subject or body 'help' to > maven-license-plugin-users-request(a)list.nuiton.org > > You can reach the person managing the list at > maven-license-plugin-users-owner(a)list.nuiton.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Maven-license-plugin-users digest..." > > > Today's Topics: > > 1. Re: Filter libraries inside generated licenses files (Tony Chemit) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 30 Aug 2010 00:23:50 +0200 > From: Tony Chemit <chemit(a)codelutin.com> > Subject: Re: [Maven-license-plugin-users] Filter libraries inside > generated licenses files > To: undisclosed-recipients:; > Message-ID: <20100830002350.4ca701e7@tc> > Content-Type: text/plain; charset=ISO-8859-1 > > Le Mon, 23 Aug 2010 01:08:08 +0300, > Petrica Grama <gpetrica(a)gmail.com> a ?crit : > > > Hello all, > > > > first of all, this is a very nice plug-in. Keep up the good work. > > > > I did an evaluation of the plug-in for using it at work, during > continuous > > integration process. The purpose was to automatically generate a list of > all > > third party libraries licenses used in our final distribution. The list > is > > supposed to be verified before release to see if all the licenses are in > > order. > > > > I was able to do all of these by using the add-third-party and > > aggregate-add-third-party goals. However, the generated files contain all > > the licenses for all the libraries used in distribution, including our > own > > libraries. I wonder if it's possible to add a filter to exclude libraries > > from the licenses files. I'd like to keep in the files only the genuine > > third party libraries and filter our products. > > > > What I've done so far was to check out the project from SVN and modify it > to > > filter all the libraries respecting some regular expression (testing if > > groupId or artifactId contains some expression given as configuration > > parameter). But I dislike this procedure as I will have to manually > maintain > > the modified project. I wonder if it's possible to provide such a > > functionality with the Maven License Plug-in. > The idea to be able to filter (include, exclude) some dependencies is a > good idea, > we will implement it soon for sure. > > Concerning the way of doing it, I can't see a better solution than to > modify your final application pom. > > What was your point by saying : > "...I wonder if it's possible to provide such a functionality with the > Maven License Plug-in." > > Could you clarifing a little more your mind. > > > > > Thank you, > > You're welcome. > > Petrica > > > > -- > Tony Chemit > -------------------- > t?l: +33 (0) 2 40 50 29 28 > email: chemit(a)codelutin.com > http://www.codelutin.com > > > ------------------------------ > > _______________________________________________ > Maven-license-plugin-users mailing list > Maven-license-plugin-users(a)list.nuiton.org > http://list.nuiton.org/cgi-bin/mailman/listinfo/maven-license-plugin-users > > > End of Maven-license-plugin-users Digest, Vol 6, Issue 3 > ******************************************************** >

1 0

Filter libraries inside generated licenses files
by Petrica Grama Aug. 29, 2010

Aug. 29, 2010

Hello all, first of all, this is a very nice plug-in. Keep up the good work. I did an evaluation of the plug-in for using it at work, during continuous integration process. The purpose was to automatically generate a list of all third party libraries licenses used in our final distribution. The list is supposed to be verified before release to see if all the licenses are in order. I was able to do all of these by using the add-third-party and aggregate-add-third-party goals. However, the generated files contain all the licenses for all the libraries used in distribution, including our own libraries. I wonder if it's possible to add a filter to exclude libraries from the licenses files. I'd like to keep in the files only the genuine third party libraries and filter our products. What I've done so far was to check out the project from SVN and modify it to filter all the libraries respecting some regular expression (testing if groupId or artifactId contains some expression given as configuration parameter). But I dislike this procedure as I will have to manually maintain the modified project. I wonder if it's possible to provide such a functionality with the Maven License Plug-in. Thank you, Petrica

3 2

Headers re-generations
by Nicolas Nobelis Aug. 14, 2010

Aug. 14, 2010

Hello, I am a user of your nice Maven Plugin that generates license files/headers. I have a question regarding a feature : is this possible, when running license:update-file-header, to force the overwriting of the headers ? It seems to me that the plugin, if it finds an header, leaves it untouched (thus not updating it). When I first run the command update-file-header, I realized that I was lacking the copyright part of the header. Because the option to overwrite the header was lacking, I had to erase all the produced headers in each of my source files. Then, after the second generation, I realized once again that the project description part was not so nice. Hence, I had once again to erase manually the headers and regenerate it. My opinion is that a property, e.g. license.overwrite, would allow the user to easily re-generate the headers. Then, specific properties for updating only the project description/the copyright/license/year wouldn't be required. As a sidenote, I noticed that if you have no inceptionYear in your pom or CLI, the plugin fail with : [INFO] could not execute goal UpdateFileHeaderMojo for reason : null Thanks by advance for your time and support ! Best regards, Nicolas

2 1