[ http://jira.codehaus.org/browse/MINSTALL-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210551#action_210551 ]
Eduard Papa edited comment on MINSTALL-41 at 2/17/10 8:58 PM: -------------------------------------------------------------- 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. was (Author: edspace): 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 thought 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. > Install with classifier does not install pom > -------------------------------------------- > > Key: MINSTALL-41 > URL: http://jira.codehaus.org/browse/MINSTALL-41 > Project: Maven 2.x Install Plugin > Issue Type: Bug > Affects Versions: 2.2 > Reporter: Michele Lorenzini > Assignee: Benjamin Bentmann > Priority: Minor > Fix For: 2.3 > > Attachments: maven-install-plugin-2.2.patch, pom.xml > > > I have a project wich I need to build only specifying a classifier (in > detail: a war project which I need to build with different profiles to > include different > configurations. So I set up different filters and the package produces > different classified wars). > When I install the artifact, I've got the attached artifact installed but the > pom is NOT installed. > The log says "No primary artifact to install, installing attached artifacts > instead". > It's maybe related to MINSTALL-18 as it seems the mojo does not recognize the > presence of a primary artifact and goes to install the attached artifacts > (without installing the POM). > Don't know if this is really a bug or if I am trying a strange/not valid > project configuration (a project without a primary artifact). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira