[
http://jira.codehaus.org/browse/MINSTALL-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=134896#action_134896 ]
Libor Kramolis commented on MINSTALL-41:
----------------------------------------
There is same problem in depoy plugin MDEPLOY-78.
> 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
> Priority: Minor
> 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
