Thanks, will hook it up with our internal build
On Sun, Jul 11, 2021 at 6:59 PM Olivier Lamy wrote:
> done
>
> On Sun, 11 Jul 2021 at 07:44, Dan Tran wrote:
>
> > possible to push the latest snapshot to
> >
> >
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/apache-mav
done
On Sun, 11 Jul 2021 at 07:44, Dan Tran wrote:
> possible to push the latest snapshot to
>
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/apache-maven
> ?
>
> Thanks
>
> -D
>
> On Sat, Jul 10, 2021 at 2:33 PM Dan Tran wrote:
>
> > Thanks, I will test out the late
possible to push the latest snapshot to
https://repository.apache.org/content/groups/snapshots/org/apache/maven/apache-maven
?
Thanks
-D
On Sat, Jul 10, 2021 at 2:33 PM Dan Tran wrote:
> Thanks, I will test out the latest 3.8
>
> -D
>
> On Sat, Jul 10, 2021 at 12:29 PM Falko Modler wrote:
>
Thanks, I will test out the latest 3.8
-D
On Sat, Jul 10, 2021 at 12:29 PM Falko Modler wrote:
> Done already: https://github.com/apache/maven/pull/482
>
> Cheers,
> Falko
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.
Done already: https://github.com/apache/maven/pull/482
Cheers,
Falko
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
I think this is the one https://github.com/apache/maven/pull/413
-D
On Sat, Jul 10, 2021 at 2:56 AM Michael Osipov wrote:
> Am 2021-07-10 um 00:52 schrieb Dan Tran:
> > ah sorry, the proposed PR merged into master. Can we back port it to
> 3.8?
>
> Which PR exactly?
>
> -
Am 2021-07-10 um 00:52 schrieb Dan Tran:
ah sorry, the proposed PR merged into master. Can we back port it to 3.8?
Which PR exactly?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
ah sorry, the proposed PR merged into master. Can we back port it to 3.8?
-D
On Fri, Jul 9, 2021 at 3:47 PM Dan Tran wrote:
> ping again :-) to keep discussion going :-)
>
> -D
>
> On Tue, May 18, 2021 at 6:20 AM Guillaume Nodet wrote:
>
>> Maybe not that many people are using parallel builds
ping again :-) to keep discussion going :-)
-D
On Tue, May 18, 2021 at 6:20 AM Guillaume Nodet wrote:
> Maybe not that many people are using parallel builds...
> Imho, the PR should be merged. I've created
> https://issues.apache.org/jira/browse/MNG-7157 to provide a better API
> and deprecate
Maybe not that many people are using parallel builds...
Imho, the PR should be merged. I've created
https://issues.apache.org/jira/browse/MNG-7157 to provide a better API
and deprecate the getArtifacts() method which is flawed (see discussion on
the PR https://github.com/apache/maven/pull/413#issu
Am 2021-05-03 um 22:15 schrieb Falko Modler:
Earlier today Michael Osipov added this note to the ticket:
I confirm that this still happens on Maven master with Resolver
1.7.0-SNAPSHOT. This isn't Resolver related because no dependency
resolution happens in the build.
I am still confused why
16, 2021 at 10:21 PM Dan Tran wrote:
we are facing the same issue at work (300+ modules), classpath
empty randomly empty
Love to see some resolution, will help to test it
Thanks
-D
On Fri, Jan 15, 2021 at 1:51 PM Falko Modler
wrote:
Hi everyone,
I'd like to raise awareness for the Maven
gt; > > > solve many issues in the Core and Resolver.
> > > > Considering my examples with ArrayList, the thread safety should
> > continue
> > > > deeper with the implementation of DefaultArtifact, etc.
> > > > In my experience, it's worth us
gt; > Considering my examples with ArrayList, the thread safety should
> continue
> > > deeper with the implementation of DefaultArtifact, etc.
> > > In my experience, it's worth using the collection which appears in the
> > > package "java.util.concurrent".
rentLinkedDequeue for simple iterators with
> small
> > amounts of elements. Alternatively use COWAL for large data and
> reordering
> > of elements by adding or removing them somewhere inside.
> >
> > Cheers
> > Tibor17
> >
> >
> >
> > O
1:51 PM Falko Modler wrote:
Hi everyone,
I'd like to raise awareness for the MavenProject concurrency problem
that is causing MNG-6843 "Parallel build fails due to missing JAR
artifacts in compilePath" [1] and probably others [2] [3] [4].
Almost a month ago, I created a ThreadLocal-based f
test it
>
> Thanks
>
> -D
>
> On Fri, Jan 15, 2021 at 1:51 PM Falko Modler wrote:
>
> > Hi everyone,
> >
> > I'd like to raise awareness for the MavenProject concurrency problem
> > that is causing MNG-6843 "Parallel build fails due to missing JAR
problem
> that is causing MNG-6843 "Parallel build fails due to missing JAR
> artifacts in compilePath" [1] and probably others [2] [3] [4].
>
> Almost a month ago, I created a ThreadLocal-based fix for this [5]
> (after another, older cloning-based approach had rais
Hi everyone,
I'd like to raise awareness for the MavenProject concurrency problem
that is causing MNG-6843 "Parallel build fails due to missing JAR
artifacts in compilePath" [1] and probably others [2] [3] [4].
Almost a month ago, I created a ThreadLocal-based fix for this [5]
19 matches
Mail list logo