Hi Erwin, I ran into the same last night. I guess 3.0.0-M1 is new and has issues/incompatibilities with the Karaf plugin.
The way I fixed it was to define the following in the pluginManagement in the pom.xml or a parent pom.xml to force versions 2.5.2 and 2.8.2 for the install and deploy plugins respectively: <build> <pluginManagement> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-install-plugin</artifactId> <version>2.5.2</version> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-deploy-plugin</artifactId> <version>2.8.2</version> </plugin> <plugin> <groupId>org.apache.karaf.tooling</groupId> <artifactId>karaf-maven-plugin</artifactId> <version>${org.apache.karaf.version}</version> <extensions>true</extensions> </plugin> </plugins> </pluginManagement> </build> Hope this helps. Thank you, Oleg > On Oct 1, 2018, at 9:49 AM, Erwin Hogeweg <erwin.hoge...@me.com> wrote: > > Hi - > > All of a sudden we are getting a maven build this error when building a karaf > distribution. This started late yesterday and happens on multiple developer > machines but not all. I have nuked my entire .m2 repo and rolled back to a > version well before the issue started but I still get the same error. > > We’re kinda scratching our heads here… Has anyone an idea what is going on? > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-install-plugin:3.0.0-M1:install > (default-install) on project my-distribution: 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] > > Karaf-4.2.0 > Java-1.8.0_92 > Maven-3.5.0 > > > Thanks, > > Erwin >