You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Chris Seieroe (JIRA)" <ji...@apache.org> on 2016/03/23 10:15:25 UTC
[jira] [Updated] (MINSTALL-120) Use pom.xml file in jar without
setting pomFile
[ https://issues.apache.org/jira/browse/MINSTALL-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Seieroe updated MINSTALL-120:
-----------------------------------
Summary: Use pom.xml file in jar without setting pomFile (was: Using pom.xml file in jar without setting pomFile)
> Use pom.xml file in jar without setting pomFile
> -----------------------------------------------
>
> Key: MINSTALL-120
> URL: https://issues.apache.org/jira/browse/MINSTALL-120
> Project: Maven Install Plugin
> Issue Type: Improvement
> Components: install:install-file
> Affects Versions: 2.5
> Reporter: Chris Seieroe
>
> I like the functionality that MINSTALL-52 offers. Now I can just specify the file name and it can read groupId, artifactId, and version from the pom.xml file inside that jar file. But if I want to use that real pom.xml file instead of the install plugin generating one, I still have to supply the pom.xml file separately. Why can't it just use the pom.xml file in the zip file like it did to find those properties?
> For example:
> mvn install:install-file -Dfile=my-maven-built-thing-1.0.jar -DgeneratePom=false
> would use the properties in the pom.xml file in that jar as well as the pom file itself instead of generating one.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)