gnodet commented on issue #576:
URL: https://github.com/apache/maven-mvnd/issues/576#issuecomment-1009676835
> What are some examples of options that would allow reusing a daemon? I can
see that treating `-Xmx` as a minimum would allow reuse (the existing daemon
has a larger max heap),
gnodet commented on issue #579:
URL: https://github.com/apache/maven-mvnd/issues/579#issuecomment-1009669911
I think this should be already fixed with
https://github.com/apache/maven-mvnd/pull/566
--
This is an automated message from the Apache Git Service.
To respond to the message,
gnodet closed issue #579:
URL: https://github.com/apache/maven-mvnd/issues/579
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
gnodet commented on pull request #577:
URL: https://github.com/apache/maven-mvnd/pull/577#issuecomment-1009667746
> Let the JVM decide the max heap size instead of using hardcoded defaults
to match the behaviour of vanilla Maven.
>
> Fixes #560
>
> I tried adding a test like:
gnodet merged pull request #566:
URL: https://github.com/apache/maven-mvnd/pull/566
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
gnodet merged pull request #573:
URL: https://github.com/apache/maven-mvnd/pull/573
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
gnodet closed issue #553:
URL: https://github.com/apache/maven-mvnd/issues/553
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
gnodet commented on issue #570:
URL: https://github.com/apache/maven-mvnd/issues/570#issuecomment-1009657052
> > So mvnd speeds up by
> > ```
> > * enabling concurrent build by default
> >
> > * cacheing a few things and help speeding up the time spent by maven
_itself_ when
[
https://issues.apache.org/jira/browse/MNG-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472498#comment-17472498
]
Michael Osipov commented on MNG-7389:
-
Yes, you need a multilayer cache which changes with the version
[
https://issues.apache.org/jira/browse/MNG-7362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-7362:
---
Affects Version/s: 3.5.0-beta-1
> DefaultArtifactResolver has spurious "Failure detected" INFO log
>
[
https://issues.apache.org/jira/browse/MNG-7362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-7362:
---
Fix Version/s: 3.8.5
(was: wontfix-candidate)
> DefaultArtifactResolver has
[
https://issues.apache.org/jira/browse/MNG-7362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472497#comment-17472497
]
Herve Boutemy commented on MNG-7362:
thank you, then it's "just delete"
> DefaultArtifactResolver has
dependabot[bot] opened a new pull request #438:
URL: https://github.com/apache/maven-surefire/pull/438
Bumps maven-docck-plugin from 1.0 to 1.1.
[![Dependabot compatibility
dependabot[bot] opened a new pull request #88:
URL: https://github.com/apache/maven-jlink-plugin/pull/88
Bumps [plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver)
from 4.2.6 to 4.2.7.
Release notes
Sourced from
dependabot[bot] opened a new pull request #437:
URL: https://github.com/apache/maven-surefire/pull/437
Bumps [junit-jupiter-params](https://github.com/junit-team/junit5) from
5.3.2 to 5.8.2.
Release notes
Sourced from
dependabot[bot] opened a new pull request #117:
URL: https://github.com/apache/maven-javadoc-plugin/pull/117
Bumps [maven-archiver](https://github.com/apache/maven-archiver) from 3.5.1
to 3.5.2.
Commits
conderls edited a comment on issue #570:
URL: https://github.com/apache/maven-mvnd/issues/570#issuecomment-1009520138
> So mvnd speeds up by
>
> * enabling concurrent build by default
>
> * cacheing a few things and help speeding up the time spent by maven
_itself_
conderls commented on issue #570:
URL: https://github.com/apache/maven-mvnd/issues/570#issuecomment-1009520138
> So mvnd speeds up by
>
> * enabling concurrent build by default
>
> * cacheing a few things and help speeding up the time spent by maven
_itself_ when
[
https://issues.apache.org/jira/browse/MNG-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472359#comment-17472359
]
Thomas Skjølberg commented on MNG-7389:
---
Another way to explain this is a multi-level cache. I agree
[
https://issues.apache.org/jira/browse/MNG-7129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472349#comment-17472349
]
Herve Boutemy edited comment on MNG-7129 at 1/10/22, 10:48 PM:
---
code is
[
https://issues.apache.org/jira/browse/MNG-7129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472349#comment-17472349
]
Herve Boutemy commented on MNG-7129:
code is finally available at
[
https://issues.apache.org/jira/browse/MNG-7362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472342#comment-17472342
]
Karl Heinz Marbaise commented on MNG-7362:
--
The log info seemed something I simply overlooked.
>
[
https://issues.apache.org/jira/browse/MNG-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472339#comment-17472339
]
Michael Osipov commented on MNG-7389:
-
Ideally, you would solve this with a Nexus repo manager
[
https://issues.apache.org/jira/browse/SUREFIRE-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472324#comment-17472324
]
BRENT RYAN commented on SUREFIRE-1971:
--
Our project is not public.
I've only been able to
[
https://issues.apache.org/jira/browse/MNG-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472319#comment-17472319
]
Thomas Skjølberg commented on MNG-7389:
---
Thanks for the input, your suggested solution seems
[
https://issues.apache.org/jira/browse/MPLUGIN-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated MPLUGIN-387:
Description:
- Upgrade plexus-component-metadata to 2.1.1
- Upgrade ASM to 9.2
[
https://issues.apache.org/jira/browse/MNG-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472291#comment-17472291
]
Michael Osipov edited comment on MNG-7386 at 1/10/22, 8:49 PM:
---
That would
[
https://issues.apache.org/jira/browse/MNG-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472291#comment-17472291
]
Michael Osipov commented on MNG-7386:
-
That would mean that {{asList()}} should removed.
>
[
https://issues.apache.org/jira/browse/MNG-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472288#comment-17472288
]
Robert Scholte commented on MNG-7386:
-
AFAIK creating new ArrayLists over and over again is kind of
[
https://issues.apache.org/jira/browse/MNG-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472279#comment-17472279
]
Michael Osipov edited comment on MNG-7389 at 1/10/22, 8:26 PM:
---
Using atime
[
https://issues.apache.org/jira/browse/MNG-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472279#comment-17472279
]
Michael Osipov commented on MNG-7389:
-
Using atime is stupid because using atime has a very severe
[
https://issues.apache.org/jira/browse/MNG-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472273#comment-17472273
]
Michael Osipov commented on MNG-7386:
-
This will likely work as well, but would like to here someone
[
https://issues.apache.org/jira/browse/MNG-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472217#comment-17472217
]
Thomas Skjølberg commented on MNG-7389:
---
The CI knows when to clean the cache, but has no good way to
electrum commented on issue #576:
URL: https://github.com/apache/maven-mvnd/issues/576#issuecomment-1009207149
What are some examples of options that would allow reusing a daemon? I can
see that treating `-Xmx` as a minimum would allow reuse (the existing daemon
has a larger max heap),
[
https://issues.apache.org/jira/browse/MNG-7362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472199#comment-17472199
]
Herve Boutemy commented on MNG-7362:
[~khmarbaise] it seems it's a personal debug message that you
[
https://issues.apache.org/jira/browse/MENFORCER-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Forrest Feaser updated MENFORCER-411:
-
Description:
It would be nice if the standard RequireSameVersions rule could search
[
https://issues.apache.org/jira/browse/MENFORCER-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Forrest Feaser updated MENFORCER-411:
-
Description:
It would be nice if the standard RequireSameVersions rule could search
fdfea edited a comment on pull request #135:
URL: https://github.com/apache/maven-enforcer/pull/135#issuecomment-1009180782
It would be nice to have some more descriptive error messages (so you know
where the conflict is coming from). Also wondering if it would make more sense
to make the
fdfea commented on pull request #135:
URL: https://github.com/apache/maven-enforcer/pull/135#issuecomment-1009180782
It would be nice to have some more descriptive error messages. Also
wondering if it would make more sense to make the DependencyConvergence rule
accept of a list of
[
https://issues.apache.org/jira/browse/MENFORCER-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Forrest Feaser updated MENFORCER-411:
-
Description:
It would be nice if the standard RequireSameVersions rule could search
[
https://issues.apache.org/jira/browse/MENFORCER-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Forrest Feaser updated MENFORCER-411:
-
Description:
It would be nice if the standard RequireSameVersions rule could search
fdfea opened a new pull request #135:
URL: https://github.com/apache/maven-enforcer/pull/135
…encies
Following this checklist to help us incorporate your
contribution quickly and easily:
- [ ] Make sure there is a [JIRA
Forrest Feaser created MENFORCER-411:
Summary: RequireSameVersions should search transitive dependencies
Key: MENFORCER-411
URL: https://issues.apache.org/jira/browse/MENFORCER-411
Project: Maven
jglick opened a new issue #579:
URL: https://github.com/apache/maven-mvnd/issues/579
While trying to use mvnd from my IDE
(https://github.com/apache/netbeans/pull/3210) I found that #420 seems to have
broken some mojos:
```console
$ gh repo clone
[
https://issues.apache.org/jira/browse/MNG-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472155#comment-17472155
]
Michael Osipov commented on MNG-7389:
-
I still don't understand why we should clean up something for CI
dependabot[bot] opened a new pull request #61:
URL: https://github.com/apache/maven-plugin-tools/pull/61
Bumps
[extra-enforcer-rules](https://github.com/mojohaus/extra-enforcer-rules) from
1.3 to 1.5.1.
Release notes
Sourced from
gnodet edited a comment on pull request #10:
URL:
https://github.com/apache/maven-clean-plugin/pull/10#issuecomment-1009093211
> When can this happen? I mean, can we create a junction in Java without
using native code?
I'm going to experiment with something like:
```
gnodet commented on pull request #10:
URL:
https://github.com/apache/maven-clean-plugin/pull/10#issuecomment-1009093211
> When can this happen? I mean, can we create a junction in Java without
using native code?
I'm experimenting with something like:
```
Path testDir
gnodet commented on a change in pull request #10:
URL: https://github.com/apache/maven-clean-plugin/pull/10#discussion_r781361531
##
File path: src/main/java/org/apache/maven/plugins/clean/Cleaner.java
##
@@ -297,6 +299,12 @@ else if ( file.exists() )
return result;
kwin commented on pull request #283:
URL: https://github.com/apache/maven-site/pull/283#issuecomment-1009072195
For me and some others it does, but feel free to refine in a follow-up. Is
there anything wrong or worse with this PR compared to the current status quo?
If not, maybe this can
[
https://issues.apache.org/jira/browse/MPLUGIN-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated MPLUGIN-387:
-
Fix Version/s: 3.6.4
> Upgrade dependencies
>
>
>
[
https://issues.apache.org/jira/browse/MPLUGIN-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz closed MPLUGIN-387.
Resolution: Fixed
> Upgrade dependencies
>
>
>
[
https://issues.apache.org/jira/browse/MNG-7349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472143#comment-17472143
]
Michael Osipov commented on MNG-7349:
-
Do you want to provide a PR for that?
> Superfluous relocation
[
https://issues.apache.org/jira/browse/MPLUGIN-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472142#comment-17472142
]
ASF GitHub Bot commented on MPLUGIN-387:
slachiewicz merged pull request #60:
URL:
[
https://issues.apache.org/jira/browse/MPLUGIN-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz reassigned MPLUGIN-387:
Assignee: Sylwester Lachiewicz
> Upgrade dependencies
>
[
https://issues.apache.org/jira/browse/MNG-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472140#comment-17472140
]
Michael Osipov commented on MNG-7388:
-
Expect Maven 5 to be very far away.
> Support Java
slachiewicz merged pull request #60:
URL: https://github.com/apache/maven-plugin-tools/pull/60
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
[
https://issues.apache.org/jira/browse/MNG-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472139#comment-17472139
]
Konrad Windszus commented on MNG-7388:
--
i personally don't need an intermediate solution. It is more
[
https://issues.apache.org/jira/browse/MNG-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472137#comment-17472137
]
Michael Osipov commented on MNG-7388:
-
True, but as intermediate solution it is acceptable, no?
>
michael-o commented on pull request #655:
URL: https://github.com/apache/maven/pull/655#issuecomment-1009041375
> > > > I have a counter/additional proposal as well:
> > > >
> > > > 1. Log a warning when MT build is requested, but only one module is
in the reactor. Hence, MT build
michael-o commented on a change in pull request #10:
URL: https://github.com/apache/maven-clean-plugin/pull/10#discussion_r781335089
##
File path: src/main/java/org/apache/maven/plugins/clean/Cleaner.java
##
@@ -297,6 +299,12 @@ else if ( file.exists() )
return
gnodet commented on pull request #10:
URL:
https://github.com/apache/maven-clean-plugin/pull/10#issuecomment-1009030242
I'm investigating if I can setup a test on windows. I've been sidetracked
by trying to switch the tests to junit 5 / plexus-testing, but it's missing the
helper
gnodet commented on pull request #655:
URL: https://github.com/apache/maven/pull/655#issuecomment-1009028105
> > > I have a counter/additional proposal as well:
> > >
> > > 1. Log a warning when MT build is requested, but only one module is in
the reactor. Hence, MT build is
famod commented on pull request #655:
URL: https://github.com/apache/maven/pull/655#issuecomment-1008962715
> > @michael-o
> > > ```
> > > 1. Log a warning when MT build is requested, but only one module is in
the reactor. Hence, MT build is pointless.
> > > ```
> >
> >
[
https://issues.apache.org/jira/browse/MNG-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472093#comment-17472093
]
Thomas Skjølberg commented on MNG-7389:
---
[~michael-o] please elaborate. Is the dependencies component
[
https://issues.apache.org/jira/browse/MCLEAN-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472088#comment-17472088
]
Hudson commented on MCLEAN-95:
--
Build succeeded in Jenkins: Maven » Maven TLP » maven-clean-plugin » master
gnodet opened a new pull request #10:
URL: https://github.com/apache/maven-clean-plugin/pull/10
[MCLEAN-93](https://issues.apache.org/jira/projects/MCLEAN/issues/MCLEAN-93)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
[
https://issues.apache.org/jira/browse/MNG-7362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472082#comment-17472082
]
Robert Scholte commented on MNG-7362:
-
So here's the weird thing: even though it is in the (maven2)
[
https://issues.apache.org/jira/browse/MNG-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472079#comment-17472079
]
Michael Osipov commented on MNG-7389:
-
I don't understand why you are explicitly requesting from us.
>
michael-o edited a comment on pull request #655:
URL: https://github.com/apache/maven/pull/655#issuecomment-1008942113
> With Guillaume's comment it looks like the warning can just be dropped at
runtime and should be moved to plugin developer side only if not explicitly set
so users will
michael-o commented on pull request #655:
URL: https://github.com/apache/maven/pull/655#issuecomment-1008942113
> With Guillaume's comment it looks like the warning can just be dropped at
runtime and should be moved to plugin developer side only if not explicitly set
so users will be
michael-o commented on pull request #655:
URL: https://github.com/apache/maven/pull/655#issuecomment-1008941405
> > I have a counter/additional proposal as well:
> >
> > 1. Log a warning when MT build is requested, but only one module is in
the reactor. Hence, MT build is pointless.
[
https://issues.apache.org/jira/browse/MCLEAN-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MCLEAN-95.
-
Resolution: Fixed
> Provide a fast deletion option
> --
>
>
[
https://issues.apache.org/jira/browse/MCLEAN-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated MCLEAN-95:
--
Issue Type: New Feature (was: Improvement)
> Provide a fast deletion option
>
[
https://issues.apache.org/jira/browse/MCLEAN-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated MCLEAN-95:
--
Fix Version/s: 3.1.1
> Provide a fast deletion option
> --
>
>
gnodet merged pull request #6:
URL: https://github.com/apache/maven-clean-plugin/pull/6
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
michael-o commented on pull request #655:
URL: https://github.com/apache/maven/pull/655#issuecomment-1008937148
@famod I have checked option 2 and I see that in `MavenCli` the builder id
is set based on the `-T` option being available. Since the reactor is not
available at that point, at
[
https://issues.apache.org/jira/browse/MNG-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472047#comment-17472047
]
Kostiantyn Liutovych commented on MNG-7386:
---
I think this fix would work for us. I do not have a
[
https://issues.apache.org/jira/browse/MNG-7349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472045#comment-17472045
]
Joep Weijers commented on MNG-7349:
---
I do think so, cause then the check is only done on the actual
[
https://issues.apache.org/jira/browse/MNG-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472042#comment-17472042
]
Konrad Windszus commented on MNG-7388:
--
Using enforcer would require every consumer build to
rmannibucau commented on pull request #655:
URL: https://github.com/apache/maven/pull/655#issuecomment-1008894943
@famod you are likely right but it still means we pollute thousands of
people instead of one for something which is 1. generally not hurting and 2.
can likely not be fixed
gnodet commented on issue #570:
URL: https://github.com/apache/maven-mvnd/issues/570#issuecomment-1008870741
So mvnd speeds up by
* enabling concurrent build by default
* cacheing a few things and help speeding up the time spent by maven
*itself* when loading the poms, the
gnodet closed issue #570:
URL: https://github.com/apache/maven-mvnd/issues/570
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
gnodet commented on issue #578:
URL: https://github.com/apache/maven-mvnd/issues/578#issuecomment-1008864823
In addition to the daemon log pointed by @ppalaga , you can enable logging
on the client using
```
MAVEN_OPTS="-DconsoleLevel=trace" mvnd.sh -v
```
--
This is an
michael-o commented on pull request #655:
URL: https://github.com/apache/maven/pull/655#issuecomment-1008859591
> @michael-o
>
> > ```
> > 1. Log a warning when MT build is requested, but only one module is in
the reactor. Hence, MT build is pointless.
> > ```
>
>
ppalaga commented on issue #578:
URL: https://github.com/apache/maven-mvnd/issues/578#issuecomment-1008858262
You may want to check the logs in `~/.m2/mvnd/registry//`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
gnodet commented on pull request #655:
URL: https://github.com/apache/maven/pull/655#issuecomment-1008855386
> I have a counter/additional proposal as well:
>
> 1. Log a warning when MT build is requested, but only one module is in the
reactor. Hence, MT build is pointless.
> 2.
chicobento commented on issue #496:
URL: https://github.com/apache/maven-mvnd/issues/496#issuecomment-1008854691
Sounds perfect. That was exactly what I was hoping for
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
[
https://issues.apache.org/jira/browse/MNG-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471967#comment-17471967
]
Michael Osipov edited comment on MNG-7386 at 1/10/22, 12:48 PM:
This the
[
https://issues.apache.org/jira/browse/MNG-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471967#comment-17471967
]
Michael Osipov edited comment on MNG-7386 at 1/10/22, 12:48 PM:
This the
hualr opened a new issue #578:
URL: https://github.com/apache/maven-mvnd/issues/578
i cant use mavn-mvnd for the maven daemon can not be connected.why?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to
[
https://issues.apache.org/jira/browse/MNG-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471967#comment-17471967
]
Michael Osipov commented on MNG-7386:
-
This the relevant ctors/methods are package private and the
[
https://issues.apache.org/jira/browse/MNG-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Skjølberg updated MNG-7389:
--
Description:
One or more popular continous integration are unable to properly manage the .m2
Thomas Skjølberg created MNG-7389:
-
Summary: Incremental .m2 cache cleanup for CI
Key: MNG-7389
URL: https://issues.apache.org/jira/browse/MNG-7389
Project: Maven
Issue Type: New Feature
findepi commented on pull request #407:
URL: https://github.com/apache/maven-surefire/pull/407#issuecomment-1008837345
Apologies, I've accidentally removed the test exclusion with TestNG 5 on JDK
17, so inevitably the build was failing. Brought it back now. The build is
green in my fork
hashhar commented on a change in pull request #577:
URL: https://github.com/apache/maven-mvnd/pull/577#discussion_r781141901
##
File path: common/src/main/java/org/mvndaemon/mvnd/common/Environment.java
##
@@ -209,7 +209,7 @@
/**
* The -Xmx value to pass to the
hashhar opened a new pull request #577:
URL: https://github.com/apache/maven-mvnd/pull/577
Let the JVM decide the max heap size instead of using hardcoded defaults
to match the behaviour of vanilla Maven.
Fixes https://github.com/apache/maven-mvnd/issues/560
I tried adding
famod commented on pull request #655:
URL: https://github.com/apache/maven/pull/655#issuecomment-1008802283
Ok, you mean extending the locking logic? Might work.
I was referring to the current state of affairs.
Not sure if there should then still be a message for users. Some
conderls commented on issue #570:
URL: https://github.com/apache/maven-mvnd/issues/570#issuecomment-1008796157
>
by default, I turned off test during compiling and packaging by
```xml
true
true
true
```
[
https://issues.apache.org/jira/browse/MNG-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471901#comment-17471901
]
Michael Osipov commented on MNG-5512:
-
Regarding login failures: Wagon HTTP Provider WILL throw an
1 - 100 of 158 matches
Mail list logo
