Op Mon, 14 Jul 2014 17:23:21 +0200 schreef Igor Fedorenko
:
Hi,
The vote has passed with the following result:
+1 (binding): Jason van Zyl, Robert Scholte, Hervé BOUTEMY
+1 (non binding): Karl-Heinz Marbaise
I will promote the artifacts to the central repo.
Also, can somebody with awesome
Hi,
The vote has passed with the following result:
+1 (binding): Jason van Zyl, Robert Scholte, Hervé BOUTEMY
+1 (non binding): Karl-Heinz Marbaise
I will promote the artifacts to the central repo.
Also, can somebody with awesome pmc powers kindly copy the source
release to the Apache Distribu
instead of removing info in the matrix comparison [1], I would have preferred
to just add a notice that the 2 other systems are out of date (or any better
explanations that I read on the ML, IIRC)
There are compatibility issues with Maven version that are reguarly told on
the ML that should be
+1
ps org.apache.maven.plugin.testing.PluginArtifactFileTest.testArtifact()
wasn't Windows-proof, that's fixed by now.
Op Tue, 08 Jul 2014 13:58:40 +0200 schreef Igor Fedorenko
:
Hi,
We solved 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740&version=20039
Ther
Can I get couple more votes please?
I didn't stress this, but this release makes plugin testing harness
compatible with maven 3.2.2, which I think is rather important if we
want to encourage plugin developers adopt new maven versions more willingly.
--
Regards,
Igor
On 2014-07-08, 16:43, Jason
It's for plugins and that enforces the version of Maven it can run in. Purely a
runtime check. It doesn't check anything at build time.
On Jul 8, 2014, at 4:40 PM, Karl Heinz Marbaise wrote:
> Hi Igor,
>
>
> > I am not sure I understand your concern about Maven versions. The test
>> harness i
Hi Igor,
> I am not sure I understand your concern about Maven versions. The test
harness itself can be built with pretty much any version of Maven
Unfortunately this is not true...you can't build with Maven 2.2.1 cause
you will get things like this:
[INFO] Scanning for projects...
[INFO]
I am not sure I understand your concern about Maven versions. The test
harness itself can be built with pretty much any version of Maven and I
expect any 3.x to work, but the plugins that use plugin testing 3.2.0
will have to use depend on Maven 3.2.1 or newer.
--
Regards,
Igor
On 2014-07-09, 0:
Hi,
checked SHA1 Ok.
Tested with Maven 3.2.1, 3.1.1, 3.0.5
Based on that I have found a small thing
The maven version can't be controlled by prerequisites only via
maven-enforcer-plugin so this will not work in Maven 3.X ...but this not
an issue for the release...
+1 (non binding)
+1
On Jul 8, 2014, at 7:58 AM, Igor Fedorenko wrote:
> Hi,
>
> We solved 4 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740&version=20039
>
> There are no issues left in JIRA
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1039/
> http://
Hi,
We solved 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740&version=20039
There are no issues left in JIRA
Staging repo:
https://repository.apache.org/content/repositories/maven-1039/
http://repository.apache.org/content/repositories/maven-1039/org/apache/maven/plug
11 matches
Mail list logo
