Hello,
I've been using Maven for 10+ years now. It's great and I still prefer it over
similar tools. Recently I encountered a scenario where it would have been nice
to be able to simply "override" a dependency. For example by specifying
_somehow_ that (in my case) commons-logging should be jcl-
Hi all,
it wouldn't surprise me if it was that ThreadLocal quickfix from my PR.
I think everyone agrees that it is a bandaid solution but well, correctness and
stability over (some) speed, IMO.
It would be nice to limit this workaround to only when aggregating goals are
involved but that seems
+1
include some interesting fixes
Thanks to take care of this!
On Thu, 5 Aug 2021 at 06:02, Michael Osipov wrote:
> Hi,
>
> We solved 68 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12349965
>
> There are still a couple of issues left in JIRA:
>
>
Am 2021-08-04 um 22:02 schrieb Michael Osipov:
Hi,
We solved 68 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12349965
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolutio
Dan,
thank you very much for testing. Do you think you could bisect to the
commit which introduced the 10% overhead? Maybe it is really the
classpath concurrency issue which has been addressed by Falko Modler.
Also can you try Maven from master and see whether you can reproduce the
10%?
Mi
