[GitHub] [maven-site] suztomo commented on a change in pull request #176: [MNGSITE-415] say Maven 3.0.x is EOL

2020-06-13 Thread GitBox 


suztomo commented on a change in pull request #176:
URL: https://github.com/apache/maven-site/pull/176#discussion_r439793731



##
File path: content/markdown/docs/history.md.vm
##
@@ -93,6 +93,22 @@ Date format is: -MM-DD
 #release( "2013-10-04" "3.1.1" 
"announce/201310.mbox/%3C0D117268-CE78-4051-9484-DE2EE770B120%40apache.org%3E" 
"true" "Java 5" "17" )
 #release( "2013-07-15" "3.1.0" 
"users/201307.mbox/%3C4C1F2A95-5EBB-473E-BC3F-4D3969A78421%40tesla.io%3E" "" "" 
"" )
 #release( "2013-06-10" "3.1.0-alpha-1" 
"users/201306.mbox/%3C2D8B1BBD-FF9E-4537-A748-857C96664161%40tesla.io%3E" "" "" 
"" )
+
+
+
+Maven 3.0.x

Review comment:
   (trivial) You may want to have different value for “name” attribute, say 
“Maven_3.0”, to distinguish this header from the one above.





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

Re: Suggestion: announce Maven 3.0.x is EOL

2020-06-13 Thread Olivier Lamy 
On Sun, 14 Jun 2020 at 04:06, Robert Scholte  wrote:

> To me these are 2 different things.
> Yes, we are going to require Maven 3.1 for our plugins (and because of API
> changes we need to be explicit about this), but that doesn't mean that
> Maven 3.0.x itself is end of life.
>
> Depending on how you ask the question, to me EOLs are either about majors
> or minors.
> It is clear to me we won't do anything for Maven 2 anymore.
> At the same time, I expect we will never do a 3.3.10 or 3.5.5.
>

If we are not marking versions as EOL we will eventually have to provide a
security fix.
In case of security issues found in 3.0.5, do we really want to have to
release 3.0.6, 3.1.2, 3.2.6 etc
I guess it's the main reason for marking versions as EOL.


>
> I don't know what people expect by a statement about EOL: nobody has a
> support contract for Maven, so talking about EOL doesn't make any sense to
> me.
> It all depends on what critical issue may appear, based on that we'll make
> our decision.
> To me it is either: EOL for Maven2 and/or with every new release the
> previous will be marked as EOL.
>

We just want to be clear in the bureaucratic POV we will not provide
security fixes for those versions marked EOL.
I'm +1 we clearly define which versions are "supported" (at least security
fixe) and which versions are EOL.


>
> Robert
>
>
>
>
> On 13-6-2020 17:26:15, Elliotte Rusty Harold  wrote:
> I think we've achieved consensus that Maven 3.0.x should no longer be
> supported by new plugin releases and 3.1.x is our minimum. Assuming
> that's true, this PR updates the history page to account for that:
>
> https://github.com/apache/maven-site/pull/176
>
> If anyone thinks we have not achieved consensus, or should not
> announce that 3.0.x is end of life, please say so.
>
> As always, please also comment on exact language of the PR, markup
> syntax, and other pages that need to be updated. Thanks.
>
> --
> Elliotte Rusty Harold
> elh...@ibiblio.org
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

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

Re: [VOTE] Release Apache Maven Surefire Plugin version 3.0.0-M5

2020-06-13 Thread Tibor Digana 
Hi Herve,

We can fork the discussion about this problem apart in the Slack.
Thx for finding this.

T


On Sat, Jun 13, 2020 at 9:35 PM Hervé BOUTEMY  wrote:

