You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Tony Chemit <tc...@apache.org> on 2014/12/08 21:39:17 UTC
[ANN] License Maven Plugin 1.8 released
The Mojo team is pleased to announce the release of the License Maven Plugin, version 1.8.
This plugin manages the license of a maven project and its dependencies
(update file headers, download dependencies licenses, check thirdparty
licenses, ...).
Description
-----------
This License Plugin has the following goals:
* license:add-third-party
Goal to generate the third-party license file. This file contains a list of
the dependencies and their licenses. Each dependency and it's license is
displayed on a single line in the format
(<license-name>) <project-name> <groupId>:<artifactId>:<version> -
<project-url>
It will also copy it in the class-path (says add the generated directory as a
resource of the build).
* license:aggregate-add-third-party
This aggregator goal (will be executed only once and only on pom projects)
executed the add-third-party on all his modules (in a parellel build cycle)
then aggreates all the third-party files in final one in the pom project.
* license:check-file-header
The goal to check if the state of header on project source files.
* license:comment-style-list
Displays all the available comment style to box file headers.
* license:download-licenses
Download the license files of all the current project's dependencies, and
generate a summary file containing a list of all dependencies and their
licenses.
* license:license-list
Display all available licenses.
* license:third-party-report
Generates a report of all third-parties detected in the module.
* license:update-file-header
The goal to update (or add) the header on project source files. This goal
replace the update-header goal which can not deal with Copyright. This goal
use a specific project file descriptor project.xml to describe all files to
update for a whole project.
* license:update-project-license
Updates (or creates) the main project license file according to the given
license defines as licenseName. Can also generate a bundled license file (to
avoid collision names in class-path). This file is by default generated in
META-INF class-path directory.
Useful links
------------
Documentation: http://mojo.codehaus.org/license-maven-plugin
JIRA: http://jira.codehaus.org/browse/MLICENSE
svn: https://svn.codehaus.org/mojo/tags/license-maven-plugin-1.8
To get this update, simply specify the version in your project's plugin
configuration:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>license-maven-plugin</artifactId>
<version>1.8</version>
</plugin>
The artifacts have been deployed to the mojo repository and will be
mirrored to central.
Release Notes
-------------
** Bug
* [MLICENSE-108] - copyright owner is not working properly
* [MLICENSE-113] - Eclipse Public License includes Eclipse Distribution License by mistake
Enjoy,
The Mojo team.
tony
--
Tony Chemit
--------------------
tél: +33 (0) 2 40 50 29 28
http://www.codelutin.com
email: chemit@codelutin.com
twitter: https://twitter.com/tchemit
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org