[
https://issues.apache.org/jira/browse/MNG-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471741#comment-17471741
]
Hudson commented on MNG-7217:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » maven-3.8
[
https://issues.apache.org/jira/browse/MNG-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471745#comment-17471745
]
Tuure Laurinolli edited comment on MNG-5974 at 1/10/22, 8:08 AM:
[
https://issues.apache.org/jira/browse/MNG-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471745#comment-17471745
]
Tuure Laurinolli commented on MNG-5974:
---
Valid in what sense?
The description is acc
[
https://issues.apache.org/jira/browse/MNG-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471745#comment-17471745
]
Tuure Laurinolli edited comment on MNG-5974 at 1/10/22, 8:09 AM:
[
https://issues.apache.org/jira/browse/MNG-7387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maarten Mulders closed MNG-7387.
Resolution: Duplicate
Repeating myself here, but:
{quote}A dependency being downloaded and stored on
gnodet commented on issue #541:
URL: https://github.com/apache/maven-mvnd/issues/541#issuecomment-1008630146
Interactions using the keyboard are currently only supported for maven
plugins which use the plexus interaction layer. The `System.in` input stream
is currently not redefined on th
[
https://issues.apache.org/jira/browse/MNG-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-5974:
Affects Version/s: 3.8.4
> ComparableVersion fails with semver.org-style milestone versions
> ---
[
https://issues.apache.org/jira/browse/MNG-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-5974:
Fix Version/s: (was: waiting-for-feedback)
> ComparableVersion fails with semver.org-style milest
[
https://issues.apache.org/jira/browse/MNG-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471756#comment-17471756
]
Michael Osipov commented on MNG-7386:
-
What about 3.8.4?
> ModelMerger$MergingList is
slachiewicz merged pull request #67:
URL: https://github.com/apache/maven-site-plugin/pull/67
--
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: issu
gnodet edited a comment on issue #541:
URL: https://github.com/apache/maven-mvnd/issues/541#issuecomment-1008630146
Interactions using the keyboard are currently only supported for maven
plugins which use the plexus interaction layer. The `System.in` input stream
is currently not redefine
kwin commented on pull request #283:
URL: https://github.com/apache/maven-site/pull/283#issuecomment-1008637870
bq. I consider anything Maven 2 related useless.
This paragraph has been there before, and is actually to stress the point
that the semantics used to be different (for the
kwin edited a comment on pull request #283:
URL: https://github.com/apache/maven-site/pull/283#issuecomment-1008637870
> I consider anything Maven 2 related useless.
This paragraph has been there before, and is actually to stress the point
that the semantics used to be different (for
michael-o commented on pull request #283:
URL: https://github.com/apache/maven-site/pull/283#issuecomment-1008640408
> > I consider anything Maven 2 related useless.
>
> This paragraph has been there before, and is actually to stress the point
that the semantics used to be different
[
https://issues.apache.org/jira/browse/MNG-7387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471763#comment-17471763
]
Tharanadha K commented on MNG-7387:
---
Thank You Maarten for your quick response. We have c
[
https://issues.apache.org/jira/browse/MNG-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471766#comment-17471766
]
Piotr Zygielo commented on MNG-5974:
the current [https://maven.apache.org/pom.html#ver
[
https://issues.apache.org/jira/browse/MNG-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated MNG-7388:
-
Summary: Support Java prerequisites for packaging "maven-plugin" (was: Add
java prerequisites for
Konrad Windszus created MNG-7388:
Summary: Add java prerequisites for packaging "maven-plugin"
Key: MNG-7388
URL: https://issues.apache.org/jira/browse/MNG-7388
Project: Maven
Issue Type: Imp
[
https://issues.apache.org/jira/browse/MNG-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471775#comment-17471775
]
Markus Heberling commented on MNG-7386:
---
3.8.4 is also affected.
{code:java}
[Run
[
https://issues.apache.org/jira/browse/MNG-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7386:
Affects Version/s: 3.8.4
> ModelMerger$MergingList is not serializable
>
[
https://issues.apache.org/jira/browse/MNG-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471781#comment-17471781
]
Michael Osipov commented on MNG-7386:
-
Maybe the list can be used, but the result wrapp
[
https://issues.apache.org/jira/browse/MNG-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471801#comment-17471801
]
Michael Osipov commented on MNG-7388:
-
I wonder why this is necessary because it if con
[
https://issues.apache.org/jira/browse/MNG-7385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7385:
Fix Version/s: 4.0.0
> Improve documentation on repository metadata
> ---
[
https://issues.apache.org/jira/browse/MNG-7385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7385:
Summary: Improve documentation on repository metadata (was: improve
documentation on repository meta
[
https://issues.apache.org/jira/browse/MNG-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471805#comment-17471805
]
Konrad Windszus edited comment on MNG-7388 at 1/10/22, 9:39 AM:
-
[
https://issues.apache.org/jira/browse/MNG-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471805#comment-17471805
]
Konrad Windszus commented on MNG-7388:
--
IMHO with the separation of Build vs Consumer
[
https://issues.apache.org/jira/browse/MNG-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471805#comment-17471805
]
Konrad Windszus edited comment on MNG-7388 at 1/10/22, 9:41 AM:
-
ppalaga commented on issue #496:
URL: https://github.com/apache/maven-mvnd/issues/496#issuecomment-1008716534
The existing network protocol between mvnd client and the daemon would work
without any change even if daemon runs on a different host. What is missing is
a discovery mechanism fo
[
https://issues.apache.org/jira/browse/MNG-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471835#comment-17471835
]
Michael Osipov commented on MNG-7388:
-
Then this needs to needs to go into the plugin d
[
https://issues.apache.org/jira/browse/MNG-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471838#comment-17471838
]
Konrad Windszus commented on MNG-7388:
--
To be honest I don't care where it ends up (po
conderls commented on issue #570:
URL: https://github.com/apache/maven-mvnd/issues/570#issuecomment-1008721913
I also did a benchmark with two scala projects, which have about 30
subprojects:
- flow-all: without maven-shade-plugin,
- offline-all: with maven-shade-plugin to build **fa
conderls edited a comment on issue #570:
URL: https://github.com/apache/maven-mvnd/issues/570#issuecomment-1008721913
I also did a benchmark with two scala projects, which have about 30
subprojects:
- flow-all: without maven-shade-plugin,
- offline-all: with maven-shade-plugin to bui
[
https://issues.apache.org/jira/browse/MNG-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated MNG-7388:
-
Summary: Support Java prerequisites for Maven plugins (was: Support Java
prerequisites for packagi
gnodet commented on issue #576:
URL: https://github.com/apache/maven-mvnd/issues/576#issuecomment-1008736597
The reason is that `mvnd` is not aware of all possible JVM options and which
one should be discriminating and which one would allow reusing a daemon, so it
only knows about a subset
gnodet edited a comment on issue #571:
URL: https://github.com/apache/maven-mvnd/issues/571#issuecomment-1008594473
This is very weird as your first report indicates the jansi library cannot
be loaded or does not find the `isatty` function, but the second indicates that
it works. The `mvn
[
https://issues.apache.org/jira/browse/MNG-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471852#comment-17471852
]
Sebb commented on MNG-5512:
---
Are you not able to test it yourself?
> Deploy uses passwords that
ppalaga commented on pull request #574:
URL: https://github.com/apache/maven-mvnd/pull/574#issuecomment-1008742971
Thanks a lot for your work, @aalmiray !
> If you feel like release-candidate should be triggered with a tag then we
can update the trigger condition.
Id vote for
gnodet commented on issue #570:
URL: https://github.com/apache/maven-mvnd/issues/570#issuecomment-1008743063
> I also did a benchmark with two scala projects, which have about 30
subprojects:
>
> * flow-all: without maven-shade-plugin,
> * offline-all: with maven-shade-plugin to b
aalmiray commented on pull request #574:
URL: https://github.com/apache/maven-mvnd/pull/574#issuecomment-1008747503
> Id vote for triggering by a tag, but how about the third option: let
release-candidate create the tag itself?
This is of course possible but here I wonder how will th
gnodet commented on issue #570:
URL: https://github.com/apache/maven-mvnd/issues/570#issuecomment-1008750142
> How come the duration for `mvn` is decreasing run after run ?
Well, it doesn't really. At least it's not really meaningful.
Do you have lots of test execution ? `mvnd` is
[
https://issues.apache.org/jira/browse/MNG-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471867#comment-17471867
]
Michael Osipov commented on MNG-5512:
-
Not really, because lack of time and I have neve
gnodet commented on pull request #655:
URL: https://github.com/apache/maven/pull/655#issuecomment-1008755120
> Looks good to me actually, but still would like someone with forked skills
have a look also. @hboutemy
Fwiw, I think with the recent locks addition in
https://github.com/ap
[
https://issues.apache.org/jira/browse/MNG-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471870#comment-17471870
]
Michael Osipov commented on MNG-7388:
-
But this isn't just only the plugin, isn't it? S
[
https://issues.apache.org/jira/browse/MNG-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471874#comment-17471874
]
Konrad Windszus commented on MNG-7388:
--
This issue is only about plugins, but for depe
[
https://issues.apache.org/jira/browse/MNG-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471877#comment-17471877
]
Sebb commented on MNG-5512:
---
Note that there are two errors here:
- not stopping when decryption
michael-o commented on pull request #655:
URL: https://github.com/apache/maven/pull/655#issuecomment-1008761636
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. Don't invo
[
https://issues.apache.org/jira/browse/MNG-7380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MNG-7380:
---
Assignee: Michael Osipov
> Don't log non-threadsafe warning if only building a single module
>
[
https://issues.apache.org/jira/browse/MNG-7380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7380:
Fix Version/s: 4.0.x-candidate
3.8.x-candidate
> Don't log non-threadsafe warning
[
https://issues.apache.org/jira/browse/MNG-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471886#comment-17471886
]
Michael Osipov commented on MNG-7388:
-
Right, let's focus on plugin. Again, have you co
[
https://issues.apache.org/jira/browse/MNG-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471888#comment-17471888
]
Michael Osipov commented on MNG-5512:
-
Yes, but should immediately fail the build. I ag
[
https://issues.apache.org/jira/browse/MNG-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471888#comment-17471888
]
Michael Osipov edited comment on MNG-5512 at 1/10/22, 11:15 AM:
-
famod commented on pull request #655:
URL: https://github.com/apache/maven/pull/655#issuecomment-1008784403
@michael-o
> 1. Log a warning when MT build is requested, but only one module is in
the reactor. Hence, MT build is pointless.
Please don't because with that I would ne
rmannibucau commented on pull request #655:
URL: https://github.com/apache/maven/pull/655#issuecomment-1008784519
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 happy
famod commented on pull request #655:
URL: https://github.com/apache/maven/pull/655#issuecomment-1008786157
> 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 happy wha
famod edited a comment on pull request #655:
URL: https://github.com/apache/maven/pull/655#issuecomment-1008784403
@michael-o
> 1. Log a warning when MT build is requested, but only one module is in
the reactor. Hence, MT build is pointless.
Please don't because with that I w
rmannibucau commented on pull request #655:
URL: https://github.com/apache/maven/pull/655#issuecomment-1008787708
but same applies to mojo, we are able to ensure a not thread safe mojo is
not executed concurrently which means the warning is never relevant to end
users, only to plugin dev s
[
https://issues.apache.org/jira/browse/MNG-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-5512:
Attachment: screenshot-1.png
> Deploy uses passwords that failed decryption; retries even if login fa
[
https://issues.apache.org/jira/browse/MNG-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471896#comment-17471896
]
Michael Osipov commented on MNG-5512:
-
I have just checked the code in master, call tre
[
https://issues.apache.org/jira/browse/MNG-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471901#comment-17471901
]
Michael Osipov commented on MNG-5512:
-
Regarding login failures: Wagon HTTP Provider WI
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
```
![image](https://user-images.githubuse
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 plugin
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 a
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 daemo
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
h
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
[
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
rep
[
https://issues.apache.org/jira/browse/MNG-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471967#comment-17471967
]
Michael Osipov commented on MNG-7386:
-
This the relevant ctors/methods are package priv
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&focusedCommentId=17471967#comment-17471967
]
Michael Osipov edited comment on MNG-7386 at 1/10/22, 12:48 PM:
-
[
https://issues.apache.org/jira/browse/MNG-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471967#comment-17471967
]
Michael Osipov edited comment on MNG-7386 at 1/10/22, 12:48 PM:
-
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 u
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. D
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
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.
> > ```
>
> Please
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 auto
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: issues-unsubscr...@
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 plugins
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 anyw
[
https://issues.apache.org/jira/browse/MNG-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472042#comment-17472042
]
Konrad Windszus commented on MNG-7388:
--
Using enforcer would require every consumer bu
[
https://issues.apache.org/jira/browse/MNG-7349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472045#comment-17472045
]
Joep Weijers commented on MNG-7349:
---
I do think so, cause then the check is only done on
[
https://issues.apache.org/jira/browse/MNG-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472047#comment-17472047
]
Kostiantyn Liutovych commented on MNG-7386:
---
I think this fix would work for us.
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 l
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: issues-uns
[
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
> --
>
>
[
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
> --
>
>
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.
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 happy
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 b
[
https://issues.apache.org/jira/browse/MNG-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472079#comment-17472079
]
Michael Osipov commented on MNG-7389:
-
I don't understand why you are explicitly reques
[
https://issues.apache.org/jira/browse/MNG-7362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472082#comment-17472082
]
Robert Scholte commented on MNG-7362:
-
So here's the weird thing: even though it is in
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/MCLEAN-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472088#comment-17472088
]
Hudson commented on MCLEAN-95:
--
Build succeeded in Jenkins: Maven » Maven TLP » maven-clean-p
[
https://issues.apache.org/jira/browse/MNG-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472093#comment-17472093
]
Thomas Skjølberg commented on MNG-7389:
---
[~michael-o] please elaborate. Is the depend
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.
> > > ```
> >
> >
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 pointles
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 methods
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 result;
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 is
[
https://issues.apache.org/jira/browse/MNG-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472137#comment-17472137
]
Michael Osipov commented on MNG-7388:
-
True, but as intermediate solution it is accepta
1 - 100 of 158 matches
Mail list logo