> +1
>
> near full reproducibility of reference artifacts with JDK 8 on Windows: 48
> artifacts are ok, just 2 still have issues:
> - surefire-3.0.0-M5-source-release.zip: I don't know why my local build
> added 3 dependency-reduced-pom.xml that do not exist in reference build
> - surefire-shadefire-3.0.0-M5.jar: some strange timestamp issues for some
> shaded content, probably a subtle maven-shade-plugin bug
>
> Regards,
>
> Hervé
>
> Le samedi 13 juin 2020, 15:46:10 CEST Tibor Digana a écrit :
> > Hi,
> >
> > We solved 40 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927
> > rsion=12344612
> >
> > There are still a couple of issues left in JIRA:
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20
> > status%20%3D%20Open%20ORDER%20BY%20priority%20DESC
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1590/
> >
> https://repository.apache.org/content/repositories/maven-1590/org/apache/mav
> > en/surefire/surefire/3.0.0-M5/surefire-3.0.0-M5-source-release.zip
> >
> > Source release checksum(s):
> > surefire-3.0.0-M5-source-release.zip  sha1:
> > 687a89ceb4a1b2e5dd472deec8d3843f2a98b68f
> > surefire-3.0.0-M5-source-release.zip  sha512:
> >
> e88ced058923b349acfe1948d4c4a7ff6f4bef08e5685f2f2ac73cfb26ad35fd6578f05309f0
> > 91081f01986b19bbca38a2fe6bf0fbd16980cd6f41228c529ee7
> >
> > Staging site:
> > http://maven.apache.org/surefire-archives/surefire-LATEST/
> >
> > Guide to testing staged releases:
> > http://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > Cheers
> > Tibor
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Apache Maven Surefire Plugin version 3.0.0-M5

2020-06-13 Thread Tibor Digana 
A big "Thank You" goes to our user and contributor Jonathan Bell who is
Assistant Professor at the George Mason University, his students, and our
Apache colleague Enrico Olivelli.
Of course a big "Thank You" goes to our Apache Maven team.

Along we speeded up the plugin with short startup and teardown time of
forked JVM. We made faster communication on the TCP level and process pipes
level as well.

Additionally, we improved smart resolver of JUnit5 Engines and fixed some
issues, see
https://github.com/apache/maven-surefire/blob/master/maven-surefire-plugin/src/site/apt/examples/junit-platform.apt.vm
Regarding the JPMS, now the users can have "module-info.java" in
src/test/java. Here the user should be more careful if the module
descriptor was used in his project due to the behavior is determined by
this descriptor. For more information, see
https://github.com/apache/maven-surefire/blob/master/maven-surefire-plugin/src/site/apt/examples/jpms.apt.vm

On Sat, Jun 13, 2020 at 10:02 PM Tibor Digana 
wrote:

> Yes, thank you Enrico.
>
> After a long time, we found a good reason to fix annoying issues which
> requires reworking some parts of the code. And also we were able to let the
> users use their implementation without asking us in Apache.
> We touched the milestone release where we could introduce the feature and
> let the people enable a new functionality.
>
> Maybe you guys know that the Surefire and Failsafe plugins were using
> std/in and std/out (pipes) as interprocess communication between Maven
> process and forked JVM.
> Often the users, especially the OSGi users, claimed that these pipes
> should be used by the tests.
> Additionally, there was a request, from one of our users at GitHub, that
> the Surefire fork VMs should be capable of distributing the load in
> horizontal direction (hardware) which would first of all require a new
> abstraction and communication facilities.
> Today we are able to accomplish this!
>
> We have introduced an abstraction which allows the users to implement
> their own communication facilities for their purposes.
> Of course, we provided two internal implementations.
> One defaults to the traditional pipes, and the second is using TCP/IP
> channels with authentication.
> The second implementation is especially interesting because you can enable
> a new way of communication using the TCP sockets:
>
>  implementation="org.apache.maven.plugin.surefire.extensions.SurefireForkNodeFactory"/>
>
>
> The std/out and std/err would be ready for use in your tests.
> One may ask, why we did not enable this TCP/IP channel by default.
> We want to let the users adapt first and check it out.
> Feel free to let us know about your findings.
>
> This approach gave you a certain freedom. For instance you can configure
> your extension.
> In the future we may introduce "bindAddress" in SurefireForkNodeFactory
> but this can be also done by the user:
>
>  implementation="org.apache.maven.plugin.surefire.extensions.SurefireForkNodeFactory">
>
> 192.168.10.15
> 
>
> In the references you can find the documentation to the Extension API and
> SPI.
> This may help you out on implementing your own extensions.
>
> References:
>
> https://github.com/apache/maven-surefire/blob/master/maven-surefire-plugin/src/site/apt/examples/process-communication.vm
>
>
>
>
>
>
> On Sat, Jun 13, 2020 at 9:15 PM Enrico Olivelli 
> wrote:
>
>> (I will cast my final vote on Monday)
>> Tibor
>> It is worth to note that this release includes the new communication
>> protocol between Maven and the forked JVM.
>> Can you please share a bit of help about how to try it?
>>
>> This is a great release of surefire, it is a big milestone for Maven and
>> Surefire
>>
>>
>> Enrico
>>
>> Il Sab 13 Giu 2020, 20:50 Michael Osipov  ha
>> scritto:
>>
>> > Am 2020-06-13 um 15:46 schrieb Tibor Digana:
>> > > Hi,
>> > >
>> > > We solved 40 issues:
>> > >
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12344612
>> > >
>> > > There are still a couple of issues left in JIRA:
>> > >
>> >
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC
>> > >
>> > > Staging repo:
>> > > https://repository.apache.org/content/repositories/maven-1590/
>> > >
>> >
>> https://repository.apache.org/content/repositories/maven-1590/org/apache/maven/surefire/surefire/3.0.0-M5/surefire-3.0.0-M5-source-release.zip
>> > >
>> > > Source release checksum(s):
>> > > surefire-3.0.0-M5-source-release.zip  sha1:
>> > > 687a89ceb4a1b2e5dd472deec8d3843f2a98b68f
>> > > surefire-3.0.0-M5-source-release.zip  sha512:
>> > >
>> >
>> e88ced058923b349acfe1948d4c4a7ff6f4bef08e5685f2f2ac73cfb26ad35fd6578f05309f091081f01986b19bbca38a2fe6bf0fbd16980cd6f41228c529ee7
>> > >
>> > > Staging site:
>> > > http://maven.apache.org/surefire-archives/surefire-LATEST/
>> > >
>> > > Guide to testing staged releases:
>> > >
>>

