You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ryan J (JIRA)" <ji...@codehaus.org> on 2010/02/16 13:13:55 UTC
[jira] Issue Comment Edited: (MINSTALL-41) Install with classifier
does not install pom
[ http://jira.codehaus.org/browse/MINSTALL-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210314#action_210314 ]
Ryan J edited comment on MINSTALL-41 at 2/16/10 6:12 AM:
---------------------------------------------------------
Can someone clarify the correct (expected) behavior of POM installation when artifacts use classifiers for me? The way I understand it the test POM provided will produce and install classified artifacts and an unclassified POM:
foobar-b-1.0-SNAPSHOT-local.jar
foobar-b-1.0-SNAPSHOT-dev.jar
foobar-b-1.0-SNAPSHOT-staging.jar
foobar-b-1.0-SNAPSHOT.pom
Eduard's comment suggests he expects the POM to also be classified:
foobar-b-1.0-SNAPSHOT-local.jar
foobar-b-1.0-SNAPSHOT-dev.jar
foobar-b-1.0-SNAPSHOT-staging.jar
foobar-b-1.0-SNAPSHOT-local.pom
foobar-b-1.0-SNAPSHOT-dev.pom
foobar-b-1.0-SNAPSHOT-staging.pom
Which is correct?
Also, Eduard, is it possible you forgot to specify a profile in the example you gave? It looks to me like an unclassified artifact was installed which would be the expected behavior if you forgot to specify a profile.
was (Author: jptech):
Can someone clarify the correct (expected) behavior of POM installation when artifacts use classifiers for me? The way I understand it the test POM provided will produce classified artifacts and an unclassified POM:
foobar-b-1.0-SNAPSHOT-local.jar
foobar-b-1.0-SNAPSHOT-dev.jar
foobar-b-1.0-SNAPSHOT-staging.jar
foobar-b-1.0-SNAPSHOT.pom
Eduard's comment suggests he expects the POM to also be classified:
foobar-b-1.0-SNAPSHOT-local.jar
foobar-b-1.0-SNAPSHOT-dev.jar
foobar-b-1.0-SNAPSHOT-staging.jar
foobar-b-1.0-SNAPSHOT-local.pom
foobar-b-1.0-SNAPSHOT-dev.pom
foobar-b-1.0-SNAPSHOT-staging.pom
Which is correct?
Also, Eduard, is it possible you forgot to specify a profile in the example you gave? It looks to me like an unclassified artifact was installed which would be the expected behavior if you forgot to specify a profile.
> 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