package a war which depends on a shaded jar or at jar

Hi all: I have a project with two modules as below: project -- module1 (shaded jar) -- module2 (war) Module2 depends on module1. And module1 packages to a shaded jar with maven shade plugin. Module2 packages to a war which depends on module1. When I try to execute mvn package, it produces a

Re: Using maven profiles for easily parallel testing?

> > > I'm thinking of a clunky approach of including tests with names starting > with [A-Ma-m] in one build configuration, and those with names starting > with [^A-Ma-m] in another build configuration. These build configuration > could have most of their actual configuration in a build template,

Re: Using maven profiles for easily parallel testing?

Hi Kevin, On 05/11/16 22:33, Kevin Burton wrote: We use TeamCity internally (which is great btw) for Maven testing. We have about 2000 tests which we continually integrate on every commit. The problem is that testing takes about 15 minutes from start to end. Is this really the time for the

Re: Using maven profiles for easily parallel testing?

> > > Is this really the time for the tests only or is this the whole build time > including the test time? If it is only the time for running the tests it > means those tests are slow... > > Yeah. I agree. The slow ones are all essentially integration tests. Some take 20-30 seconds as they

Re: Using maven profiles for easily parallel testing?

On Sun, Nov 6, 2016 at 8:48 AM Kevin Burton wrote: > > If you like to parallize the unit tests themself you have to configure > > maven-surefire-plugin accordingly...I recommend reading the doc about > that > > subject[2]. > > Ah.. interesting. Those changes should be

Re: Build behavior differences between 3.2.5 and 3.3.9 with dependency shading

yes that was the advice I gave on this thread originally. you do have to fight a bit with the shade plugin to get them shaded in though... which is why I think we may need to rethink how we do shade On 6 November 2016 at 22:36, Jörg Schaible wrote: > Stephen Connolly

Re: package a war which depends on a shaded jar or at jar

There are two solutions. 1. Use Maven < 3.3.0 2. Mark the dependencies that are shaded as optional or provided in the module doing the shading In the transition from Maven 3.2.x to Maven 3.3.x the internal model was made read-only which rendered the hacks that the shade plugin has been using (to

Re: Build behavior differences between 3.2.5 and 3.3.9 with dependency shading

Stephen Connolly wrote: > Hmmm I did some digging... > > https://maven.apache.org/ref/3.2.3/apidocs/org/apache/maven/artifact/handler/ArtifactHandler.html#isIncludesDependencies() > is i think the idea JvZ was hinting at. > > For the case where a shaded JAR shades *everything* then a custom >

Re: Build behavior differences between 3.2.5 and 3.3.9 with dependency shading

Hmmm I did some digging... https://maven.apache.org/ref/3.2.3/apidocs/org/apache/maven/artifact/handler/ArtifactHandler.html#isIncludesDependencies() is i think the idea JvZ was hinting at. For the case where a shaded JAR shades *everything* then a custom packaging will work as we could set this

RE: Possible to make a release of maven-changes-plugin

Hi, I had some time off so I missed the 72 hrs window but I can see that you voted for release anyway. Nice!! Thx, //mike -Original Message- From: Sent: den 29 oktober 2016 20:46 To: Maven Users List Subject: Re: Possible to make a release of