Re: [VOTE] Release Apache Maven Surefire Plugin version 3.0.0-M5

2020-06-13 Thread Tibor Digana 
Yes, thank you Enrico.

After a long time, we found a good reason to fix annoying issues which
requires reworking some parts of the code. And also we were able to let the
users use their implementation without asking us in Apache.
We touched the milestone release where we could introduce the feature and
let the people enable a new functionality.

Maybe you guys know that the Surefire and Failsafe plugins were using
std/in and std/out (pipes) as interprocess communication between Maven
process and forked JVM.
Often the users, especially the OSGi users, claimed that these pipes should
be used by the tests.
Additionally, there was a request, from one of our users at GitHub, that
the Surefire fork VMs should be capable of distributing the load in
horizontal direction (hardware) which would first of all require a new
abstraction and communication facilities.
Today we are able to accomplish this!

We have introduced an abstraction which allows the users to implement their
own communication facilities for their purposes.
Of course, we provided two internal implementations.
One defaults to the traditional pipes, and the second is using TCP/IP
channels with authentication.
The second implementation is especially interesting because you can enable
a new way of communication using the TCP sockets:




The std/out and std/err would be ready for use in your tests.
One may ask, why we did not enable this TCP/IP channel by default.
We want to let the users adapt first and check it out.
Feel free to let us know about your findings.

This approach gave you a certain freedom. For instance you can configure
your extension.
In the future we may introduce "bindAddress" in SurefireForkNodeFactory but
this can be also done by the user:



192.168.10.15


In the references you can find the documentation to the Extension API and
SPI.
This may help you out on implementing your own extensions.

References:
https://github.com/apache/maven-surefire/blob/master/maven-surefire-plugin/src/site/apt/examples/process-communication.vm






On Sat, Jun 13, 2020 at 9:15 PM Enrico Olivelli  wrote:

