+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)..
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
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
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
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:
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
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
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
+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:
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
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
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
12 matches
Mail list logo