jira-importer commented on issue #306: URL: https://github.com/apache/maven-install-plugin/issues/306#issuecomment-2771866652
**[T Vorschuetz](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tvo)** commented There is another inconsistency to version 2.5.2 that is pointing to the same issue. If generatePom is set to true in 2.x.x, a minimalistic POM has been generated and installed instead of the existing pom.xml. Since 3.0.0-M1 it is not possible to force a generation of a minimalistic POM even if genratePom is set to true if a pom is existing. So, in terms the jar file that should be installed is generated by maven, generatePom does not have any effect anymore. Let's assume you would like to build a jar that uses a parent pom just for the creation of the jar itself including some depencies for testing the jar during the creation and you would like to install and deploy this jar for later use in further projects without those information, in 2.5.2 it was simply done by using generatePom=true. Now you have to configure the flatten plugin to generate a minimalistic POM first. From my-point-of-view generatePom is not used in most of the times since install-file tries to fetch a POM from inside the jar and this cannot be configured not to be done. Regards, Tiemo -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