> (I will cast my final vote on Monday)
> Tibor
> It is worth to note that this release includes the new communication
> protocol between Maven and the forked JVM.
> Can you please share a bit of help about how to try it?
>
> This is a great release of surefire, it is a big milestone for Maven and
> Surefire
>
>
> Enrico
>
> Il Sab 13 Giu 2020, 20:50 Michael Osipov  ha scritto:
>
> > Am 2020-06-13 um 15:46 schrieb Tibor Digana:
> > > Hi,
> > >
> > > We solved 40 issues:
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12344612
> > >
> > > There are still a couple of issues left in JIRA:
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC
> > >
> > > Staging repo:
> > > https://repository.apache.org/content/repositories/maven-1590/
> > >
> >
> https://repository.apache.org/content/repositories/maven-1590/org/apache/maven/surefire/surefire/3.0.0-M5/surefire-3.0.0-M5-source-release.zip
> > >
> > > Source release checksum(s):
> > > surefire-3.0.0-M5-source-release.zip  sha1:
> > > 687a89ceb4a1b2e5dd472deec8d3843f2a98b68f
> > > surefire-3.0.0-M5-source-release.zip  sha512:
> > >
> >
> e88ced058923b349acfe1948d4c4a7ff6f4bef08e5685f2f2ac73cfb26ad35fd6578f05309f091081f01986b19bbca38a2fe6bf0fbd16980cd6f41228c529ee7
> > >
> > > Staging site:
> > > http://maven.apache.org/surefire-archives/surefire-LATEST/
> > >
> > > Guide to testing staged releases:
> > > http://maven.apache.org/guides/development/guide-testing-releases.html
> > >
> > > Vote open for 72 hours.
> >
> > Massive and impressive!
> >
> > +1
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>

Re: [VOTE] Release Apache Maven Surefire Plugin version 3.0.0-M5

2020-06-13 Thread Hervé BOUTEMY 
+1

near full reproducibility of reference artifacts with JDK 8 on Windows: 48 
artifacts are ok, just 2 still have issues:
- surefire-3.0.0-M5-source-release.zip: I don't know why my local build added 3 
dependency-reduced-pom.xml that do not exist in reference build
- surefire-shadefire-3.0.0-M5.jar: some strange timestamp issues for some 
shaded content, probably a subtle maven-shade-plugin bug

Regards,

Hervé

Le samedi 13 juin 2020, 15:46:10 CEST Tibor Digana a écrit :
> Hi,
> 
> We solved 40 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927
> rsion=12344612
> 
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20
> status%20%3D%20Open%20ORDER%20BY%20priority%20DESC
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1590/
> https://repository.apache.org/content/repositories/maven-1590/org/apache/mav
> en/surefire/surefire/3.0.0-M5/surefire-3.0.0-M5-source-release.zip
> 
> Source release checksum(s):
> surefire-3.0.0-M5-source-release.zip  sha1:
> 687a89ceb4a1b2e5dd472deec8d3843f2a98b68f
> surefire-3.0.0-M5-source-release.zip  sha512:
> e88ced058923b349acfe1948d4c4a7ff6f4bef08e5685f2f2ac73cfb26ad35fd6578f05309f0
> 91081f01986b19bbca38a2fe6bf0fbd16980cd6f41228c529ee7
> 
> Staging site:
> http://maven.apache.org/surefire-archives/surefire-LATEST/
> 
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> Cheers
> Tibor





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

Re: [VOTE] Release Apache Maven Surefire Plugin version 3.0.0-M5

2020-06-13 Thread Enrico Olivelli 
(I will cast my final vote on Monday)
Tibor
It is worth to note that this release includes the new communication
protocol between Maven and the forked JVM.
Can you please share a bit of help about how to try it?

This is a great release of surefire, it is a big milestone for Maven and
Surefire


Enrico

Il Sab 13 Giu 2020, 20:50 Michael Osipov  ha scritto:

> Am 2020-06-13 um 15:46 schrieb Tibor Digana:
> > Hi,
> >
> > We solved 40 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12344612
> >
> > There are still a couple of issues left in JIRA:
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1590/
> >
> https://repository.apache.org/content/repositories/maven-1590/org/apache/maven/surefire/surefire/3.0.0-M5/surefire-3.0.0-M5-source-release.zip
> >
> > Source release checksum(s):
> > surefire-3.0.0-M5-source-release.zip  sha1:
> > 687a89ceb4a1b2e5dd472deec8d3843f2a98b68f
> > surefire-3.0.0-M5-source-release.zip  sha512:
> >
> e88ced058923b349acfe1948d4c4a7ff6f4bef08e5685f2f2ac73cfb26ad35fd6578f05309f091081f01986b19bbca38a2fe6bf0fbd16980cd6f41228c529ee7
> >
> > Staging site:
> > http://maven.apache.org/surefire-archives/surefire-LATEST/
> >
> > Guide to testing staged releases:
> > http://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for 72 hours.
>
> Massive and impressive!
>
> +1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Apache Maven Surefire Plugin version 3.0.0-M5

