[
https://issues.apache.org/jira/browse/MINSTALL-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17571896#comment-17571896
]
Domagoj Cosic commented on MINSTALL-151:
----------------------------------------
The issue is far worse. There is no possibility to create a main artifact with
classifier, at least not with common plugins like maven-jar-plugin, perhaps not
at all. And the install plugin even cannot be used with custom lifecycles if
there is no main artifact. Just really only pom packaging. It is hard coded!
Why?
> Projects without primary artifacts, but with attachment artifacts fail install
> ------------------------------------------------------------------------------
>
> Key: MINSTALL-151
> URL: https://issues.apache.org/jira/browse/MINSTALL-151
> Project: Maven Install Plugin
> Issue Type: Bug
> Affects Versions: 3.0.0-M1
> Reporter: Peter Huffer
> Priority: Major
> Attachments: minstall-151.zip
>
>
> I have a module which has a packaging of {{feature}} from the
> {{karaf-maven-plugin}}. When running the {{mvn install}} command, the
> following error occurs:
> {code:java}
> Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:3.0.0-M1:install
> (default-install) on project <project_name>: NoFileAssignedException: The
> packaging plugin for this project did not assign a main file to the project
> but it has attachments. Change packaging to 'pom'. -> [Help 1]
> {code}
> Reverting back to version {{2.5.2}} made the {{mvn install}} command succeed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
