[MINSTALL-151] Projects without primary artifacts, but with attachment artifacts fail install

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-M1
• Fix Version/s: 3.1.1
• Assignee: Slawomir Jaranowski
• Reporter: Peter Huffer
• Created: 01/Oct/18 15:38
• Updated: 30/May/23 16:55
• Resolved: 22/Apr/23 10:43

Description

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:

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]

Reverting back to version 2.5.2 made the mvn install command succeed.

Issue Links

• duplicates: MINSTALL-152 Maven Install Plugin Version 3.0.0-M1 unable to build POMs with packaging set "feature"
• is blocked by: MSHARED-760 Do not fail if no main artifact has been set, but attachments existing
• is fixed by: MINSTALL-189 Add parameter to lax project validation
• is related to: MINSTALL-118 MavenProject with only attachments must have packaging "pom"
• is related to: MINSTALL-169 Handle non-pom packaging with only a pom artifact
• relates to: MDEPLOY-288 Deploy is failed when no primary artifact is present