2020-06-13 Thread Michael Osipov 

Am 2020-06-13 um 15:46 schrieb Tibor Digana:

Hi,

We solved 40 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12344612

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

Staging repo:
https://repository.apache.org/content/repositories/maven-1590/
https://repository.apache.org/content/repositories/maven-1590/org/apache/maven/surefire/surefire/3.0.0-M5/surefire-3.0.0-M5-source-release.zip

Source release checksum(s):
surefire-3.0.0-M5-source-release.zip  sha1:
687a89ceb4a1b2e5dd472deec8d3843f2a98b68f
surefire-3.0.0-M5-source-release.zip  sha512:
e88ced058923b349acfe1948d4c4a7ff6f4bef08e5685f2f2ac73cfb26ad35fd6578f05309f091081f01986b19bbca38a2fe6bf0fbd16980cd6f41228c529ee7

Staging site:
http://maven.apache.org/surefire-archives/surefire-LATEST/

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

Vote open for 72 hours.


Massive and impressive!

+1

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

Re: Suggestion: announce Maven 3.0.x is EOL

2020-06-13 Thread Robert Scholte 
To me these are 2 different things.
Yes, we are going to require Maven 3.1 for our plugins (and because of API 
changes we need to be explicit about this), but that doesn't mean that Maven 
3.0.x itself is end of life.

Depending on how you ask the question, to me EOLs are either about majors or 
minors.
It is clear to me we won't do anything for Maven 2 anymore.
At the same time, I expect we will never do a 3.3.10 or 3.5.5.

I don't know what people expect by a statement about EOL: nobody has a support 
contract for Maven, so talking about EOL doesn't make any sense to me.
It all depends on what critical issue may appear, based on that we'll make our 
decision.
To me it is either: EOL for Maven2 and/or with every new release the previous 
will be marked as EOL.

Robert




On 13-6-2020 17:26:15, Elliotte Rusty Harold  wrote:
I think we've achieved consensus that Maven 3.0.x should no longer be
supported by new plugin releases and 3.1.x is our minimum. Assuming
that's true, this PR updates the history page to account for that:

https://github.com/apache/maven-site/pull/176

If anyone thinks we have not achieved consensus, or should not
announce that 3.0.x is end of life, please say so.

As always, please also comment on exact language of the PR, markup
syntax, and other pages that need to be updated. Thanks.

--
Elliotte Rusty Harold
elh...@ibiblio.org

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

Re: Suggestion: announce Maven 3.0.x is EOL

2020-06-13 Thread Tibor Digana 
Thx that you have made this.
yes, i also understood a general acceptance of this proposal.
let's push this soon.

On Sat, Jun 13, 2020 at 5:26 PM Elliotte Rusty Harold 
wrote:

> I think we've achieved consensus that Maven 3.0.x should no longer be
> supported by new plugin releases and 3.1.x is our minimum. Assuming
> that's true, this PR updates the history page to account for that:
>
> https://github.com/apache/maven-site/pull/176
>
> If anyone thinks we have not achieved consensus, or should not
> announce that 3.0.x is end of life, please say so.
>
> As always, please also comment on exact language of the PR, markup
> syntax, and other pages that need to be updated. Thanks.
>
> --
> Elliotte Rusty Harold
> elh...@ibiblio.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 Surefire Plugin version 3.0.0-M5

2020-06-13 Thread Romain Manni-Bucau 
Mainly just ran some sanity checks but looks ok, +1 (non binding)

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le sam. 13 juin 2020 à 15:46, Tibor Digana  a
écrit :

> Hi,
>
> We solved 40 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12344612
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1590/
>
> https://repository.apache.org/content/repositories/maven-1590/org/apache/maven/surefire/surefire/3.0.0-M5/surefire-3.0.0-M5-source-release.zip
>
> Source release checksum(s):
> surefire-3.0.0-M5-source-release.zip  sha1:
> 687a89ceb4a1b2e5dd472deec8d3843f2a98b68f
> surefire-3.0.0-M5-source-release.zip  sha512:
>
> e88ced058923b349acfe1948d4c4a7ff6f4bef08e5685f2f2ac73cfb26ad35fd6578f05309f091081f01986b19bbca38a2fe6bf0fbd16980cd6f41228c529ee7
>
> Staging site:
> http://maven.apache.org/surefire-archives/surefire-LATEST/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Cheers
> Tibor
>

