[GitHub] maven-indexer issue #17: Migration to Lucene 6.1.0

[olamy]

Github user olamy commented on the issue:

https://github.com/apache/maven-indexer/pull/17
  
@scela fair enough. But as Lucene API change really often... Maybe migrate 
to the latest now so we are safe for a bit of time :-) 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[RESULT] [VOTE] Apache Maven Compiler 3.6.2

[Olivier Lamy]

Hi,
The vote has passed with the following result:
+1: Stephane, Robert, Herve, Karl, Olivier

I will finish release process.

Cheers
-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

[ANN] Apache Maven Enforcer Plugin 3.0.0-M1 Released

[Robert Scholte]

The Apache Maven team is pleased to announce the release of the Apache  
Maven Enforcer Plugin, version 3.0.0-M1


The Enforcer plugin provides goals to control certain environmental  
constraints such as Maven version, JDK version and OS family along with  
many more standard rules and user created rules.


https://maven.apache.org/enforcer/maven-enforcer-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-enforcer-plugin
  3.0.0-M1


You can download the appropriate sources etc. from the download page:

https://maven.apache.org/enforcer/download.cgi

NOTE: this is a milestone release, because there are still some open  
issues which need to be fixed before the official 3.0.0.
This release is mainly there to provide a Java9 compatible plugin  
(previous versions of some rules fail the build).



Release Notes - Maven Enforcer Plugin - Version 3.0.0-M1

** Bug
* [MENFORCER-234] - Link to plugin's web site is reported as  
redirected by maven linkcheck plugin.
* [MENFORCER-239] - Fix link in navigation  
(enforcer/maven-enforcer-plugin/index.html) RESOURCES

* [MENFORCER-240] - Link to page does not work
* [MENFORCER-265] - Get site generation working
* [MENFORCER-274] - Use of RequireJavaVersion with Java-9 breaking  
starting at b175


** Improvement
* [MENFORCER-228] - DependencyConvergence: Simplify logging errors
* [MENFORCER-253] - Upgrade maven-shared-components parent to version  
30
* [MENFORCER-259] - The rule BanDuplicatePomDependencyVersions is not  
documented

* [MENFORCER-263] - Upgrade mrm-maven-plugin to 1.0.0
* [MENFORCER-266] - Remove usage of prerequisites in parent pom
* [MENFORCER-267] - Upgrade to make Maven 3+

** New Feature
* [MENFORCER-204] - Add new rule: should be able to make sure that  
project artifact is a Snapshot

* [MENFORCER-247] - Add a "require file checksum" rule
* [MENFORCER-273] - RequireUpperBoundDeps.excludes

** Task
* [MENFORCER-272] - Allow site generation to work


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[RESULT][VOTE] Release Apache Maven Enforcer Plugin version 3.0.0-M1

[Robert Scholte]

Hi,

The vote has passed with the following result:

+1 : Peter Ansell, Karl Heinz Marbaise, Manfred Moser, Olivier Lamy,  
Stephane Nicoll, Hervé BOUTEMY, Robert Scholte


PMC quorum: reached

I will promote the artifacts to the central repo.

On Wed, 26 Jul 2017 22:58:53 +0200, Robert Scholte   
wrote:



Hi,

We solved 14 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520=12330768=Text

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317520%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1349
https://repository.apache.org/service/local/repositories/maven-1349/content/org/apache/maven/enforcer/enforcer/3.0.0-M1/enforcer-3.0.0-M1-source-release.zip

Source release checksum(s):
enforcer-3.0.0-M1-source-release.zip sha1:  
20b6e4800bb6357a25db6da3bdacc45675b9b5c8


Staging site:
https://maven.apache.org/enforcer-archives/enforcer-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

NOTE: this is a milestone release, because there are still some open  
issues which need to be fixed before the official 3.0.0.
This release is mainly there to provide a Java9 compatible plugin  
(previous versions fail the build).


Vote open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven Enforcer Plugin version 3.0.0-M1

[Robert Scholte]

+1

On Wed, 26 Jul 2017 22:58:53 +0200, Robert Scholte   
wrote:



