On 30/11/2020 08:50, Romain Manni-Bucau wrote: > Hi Mark > > my guess is that apijar execution must add <classifier>api</classifier> (or > any value) > > this way you get the default jar but also this particular one.
Thanks. That did it. Fix pushed. Mark > > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <https://rmannibucau.metawerx.net/> | Old Blog > <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > <https://www.packtpub.com/application-development/java-ee-8-high-performance> > > > Le lun. 30 nov. 2020 à 09:40, Mark Thomas <ma...@apache.org> a écrit : > >> Hi, >> >> I've stumbled across the following error when trying to build a clean >> clone of commons-logging with Maven 3.6.3 and Java 8u275 >> >> git clone g...@github.com:apache/commons-logging.git asf-commons-logging >> cd asf-commons-logging >> mvn clean package >> ... >> Failed to execute goal >> org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (apijar) on project >> commons-logging: You have to use a classifier to attach supplemental >> artifacts to the project instead of replacing them. -> [Help 1] >> >> My Maven foo is limited. Any hints on what needs changing in the POM to >> fix this? >> >> Mark >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
