Re: [LOGGING] Build errors

Have to admit I find the setup quite complex for a "commons" project too (and the fact tests don't run in the IDE without configuring the failsafe system properties is quite an issue IMHO). Guess the maven way is to split it in modules instead of doing N real artifacts (3 here) in one module (a

Re: [LOGGING] Build errors

On 30/11/2020 09:14, Romain Manni-Bucau wrote: > I think you need to adjust failsafe configuration, it passes the jar paths > as system properties. > Setting classifier without (instead of ) you move from > c-l--.jar to c-l-- so tests will > likely fail. > > Another weird thing is the last "full

Re: [LOGGING] Build errors

I think you need to adjust failsafe configuration, it passes the jar paths as system properties. Setting classifier without (instead of ) you move from c-l--.jar to c-l-- so tests will likely fail. Another weird thing is the last "full jar" dependency which has a classifier, I think the id of

Re: [LOGGING] Build errors

On 30/11/2020 08:50, Romain Manni-Bucau wrote: > Hi Mark > > my guess is that apijar execution must add api (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

Re: [LOGGING] Build errors

Hi Mark my guess is that apijar execution must add api (or any value) this way you get the default jar but also this particular one. Romain Manni-Bucau @rmannibucau | Blog | Old Blog |

[LOGGING] Build errors

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