Hi,

We solved 14 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520=12330768=Text

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317520%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1349
https://repository.apache.org/service/local/repositories/maven-1349/content/org/apache/maven/enforcer/enforcer/3.0.0-M1/enforcer-3.0.0-M1-source-release.zip

Source release checksum(s):
enforcer-3.0.0-M1-source-release.zip sha1:  
20b6e4800bb6357a25db6da3bdacc45675b9b5c8


Staging site:
https://maven.apache.org/enforcer-archives/enforcer-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

NOTE: this is a milestone release, because there are still some open  
issues which need to be fixed before the official 3.0.0.
This release is mainly there to provide a Java9 compatible plugin  
(previous versions fail the build).


Vote open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: MNG-6123 for Maven 3.5.1

[Robert Scholte]

Hi Karl Heinz,

comparing the key is often good enough, but I wonder if we should include  
the packaging type as well.
On the other hand, if there's another module with the same GA, then you'll  
have an issue as well.


Would be good to add a comment here that says ignoring type and  
classifiers is intended and seems valid here for the reason mentioned  
above.


thanks,
Robert

On Sun, 30 Jul 2017 13:25:12 +0200, Karl Heinz Marbaise  
 wrote:



Hi Robert,

On 30/07/17 12:56, Robert Scholte wrote:

I'm missing the code change, I see only IT changes.


Sure...missed the link:

https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=65bb3030193db6b5c0d55c0f00f94f2dc77b801d

On the branch:
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=shortlog;h=refs/heads/MNG-6123-detect-self-references


Kind regards
Karl Heinz Marbaise
 On Fri, 28 Jul 2017 22:03:15 +0200, Karl Heinz Marbaise  
 wrote:



Hi,

I would like to integrate MNG-6123[1] into Maven 3.5.1 (master)..which  
needs a small change to one of the integration tests[2]


The IT's are fine see[3]

Are any objections?

If there are no objections I would like to merge to master on  
tuesday...


Kind regards
Karl Heinz Marbaise


[1]: https://issues.apache.org/jira/browse/MNG-6123
[2]:  
https://git-wip-us.apache.org/repos/asf?p=maven-integration-testing.git;a=commit;h=3a1f095ec845c94b8e21ea28e4ffe69a01c29f4b  
[3]:  
https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-jenkinsfile/job/MNG-6123-detect-self-references/  
-

To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

 -
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org




Mit freundlichem Gruß
Karl-Heinz Marbaise


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Apache Maven Compiler 3.6.2

[Robert Scholte]

Hi,

All these tests are actually testing other libraries:

error-prone-compiler: javac-with-errorprone
groovy-project-with-new-plexus-compiler:  
groovy-eclipse-compiler

MCOMPILER-197: true

So it means that those libraries nor Java 9 ready, but the  
maven-compiler-plugin itself is.


Robert

On Sun, 30 Jul 2017 15:21:51 +0200, Karl Heinz Marbaise  
 wrote:



Hi,

I have rechecked the whole log files (testing my release checker script  
;-() of the runs and found the following for the JDK 9 tests:


And yes the error message is correct cause the "modules" in the JDK 9 is  
a single file and not a directory...(was there change?)...



[ERROR] Failed to execute goal  
org.apache.maven.plugins:maven-compiler-plugin:3.6.2:compile  
(default-compile) on project error-prone-compiler: Fatal error  
compiling: CompilerException: InvocationTargetException:  
java.nio.file.NotDirectoryException:  
/Library/Java/JavaVirtualMachines/jdk1.9.0_ea+180.jdk/Contents/Home/lib/modules  
-> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to  
execute goal  
org.apache.maven.plugins:maven-compiler-plugin:3.6.2:compile  
(default-compile) on project error-prone-compiler: Fatal error compiling
	at  
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
	at  
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at  
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at  
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
	at  
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
	at  
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
	at  
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)

Furthermore I found the following:

