I don't think so, but I believe I've explained pretty much everything about it. I found about it from this<https://jira.jboss.org/jira/browse/JBBUILD-477>task in JBoss JIRA. From there I followed a link to plugin source code. The plugin mojo class<https://anonsvn.jboss.org/repos/maven/plugins/jboss/trunk/maven-jboss-license-plugin/src/main/java/org/jboss/maven/plugins/license/DownloadLicensesMojo.java>is really simple one, every Java developer should be able to read it easily. Plugin only has a single download-liceses goal, by default bound to generate-resources phase, and I've mentioned both parameters (outputDirectory, and quiet) in the earlier example. In the mojo class source you can see how downloaded license file gets it's name (see getLicenseFileName method).
Regards, Stevo. 2009/6/24 Todd Thiessen <[email protected]> > Thats good to know Stevo. Thanks. > > Is there a site which describes this plugin and its goals? > > --- > Todd Thiessen > > > > -----Original Message----- > > From: Stevo Slavic [mailto:[email protected]] > > Sent: Wednesday, June 24, 2009 2:34 AM > > To: Maven Users List > > Subject: Re: How does maven handle artifact's license files? > > > > It scans through your project's dependencies, looks for > > licenses definitions, and tries to download them (based on > > given license URL) into a destination you designate via > > outputDirectory parameter (defaults to > > ${project.build.directory}/licenses). It can do the license > > scanning/downloading quietly (defaults to false), not to > > report warnings if license can not be found or downloaded. To > > automatically embed downloaded licenses into your jar or war > > you can use build helper plugin or assembly plugin - wish > > jar/war plugins were enough. > > > > As already stated, problem is that many library vendors don't > > include the license info in artefact pom's, but also many > > include it in their own special way, so you will e.g. get > > multiple differently named Apache 2 licenses, invalid URL's, > > or BSD license template library vendor failed to customize, ... > > > > Regards, > > Stevo. > > > > On Wed, Jun 24, 2009 at 4:35 AM, David Hoffer > > <[email protected]> wrote: > > > > > What does the maven-jboss-license-plugin do? > > > > > > > > > On Tue, Jun 23, 2009 at 5:03 PM, Stevo Slavić > > <[email protected]> wrote: > > > > > > > ... > > > > <pluginRepositories> > > > > ... > > > > <pluginRepository> > > > > <id>repository.jboss.org</id> > > > > <url>http://repository.jboss.org/maven2</url> > > > > <releases> > > > > <enabled>true</enabled> > > > > </releases> > > > > <snapshots> > > > > <enabled>false</enabled> > > > > </snapshots> > > > > </pluginRepository> > > > > ... > > > > </pluginRepositories> > > > > ... > > > > <build> > > > > ... > > > > <plugins> > > > > ... > > > > <plugin> > > > > <groupId>org.jboss.maven.plugins</groupId> > > > > <artifactId>maven-jboss-license-plugin</artifactId> > > > > <version>1.0.0</version> > > > > <executions> > > > > <execution> > > > > <id>download-licenses</id> > > > > <phase>generate-resources</phase> > > > > <goals> > > > > <goal>download-licenses</goal> > > > > </goals> > > > > <configuration> > > > > > > > > > > > > > > > > > <outputDirectory>${project.build.directory}/generated-resources/licens > > > es</outputDirectory> > > > > <quiet>false</quiet> > > > > </configuration> > > > > </execution> > > > > </executions> > > > > </plugin> > > > > ... > > > > </plugins> > > > > ... > > > > </build> > > > > ... > > > > > > > > Regards, > > > > Stevo. > > > > > > > > On Tue, Jun 23, 2009 at 8:57 PM, David Hoffer <[email protected]> > > > wrote: > > > > > > > > > The report does show a list of known licenses and which > > artifact > > > > > is associated with each. However most just say Unknown (likely > > > > > because > > > like > > > > > you say the pom is missing the information). > > > > > > > > > > However this doesn't help the end product, that is, it > > doesn't do > > > > > what > > > > the > > > > > license says is needed...rather its just an > > informational report. > > > > > > > > > > For instance, for the apache license, doesn't a copy of the > > > > > license > > > have > > > > to > > > > > come with the product/application? I thought I heard, > > some time > > > > > ago, > > > > that > > > > > maven was working on automating this just like they do > > for runtime > > > > > artifacts. > > > > > > > > > > -Dave > > > > > > > > > > On Tue, Jun 23, 2009 at 12:45 PM, Todd Thiessen > > > > > <[email protected]> > > > > > wrote: > > > > > > > > > > > The dependencies report show all transitive licenses that your > > > project > > > > > > uses. I believe this report is part of the default maven site > > > > > > generation. > > > > > > > > > > > > Of course if artifacts don't have any license information in > > > > > > their > > > pom, > > > > > > no information will be shown in the report. > > > > > > > > > > > > --- > > > > > > Todd Thiessen > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > From: David Hoffer [mailto:[email protected]] > > > > > > > Sent: Tuesday, June 23, 2009 2:40 PM > > > > > > > To: Maven Users List > > > > > > > Subject: How does maven handle artifact's license files? > > > > > > > > > > > > > > Does maven have support for tracking license files my > > > > > > > dependent artifacts may have and doing something with these > > > > > > > files, such as installing with my > > product/application? If so, how? > > > > > > > > > > > > > > (Ideally I want to deploy license docs with each > > artifact that > > > > > > > needs one (ideally public artifacts should already have > > > > > > > this) then I want to include all these in a > > specific location > > > > > > > in my war.) > > > > > > > > > > > > > > -Dave > > > > > > > > > > > > > > > > > > > > > ---------------------------------------------------------------- > > > > > > ----- To unsubscribe, e-mail: > > [email protected] > > > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
