Filter libraries inside generated licenses files
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
Hi Pertica, first of all, thank you for your feedback, it is greatly appreciated as we just started to communicate a little about this project. Le 23/08/2010 00:08, Petrica Grama 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.
We did not have this need so did not think about it, but yes, this could be a nice feature to add. I just added it onto the feature request tracker (http://nuiton.org/issues/show/818). Are your modifications regarding this feature able to be merged in the project ? If so, maybe you can send us a patch and we can integrate it. Anyway, thank you for this report. Jean
Le Mon, 23 Aug 2010 01:08:08 +0300, Petrica Grama <gpetrica@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@codelutin.com http://www.codelutin.com
participants (3)
-
Jean Couteau -
Petrica Grama -
Tony Chemit