Re: Prepared Maven 3.5.3 Release Notes

[Stephen Connolly]

Thanks for writing these up... I was going to do it today, but you saved me
the work!

On Sat 24 Feb 2018 at 20:47, Karl Heinz Marbaise  wrote:

> Hi to all,
>
> I have prepared Maven 3.5.3 Release notes.
>
> You can take a look here:
>
>
> https://github.com/khmarbaise/maven-release-notes/blob/master/content/markdown/docs/3.5.3/release-notes.md
>
> If you have improvements/ideas/supplementals etc. don't hesitate to
> contact me or make a PR...
>
> Kind regards
> Karl Heinz Marbaise
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --
Sent from my phone

Re: Surefire roadmap

[Tibor Digana]

Hello Olivier, Robert,

I think this issue you saw was caused by the old hack with commons-lang3 in
module surefire-booter/pom.xml.
I reproduced it on WindowsXP but not on Windows7, funny.
I removed the change in the pom.xml and committed (git push force) to our
branch SUREFIRE-1489. Now the branch SUREFIRE-1489 contains changes from
three JIRAs, but that's ok, we will create new ones according to Jiras.
I run this command:

mvn clean install -P run-its -Dintegration-test-port=8000
-Dintegration-test-stop-port=8001 "-Djdk.home=d:\Program
Files\Java\jdk10" -Djacoco.skip=true

I am overriding the branch, so it is better to clone it fresh.

Please let me know if it is fine on your side.

With Best Regards,
Tibor




On Sun, Feb 25, 2018 at 2:51 AM, Tibor Digana 
wrote:

> Try to delete local maven repository on Travis and run the branch
> SUREFIRE-1489 with --no-snapshot-updates.
> I hope we will have good results.
> Good night!
>
> On Sun, Feb 25, 2018 at 2:34 AM, Tibor Digana 
> wrote:
>
>> What branch is for the build /maven-surefire-fs?
>> Any special build configuration or sources are different from master?
>>
>> On Sun, Feb 25, 2018 at 2:28 AM, Olivier Lamy  wrote:
>>
>>> Did you read my emails? The thread with subject " [3/3] maven-surefire
>>> git
>>> commit: Revert "[SUREFIRE-1473] upgrade commons-lang3 to avoid NPE on
>>> jdk10" "
>>> I assume no so here few links
>>> https://builds.apache.org/view/M-R/view/Maven/job/maven-
>>> surefire-fs/2/console
>>> https://jenkins.webtide.net/job/sandbox/job/surefire-master-
>>> jdk8/4/console
>>> https://travis-ci.org/olamy/maven-surefire/builds/345611495
>>>
>>> There are all Jenkins or Travis builds with an empty maven repo.
>>>
>>>
>>>
>>> On 25 February 2018 at 11:11, Tibor Digana 
>>> wrote:
>>>
>>> > Hi Olivier,
>>> >
>>> > I am trying to be friendly and helpful.
>>> >
>>> > Maybe a hint:
>>> > One problem I found weeks ago was in Maven Central which contained a
>>> > SNAPSHOT version built with Java 1.7.
>>> > I had to do this on my PC:
>>> > $ mvn
>>> > org.codehaus.mojo:build-helper-maven-plugin:3.0.0:remove-pro
>>> ject-artifact
>>> > -Dbuildhelper.failOnError=false
>>> > $ mvn install *-nsu*
>>> > and try with JAVA_HOME=JDK 1.8 for first time and then with
>>> jdk.home=...
>>> > with other JDKs.
>>> >
>>> > I remember your mail and the stacktrace with commons-lang3-3.5.jar but
>>> I
>>> > could not reproduce identical symptoms on my PC and Jenkins lately.
>>> > Therefore I have opened the master log [1] and I do not see that
>>> stacktrace
>>> > you had before.
>>> > I am building locally and on Jenkins almost every day but the issue
>>> with
>>> > calling commons-lang3 has not occurred, sorry.
>>> >
>>>
>>> See above. Maybe it's "it fail on my machine" or "it works on my machine"
>>> BUT I have produced a lot of evidences there is a problem so please do
>>> not
>>> ignore that
>>>
>>>
>>> >
>>> > I would like to help you but I do not know what's going on your PC.
>>> Maybe
>>> > on Sunday we should talk on IRC, I am open for that.
>>>
>>>
>>> > Not everyone can do whatever. Everybody has to open a branch with a
>>> name of
>>> > Jira, kindly ask the developers to talk about long term concept, to
>>> make a
>>> > code-review and wait for a response. We are not always available and
>>> > therefore we have to wait for someone else and sometimes we have to
>>> find a
>>> > person in commit list, go to the developer, track her/him on e-mail and
>>> > IRC.
>>> > But I would prefer IRC during the day or evening.
>>> >
>>>
>>> I don't think irc is a good place for decisions as it's limited number of
>>> participants.
>>> I see our project as a community and not as a limited number of people
>>> who
>>> can be on irc at a certain time.
>>> Mailing list are the basis of how Apache projects works because you have
>>> history (you can search), async response mode etc...
>>>
>>> Anyway I asked here fro having master jdk7 minimum with bumping version
>>> to
>>> 3.0.0.
>>> we can have a maintenance branch 2.x
>>> But let's move forward before jdk7 get deprecated (oh oops it's already
>>> the
>>> case).
>>> Joke apart. I really want a release supporting jdk10 at least something
>>> not
>>> failing with CNFE
>>>
>>>
>>> >
>>> > [1]:
>>> > https://builds.apache.org/job/maven-wip/job/maven-surefire/
>>> > job/master/20/consoleFull
>>> >
>>> > Cheers
>>> > Tibor
>>> >
>>> >
>>> >
>>> >
>>> > On Sun, Feb 25, 2018 at 12:47 AM, Olivier Lamy 
>>> wrote:
>>> >
>>> > > Please Tibor read the emails and I'm so sorry to repeat again myself
>>> but
>>> > > it looks you do not listen anyone...
>>> > > MASTER DOESN'T BUILD!!!
>>> > > using jdk7 or jdk8 or jdk9 or jdk10
>>> > > I send few links with failure and as far as I can understand from the
>>> > > thread neither Robert can build it!!
>>> > > We must first fix that!!!
>>> > >
>>> > >
>>> > > On 25 February 2018 at 

Re: Surefire roadmap

[Tibor Digana]

Try to delete local maven repository on Travis and run the branch
SUREFIRE-1489 with --no-snapshot-updates.
I hope we will have good results.
Good night!

On Sun, Feb 25, 2018 at 2:34 AM, Tibor Digana 
wrote:

> What branch is for the build /maven-surefire-fs?
> Any special build configuration or sources are different from master?
>
> On Sun, Feb 25, 2018 at 2:28 AM, Olivier Lamy  wrote:
>
>> Did you read my emails? The thread with subject " [3/3] maven-surefire git
>> commit: Revert "[SUREFIRE-1473] upgrade commons-lang3 to avoid NPE on
>> jdk10" "
>> I assume no so here few links
>> https://builds.apache.org/view/M-R/view/Maven/job/maven-
>> surefire-fs/2/console
>> https://jenkins.webtide.net/job/sandbox/job/surefire-master-
>> jdk8/4/console
>> https://travis-ci.org/olamy/maven-surefire/builds/345611495
>>
>> There are all Jenkins or Travis builds with an empty maven repo.
>>
>>
>>
>> On 25 February 2018 at 11:11, Tibor Digana 
>> wrote:
>>
>> > Hi Olivier,
>> >
>> > I am trying to be friendly and helpful.
>> >
>> > Maybe a hint:
>> > One problem I found weeks ago was in Maven Central which contained a
>> > SNAPSHOT version built with Java 1.7.
>> > I had to do this on my PC:
>> > $ mvn
>> > org.codehaus.mojo:build-helper-maven-plugin:3.0.0:remove-
>> project-artifact
>> > -Dbuildhelper.failOnError=false
>> > $ mvn install *-nsu*
>> > and try with JAVA_HOME=JDK 1.8 for first time and then with jdk.home=...
>> > with other JDKs.
>> >
>> > I remember your mail and the stacktrace with commons-lang3-3.5.jar but I
>> > could not reproduce identical symptoms on my PC and Jenkins lately.
>> > Therefore I have opened the master log [1] and I do not see that
>> stacktrace
>> > you had before.
>> > I am building locally and on Jenkins almost every day but the issue with
>> > calling commons-lang3 has not occurred, sorry.
>> >
>>
>> See above. Maybe it's "it fail on my machine" or "it works on my machine"
>> BUT I have produced a lot of evidences there is a problem so please do not
>> ignore that
>>
>>
>> >
>> > I would like to help you but I do not know what's going on your PC.
>> Maybe
>> > on Sunday we should talk on IRC, I am open for that.
>>
>>
>> > Not everyone can do whatever. Everybody has to open a branch with a
>> name of
>> > Jira, kindly ask the developers to talk about long term concept, to
>> make a
>> > code-review and wait for a response. We are not always available and
>> > therefore we have to wait for someone else and sometimes we have to
>> find a
>> > person in commit list, go to the developer, track her/him on e-mail and
>> > IRC.
>> > But I would prefer IRC during the day or evening.
>> >
>>
>> I don't think irc is a good place for decisions as it's limited number of
>> participants.
>> I see our project as a community and not as a limited number of people who
>> can be on irc at a certain time.
>> Mailing list are the basis of how Apache projects works because you have
>> history (you can search), async response mode etc...
>>
>> Anyway I asked here fro having master jdk7 minimum with bumping version to
>> 3.0.0.
>> we can have a maintenance branch 2.x
>> But let's move forward before jdk7 get deprecated (oh oops it's already
>> the
>> case).
>> Joke apart. I really want a release supporting jdk10 at least something
>> not
>> failing with CNFE
>>
>>
>> >
>> > [1]:
>> > https://builds.apache.org/job/maven-wip/job/maven-surefire/
>> > job/master/20/consoleFull
>> >
>> > Cheers
>> > Tibor
>> >
>> >
>> >
>> >
>> > On Sun, Feb 25, 2018 at 12:47 AM, Olivier Lamy 
>> wrote:
>> >
>> > > Please Tibor read the emails and I'm so sorry to repeat again myself
>> but
>> > > it looks you do not listen anyone...
>> > > MASTER DOESN'T BUILD!!!
>> > > using jdk7 or jdk8 or jdk9 or jdk10
>> > > I send few links with failure and as far as I can understand from the
>> > > thread neither Robert can build it!!
>> > > We must first fix that!!!
>> > >
>> > >
>> > > On 25 February 2018 at 09:17, Tibor Digana 
>> > wrote:
>> > >
>> > >> Sorry, I have to repeat myself because of undelivered message(s) to
>> > Maven
>> > >> mailing list.
>> > >>
>> > >> For clarifying the Surefire goes with Java 6. If you want to run your
>> > >> tests with JDK10 or lower you have to specify the system property
>> > >> -Djdk.home=/path/to/jdk10 and the you will see that the tests pass.
>> Go
>> > to
>> > >> target/surefire-reports and failsafe-reports and target/it/** and
>> check
>> > the
>> > >> "java.home" and you will see your /path/to/jdk10.
>> > >>
>> > >
>> > >
>> > > I KNOW HOW IT WORKS AND AGAIN MY POINT IS whenever jdk you use MASTER
>> > > DOESN'T BUILD!!
>> > >
>> > >
>> > >> One more remark I got the Jenkins working [1]. The whole problem was
>> > with
>> > >> the call withMaven() in Jenkinsfile. After I switched back to
>> withEnv()
>> > the
>> > >> logs, InterruptedException has gone!
>> > >> I reported 

Re: Surefire roadmap

[Tibor Digana]

What branch is for the build /maven-surefire-fs?
Any special build configuration or sources are different from master?

On Sun, Feb 25, 2018 at 2:28 AM, Olivier Lamy  wrote:

> Did you read my emails? The thread with subject " [3/3] maven-surefire git
> commit: Revert "[SUREFIRE-1473] upgrade commons-lang3 to avoid NPE on
> jdk10" "
> I assume no so here few links
> https://builds.apache.org/view/M-R/view/Maven/job/maven-
> surefire-fs/2/console
> https://jenkins.webtide.net/job/sandbox/job/surefire-master-jdk8/4/console
> https://travis-ci.org/olamy/maven-surefire/builds/345611495
>
> There are all Jenkins or Travis builds with an empty maven repo.
>
>
>
> On 25 February 2018 at 11:11, Tibor Digana  wrote:
>
> > Hi Olivier,
> >
> > I am trying to be friendly and helpful.
> >
> > Maybe a hint:
> > One problem I found weeks ago was in Maven Central which contained a
> > SNAPSHOT version built with Java 1.7.
> > I had to do this on my PC:
> > $ mvn
> > org.codehaus.mojo:build-helper-maven-plugin:3.0.0:
> remove-project-artifact
> > -Dbuildhelper.failOnError=false
> > $ mvn install *-nsu*
> > and try with JAVA_HOME=JDK 1.8 for first time and then with jdk.home=...
> > with other JDKs.
> >
> > I remember your mail and the stacktrace with commons-lang3-3.5.jar but I
> > could not reproduce identical symptoms on my PC and Jenkins lately.
> > Therefore I have opened the master log [1] and I do not see that
> stacktrace
> > you had before.
> > I am building locally and on Jenkins almost every day but the issue with
> > calling commons-lang3 has not occurred, sorry.
> >
>
> See above. Maybe it's "it fail on my machine" or "it works on my machine"
> BUT I have produced a lot of evidences there is a problem so please do not
> ignore that
>
>
> >
> > I would like to help you but I do not know what's going on your PC. Maybe
> > on Sunday we should talk on IRC, I am open for that.
>
>
> > Not everyone can do whatever. Everybody has to open a branch with a name
> of
> > Jira, kindly ask the developers to talk about long term concept, to make
> a
> > code-review and wait for a response. We are not always available and
> > therefore we have to wait for someone else and sometimes we have to find
> a
> > person in commit list, go to the developer, track her/him on e-mail and
> > IRC.
> > But I would prefer IRC during the day or evening.
> >
>
> I don't think irc is a good place for decisions as it's limited number of
> participants.
> I see our project as a community and not as a limited number of people who
> can be on irc at a certain time.
> Mailing list are the basis of how Apache projects works because you have
> history (you can search), async response mode etc...
>
> Anyway I asked here fro having master jdk7 minimum with bumping version to
> 3.0.0.
> we can have a maintenance branch 2.x
> But let's move forward before jdk7 get deprecated (oh oops it's already the
> case).
> Joke apart. I really want a release supporting jdk10 at least something not
> failing with CNFE
>
>
> >
> > [1]:
> > https://builds.apache.org/job/maven-wip/job/maven-surefire/
> > job/master/20/consoleFull
> >
> > Cheers
> > Tibor
> >
> >
> >
> >
> > On Sun, Feb 25, 2018 at 12:47 AM, Olivier Lamy  wrote:
> >
> > > Please Tibor read the emails and I'm so sorry to repeat again myself
> but
> > > it looks you do not listen anyone...
> > > MASTER DOESN'T BUILD!!!
> > > using jdk7 or jdk8 or jdk9 or jdk10
> > > I send few links with failure and as far as I can understand from the
> > > thread neither Robert can build it!!
> > > We must first fix that!!!
> > >
> > >
> > > On 25 February 2018 at 09:17, Tibor Digana 
> > wrote:
> > >
> > >> Sorry, I have to repeat myself because of undelivered message(s) to
> > Maven
> > >> mailing list.
> > >>
> > >> For clarifying the Surefire goes with Java 6. If you want to run your
> > >> tests with JDK10 or lower you have to specify the system property
> > >> -Djdk.home=/path/to/jdk10 and the you will see that the tests pass. Go
> > to
> > >> target/surefire-reports and failsafe-reports and target/it/** and
> check
> > the
> > >> "java.home" and you will see your /path/to/jdk10.
> > >>
> > >
> > >
> > > I KNOW HOW IT WORKS AND AGAIN MY POINT IS whenever jdk you use MASTER
> > > DOESN'T BUILD!!
> > >
> > >
> > >> One more remark I got the Jenkins working [1]. The whole problem was
> > with
> > >> the call withMaven() in Jenkinsfile. After I switched back to
> withEnv()
> > the
> > >> logs, InterruptedException has gone!
> > >> I reported several improvements that Olivier did not like to improve
> but
> > >> I think there is no any significant showstopper for 2.21.0.
> > >>
> > >
> > > I have no idea what you're talking about? Do you have any email threads
> > or
> > > jira where I say that?
> > >
> > >
> > >> I will now talk about the Jiras improvements with Olivier in GitHub
> and
> > I
> > >> hope we will make the release 

Re: Surefire roadmap

[Tibor Digana]

Hi Robert, Olivier,

Finally I am happy that the build #15 [1] passed successfully in the branch
surefire-1498.
I am open to help you building the project on your PC.
I will connect to IRC in the evening or afternoon.

[1]:
https://builds.apache.org/job/maven-wip/job/maven-surefire/job/SUREFIRE-1489/

Cheers
Tibor


On Sun, Feb 25, 2018 at 2:11 AM, Tibor Digana 
wrote:

> Hi Olivier,
>
> I am trying to be friendly and helpful.
>
> Maybe a hint:
> One problem I found weeks ago was in Maven Central which contained a
> SNAPSHOT version built with Java 1.7.
> I had to do this on my PC:
> $ mvn 
> org.codehaus.mojo:build-helper-maven-plugin:3.0.0:remove-project-artifact
> -Dbuildhelper.failOnError=false
> $ mvn install *-nsu*
> and try with JAVA_HOME=JDK 1.8 for first time and then with jdk.home=...
> with other JDKs.
>
> I remember your mail and the stacktrace with commons-lang3-3.5.jar but I
> could not reproduce identical symptoms on my PC and Jenkins lately.
> Therefore I have opened the master log [1] and I do not see that
> stacktrace you had before.
> I am building locally and on Jenkins almost every day but the issue with
> calling commons-lang3 has not occurred, sorry.
>
> I would like to help you but I do not know what's going on your PC. Maybe
> on Sunday we should talk on IRC, I am open for that.
>
> Not everyone can do whatever. Everybody has to open a branch with a name
> of Jira, kindly ask the developers to talk about long term concept, to make
> a code-review and wait for a response. We are not always available and
> therefore we have to wait for someone else and sometimes we have to find a
> person in commit list, go to the developer, track her/him on e-mail and IRC.
> But I would prefer IRC during the day or evening.
>
> [1]: https://builds.apache.org/job/maven-wip/job/maven-surefire/
> job/master/20/consoleFull
>
> Cheers
> Tibor
>
>
>
>
> On Sun, Feb 25, 2018 at 12:47 AM, Olivier Lamy  wrote:
>
>> Please Tibor read the emails and I'm so sorry to repeat again myself but
>> it looks you do not listen anyone...
>> MASTER DOESN'T BUILD!!!
>> using jdk7 or jdk8 or jdk9 or jdk10
>> I send few links with failure and as far as I can understand from the
>> thread neither Robert can build it!!
>> We must first fix that!!!
>>
>>
>> On 25 February 2018 at 09:17, Tibor Digana 
>> wrote:
>>
>>> Sorry, I have to repeat myself because of undelivered message(s) to
>>> Maven mailing list.
>>>
>>> For clarifying the Surefire goes with Java 6. If you want to run your
>>> tests with JDK10 or lower you have to specify the system property
>>> -Djdk.home=/path/to/jdk10 and the you will see that the tests pass. Go to
>>> target/surefire-reports and failsafe-reports and target/it/** and check the
>>> "java.home" and you will see your /path/to/jdk10.
>>>
>>
>>
>> I KNOW HOW IT WORKS AND AGAIN MY POINT IS whenever jdk you use MASTER
>> DOESN'T BUILD!!
>>
>>
>>> One more remark I got the Jenkins working [1]. The whole problem was
>>> with the call withMaven() in Jenkinsfile. After I switched back to
>>> withEnv() the logs, InterruptedException has gone!
>>> I reported several improvements that Olivier did not like to improve but
>>> I think there is no any significant showstopper for 2.21.0.
>>>
>>
>> I have no idea what you're talking about? Do you have any email threads
>> or jira where I say that?
>>
>>
>>> I will now talk about the Jiras improvements with Olivier in GitHub and
>>> I hope we will make the release soon!
>>>
>>> I still do not understand what codeline you run and why you have
>>> problems with runtime if I did not have several months and I tested with
>>> JDK8 u162, u132, u121.
>>> Please post a link to your codeline because I highly doubt that you are
>>> testing the identical code with me!
>>>
>>
>> PLEASE READ ALL THE PREVIOUS EMAIL I SENT WITH BUILD FAILURE ON PUBLIC
>> JENKINS
>>
>>
>>>
>>> [1]: https://builds.apache.org/job/maven-wip/job/maven-surefire/j
>>> ob/SUREFIRE-1489/
>>>
>>> For better clarification 2.21.0 is using modulepath - we have
>>> integration test for Jigsaw modularity and modulepath is activated for JDK
>>> 9+.
>>> NPE was fixed in 2.21.0 - check the release notes.
>>> We are no more calling the problematic method from commons-lang3 which
>>> caused NPE. This does not require any upgrade of commons-lang3 till 3.0.0.
>>> Please follow the build [1].
>>>
>>> Cheers
>>> Tibor
>>>
>>>
>>> On Sat, Feb 24, 2018 at 3:22 PM, Robert Scholte 
>>> wrote:
>>>
 Hi,

 I've noticed some unsatisfying discussions regarding surefire, so let
 me try to help moving this forward.

>>>
>> I'm just not happy about how people do not listen neither read emails
>> Emails is the primary way of working at Apache because of different
>> timezone etc...
>> IRC is just a volatile dicussion channel when you disconnect you cannot
>> read history, later reply from someone (perso I often shutdown my 

Re: Surefire roadmap

[Olivier Lamy]

Did you read my emails? The thread with subject " [3/3] maven-surefire git
commit: Revert "[SUREFIRE-1473] upgrade commons-lang3 to avoid NPE on
jdk10" "
I assume no so here few links
https://builds.apache.org/view/M-R/view/Maven/job/maven-
surefire-fs/2/console
https://jenkins.webtide.net/job/sandbox/job/surefire-master-jdk8/4/console
https://travis-ci.org/olamy/maven-surefire/builds/345611495

There are all Jenkins or Travis builds with an empty maven repo.



On 25 February 2018 at 11:11, Tibor Digana  wrote:

> Hi Olivier,
>
> I am trying to be friendly and helpful.
>
> Maybe a hint:
> One problem I found weeks ago was in Maven Central which contained a
> SNAPSHOT version built with Java 1.7.
> I had to do this on my PC:
> $ mvn
> org.codehaus.mojo:build-helper-maven-plugin:3.0.0:remove-project-artifact
> -Dbuildhelper.failOnError=false
> $ mvn install *-nsu*
> and try with JAVA_HOME=JDK 1.8 for first time and then with jdk.home=...
> with other JDKs.
>
> I remember your mail and the stacktrace with commons-lang3-3.5.jar but I
> could not reproduce identical symptoms on my PC and Jenkins lately.
> Therefore I have opened the master log [1] and I do not see that stacktrace
> you had before.
> I am building locally and on Jenkins almost every day but the issue with
> calling commons-lang3 has not occurred, sorry.
>

See above. Maybe it's "it fail on my machine" or "it works on my machine"
BUT I have produced a lot of evidences there is a problem so please do not
ignore that


>
> I would like to help you but I do not know what's going on your PC. Maybe
> on Sunday we should talk on IRC, I am open for that.


> Not everyone can do whatever. Everybody has to open a branch with a name of
> Jira, kindly ask the developers to talk about long term concept, to make a
> code-review and wait for a response. We are not always available and
> therefore we have to wait for someone else and sometimes we have to find a
> person in commit list, go to the developer, track her/him on e-mail and
> IRC.
> But I would prefer IRC during the day or evening.
>

I don't think irc is a good place for decisions as it's limited number of
participants.
I see our project as a community and not as a limited number of people who
can be on irc at a certain time.
Mailing list are the basis of how Apache projects works because you have
history (you can search), async response mode etc...

Anyway I asked here fro having master jdk7 minimum with bumping version to
3.0.0.
we can have a maintenance branch 2.x
But let's move forward before jdk7 get deprecated (oh oops it's already the
case).
Joke apart. I really want a release supporting jdk10 at least something not
failing with CNFE


>
> [1]:
> https://builds.apache.org/job/maven-wip/job/maven-surefire/
> job/master/20/consoleFull
>
> Cheers
> Tibor
>
>
>
>
> On Sun, Feb 25, 2018 at 12:47 AM, Olivier Lamy  wrote:
>
> > Please Tibor read the emails and I'm so sorry to repeat again myself but
> > it looks you do not listen anyone...
> > MASTER DOESN'T BUILD!!!
> > using jdk7 or jdk8 or jdk9 or jdk10
> > I send few links with failure and as far as I can understand from the
> > thread neither Robert can build it!!
> > We must first fix that!!!
> >
> >
> > On 25 February 2018 at 09:17, Tibor Digana 
> wrote:
> >
> >> Sorry, I have to repeat myself because of undelivered message(s) to
> Maven
> >> mailing list.
> >>
> >> For clarifying the Surefire goes with Java 6. If you want to run your
> >> tests with JDK10 or lower you have to specify the system property
> >> -Djdk.home=/path/to/jdk10 and the you will see that the tests pass. Go
> to
> >> target/surefire-reports and failsafe-reports and target/it/** and check
> the
> >> "java.home" and you will see your /path/to/jdk10.
> >>
> >
> >
> > I KNOW HOW IT WORKS AND AGAIN MY POINT IS whenever jdk you use MASTER
> > DOESN'T BUILD!!
> >
> >
> >> One more remark I got the Jenkins working [1]. The whole problem was
> with
> >> the call withMaven() in Jenkinsfile. After I switched back to withEnv()
> the
> >> logs, InterruptedException has gone!
> >> I reported several improvements that Olivier did not like to improve but
> >> I think there is no any significant showstopper for 2.21.0.
> >>
> >
> > I have no idea what you're talking about? Do you have any email threads
> or
> > jira where I say that?
> >
> >
> >> I will now talk about the Jiras improvements with Olivier in GitHub and
> I
> >> hope we will make the release soon!
> >>
> >> I still do not understand what codeline you run and why you have
> problems
> >> with runtime if I did not have several months and I tested with JDK8
> u162,
> >> u132, u121.
> >> Please post a link to your codeline because I highly doubt that you are
> >> testing the identical code with me!
> >>
> >
> > PLEASE READ ALL THE PREVIOUS EMAIL I SENT WITH BUILD FAILURE ON PUBLIC
> > JENKINS
> >
> >
> >>
> >> [1]: 

Re: Surefire roadmap

[Tibor Digana]

Hi Olivier,

I am trying to be friendly and helpful.

Maybe a hint:
One problem I found weeks ago was in Maven Central which contained a
SNAPSHOT version built with Java 1.7.
I had to do this on my PC:
$ mvn
org.codehaus.mojo:build-helper-maven-plugin:3.0.0:remove-project-artifact
-Dbuildhelper.failOnError=false
$ mvn install *-nsu*
and try with JAVA_HOME=JDK 1.8 for first time and then with jdk.home=...
with other JDKs.

I remember your mail and the stacktrace with commons-lang3-3.5.jar but I
could not reproduce identical symptoms on my PC and Jenkins lately.
Therefore I have opened the master log [1] and I do not see that stacktrace
you had before.
I am building locally and on Jenkins almost every day but the issue with
calling commons-lang3 has not occurred, sorry.

I would like to help you but I do not know what's going on your PC. Maybe
on Sunday we should talk on IRC, I am open for that.

Not everyone can do whatever. Everybody has to open a branch with a name of
Jira, kindly ask the developers to talk about long term concept, to make a
code-review and wait for a response. We are not always available and
therefore we have to wait for someone else and sometimes we have to find a
person in commit list, go to the developer, track her/him on e-mail and IRC.
But I would prefer IRC during the day or evening.

[1]:
https://builds.apache.org/job/maven-wip/job/maven-surefire/job/master/20/consoleFull

Cheers
Tibor




On Sun, Feb 25, 2018 at 12:47 AM, Olivier Lamy  wrote:

> Please Tibor read the emails and I'm so sorry to repeat again myself but
> it looks you do not listen anyone...
> MASTER DOESN'T BUILD!!!
> using jdk7 or jdk8 or jdk9 or jdk10
> I send few links with failure and as far as I can understand from the
> thread neither Robert can build it!!
> We must first fix that!!!
>
>
> On 25 February 2018 at 09:17, Tibor Digana  wrote:
>
>> Sorry, I have to repeat myself because of undelivered message(s) to Maven
>> mailing list.
>>
>> For clarifying the Surefire goes with Java 6. If you want to run your
>> tests with JDK10 or lower you have to specify the system property
>> -Djdk.home=/path/to/jdk10 and the you will see that the tests pass. Go to
>> target/surefire-reports and failsafe-reports and target/it/** and check the
>> "java.home" and you will see your /path/to/jdk10.
>>
>
>
> I KNOW HOW IT WORKS AND AGAIN MY POINT IS whenever jdk you use MASTER
> DOESN'T BUILD!!
>
>
>> One more remark I got the Jenkins working [1]. The whole problem was with
>> the call withMaven() in Jenkinsfile. After I switched back to withEnv() the
>> logs, InterruptedException has gone!
>> I reported several improvements that Olivier did not like to improve but
>> I think there is no any significant showstopper for 2.21.0.
>>
>
> I have no idea what you're talking about? Do you have any email threads or
> jira where I say that?
>
>
>> I will now talk about the Jiras improvements with Olivier in GitHub and I
>> hope we will make the release soon!
>>
>> I still do not understand what codeline you run and why you have problems
>> with runtime if I did not have several months and I tested with JDK8 u162,
>> u132, u121.
>> Please post a link to your codeline because I highly doubt that you are
>> testing the identical code with me!
>>
>
> PLEASE READ ALL THE PREVIOUS EMAIL I SENT WITH BUILD FAILURE ON PUBLIC
> JENKINS
>
>
>>
>> [1]: https://builds.apache.org/job/maven-wip/job/maven-surefire/j
>> ob/SUREFIRE-1489/
>>
>> For better clarification 2.21.0 is using modulepath - we have integration
>> test for Jigsaw modularity and modulepath is activated for JDK 9+.
>> NPE was fixed in 2.21.0 - check the release notes.
>> We are no more calling the problematic method from commons-lang3 which
>> caused NPE. This does not require any upgrade of commons-lang3 till 3.0.0.
>> Please follow the build [1].
>>
>> Cheers
>> Tibor
>>
>>
>> On Sat, Feb 24, 2018 at 3:22 PM, Robert Scholte 
>> wrote:
>>
>>> Hi,
>>>
>>> I've noticed some unsatisfying discussions regarding surefire, so let me
>>> try to help moving this forward.
>>>
>>
> I'm just not happy about how people do not listen neither read emails
> Emails is the primary way of working at Apache because of different
> timezone etc...
> IRC is just a volatile dicussion channel when you disconnect you cannot
> read history, later reply from someone (perso I often shutdown my laptop)
>
>
>>
>>> Here's the situation as I see it:
>>> - Surefire 2.20.1 is the latest released version (2017-09-15)
>>>
>>> - 2.20.1 doesn't use the modulepath yet, that will be part of the next
>>> release. A lot of people are waiting for this even before the official
>>> release of JDK9.
>>>
>>> - Surefire 2.x is is still JDK 1.6 compatible, the requirement of JDK
>>> 1.7 is planned for surefire 3.0.0
>>>
>>
> I'm fine with that so we can have a branch 2.x with jdk6 compatible
> And master 3.0.0 with jdk7 requirement.
> Does it sound reasonnable?
>

Re: Surefire roadmap

[Olivier Lamy]

Please Tibor read the emails and I'm so sorry to repeat again myself but it
looks you do not listen anyone...
MASTER DOESN'T BUILD!!!
using jdk7 or jdk8 or jdk9 or jdk10
I send few links with failure and as far as I can understand from the
thread neither Robert can build it!!
We must first fix that!!!


On 25 February 2018 at 09:17, Tibor Digana  wrote:

> Sorry, I have to repeat myself because of undelivered message(s) to Maven
> mailing list.
>
> For clarifying the Surefire goes with Java 6. If you want to run your
> tests with JDK10 or lower you have to specify the system property
> -Djdk.home=/path/to/jdk10 and the you will see that the tests pass. Go to
> target/surefire-reports and failsafe-reports and target/it/** and check the
> "java.home" and you will see your /path/to/jdk10.
>


I KNOW HOW IT WORKS AND AGAIN MY POINT IS whenever jdk you use MASTER
DOESN'T BUILD!!


> One more remark I got the Jenkins working [1]. The whole problem was with
> the call withMaven() in Jenkinsfile. After I switched back to withEnv() the
> logs, InterruptedException has gone!
> I reported several improvements that Olivier did not like to improve but I
> think there is no any significant showstopper for 2.21.0.
>

I have no idea what you're talking about? Do you have any email threads or
jira where I say that?


> I will now talk about the Jiras improvements with Olivier in GitHub and I
> hope we will make the release soon!
>
> I still do not understand what codeline you run and why you have problems
> with runtime if I did not have several months and I tested with JDK8 u162,
> u132, u121.
> Please post a link to your codeline because I highly doubt that you are
> testing the identical code with me!
>

PLEASE READ ALL THE PREVIOUS EMAIL I SENT WITH BUILD FAILURE ON PUBLIC
JENKINS


>
> [1]: https://builds.apache.org/job/maven-wip/job/maven-surefire/j
> ob/SUREFIRE-1489/
>
> For better clarification 2.21.0 is using modulepath - we have integration
> test for Jigsaw modularity and modulepath is activated for JDK 9+.
> NPE was fixed in 2.21.0 - check the release notes.
> We are no more calling the problematic method from commons-lang3 which
> caused NPE. This does not require any upgrade of commons-lang3 till 3.0.0.
> Please follow the build [1].
>
> Cheers
> Tibor
>
>
> On Sat, Feb 24, 2018 at 3:22 PM, Robert Scholte 
> wrote:
>
>> Hi,
>>
>> I've noticed some unsatisfying discussions regarding surefire, so let me
>> try to help moving this forward.
>>
>
I'm just not happy about how people do not listen neither read emails
Emails is the primary way of working at Apache because of different
timezone etc...
IRC is just a volatile dicussion channel when you disconnect you cannot
read history, later reply from someone (perso I often shutdown my laptop)


>
>> Here's the situation as I see it:
>> - Surefire 2.20.1 is the latest released version (2017-09-15)
>>
>> - 2.20.1 doesn't use the modulepath yet, that will be part of the next
>> release. A lot of people are waiting for this even before the official
>> release of JDK9.
>>
>> - Surefire 2.x is is still JDK 1.6 compatible, the requirement of JDK 1.7
>> is planned for surefire 3.0.0
>>
>
I'm fine with that so we can have a branch 2.x with jdk6 compatible
And master 3.0.0 with jdk7 requirement.
Does it sound reasonnable?


>
>> - 2.20.1 doesn't run on JDK10, it gets an NPE caused by commons-lang when
>> trying to get the Java version. The version of commons-lang where this is
>> fixed required JDK 1.7 (which clashes with the previous bullet)
>>
>> - After the next version (2.21), surefire will focus on 3.0.0
>>
>> - There's no agreement that the current master works with JDK10. One of
>> the things I noticed is that you need to run surefire with a special set of
>> arguments. I haven't been able to build it locally, so I cannot judge it.
>>
>> - Surefire is a huge, complex project and Tibor has taken the
>> responsibility for maintaining this project.
>>
>
I do not see such role at Apache. everyone can work on the project with the
same right.
There is no BDFL rule and NO one can revert commits from others without
discussion.
I guess that's the problem here I keep sending emails I have no response!!


>
>> What I would like to see is:
>> - What's blocking a release right now? Is it just CI? Knowing that CI has
>> changed a lot the last couple of months, did it just expose *unknown
>> issues* compared to 2.20.1?
>> - Is the master at its current state already an improvement compared to
>> 2.20.1?
>> - What would be the estimated release date for surefire.
>> - If this date is too unsure or takes too long, can Olivier create a
>> branch and do a 21.1-JDK10 release? or beta1?
>>
>> My main issue is : we should work towards a new release, because 2.20.1
>> doesn't work with JDK10 and there's no workaround.
>> IMHO this doesn't have to be an official surefire release, we can add
>> some special qualifier to at least help those 

Re: Surefire roadmap

[Tibor Digana]

 Sorry, I have to repeat myself because of undelivered message(s) to Maven
mailing list.

For clarifying the Surefire goes with Java 6. If you want to run your tests
with JDK10 or lower you have to specify the system property
-Djdk.home=/path/to/jdk10 and the you will see that the tests pass. Go to
target/surefire-reports and failsafe-reports and target/it/** and check the
"java.home" and you will see your /path/to/jdk10.
One more remark I got the Jenkins working [1]. The whole problem was with
the call withMaven() in Jenkinsfile. After I switched back to withEnv() the
logs, InterruptedException has gone!
I reported several improvements that Olivier did not like to improve but I
think there is no any significant showstopper for 2.21.0.
I will now talk about the Jiras improvements with Olivier in GitHub and I
hope we will make the release soon!

I still do not understand what codeline you run and why you have problems
with runtime if I did not have several months and I tested with JDK8 u162,
u132, u121.
Please post a link to your codeline because I highly doubt that you are
testing the identical code with me!

[1]: https://builds.apache.org/job/maven-wip/job/maven-surefire/
job/SUREFIRE-1489/

For better clarification 2.21.0 is using modulepath - we have integration
test for Jigsaw modularity and modulepath is activated for JDK 9+.
NPE was fixed in 2.21.0 - check the release notes.
We are no more calling the problematic method from commons-lang3 which
caused NPE. This does not require any upgrade of commons-lang3 till 3.0.0.
Please follow the build [1].

Cheers
Tibor


On Sat, Feb 24, 2018 at 3:22 PM, Robert Scholte 
wrote:

> Hi,
>
> I've noticed some unsatisfying discussions regarding surefire, so let me
> try to help moving this forward.
>
> Here's the situation as I see it:
> - Surefire 2.20.1 is the latest released version (2017-09-15)
>
> - 2.20.1 doesn't use the modulepath yet, that will be part of the next
> release. A lot of people are waiting for this even before the official
> release of JDK9.
>
> - Surefire 2.x is is still JDK 1.6 compatible, the requirement of JDK 1.7
> is planned for surefire 3.0.0
>
> - 2.20.1 doesn't run on JDK10, it gets an NPE caused by commons-lang when
> trying to get the Java version. The version of commons-lang where this is
> fixed required JDK 1.7 (which clashes with the previous bullet)
>
> - After the next version (2.21), surefire will focus on 3.0.0
>
> - There's no agreement that the current master works with JDK10. One of
> the things I noticed is that you need to run surefire with a special set of
> arguments. I haven't been able to build it locally, so I cannot judge it.
>
> - Surefire is a huge, complex project and Tibor has taken the
> responsibility for maintaining this project.
>
> What I would like to see is:
> - What's blocking a release right now? Is it just CI? Knowing that CI has
> changed a lot the last couple of months, did it just expose *unknown
> issues* compared to 2.20.1?
> - Is the master at its current state already an improvement compared to
> 2.20.1?
> - What would be the estimated release date for surefire.
> - If this date is too unsure or takes too long, can Olivier create a
> branch and do a 21.1-JDK10 release? or beta1?
>
> My main issue is : we should work towards a new release, because 2.20.1
> doesn't work with JDK10 and there's no workaround.
> IMHO this doesn't have to be an official surefire release, we can add some
> special qualifier to at least help those who need to work with JDK10.
>
> thanks,
> Robert
>

Re: [VOTE] Release Apache Maven 3.5.3

[Stephen Connolly]

On 24 February 2018 at 22:00, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> Hi,
>
> We solved 22 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12341428=Text=12316922
>
> There are 381 issues left in JIRA for Maven core:
> https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%
> 20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1401/
>
> The distributable binaries and sources can be found here:
> https://repository.apache.org/content/repositories/maven-
> 1401/org/apache/maven/apache-maven/3.5.3/
>
> Specifically the zip, tarball and source archives can be found here:
> https://repository.apache.org/content/repositories/maven-
> 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.zip
> https://repository.apache.org/content/repositories/maven-
> 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.tar.gz
> https://repository.apache.org/content/repositories/maven-
> 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.zip
> https://repository.apache.org/content/repositories/maven-
> 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.tar.gz
>
> The release artifacts are staged for distribution in:
> https://dist.apache.org/repos/dist/dev/maven/maven-3/3.5.3
>
> Source release checksum(s):
> apache-maven-3.5.3-src.tar.gz sha1: 60905d8b8b025b091f456ec25ad60dda56c26ad5
> sha256: 471748340cdc7f78b0b0c7bdf9e5399738e6721c08e166f59ef400f1dd107e19
> apache-maven-3.5.3-src.zip: sha1: a9be51d571165261dfb2e0c8ecc6b4f1c4c96766
> sha256: 109ac07fa337e582b8e6741f179e9f09166cae0fc9b3f44d4a35a2a2c7ccbd57
>
> Git tag:
> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=
> 3383c37e1f9e9b3bc3df5050c29c8aff9f295297
>
> Staging site:
> https://maven.apache.org/components/ref/3-LATEST/
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Thanks,
>
> Stephen.
>


$ sra https://repository.apache.org/content/repositories/maven-1401 3.5.3
Analyzer...

stagingUrl: https://repository.apache.org/content/repositories/maven-1401
groupId: org.apache.maven
artifactId: apache-maven
version: 3.5.3

Source ZIP url exists.
https://repository.apache.org/content/repositories/maven-1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.zip

Source ZIP SHA1 url exists.
https://repository.apache.org/content/repositories/maven-1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.zip.sha1

Binary ZIP url exists.
https://repository.apache.org/content/repositories/maven-1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.zip

Binary ZIP SHA1 url exists.
https://repository.apache.org/content/repositories/maven-1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.zip.sha1

Calculated SHA1 of source ZIP matches published SHA1 of source ZIP.
a9be51d571165261dfb2e0c8ecc6b4f1c4c96766

Calculated SHA1 of binary ZIP matches published SHA1 of binary ZIP.
4a4844990333e2548540729ce9ab57f52a63148d

Git revision of release as determined from
maven-core-3.5.3.jar:org/apache/maven/messages/build.properties(buildNumber):
3383c37e1f9e9b3bc3df5050c29c8aff9f295297

Files that are present in the source distribution but not in the source
revision:
DEPENDENCIES

[VOTE] Release Apache Maven 3.5.3

[Stephen Connolly]

Hi,

We solved 22 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12341428=Text=12316922

There are 381 issues left in JIRA for Maven core:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC

Staging repo:
https://repository.apache.org/content/repositories/maven-1401/

The distributable binaries and sources can be found here:
https://repository.apache.org/content/repositories/maven-1401/org/apache/maven/apache-maven/3.5.3/

Specifically the zip, tarball and source archives can be found here:
https://repository.apache.org/content/repositories/maven-1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.zip
https://repository.apache.org/content/repositories/maven-1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.tar.gz
https://repository.apache.org/content/repositories/maven-1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.zip
https://repository.apache.org/content/repositories/maven-1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.tar.gz

The release artifacts are staged for distribution in:
https://dist.apache.org/repos/dist/dev/maven/maven-3/3.5.3

Source release checksum(s):
apache-maven-3.5.3-src.tar.gz sha1:
60905d8b8b025b091f456ec25ad60dda56c26ad5
sha256: 471748340cdc7f78b0b0c7bdf9e5399738e6721c08e166f59ef400f1dd107e19
apache-maven-3.5.3-src.zip: sha1: a9be51d571165261dfb2e0c8ecc6b4f1c4c96766
sha256: 109ac07fa337e582b8e6741f179e9f09166cae0fc9b3f44d4a35a2a2c7ccbd57

Git tag:
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=3383c37e1f9e9b3bc3df5050c29c8aff9f295297

Staging site:
https://maven.apache.org/components/ref/3-LATEST/

Vote open for 72 hours.

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

Thanks,

Stephen.

Re: Prepared Maven 3.5.3 Release Notes

[Gary Gregory]

On Sat, Feb 24, 2018 at 2:24 PM, Karl Heinz Marbaise 
wrote:

> Hi Gary,
>
> On 24/02/18 22:02, Gary Gregory wrote:
>
>> Hi All,
>>
>> Thank you for preparing a release.
>>
>
> You're weclome.
>
>
>> As a user, this is useless:
>>
>> Bugs:
>>
>> - MNG-6323  reporter:
>> Ben Caradoc-Davies
>> - MNG-6320  reporter:
>> Eugene Pliskin
>> - MNG-6300  reporter:
>> Andreas Kurth
>> - MNG-6298  reporter:
>> Ryan Heaton
>> - MNG-6296  reporter:
>> Robin Müller
>> - MNG-6282  reporter:
>> Dejan Stojadinović
>> - MNG-6255  reporter:
>> Andrew Kennedy
>>
>> Improvements:
>>
>> - MNG-6340  reporter:
>> Tony Guan
>> - MNG-6306  reporter:
>> Andy Wilkinson
>> - MNG-5992  reporter:
>> Ryan J. McDonough
>>
>> I need to see the ticket DESCRIPTION. I do not care about the AUTHOR.
>>
>
> Sorry but I do care about the authors of the tickets, cause it shows
> their interest in helping making Maven better and contributing to Maven
> and I will honor those people at least with mentioning them in the Release
> Notes.
>

Hi,

I am not suggesting removal of the names of folks who have contributed,
just the addition of the ticket description. And yes, after scrolling down
I found the information I was looking for, which I expect to see front and
center in RNs, not deeper in.

Cheers,
Gary


>
> This is the foundation of an open source project or in other words the
> community we have here.
>
> I have a complete different opinion about that in particular in my Role as
> a Apache Maven PMC
>
> Sorry to say that in a very clear and maybe a little harsh way sorry if
> you grasp it that way.
>
> Apart from that I have added detailed descriptions about the changes which
> have been made and what they mean. Furthermore you will find a list of the
> tickets also and of course a link to the JIRA.
>
> If you have supplementals/enhancements/fixes or improvements for example
> the descriptions please feel free to add PR's or open at least issues on
> the git repository or make suggestions here on the mailing list...
>
> Kind regards
> Karl Heinz Marbaise
> Apache Maven PMC
>
>
>
>> Thank you,
>> Gary
>>
>> On Sat, Feb 24, 2018 at 1:47 PM, Karl Heinz Marbaise 
>> wrote:
>>
>> Hi to all,
>>>
>>> I have prepared Maven 3.5.3 Release notes.
>>>
>>> You can take a look here:
>>>
>>> https://github.com/khmarbaise/maven-release-notes/blob/maste
>>> r/content/markdown/docs/3.5.3/release-notes.md
>>>
>>> If you have improvements/ideas/supplementals etc. don't hesitate to
>>> contact me or make a PR...
>>>
>>> Kind regards
>>> Karl Heinz Marbaise
>>>
>>

Re: Prepared Maven 3.5.3 Release Notes

[Karl Heinz Marbaise]

Hi Gary,

On 24/02/18 22:02, Gary Gregory wrote:

Hi All,

Thank you for preparing a release.


You're weclome.



As a user, this is useless:

Bugs:

- MNG-6323  reporter:
Ben Caradoc-Davies
- MNG-6320  reporter:
Eugene Pliskin
- MNG-6300  reporter:
Andreas Kurth
- MNG-6298  reporter:
Ryan Heaton
- MNG-6296  reporter:
Robin Müller
- MNG-6282  reporter:
Dejan Stojadinović
- MNG-6255  reporter:
Andrew Kennedy

Improvements:

- MNG-6340  reporter:
Tony Guan
- MNG-6306  reporter:
Andy Wilkinson
- MNG-5992  reporter:
Ryan J. McDonough

I need to see the ticket DESCRIPTION. I do not care about the AUTHOR.


Sorry but I do care about the authors of the tickets, cause it shows
their interest in helping making Maven better and contributing to Maven 
and I will honor those people at least with mentioning them in the 
Release Notes.


This is the foundation of an open source project or in other words the 
community we have here.


I have a complete different opinion about that in particular in my Role 
as a Apache Maven PMC


Sorry to say that in a very clear and maybe a little harsh way sorry if 
you grasp it that way.


Apart from that I have added detailed descriptions about the changes 
which have been made and what they mean. Furthermore you will find a 
list of the tickets also and of course a link to the JIRA.


If you have supplementals/enhancements/fixes or improvements for example 
the descriptions please feel free to add PR's or open at least issues on 
the git repository or make suggestions here on the mailing list...


Kind regards
Karl Heinz Marbaise
Apache Maven PMC




Thank you,
Gary

On Sat, Feb 24, 2018 at 1:47 PM, Karl Heinz Marbaise 
wrote:


Hi to all,

I have prepared Maven 3.5.3 Release notes.

You can take a look here:

https://github.com/khmarbaise/maven-release-notes/blob/maste
r/content/markdown/docs/3.5.3/release-notes.md

If you have improvements/ideas/supplementals etc. don't hesitate to
contact me or make a PR...

Kind regards
Karl Heinz Marbaise


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

Re: Prepared Maven 3.5.3 Release Notes

[Gary Gregory]

Hi All,

Thank you for preparing a release.

As a user, this is useless:

Bugs:

   - MNG-6323  reporter:
   Ben Caradoc-Davies
   - MNG-6320  reporter:
   Eugene Pliskin
   - MNG-6300  reporter:
   Andreas Kurth
   - MNG-6298  reporter:
   Ryan Heaton
   - MNG-6296  reporter:
   Robin Müller
   - MNG-6282  reporter:
   Dejan Stojadinović
   - MNG-6255  reporter:
   Andrew Kennedy

Improvements:

   - MNG-6340  reporter:
   Tony Guan
   - MNG-6306  reporter:
   Andy Wilkinson
   - MNG-5992  reporter:
   Ryan J. McDonough

I need to see the ticket DESCRIPTION. I do not care about the AUTHOR.

Thank you,
Gary

On Sat, Feb 24, 2018 at 1:47 PM, Karl Heinz Marbaise 
wrote:

> Hi to all,
>
> I have prepared Maven 3.5.3 Release notes.
>
> You can take a look here:
>
> https://github.com/khmarbaise/maven-release-notes/blob/maste
> r/content/markdown/docs/3.5.3/release-notes.md
>
> If you have improvements/ideas/supplementals etc. don't hesitate to
> contact me or make a PR...
>
> Kind regards
> Karl Heinz Marbaise
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Prepared Maven 3.5.3 Release Notes

[Karl Heinz Marbaise]

Hi to all,

I have prepared Maven 3.5.3 Release notes.

You can take a look here:

https://github.com/khmarbaise/maven-release-notes/blob/master/content/markdown/docs/3.5.3/release-notes.md

If you have improvements/ideas/supplementals etc. don't hesitate to 
contact me or make a PR...


Kind regards
Karl Heinz Marbaise

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

Re: Surefire roadmap

[Robert Scholte]

Hi Olivier,

"I haven't been able to build it locally, so I cannot judge it."
So no.

This is where JAVA_HOME points to JDK8 and just executing "mvn clean  
verify", which fails on the unittests of Surefire Booter.


Robert

On Sat, 24 Feb 2018 20:24:47 +0100, Olivier Lamy  wrote:


Robert
I have a very simple question: does surefire master build for you even  
with

jdk7 or 8?
I keep asking that but it looks no one has try and no one answer this
question.
So please first let us know

On Sun, 25 Feb 2018 at 12:22 am, Robert Scholte 
wrote:


Hi,

I've noticed some unsatisfying discussions regarding surefire, so let me
try to help moving this forward.

Here's the situation as I see it:
- Surefire 2.20.1 is the latest released version (2017-09-15)

- 2.20.1 doesn't use the modulepath yet, that will be part of the next
release. A lot of people are waiting for this even before the official
release of JDK9.

- Surefire 2.x is is still JDK 1.6 compatible, the requirement of JDK  
1.7

is planned for surefire 3.0.0

- 2.20.1 doesn't run on JDK10, it gets an NPE caused by commons-lang  
when
trying to get the Java version. The version of commons-lang where this  
is

fixed required JDK 1.7 (which clashes with the previous bullet)

- After the next version (2.21), surefire will focus on 3.0.0

- There's no agreement that the current master works with JDK10. One of
the things I noticed is that you need to run surefire with a special set
of arguments. I haven't been able to build it locally, so I cannot judge
it.

- Surefire is a huge, complex project and Tibor has taken the
responsibility for maintaining this project.

What I would like to see is:
- What's blocking a release right now? Is it just CI? Knowing that CI  
has

changed a lot the last couple of months, did it just expose *unknown
issues* compared to 2.20.1?
- Is the master at its current state already an improvement compared to
2.20.1?
- What would be the estimated release date for surefire.
- If this date is too unsure or takes too long, can Olivier create a
branch and do a 21.1-JDK10 release? or beta1?

My main issue is : we should work towards a new release, because 2.20.1
doesn't work with JDK10 and there's no workaround.
IMHO this doesn't have to be an official surefire release, we can add  
some

special qualifier to at least help those who need to work with JDK10.

thanks,
Robert

-
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


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

Re: Surefire roadmap

[Olivier Lamy]

Robert
I have a very simple question: does surefire master build for you even with
jdk7 or 8?
I keep asking that but it looks no one has try and no one answer this
question.
So please first let us know

On Sun, 25 Feb 2018 at 12:22 am, Robert Scholte 
wrote:

> Hi,
>
> I've noticed some unsatisfying discussions regarding surefire, so let me
> try to help moving this forward.
>
> Here's the situation as I see it:
> - Surefire 2.20.1 is the latest released version (2017-09-15)
>
> - 2.20.1 doesn't use the modulepath yet, that will be part of the next
> release. A lot of people are waiting for this even before the official
> release of JDK9.
>
> - Surefire 2.x is is still JDK 1.6 compatible, the requirement of JDK 1.7
> is planned for surefire 3.0.0
>
> - 2.20.1 doesn't run on JDK10, it gets an NPE caused by commons-lang when
> trying to get the Java version. The version of commons-lang where this is
> fixed required JDK 1.7 (which clashes with the previous bullet)
>
> - After the next version (2.21), surefire will focus on 3.0.0
>
> - There's no agreement that the current master works with JDK10. One of
> the things I noticed is that you need to run surefire with a special set
> of arguments. I haven't been able to build it locally, so I cannot judge
> it.
>
> - Surefire is a huge, complex project and Tibor has taken the
> responsibility for maintaining this project.
>
> What I would like to see is:
> - What's blocking a release right now? Is it just CI? Knowing that CI has
> changed a lot the last couple of months, did it just expose *unknown
> issues* compared to 2.20.1?
> - Is the master at its current state already an improvement compared to
> 2.20.1?
> - What would be the estimated release date for surefire.
> - If this date is too unsure or takes too long, can Olivier create a
> branch and do a 21.1-JDK10 release? or beta1?
>
> My main issue is : we should work towards a new release, because 2.20.1
> doesn't work with JDK10 and there's no workaround.
> IMHO this doesn't have to be an official surefire release, we can add some
> special qualifier to at least help those who need to work with JDK10.
>
> thanks,
> Robert
>
> -
> 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

Surefire roadmap

[Robert Scholte]

Hi,

I've noticed some unsatisfying discussions regarding surefire, so let me  
try to help moving this forward.


Here's the situation as I see it:
- Surefire 2.20.1 is the latest released version (2017-09-15)

- 2.20.1 doesn't use the modulepath yet, that will be part of the next  
release. A lot of people are waiting for this even before the official  
release of JDK9.


- Surefire 2.x is is still JDK 1.6 compatible, the requirement of JDK 1.7  
is planned for surefire 3.0.0


- 2.20.1 doesn't run on JDK10, it gets an NPE caused by commons-lang when  
trying to get the Java version. The version of commons-lang where this is  
fixed required JDK 1.7 (which clashes with the previous bullet)


- After the next version (2.21), surefire will focus on 3.0.0

- There's no agreement that the current master works with JDK10. One of  
the things I noticed is that you need to run surefire with a special set  
of arguments. I haven't been able to build it locally, so I cannot judge  
it.


- Surefire is a huge, complex project and Tibor has taken the  
responsibility for maintaining this project.


What I would like to see is:
- What's blocking a release right now? Is it just CI? Knowing that CI has  
changed a lot the last couple of months, did it just expose *unknown  
issues* compared to 2.20.1?
- Is the master at its current state already an improvement compared to  
2.20.1?

- What would be the estimated release date for surefire.
- If this date is too unsure or takes too long, can Olivier create a  
branch and do a 21.1-JDK10 release? or beta1?


My main issue is : we should work towards a new release, because 2.20.1  
doesn't work with JDK10 and there's no workaround.
IMHO this doesn't have to be an official surefire release, we can add some  
special qualifier to at least help those who need to work with JDK10.


thanks,
Robert

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

Re: Jenkins build hangs and logs grow up to 27GB

[Stephen Connolly]

/consoleFull should stream the raw console

On Sat 24 Feb 2018 at 10:28, Tibor Digana  wrote:

> I guess there would be many lines with InterruptedException, but unless we
> download log file we would not be sure.
> How to download it other way than through the HTTP link /console ?
>
> On Sat, Feb 24, 2018 at 10:48 AM, Tibor Digana 
> wrote:
>
> > Hello Stephen,
> >
> > I disabled the Jenkins agent using your hint [1].
> > I used zip() and archived build reports and logs of all ITs.
> > I used lock() on short running failsafe ITs.
> >
> > Now the build is successful.
> >
> > After this another bad thing happened.
> > The logs size was 27GB several hours ago. Now Jenkins does not show you
> > the logs at all.
> >
> > Long time ago when I used withEnv() I did not have these problem.
> > I would like to check it out with that and compare the results.
> >
> > Can you have a look in the build [2]? Maybe you would find a root cause.
> I
> > am trying in the branch SUREFIRE-1489.
> >
> > [1]: true
> > [2]: https://builds.apache.org/job/maven-wip/job/maven-surefire/
> > job/SUREFIRE-1489/8/
> >
> > Thx
> > Tibor
> >
> >
>
-- 
Sent from my phone

[VOTE] Release Apache Maven JDeps Plugin version 3.1.1

[Robert Scholte]

Hi,

We solved 6 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319223=12341552=Text

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

Staging repo:
https://repository.apache.org/content/repositories/maven-1398
https://repository.apache.org/content/repositories/maven-1398/org/apache/maven/plugins/maven-jdeps-plugin/3.1.1/maven-jdeps-plugin-3.1.1-source-release.zip

Source release checksum(s):
maven-jdeps-plugin-3.1.1-source-release.zip sha1:  
14638ed958c6fde194f4ddc5955ac476c3d40abe


Staging site:
https://maven.apache.org/plugins-archives/maven-jdeps-plugin-LATEST/

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

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

Re: [3/3] maven-surefire git commit: Revert "[SUREFIRE-1473] upgrade commons-lang3 to avoid NPE on jdk10"

[Olivier Lamy]

fail with travis as well
https://travis-ci.org/olamy/maven-surefire/builds/345611495

On 24 February 2018 at 20:30, Olivier Lamy  wrote:

> ping.
> Am I the only one having issue building surefire master?
> If no response I will re apply my commits.
>
>
> On 22 February 2018 at 21:44, Olivier Lamy  wrote:
>
>> ping.
>> You reverted my commit but this doesn't work!
>> As I don't want to turn as a "it doesn't work on my machine" I tried with
>> different machines and even provide you some links to different jenkins
>> freestyle build but nothing happened.
>> https://builds.apache.org/view/M-R/view/Maven/job/maven-sure
>> fire-fs/2/console
>> or
>> https://jenkins.webtide.net/job/sandbox/job/surefire-master-
>> jdk8/4/console
>> seems to work with your Jenkinsfile and using withMaven but definitely
>> doesn't work locally or using jenkins freestyle (no time to debug the
>> reason but something evil maybe :-) )
>> So I really want to move forward and having a surefire ready to be used
>> with jdk10.
>> first jdk10 RC has been released and it doesn't work with Maven so we
>> need to do something.
>> What is the problem to use commons-lang3 3.7 and make surefire as 1.7
>> minimum.
>> I asked on the mailing list and didn't have any negative response so I
>> did the upgrade and you reverted it.
>> You reverted my commits without any explanations so maybe you have good
>> reasons but please explain!
>>
>>
>>
>> On 19 February 2018 at 18:39, Olivier Lamy  wrote:
>>
>>> I setup a very simple freestyle build on ASF Jenkins and got the same
>>> error as I have locally:
>>> https://builds.apache.org/view/M-R/view/Maven/job/maven-sure
>>> fire-fs/1/console
>>>
>>> On 19 February 2018 at 08:22, Olivier Lamy  wrote:
>>>
 well maybe ignore this test until it's fixed...
 Anyway there are some flaky tests which machine dependant and this
 prevent the build to continue on a ci machine I use
 https://jenkins.webtide.net/job/sandbox/

 java.lang.AssertionError: expected:<1.0> but was:<11335.0>
 at org.junit.Assert.fail(Assert.java:88)
 at org.junit.Assert.failNotEquals(Assert.java:834)
 at org.junit.Assert.assertEquals(Assert.java:575)
 at org.junit.Assert.assertEquals(Assert.java:700)
 at org.apache.maven.surefire.junitcore.pc.ParallelComputerUtilT
 est.withoutShutdown(ParallelComputerUtilTest.java:984)

 Could we use a range rather than a strict value for this test? (depends
 on used machine but not sure we can rely on a strict timing)

 To answer your question I easily reproduce the failure with master
 locally with jdk10

  /Library/Java/JavaVirtualMachines/jdk-10.jdk/Contents/Home/bin/java
 -version

 java version "10-ea" 2018-03-20

 Java(TM) SE Runtime Environment 18.3 (build 10-ea+42)

 Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10-ea+42, mixed mode)


 mvn -v

 *Apache Maven 3.5.3-SNAPSHOT (99e66229aca82e12292d0e481d8e71158cc52ca4;
 2018-02-08T09:39:06+10:00)*

 Maven home: /Users/olamy/softs/maven/trunk

 Java version: 1.8.0_121, vendor: Oracle Corporation

 Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/
 Home/jre

 Default locale: en_AU, platform encoding: UTF-8

 OS name: "mac os x", version: "10.13.3", arch: "x86_64", family: "mac"


 failure

 java.lang.NoClassDefFoundError: org/apache/commons/lang3/SystemUtils

 at org.apache.maven.surefire.booter.PpidChecker.canUse(PpidChec
 ker.java:74)

 at org.apache.maven.surefire.booter.PpidCheckerTest.shouldNotFi
 ndSuchPID(PpidCheckerTest.java:100)

 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
 Method)

 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invo
 ke(NativeMethodAccessorImpl.java:62)

 at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.
 invoke(DelegatingMethodAccessorImpl.java:43)

 at java.base/java.lang.reflect.Method.invoke(Method.java:564)

 at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(
 FrameworkMethod.java:50)

 at org.junit.internal.runners.model.ReflectiveCallable.run(Refl
 ectiveCallable.java:12)

 at org.junit.runners.model.FrameworkMethod.invokeExplosively(Fr
 ameworkMethod.java:47)

 at org.junit.internal.runners.statements.InvokeMethod.evaluate(
 InvokeMethod.java:17)

 at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)

 at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit
 4ClassRunner.java:78)

 at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit
 4ClassRunner.java:57)

 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)

 at 

Re: [3/3] maven-surefire git commit: Revert "[SUREFIRE-1473] upgrade commons-lang3 to avoid NPE on jdk10"

[Olivier Lamy]

ping.
Am I the only one having issue building surefire master?
If no response I will re apply my commits.


On 22 February 2018 at 21:44, Olivier Lamy  wrote:

> ping.
> You reverted my commit but this doesn't work!
> As I don't want to turn as a "it doesn't work on my machine" I tried with
> different machines and even provide you some links to different jenkins
> freestyle build but nothing happened.
> https://builds.apache.org/view/M-R/view/Maven/job/maven-
> surefire-fs/2/console
> or
> https://jenkins.webtide.net/job/sandbox/job/surefire-master-jdk8/4/console
> seems to work with your Jenkinsfile and using withMaven but definitely
> doesn't work locally or using jenkins freestyle (no time to debug the
> reason but something evil maybe :-) )
> So I really want to move forward and having a surefire ready to be used
> with jdk10.
> first jdk10 RC has been released and it doesn't work with Maven so we need
> to do something.
> What is the problem to use commons-lang3 3.7 and make surefire as 1.7
> minimum.
> I asked on the mailing list and didn't have any negative response so I did
> the upgrade and you reverted it.
> You reverted my commits without any explanations so maybe you have good
> reasons but please explain!
>
>
>
> On 19 February 2018 at 18:39, Olivier Lamy  wrote:
>
>> I setup a very simple freestyle build on ASF Jenkins and got the same
>> error as I have locally:
>> https://builds.apache.org/view/M-R/view/Maven/job/maven-sure
>> fire-fs/1/console
>>
>> On 19 February 2018 at 08:22, Olivier Lamy  wrote:
>>
>>> well maybe ignore this test until it's fixed...
>>> Anyway there are some flaky tests which machine dependant and this
>>> prevent the build to continue on a ci machine I use
>>> https://jenkins.webtide.net/job/sandbox/
>>>
>>> java.lang.AssertionError: expected:<1.0> but was:<11335.0>
>>> at org.junit.Assert.fail(Assert.java:88)
>>> at org.junit.Assert.failNotEquals(Assert.java:834)
>>> at org.junit.Assert.assertEquals(Assert.java:575)
>>> at org.junit.Assert.assertEquals(Assert.java:700)
>>> at org.apache.maven.surefire.junitcore.pc.ParallelComputerUtilT
>>> est.withoutShutdown(ParallelComputerUtilTest.java:984)
>>>
>>> Could we use a range rather than a strict value for this test? (depends
>>> on used machine but not sure we can rely on a strict timing)
>>>
>>> To answer your question I easily reproduce the failure with master
>>> locally with jdk10
>>>
>>>  /Library/Java/JavaVirtualMachines/jdk-10.jdk/Contents/Home/bin/java
>>> -version
>>>
>>> java version "10-ea" 2018-03-20
>>>
>>> Java(TM) SE Runtime Environment 18.3 (build 10-ea+42)
>>>
>>> Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10-ea+42, mixed mode)
>>>
>>>
>>> mvn -v
>>>
>>> *Apache Maven 3.5.3-SNAPSHOT (99e66229aca82e12292d0e481d8e71158cc52ca4;
>>> 2018-02-08T09:39:06+10:00)*
>>>
>>> Maven home: /Users/olamy/softs/maven/trunk
>>>
>>> Java version: 1.8.0_121, vendor: Oracle Corporation
>>>
>>> Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/
>>> Home/jre
>>>
>>> Default locale: en_AU, platform encoding: UTF-8
>>>
>>> OS name: "mac os x", version: "10.13.3", arch: "x86_64", family: "mac"
>>>
>>>
>>> failure
>>>
>>> java.lang.NoClassDefFoundError: org/apache/commons/lang3/SystemUtils
>>>
>>> at org.apache.maven.surefire.booter.PpidChecker.canUse(PpidChec
>>> ker.java:74)
>>>
>>> at org.apache.maven.surefire.booter.PpidCheckerTest.shouldNotFi
>>> ndSuchPID(PpidCheckerTest.java:100)
>>>
>>> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
>>> Method)
>>>
>>> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invo
>>> ke(NativeMethodAccessorImpl.java:62)
>>>
>>> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.
>>> invoke(DelegatingMethodAccessorImpl.java:43)
>>>
>>> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
>>>
>>> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(
>>> FrameworkMethod.java:50)
>>>
>>> at org.junit.internal.runners.model.ReflectiveCallable.run(Refl
>>> ectiveCallable.java:12)
>>>
>>> at org.junit.runners.model.FrameworkMethod.invokeExplosively(Fr
>>> ameworkMethod.java:47)
>>>
>>> at org.junit.internal.runners.statements.InvokeMethod.evaluate(
>>> InvokeMethod.java:17)
>>>
>>> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>>>
>>> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit
>>> 4ClassRunner.java:78)
>>>
>>> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit
>>> 4ClassRunner.java:57)
>>>
>>> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>>>
>>> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>>>
>>> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>>>
>>> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>>>
>>> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>>>
>>> at 

Re: Jenkins build hangs and logs grow up to 27GB

[Tibor Digana]

I guess there would be many lines with InterruptedException, but unless we
download log file we would not be sure.
How to download it other way than through the HTTP link /console ?

On Sat, Feb 24, 2018 at 10:48 AM, Tibor Digana 
wrote:

> Hello Stephen,
>
> I disabled the Jenkins agent using your hint [1].
> I used zip() and archived build reports and logs of all ITs.
> I used lock() on short running failsafe ITs.
>
> Now the build is successful.
>
> After this another bad thing happened.
> The logs size was 27GB several hours ago. Now Jenkins does not show you
> the logs at all.
>
> Long time ago when I used withEnv() I did not have these problem.
> I would like to check it out with that and compare the results.
>
> Can you have a look in the build [2]? Maybe you would find a root cause. I
> am trying in the branch SUREFIRE-1489.
>
> [1]: true
> [2]: https://builds.apache.org/job/maven-wip/job/maven-surefire/
> job/SUREFIRE-1489/8/
>
> Thx
> Tibor
>
>

Jenkins build hangs and logs grow up to 27GB

[Tibor Digana]

Hello Stephen,

I disabled the Jenkins agent using your hint [1].
I used zip() and archived build reports and logs of all ITs.
I used lock() on short running failsafe ITs.

Now the build is successful.

After this another bad thing happened.
The logs size was 27GB several hours ago. Now Jenkins does not show you the
logs at all.

Long time ago when I used withEnv() I did not have these problem.
I would like to check it out with that and compare the results.

Can you have a look in the build [2]? Maybe you would find a root cause. I
am trying in the branch SUREFIRE-1489.

[1]: true
[2]:
https://builds.apache.org/job/maven-wip/job/maven-surefire/job/SUREFIRE-1489/8/

Thx
Tibor