[parsing  
/Users/kama/maven-release-checker/release-test/jdk1.9.0_ea+180.jdk/apache-maven-3.0.5/maven-compiler-plugin-3.6.2/target/it/groovy-project-with-new-plexus-compiler/src/main/groovy/Helloable.groovy  
- #1/3]
[parsing  
/Users/kama/maven-release-checker/release-test/jdk1.9.0_ea+180.jdk/apache-maven-3.0.5/maven-compiler-plugin-3.6.2/target/it/groovy-project-with-new-plexus-compiler/src/main/groovy/GroovyHello.groovy  
- #2/3]
[parsing  
/Users/kama/maven-release-checker/release-test/jdk1.9.0_ea+180.jdk/apache-maven-3.0.5/maven-compiler-plugin-3.6.2/target/it/groovy-project-with-new-plexus-compiler/src/main/groovy/GroovyMain.groovy  
- #3/3]

[readinggroovy/lang/GroovyObject.class]
[readinggroovy/lang/MetaClass.class]
[analyzing  
/Users/kama/maven-release-checker/release-test/jdk1.9.0_ea+180.jdk/apache-maven-3.0.5/maven-compiler-plugin-3.6.2/target/it/groovy-project-with-new-plexus-compiler/src/main/groovy/Helloable.groovy  
- #1/3]

Annotation processing got disabled, since it requires a 1.6 compliant JVM
--
1. ERROR in  
/Users/kama/maven-release-checker/release-test/jdk1.9.0_ea+180.jdk/apache-maven-3.0.5/maven-compiler-plugin-3.6.2/target/it/groovy-project-with-new-plexus-compiler/src/main/groovy/Helloable.groovy  
(at line 1)

/*
^
[analyzing  
/Users/kama/maven-release-checker/release-test/jdk1.9.0_ea+180.jdk/apache-maven-3.0.5/maven-compiler-plugin-3.6.2/target/it/groovy-project-with-new-plexus-compiler/src/main/groovy/GroovyHello.groovy  
- #2/3]
[completed  
/Users/kama/maven-release-checker/release-test/jdk1.9.0_ea+180.jdk/apache-maven-3.0.5/maven-compiler-plugin-3.6.2/target/it/groovy-project-with-new-plexus-compiler/src/main/groovy/Helloable.groovy  
- #1/3]
[analyzing  
/Users/kama/maven-release-checker/release-test/jdk1.9.0_ea+180.jdk/apache-maven-3.0.5/maven-compiler-plugin-3.6.2/target/it/groovy-project-with-new-plexus-compiler/src/main/groovy/GroovyMain.groovy  
- #3/3]
[completed  
/Users/kama/maven-release-checker/release-test/jdk1.9.0_ea+180.jdk/apache-maven-3.0.5/maven-compiler-plugin-3.6.2/target/it/groovy-project-with-new-plexus-compiler/src/main/groovy/GroovyHello.groovy  
- #2/3]

[writingGroovyMain.class - #1]
The type java.lang.Object cannot be resolved. It is indirectly  
referenced from required .class files

--
--
2. ERROR in  
/Users/kama/maven-release-checker/release-test/jdk1.9.0_ea+180.jdk/apache-maven-3.0.5/maven-compiler-plugin-3.6.2/target/it/groovy-project-with-new-plexus-compiler/src/main/groovy/GroovyHello.groovy  
(at line 1)

/*
^
The type java.lang.String cannot be resolved. It is indirectly  
referenced from required .class files

--
[completed  

Re: [VOTE] Apache Maven Compiler 3.6.2

[Karl Heinz Marbaise]

Hi,

I have rechecked the whole log files (testing my release checker script 
;-() of the runs and found the following for the JDK 9 tests:


And yes the error message is correct cause the "modules" in the JDK 9 is 
a single file and not a directory...(was there change?)...



[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.6.2:compile 
(default-compile) on project error-prone-compiler: Fatal error 
compiling: CompilerException: InvocationTargetException: 
java.nio.file.NotDirectoryException: 
/Library/Java/JavaVirtualMachines/jdk1.9.0_ea+180.jdk/Contents/Home/lib/modules 
-> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to 
execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.6.2:compile 
(default-compile) on project error-prone-compiler: Fatal error compiling
	at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
	at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
	at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
	at 
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
	at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)

Furthermore I found the following:

[parsing 
/Users/kama/maven-release-checker/release-test/jdk1.9.0_ea+180.jdk/apache-maven-3.0.5/maven-compiler-plugin-3.6.2/target/it/groovy-project-with-new-plexus-compiler/src/main/groovy/Helloable.groovy 
- #1/3]
[parsing 
/Users/kama/maven-release-checker/release-test/jdk1.9.0_ea+180.jdk/apache-maven-3.0.5/maven-compiler-plugin-3.6.2/target/it/groovy-project-with-new-plexus-compiler/src/main/groovy/GroovyHello.groovy 
- #2/3]
[parsing 
/Users/kama/maven-release-checker/release-test/jdk1.9.0_ea+180.jdk/apache-maven-3.0.5/maven-compiler-plugin-3.6.2/target/it/groovy-project-with-new-plexus-compiler/src/main/groovy/GroovyMain.groovy 
- #3/3]

[readinggroovy/lang/GroovyObject.class]
[readinggroovy/lang/MetaClass.class]
[analyzing 
/Users/kama/maven-release-checker/release-test/jdk1.9.0_ea+180.jdk/apache-maven-3.0.5/maven-compiler-plugin-3.6.2/target/it/groovy-project-with-new-plexus-compiler/src/main/groovy/Helloable.groovy 
- #1/3]

Annotation processing got disabled, since it requires a 1.6 compliant JVM
--
1. ERROR in 
/Users/kama/maven-release-checker/release-test/jdk1.9.0_ea+180.jdk/apache-maven-3.0.5/maven-compiler-plugin-3.6.2/target/it/groovy-project-with-new-plexus-compiler/src/main/groovy/Helloable.groovy 
(at line 1)

/*
^
[analyzing 
/Users/kama/maven-release-checker/release-test/jdk1.9.0_ea+180.jdk/apache-maven-3.0.5/maven-compiler-plugin-3.6.2/target/it/groovy-project-with-new-plexus-compiler/src/main/groovy/GroovyHello.groovy 
- #2/3]
[completed 
/Users/kama/maven-release-checker/release-test/jdk1.9.0_ea+180.jdk/apache-maven-3.0.5/maven-compiler-plugin-3.6.2/target/it/groovy-project-with-new-plexus-compiler/src/main/groovy/Helloable.groovy 
- #1/3]
[analyzing 
/Users/kama/maven-release-checker/release-test/jdk1.9.0_ea+180.jdk/apache-maven-3.0.5/maven-compiler-plugin-3.6.2/target/it/groovy-project-with-new-plexus-compiler/src/main/groovy/GroovyMain.groovy 
- #3/3]
[completed 
/Users/kama/maven-release-checker/release-test/jdk1.9.0_ea+180.jdk/apache-maven-3.0.5/maven-compiler-plugin-3.6.2/target/it/groovy-project-with-new-plexus-compiler/src/main/groovy/GroovyHello.groovy 
- #2/3]

[writingGroovyMain.class - #1]
The type java.lang.Object cannot be resolved. It is indirectly 
referenced from required .class files

--
--
2. ERROR in 
/Users/kama/maven-release-checker/release-test/jdk1.9.0_ea+180.jdk/apache-maven-3.0.5/maven-compiler-plugin-3.6.2/target/it/groovy-project-with-new-plexus-compiler/src/main/groovy/GroovyHello.groovy 
(at line 1)

/*
^
The type java.lang.String cannot be resolved. It is indirectly 
referenced from required .class files

--
[completed 
/Users/kama/maven-release-checker/release-test/jdk1.9.0_ea+180.jdk/apache-maven-3.0.5/maven-compiler-plugin-3.6.2/target/it/groovy-project-with-new-plexus-compiler/src/main/groovy/GroovyMain.groovy 
- #3/3]

[3 units compiled]
[1 .class file generated]
[INFO] Compilation complete.  Compiled 3 files.
[DEBUG] incrementalBuildHelper#afterRebuildExecution
[INFO] -
[ERROR] COMPILATION ERROR :



So for JDK 9 there is a problem in there...

[INFO] --- 

Re: MNG-6174 for Maven 3.5.1

[Karl Heinz Marbaise]

Hi

On 30/07/17 12:58, Robert Scholte wrote:

+1, we'll never going to support model 3.0.0.


I hope so ;-)..


This will be different when introducing model 5.0.0; in that case we 
will need both.


This is small step into this direction and to make a kind of 
housekeeping.. which  makes it easier to start with model 5.0.0...;-)..


Kind regards
Karl Heinz Marbaise



On Fri, 28 Jul 2017 22:07:51 +0200, Karl Heinz Marbaise 
 wrote:



Hi,

I would like to integrate MNG-6174[1] into Maven 3.5.1 (master)..

The IT's are fine see[2]

Are any objections?

If there are no objections I would like to merge to master on tuesday...

Kind regards
Karl Heinz Marbaise

[1]: https://issues.apache.org/jira/browse/MNG-6174
[2]: 
https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-jenkinsfile/job/mvn-3.5.1%252FMNG-6174/ 



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: MNG-6123 for Maven 3.5.1

[Karl Heinz Marbaise]

Hi Robert,

On 30/07/17 12:56, Robert Scholte wrote:

I'm missing the code change, I see only IT changes.


Sure...missed the link:

https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=65bb3030193db6b5c0d55c0f00f94f2dc77b801d

On the branch:
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=shortlog;h=refs/heads/MNG-6123-detect-self-references


Kind regards
Karl Heinz Marbaise


On Fri, 28 Jul 2017 22:03:15 +0200, Karl Heinz Marbaise 
 wrote:



Hi,

I would like to integrate MNG-6123[1] into Maven 3.5.1 (master)..which 
needs a small change to one of the integration tests[2]


The IT's are fine see[3]

Are any objections?

If there are no objections I would like to merge to master on tuesday...

Kind regards
Karl Heinz Marbaise


[1]: https://issues.apache.org/jira/browse/MNG-6123
[2]: 
https://git-wip-us.apache.org/repos/asf?p=maven-integration-testing.git;a=commit;h=3a1f095ec845c94b8e21ea28e4ffe69a01c29f4b 

[3]: 
https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-jenkinsfile/job/MNG-6123-detect-self-references/ 



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org





Mit freundlichem Gruß
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz MarbaiseUSt.IdNr: DE191347579
Hauptstrasse 177
52146 Würselen   http://www.soebes.de

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: MNG-6174 for Maven 3.5.1

[Robert Scholte]

+1, we'll never going to support model 3.0.0.
This will be different when introducing model 5.0.0; in that case we will  
need both.


On Fri, 28 Jul 2017 22:07:51 +0200, Karl Heinz Marbaise  
 wrote:



Hi,

I would like to integrate MNG-6174[1] into Maven 3.5.1 (master)..

The IT's are fine see[2]

Are any objections?

If there are no objections I would like to merge to master on tuesday...

Kind regards
Karl Heinz Marbaise

[1]: https://issues.apache.org/jira/browse/MNG-6174
[2]:  
https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-jenkinsfile/job/mvn-3.5.1%252FMNG-6174/


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: MNG-6123 for Maven 3.5.1

[Robert Scholte]

I'm missing the code change, I see only IT changes.

On Fri, 28 Jul 2017 22:03:15 +0200, Karl Heinz Marbaise  
 wrote:



Hi,

I would like to integrate MNG-6123[1] into Maven 3.5.1 (master)..which  
needs a small change to one of the integration tests[2]


The IT's are fine see[3]

Are any objections?

If there are no objections I would like to merge to master on tuesday...

Kind regards
Karl Heinz Marbaise


[1]: https://issues.apache.org/jira/browse/MNG-6123
[2]:  
https://git-wip-us.apache.org/repos/asf?p=maven-integration-testing.git;a=commit;h=3a1f095ec845c94b8e21ea28e4ffe69a01c29f4b
[3]:  
https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-jenkinsfile/job/MNG-6123-detect-self-references/


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org