Recently I've updated maven-jar-plugin to upstream version 3.0.0. This update caused a few packages to fail to build. I will try to take care of fixing most (all?) of broken packages, but in case someone needs to fix a build problem by themselves, I'm sharing solutions to common problems. Common problem nr 1 ------------------- Plugin fails with error message: "You have to use a classifier to attach supplemental artifacts to the project instead of replacing them." It means that project defines its own JAR plugin executions, which are trying to override JAR(s) generated by default executions. A solution to most of cases like that would be skipping default execution, for eg.: http://pkgs.fedoraproject.org/cgit/cal10n.git/commit/?id=f6b14c5 Common problem nr 2 ------------------- Plugin fails with error message: "You are using 'useDefaultManifestFile' which has been removed from the maven-jar-plugin. Please see the >>Major Version Upgrade to version 3.0.0<< on the plugin site." As the error message and website say, you need to use Maven Archiver configuration instead of deprecated 'useDefaultManifestFile', for eg.: http://pkgs.fedoraproject.org/cgit/rpms/easymock.git/tree/easymock-port-to-maven-jar-plugin-3.patch?id=3d407bc -- Mikolaj Izdebski Software Engineer, Red Hat IRC: mizdebsk -- java-devel mailing list java-devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/java-devel@xxxxxxxxxxxxxxxxxxxxxxx
