[
https://issues.apache.org/jira/browse/MINSTALL-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707258#comment-16707258
]
Robert Andersson commented on MINSTALL-151:
-------------------------------------------
What about this use-case:
[https://stackoverflow.com/questions/352612/how-to-get-maven-to-run-warexploded-but-not-warwar]
If I understand the discussion above this simple solution will no longer work:
[https://stackoverflow.com/a/11134940]
Instead something more complicated along this line is needed:
[https://stackoverflow.com/a/1449740]
Is the extra complexity for this simple use-case expected and desired?
> 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
(v7.6.3#76005)
