Re: easing Maven parent poms management

MPOM-95 [1] created I'll start the work on this Regards, Hervé [1] https://issues.apache.org/jira/browse/MPOM-95 Le dimanche 1 novembre 2015 10:03:34 Hervé BOUTEMY a écrit : > Currently, we have 5 Maven parent POMs [1] (not counting Doxia), each with > its own release cycle. > Releasing each se

Re: Shade plugin from directories instead of jars in multimodule builds ?

Run the build with -X and see what mojos are executed for mshade171-base project: [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ mshade171-base --- [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ mshade171-base --- [INFO] --- maven-compiler-plug

Re: Build failed in Jenkins: dist-tool-plugin #1053

Hi, so on this repository: https://github.com/apache/maven-indexer/ there has nothing changed... Hm... Kind regards Karl Heinz Marbaise On 11/14/15 7:29 PM, Karl Heinz Marbaise wrote: Hi, It looks like Tamás has made releases from here: https://github.com/sonatype/maven-indexer/commits/so

Re: Build failed in Jenkins: dist-tool-plugin #1053

Hi, It looks like Tamás has made releases from here: https://github.com/sonatype/maven-indexer/commits/sonatype-release Hm...Not a good idea from my point of view...without a VOTE nothing at all Kind regards Karl Heinz Marbaise On 11/14/15 7:02 PM, Karl Heinz Marbaise wrote: Hi Hervé,

Re: Build failed in Jenkins: dist-tool-plugin #1053

Hi Hervé, i think we should contact Tamás.. that looks strange... Kind regards Karl Heinz Marbaise On 11/14/15 6:49 PM, Karl Heinz Marbaise wrote: Hi Hervé, The site only shows 5.1.1 https://maven.apache.org/maven-indexer/ Furthermore the ASF repository shows 5.1.1, 5.1.2... and central sho

Re: Build failed in Jenkins: dist-tool-plugin #1053

Hi Hervé, The site only shows 5.1.1 https://maven.apache.org/maven-indexer/ Furthermore the ASF repository shows 5.1.1, 5.1.2... and central shows something different... which i can't explain nor that i can remember about a VOTE... I have checked the signature file gpg: Signature made Wed Nov

Re: Build failed in Jenkins: dist-tool-plugin #1053

> Generating "Dist Tool> Check Sites" report --- > dist-tool-plugin:1.0-SNAPSHOT:check-site Downloading: > https://repo.maven.apache.org/maven2/org/apache/maven/indexer/maven-indexer > /5.1.2-c65990c/maven-indexer-5.1.2-c65990c.pom [ERROR] Error resolving > project artifact: Could not find artifact

Re: Shade plugin from directories instead of jars in multimodule builds ?

I've been using the test project attached to https://issues.apache.org/jira/browse/MSHADE-171, single threaded. Shade is bound to package. I really dont understand this :) K 2015-11-14 13:57 GMT+01:00 Igor Fedorenko : > I believe "mvn clean package" runs the default lifecycle twice, first to >

Re: Shade plugin from directories instead of jars in multimodule builds ?

I believe "mvn clean package" runs the default lifecycle twice, first to "package" phase, when reactor dependencies are resolved to packaged jars, then to "test" phase, when reactor dependencies are resolved to target/classes folders. I am surprised shade plugin is called during "test" run at all.

Re: Shade plugin from directories instead of jars in multimodule builds ?

Op Sat, 14 Nov 2015 11:53:41 +0100 schreef Kristian Rosenvold : While working on MSHADE-171, I figured I'd take a stab at making shade work from the "target" folder instead of just the assembled finished jar. I implemented this, and it works kinda-ok, but then I realized that I'm not producin

Shade plugin from directories instead of jars in multimodule builds ?

While working on MSHADE-171, I figured I'd take a stab at making shade work from the "target" folder instead of just the assembled finished jar. I implemented this, and it works kinda-ok, but then I realized that I'm not producing the same output as I would from "package", since there is no META-I