[GitHub] [maven-site] Tibor17 commented on pull request #176: [MNGSITE-415] say Maven 3.0.x is EOL

2020-06-13 Thread GitBox 


Tibor17 commented on pull request #176:
URL: https://github.com/apache/maven-site/pull/176#issuecomment-643656541


   +1



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

Suggestion: announce Maven 3.0.x is EOL

2020-06-13 Thread Elliotte Rusty Harold 
I think we've achieved consensus that Maven 3.0.x should no longer be
supported by new plugin releases and 3.1.x is our minimum. Assuming
that's true, this PR updates the history page to account for that:

https://github.com/apache/maven-site/pull/176

If anyone thinks we have not achieved consensus, or should not
announce that 3.0.x is end of life, please say so.

As always, please also comment on exact language of the PR, markup
syntax, and other pages that need to be updated. Thanks.

-- 
Elliotte Rusty Harold
elh...@ibiblio.org

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

[GitHub] [maven-site] elharo opened a new pull request #176: [MNGSITE-415] say Maven 3.0.x is EOL

2020-06-13 Thread GitBox 


elharo opened a new pull request #176:
URL: https://github.com/apache/maven-site/pull/176


   Pushed for discussion



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

[VOTE] Release Apache Maven Surefire Plugin version 3.0.0-M5

2020-06-13 Thread Tibor Digana 
Hi,

We solved 40 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12344612

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

Staging repo:
https://repository.apache.org/content/repositories/maven-1590/
https://repository.apache.org/content/repositories/maven-1590/org/apache/maven/surefire/surefire/3.0.0-M5/surefire-3.0.0-M5-source-release.zip

Source release checksum(s):
surefire-3.0.0-M5-source-release.zip  sha1:
687a89ceb4a1b2e5dd472deec8d3843f2a98b68f
surefire-3.0.0-M5-source-release.zip  sha512:
e88ced058923b349acfe1948d4c4a7ff6f4bef08e5685f2f2ac73cfb26ad35fd6578f05309f091081f01986b19bbca38a2fe6bf0fbd16980cd6f41228c529ee7

Staging site:
http://maven.apache.org/surefire-archives/surefire-LATEST/

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

Vote open for 72 hours.

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

Cheers
Tibor

List of public pgp key servers

2020-06-13 Thread Slawomir Jaranowski 
Hi,

Are there any informations / documentations / recommendations which key
servers should be used to publish public key.

On site
https://maven.apache.org/repository/guide-central-repository-upload.html#pgp-signature
we have "like" http://pgp.mit.edu/
and on site
https://central.sonatype.org/pages/working-with-pgp-signatures.html#distributing-your-public-key
we have example with hkp://pool.sks-keyservers.net

I also asked Sonatype about it - and I'm waiting for a response.

-- 
Sławomir Jaranowski

Re: Maven Plugin Tests Need maven-compat to Run

2020-06-13 Thread Robert Scholte 
That's a known issue, see 
https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies

Giving it the test-scope is acceptable.

thanks,
Robert

On 13-6-2020 01:56:46, Ian Lavallee  wrote:
Hi all,

I am working on getting a dependencyGraphBuilder working in its own project
with up to date dependencies (maven-resolver-api etc) as I was having a lot
of issues with some of the older code when trying to update the
dependency-plugin directly.

I used maven-plugin-testing-harness to test the plugin per
https://maven.apache.org/plugin-developers/plugin-testing.html but the test
fails unless I use maven-compat which I should avoid per
http://maven.apache.org/ref/3.6.3/maven-compat/. I've tried reading the
documentation but can't find a solution other than maven-compat. Is there a
better or newer way to test this so I can avoid maven-compat?

Github for project:
https://github.com/GoogleCloudPlatform/cloud-opensource-java/tree/DependencyGraphBuilderMojo/verboseTree-maven-plugin
(branch is DependencyGraphBuilderMojo)

Note this repo has many projects but everything is in reference to
verboseTree-maven-plugin

Any help/documentation links are greatly appreciated,
Ian