Re: Some Maven Eclipse Questions

2015-12-10 Thread Anders Hammar
These questions are better suited for the m2e mailing list. https://dev.eclipse.org/mailman/listinfo/m2e-users /Anders (mobile) On Dec 11, 2015 06:16, "Sony Antony" wrote: > 1. Noticed that even when I use the EMBEDDED maven inside m2e, it is > creating a new JVM - different from the JVM running

Some Maven Eclipse Questions

2015-12-10 Thread Sony Antony
1. Noticed that even when I use the EMBEDDED maven inside m2e, it is creating a new JVM - different from the JVM running Eclipse - for maven install ( even for cleam ). Is this always the case ? ( Im trying to see if this happened because of some issues with my setup ) 2. I have a multip project.

[Jigsaw] Get involved and stay informed about Maven and JDK9 Jigsaw

2015-12-10 Thread Robert Scholte
Hi, the Apache Maven team has decided to introduce a new subject prefix for the maven-dev mailinglist[1]. Messages prefixed with [Jigsaw] will be used to share information about Mavens progress on adopting JDK9 Jigsaw. Current status: I've been able to package the current codebase of Maven

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

2015-12-10 Thread Stephen Connolly
You need to do this in any module that is producing a dependency reduced pom (and only in those modules) You can leave the version being inherited from dependencyManagement. I advise using the optional technique until Jason gets a new packaging for dependency reduced artifacts (or decides to agre

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

2015-12-10 Thread Robert Metzger
Okay, the true suggestion sounds interesting. I'll try that out. However, I'm still wondering why the behavior between 3.2 and 3.3 is different? Our CI system runs Maven 3.2, so the shading is done correctly there. If a project committer now adds a guava dependency and forgets the , we end up with

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

2015-12-10 Thread Stephen Connolly
Dependency reduced poms require mutation of the model after the build started. JvZ is investigating a different packaging type to resolve this... Workaround for now is to mark all the dependencies that are removed as true so that they are no longer transitive and that way the effective reactor Pom

Build behavior differences between 3.2.5 and 3.3.9 with dependency shading

2015-12-10 Thread Robert Metzger
Hi, The Apache Flink project is using Maven for dependency management. We shade Google's Guava away (to org.apache.flink.shaded.com.google.commons) to avoid conflicts with user guava versions. Building Flink with Maven 3.2.5 will create a valid fat-jar without guava. However, Maven 3.3.9 (and oth