I ran it locally. Also ran it via a local Jenkins instance, same results.
>
> Enrico
>
>>
>> current maven-jar-plugin (master) is using maven-shared-utils-3.2.1
>> After running this, I don't see new/hanging java processes
>>
>> Robert
>>
>> On Sat, 12 Jan 2019 12:59:08 +0100, Tibor Digana
>> <
[hidden email]> wrote:
>>
>> >>> which commit could have broken shared utils ?
>> >
>> > I have picked up three candidate commits:
>> >
>> > 362805fbf6341523edfdf509905812acb42f6a97
>> > fd082c077c78f8ce83fce2a92f0265e83599a42f
>> > f2246e0653b185297451902ee278e6aec1ff470e
>> >
>> > Those devs who have Windows should run the build of maven-jar-plugin
>> (mvn
>> > verify -P run-its) and list all Java processes after the build.
>> > This process should repeat with maven-shared-utils:3.1.0 and again
>> list
>> > all
>> > Java processes.
>> > Logically there should not be any Java processes alive after the build
>> > has
>> > completed.
>> >
>> > Then we can decide whether we will find the commit and release a new
>> > version of maven-shared-utils or we will downgrade it in all
>> > usages/projects/branches together with testing on Jenkins.
>> > Cheers
>> > T
>> >
>> >
>> >
>> >
>> > On Sat, Jan 12, 2019 at 11:50 AM Enrico Olivelli <
[hidden email]>
>> > wrote:
>> >
>> >> Il giorno sab 12 gen 2019 alle ore 11:45 Enrico Olivelli
>> >> <
[hidden email]> ha scritto:
>> >> >
>> >> >
>> >> >
>> >> > Il sab 12 gen 2019, 11:39 Tibor Digana <
[hidden email]> ha
>> >> scritto:
>> >> >>
>> >> >> Such a drastic change?
>> >> >
>> >> >
>> >> > If that version is buggy we should fix it or drop it.
>> >> >
>> >> > Do we have already released that buggy version to users?
>> >> >
>> >> >
>> >> > How did you see our processes on Jenkins slave? Do you have access
>> to
>> >> slaves console?
>> >> >
>> >>
>> >> b.q.
>> >> which commit could have broken shared utils ?
>> >>
https://github.com/apache/maven-shared-utils/commits/master>> >>
>> >>
>> >> Enrico
>> >>
>> >>
>> >> > Enrico
>> >> >
>> >> >
>> >> >> First we should get the confidence using Jenkins CI for a long
>> time
>> >> run.
>> >> >>
>> >> >> On Sat, Jan 12, 2019 at 11:20 AM Enrico Olivelli
>> >> <
[hidden email]>
>> >> >> wrote:
>> >> >>
>> >> >> > Can't we rollback to the previous version instead of a snapshot?
>> >> >> >
>> >> >> > Enrico
>> >> >> >
>> >> >> > Il sab 12 gen 2019, 09:23 Tibor Digana <
[hidden email]>
>> ha
>> >> >> > scritto:
>> >> >> >
>> >> >> > > I think we should downgrade maven-shared-utils to 3.1.0 in the
>> >> >> > m-invoker-p
>> >> >> > > because we found the same problem in surefire:3.0.0-M1.
>> >> >> > > We did not have time to fix it and I have realized the
>> connection
>> >> to the
>> >> >> > > Invoker just now.
>> >> >> > > Faster than a release is to deploy SNAPSHOT version of the
>> >> Invoker
>> >> and
>> >> >> > use
>> >> >> > > it in JAR plugin and we will see again fully working Jenkins
>> >> build
>> >> >> > >
>> >> >> >
>> >>
>>
https://builds.apache.org/job/maven-box/job/maven-jar-plugin/job/MJAR-238/>> >> >> > > The precondition is to ask the INFRA to restart all Windows or
>> >> kill
>> >> all
>> >> >> > > Java processes.
>> >> >> > > T
>> >> >> > >
>> >> >> > --
>> >> >> >
>> >> >> >
>> >> >> > -- Enrico Olivelli
>> >> >> >
>> >> >
>> >> > --
>> >> >
>> >> >
>> >> > -- Enrico Olivelli
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail:
[hidden email]
>> >> For additional commands, e-mail:
[hidden email]
>> >>
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
[hidden email]
>> For additional commands, e-mail:
[hidden email]
>>
>> --
>
>
> -- Enrico Olivelli
Locked
