[
https://issues.apache.org/jira/browse/MINSTALL-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16634369#comment-16634369
]
Karl Heinz Marbaise commented on MINSTALL-151:
----------------------------------------------
[~gsfernandes] You are right with ...it was working before for a long
time...but that is a major version release which can break and will break
things otherwise we would never be able to evolve things...
The point with 3.0.0-M1 is: It is released (now in central) and can't go back
or being changed or being removed ....only with 3.0.0-M2 etc. or 3.0.0 I can do
changes in it...
What I can do is: Release a version 3.0.0-M2 which will produce a WARNING with
a Hint becoming an error with final 3.0.0 release? But usually WARNINGs are
ignored...
Furthermore it shows how many people do not correctly pin the version of their
plugins...
Apart from that I fear that many custom plugins are doing this wrong...
> 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)