jira-importer commented on issue #178: URL: https://github.com/apache/maven-install-plugin/issues/178#issuecomment-2771845508
**[Eduard Papa](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=epapa)** commented You are correct Ryan, I did expect the pom to be classified. I could bet I have seen maven do that a couple of years ago but it might have been a proprietary plugin at the place where I worked. Maybe they accomplished that by appending the "classifier" to the version number. I was hoping that this issue resolved MNG-2759 but it doesn't seem to. I have a parent project with multiple modules. parent --config --service --web The web module depends on classified service module which depends on classified config module. I was using ${buildName} as a classifier for the modules and in the command line was specifying -DbuildName=dev/test/prod. This worked fine when I built from the parent, but when I built just the web module (subdirectory of parent) it failed to resolve the ${buildName} classifier on the transitive config. So even though I was building with -DbuildName=prod, the dependencies were resolved as --web-prod ----service-prod --------config-dev I was hoping that the install plugin would create a classified pom of the service module, in which it would replace the ${buildName} classifier with dev/test/prod value specified at the time it was built. -- 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
