[
https://issues.apache.org/jira/browse/MDEPLOY-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14575624#comment-14575624
]
Robert Scholte commented on MDEPLOY-196:
----------------------------------------
IMHO the {{install-file}} goal should never be called from commandline and
defined within a {{pom.xml}}, hence it doesn't make sense to add configuration
for additional elements such as licenses.
Based on your example I wonder what you are trying to do and why you are not
using the standard {{install}} goal as part of the build lifecycle. If you
explain the reason why you want to install artifacts like this, maybe we can
help you with a better approach.
> As a user, I would like to be to specify the 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)
