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

[Olivier Lamy]

+1 tested on some projects

On Thu, 6 Dec 2018 at 8:26 am, Tibor Digana  wrote:

> Hi,
>
> We solved 15 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12344396
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/i#issues/?jql=project+%3D+SUREFIRE+AND+status+%3D+Open+ORDER+BY+priority+DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1472/
>
> https://repository.apache.org/service/local/repositories/maven-1472/content/org/apache/maven/surefire/surefire/3.0.0-M2/surefire-3.0.0-M2-source-release.zip
>
> Source release checksum(s):
> surefire-3.0.0-M2-source-release.zip sha1:
> 421f6fda2367d128007b84b213690db348a8b2c6
> surefire-3.0.0-M2-source-release.zip sha512:
>
> ed02ac46eec7f632180e00487f65901420908ea5afc0e507350c2fa529a6278f73f32f915bcd1dee0bcdffbf391d045b9f3cfe557003d02af9e2dc91ddb31212
>
> 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
>
> BR
> Tibor
>
-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: parallelise not overlapping tasks

[Mickael Istria]

Ok, my bad, thanks for the hint.

Re: parallelise not overlapping tasks

[Romain Manni-Bucau]

Mojos already have the ability to say if they are threadsafe, what do you
see missing?

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



Le jeu. 6 déc. 2018 à 15:23, Mickael Istria  a écrit :

> I think there is a difference between scheduling tasks (one is after the
> other) and assuming that 2 tasks that are ready can run in parallel.
> Adding scheduling data would be helpful and get rid of the concept of
> phases, for sure; but we also -and more importantly- need the existing
> mojos to be audited and be able to declare whether they're thread-safe
> before running them in parallel, and this sounds like a gigantic work.
>

Re: parallelise not overlapping tasks

[Mickael Istria]

I think there is a difference between scheduling tasks (one is after the
other) and assuming that 2 tasks that are ready can run in parallel.
Adding scheduling data would be helpful and get rid of the concept of
phases, for sure; but we also -and more importantly- need the existing
mojos to be audited and be able to declare whether they're thread-safe
before running them in parallel, and this sounds like a gigantic work.

Re: parallelise not overlapping tasks

[Romain Manni-Bucau]

Currently maven can't but I expect a way to do it, either in the next xsd
as originally proposed or, why not, with a naming convention in the id of
the execution (my-exec#after#other-exec or something
like that if we want it before maven 4)

The nice thing is that once done it makes phases pretty much useless (it is
just about making implicit these dependencies) and it makes the whole build
parallelizable and not just modules which will often find some bottleneck
modules in projects building a distribution.

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



Le jeu. 6 déc. 2018 à 14:44, Mickael Istria  a écrit :

> Hi,
>
> > any way we move that topic forward beginning of next year?
>
> I guess providing patches would be the best way ;)
>
> I'm coming late in this discussion and I'm a newcomer on that list, so I
> could miss context. This could relate to an effort we are doing in Eclipse
> IDE (and Eclipse m2e) to run module builds in parallel. One question I have
> is how do you know 2 tasks aren't conflicting? We didn't figure out a safe
> way to know that in m2e, maybe I missed something?
>
> Cheers,
>

Re: parallelise not overlapping tasks

[Mickael Istria]

Hi,

> any way we move that topic forward beginning of next year?

I guess providing patches would be the best way ;)

I'm coming late in this discussion and I'm a newcomer on that list, so I
could miss context. This could relate to an effort we are doing in Eclipse
IDE (and Eclipse m2e) to run module builds in parallel. One question I have
is how do you know 2 tasks aren't conflicting? We didn't figure out a safe
way to know that in m2e, maybe I missed something?

Cheers,

Re: parallelise not overlapping tasks

[Romain Manni-Bucau]

Hey guys,

any way we move that topic forward beginning of next year?

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



Le lun. 22 janv. 2018 à 01:04, Tibor Digana  a
écrit :

