You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2016/10/14 09:21:21 UTC
[jira] [Comment Edited] (MDEPLOY-196) Add support for specifying
customs licenses for a generated default pom
[ https://issues.apache.org/jira/browse/MDEPLOY-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15574758#comment-15574758 ]
Michael Osipov edited comment on MDEPLOY-196 at 10/14/16 9:21 AM:
------------------------------------------------------------------
No reaction from the reporter for more than year.
was (Author: michael-o):
No reacton from the reporter for more than year.
> Add support for specifying customs licenses for a generated default pom
> -----------------------------------------------------------------------
>
> Key: MDEPLOY-196
> URL: https://issues.apache.org/jira/browse/MDEPLOY-196
> Project: Maven Deploy Plugin
> Issue Type: Story
> Reporter: Kyle Holohan
>
> It would be nice to be able to specify the licenses that we want to include in the generated pom file. Something along the lines of this:
> {code:xml}
> <plugin>
> <artifactId>maven-install-plugin</artifactId>
> <configuration>
> <groupId>org.apache.maven.test</groupId>
> <artifactId>maven-install-file-test</artifactId>
> <version>1.0-SNAPSHOT</version>
> <packaging>jar</packaging>
> <file>${basedir}/target/test-classes/unit/install-file-basic-test/target/maven-install-test-1.0-SNAPSHOT.jar
> </file>
> <localRepository>${localRepository}</localRepository>
> <licenses>
> <license>
> <name>Apache License, Version 2.0</name>
> <url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
> </license>
> </licenses>
> </configuration>
> </plugin>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)