[
https://issues.apache.org/jira/browse/MINSTALL-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17966003#comment-17966003
]
Olivier Lamy commented on MINSTALL-120:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-install-plugin#249|https://github.com/apache/maven-install-plugin/issues/249].
> 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 (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: install:install-file
> Affects Versions: 2.5
> Reporter: Chris Seieroe
> Assignee: Guillaume Boué
> Priority: Major
>
> 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
(v8.20.10#820010)
