Re: [MNG-5761] Dependency management is not transitive.

You are right, I was using the old version of the test project. The latest version does work with 3.4 and does make sense. Thank you for the explanation. -- Regards, Igor On Sat, Nov 19, 2016, at 09:36 PM, Christian Schulte wrote: > Am 11/20/16 um 03:28 schrieb Igor Fedorenko: > > I am sorry, C

Re: [MNG-5761] Dependency management is not transitive.

Am 11/20/16 um 03:28 schrieb Igor Fedorenko: > I am sorry, Christian, I must be missing something obvious. When I try > building the IT project you suggested as an expect of correct parent > version usage [1] I get the error below when using current 3.4 master. > Are you able to build the project s

Re: [MNG-5761] Dependency management is not transitive.

I am sorry, Christian, I must be missing something obvious. When I try building the IT project you suggested as an expect of correct parent version usage [1] I get the error below when using current 3.4 master. Are you able to build the project successfully? [INFO] Scanning for projects... [ERROR

Re: [MNG-5761] Dependency management is not transitive.

Am 11/20/16 um 02:56 schrieb Christian Schulte: > Am 11/20/16 um 00:12 schrieb Igor Fedorenko: >> Let me rephrase my question. What IT shows how to use parent version >> ranges with Maven 3.4? > > MNG-2199 > >

Re: [MNG-5761] Dependency management is not transitive.

When implementing parent version ranges, I also noticed MNG-5840. I did not know what to do about it because there has been comments around stating that the version is ingored intentionally somehow. I thought it is intentional the local parent resolution is ignoring the version element and did not

Re: [MNG-5761] Dependency management is not transitive.

Am 11/20/16 um 00:12 schrieb Igor Fedorenko: > Let me rephrase my question. What IT shows how to use parent version > ranges with Maven 3.4? MNG-2199

Re: [MNG-5761] Dependency management is not transitive.

Given all the bugs I found in parent version ranges, it would not surprise me if it had previously been appearing to work as long as you have a full reactor, but using -pl to slice and dice the reactor or building individual modules by cd-ing into them But anyway YMMV On Sat 19 Nov 2016 at 23:12,

Re: [MNG-5761] Dependency management is not transitive.

Let me rephrase my question. What IT shows how to use parent version ranges with Maven 3.4? We actually use parent version ranges quite extensively internally, so I am trying to assess the impact of 3.4 changes for our users. -- Regards, Igor On Sat, Nov 19, 2016, at 05:57 PM, Christian Schulte

Re: [MNG-5761] Dependency management is not transitive.

Am 11/19/16 um 23:57 schrieb Christian Schulte: > Am 11/19/16 um 13:35 schrieb Igor Fedorenko: >> What is parent version range syntax that works with 3.4? Or you are >> saying parent version ranges are not supported at all now? To not confuse anyone. The parent version range feature is not about s

Re: [MNG-5761] Dependency management is not transitive.

Am 11/19/16 um 13:35 schrieb Igor Fedorenko: > What is parent version range syntax that works with 3.4? Or you are > saying parent version ranges are not supported at all now? They got introduced in 3.2.2. This commit

Re: [VOTE] Release Apache Maven Resources Plugin version 3.0.2

I noticed a comment on MRESOURCES-230[1] that the issue is actually not fixed. Based on this comment I think there should be a test for it, even though the root cause is in a different project. Robert [1] https://issues.apache.org/jira/browse/MRESOURCES-230 On Sun, 13 Nov 2016 22:26:37 +010

Re: [VOTE] Release Apache Maven Resources Plugin version 3.0.2

Hi, +1 from me. checked with Maven 3.0.5, 3.1.1, 3.2.5, 3.3.9 without any issue. checked sha Ok. Site looks good so far. Kind regards Karl Heinz On 13/11/16 22:26, Christian Schulte wrote: Hi, We solved 3 issues: * [MRESOURCES-230] - Can't escape the escape string * [MRESOURCES-233

[GitHub] maven issue #97: .travis and SonarQube.com support

Github user trajano commented on the issue: https://github.com/apache/maven/pull/97 I am also thinking perhaps we can simplify this by removing the other axis. We should be able to target JDK7 as per the `README.md` and just set the JDK to Oracle 8 before Sonar execution. --- If yo

[GitHub] maven issue #97: .travis and SonarQube.com support

Github user trajano commented on the issue: https://github.com/apache/maven/pull/97 @bellingard how about we have target env + jdk + etc basically a single node then add a sonar execution. Sonar add on would also need to have a JDK that is associated with the add on (for sonar runne

Re: [MNG-5761] Dependency management is not transitive.

What is parent version range syntax that works with 3.4? Or you are saying parent version ranges are not supported at all now? -- Regards, Igor On Fri, Nov 18, 2016, at 10:57 PM, Christian Schulte wrote: > Am 11/19/16 um 03:58 schrieb Igor Fedorenko: > > Thank you for the analysis of the IT fail

[GitHub] maven issue #97: .travis and SonarQube.com support

Github user bellingard commented on the issue: https://github.com/apache/maven/pull/97 @trajano IMO, this is not the solution. What if you were defining other axis for the build (not related to Java version)? You'd still have to handle this manually. We'll try to think about this. -