> I am facing very slow Maven reporting/site.
> I have optimized JavaDoc and avoided the javadoc plugin downloading
> sources, Java API which has improved the performance but still Site takes 8
> minutes at least to complete.
> It would be worth to mark some reporting plugins running in parallel in
> aggregator POM.
>
> On Fri, Jan 19, 2018 at 2:20 PM, Romain Manni-Bucau  >
> wrote:
>
> > Hi guys,
> >
> > there is no way to parallelize not conflicting tasks for a same phase at
> > the moment right? Any way it gets under the radar?
> >
> > A common example is to run all code analyzis concurrently (findbugs, pmd,
> > checkstyle, ...) at the same time without waiting for one then the other
> > etc since all can be very long.
> >
> > It could be nice an fancy to define part of the reactor parallelisablity
> in
> > the pom, like:
> >
> > 
> > 
> > process-sources
> > 
> > 
> >   ...
> >   ...
> >   ...
> >   ...
> > 
> > 
> >   ...
> >   ...
> >   ...
> >   ...
> > 
> > 
> > 
> > 
> >
> > anything to enhance it?
> >
> > Romain Manni-Bucau
> > @rmannibucau  |  Blog
> >  | Old Blog
> >  | Github  > rmannibucau> |
> > LinkedIn 
> >
>

MNG-6533 and MNG-6529

[Mickael Istria]

Hi all,

As part of a major performance improvement in m2e, we'd like to use the
ProjectBuilder.build(list_of_poms, ...) which drastically reduce CPU and
RAM consumption compared to iterating on ProjectBuilder.build(single_pom,
...).
We identified 2 relatively small limitations blocking m2e from adoption
ProjectBuilder.build(list_of_poms,...) that seems to just be missing
features compared to ProjectBuilder.build(single_pom...) because no-one
needed them to so far. We're covered these 2 issues in MNG-6529 and
MNG-6533; and there are pull requests open for both.
We'd appreciate if those can be targeted for review (and if everything is
fine, merge) as part of next release.

Thanks in advance.
-- 
Mickael Istria
Eclipse IDE 
developer, for Red Hat Developers 

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

[Enrico Olivelli]

+1 (non binding)
- tested on Linux Fedora 28
- checked signatures and checksum

great work !
Enrico
Il giorno gio 6 dic 2018 alle ore 06:45 Romain Manni-Bucau
 ha scritto:
>
> +1 (non binding)
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github  |
> LinkedIn  | Book
> 
>
>
> Le mer. 5 déc. 2018 à 23:49, krystian.no...@gmail.com <
> krystian.no...@gmail.com> a écrit :
>
> > +1
> >
> > Cheers,
> > Krystian
> >
> > On 2018/12/05 22:26:44, Tibor Digana  wrote:
> > > Hi,
> > >
> > > We solved 15 issues:
> > >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12344396
> > >
> > > There are still a couple of issues left in JIRA:
> > >
> > https://issues.apache.org/jira/i#issues/?jql=project+%3D+SUREFIRE+AND+status+%3D+Open+ORDER+BY+priority+DESC
> > >
> > > Staging repo:
> > > https://repository.apache.org/content/repositories/maven-1472/
> > >
> > https://repository.apache.org/service/local/repositories/maven-1472/content/org/apache/maven/surefire/surefire/3.0.0-M2/surefire-3.0.0-M2-source-release.zip
> > >
> > > Source release checksum(s):
> > > surefire-3.0.0-M2-source-release.zip sha1:
> > > 421f6fda2367d128007b84b213690db348a8b2c6
> > > surefire-3.0.0-M2-source-release.zip sha512:
> > >
> > ed02ac46eec7f632180e00487f65901420908ea5afc0e507350c2fa529a6278f73f32f915bcd1dee0bcdffbf391d045b9f3cfe557003d02af9e2dc91ddb31212
> > >
> > > 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
> > >
> > > BR
> > > Tibor
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >

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