[
https://issues.apache.org/jira/browse/MWRAPPER-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MWRAPPER-35:
--
Fix Version/s: 3.1.0
> don't copy mvnwDebug* scripts by default
>
Herve Boutemy created MWRAPPER-35:
-
Summary: don't copy mvnwDebug* scripts by default
Key: MWRAPPER-35
URL: https://issues.apache.org/jira/browse/MWRAPPER-35
Project: Maven Wrapper
Issue
[
https://issues.apache.org/jira/browse/MWRAPPER-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456196#comment-17456196
]
Herve Boutemy commented on MWRAPPER-32:
---
isn't PR#5 a working first step?
> Use Maven core
[
https://issues.apache.org/jira/browse/MWRAPPER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MWRAPPER-16:
--
Fix Version/s: 3.2.0
> update mvnw scripts to launch target Maven mvn scripts, to enforce
[
https://issues.apache.org/jira/browse/MWRAPPER-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MWRAPPER-32:
--
Fix Version/s: 3.1.0
> Use Maven core component in provided scope
>
[
https://issues.apache.org/jira/browse/MWRAPPER-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MWRAPPER-34:
--
Description:
consistent with Maven 3.3.1+ https://maven.apache.org/docs/history.html
Java 7
michael-o commented on pull request #631:
URL: https://github.com/apache/maven/pull/631#issuecomment-989575866
>
All lower: https://github.com/apache/maven-site/tree/master/content/markdown
I don't know where you have the uppercase convention from, but as far as I
know this
[
https://issues.apache.org/jira/browse/MWRAPPER-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456182#comment-17456182
]
Herve Boutemy commented on MWRAPPER-33:
---
I'm not a fan of forcing people to upgrade if not
slachiewicz closed pull request #78:
URL: https://github.com/apache/maven-compiler-plugin/pull/78
--
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:
dependabot[bot] commented on pull request #78:
URL:
https://github.com/apache/maven-compiler-plugin/pull/78#issuecomment-989429266
OK, I won't notify you again about this release, but will get in touch when
a new version is available. You can also ignore all major, minor, or patch
slachiewicz merged pull request #70:
URL: https://github.com/apache/maven-compiler-plugin/pull/70
--
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:
slachiewicz merged pull request #71:
URL: https://github.com/apache/maven-compiler-plugin/pull/71
--
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:
slachiewicz merged pull request #77:
URL: https://github.com/apache/maven-compiler-plugin/pull/77
--
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:
dependabot[bot] commented on pull request #176:
URL:
https://github.com/apache/maven-dependency-plugin/pull/176#issuecomment-989426323
OK, I won't notify you again about this release, but will get in touch when
a new version is available. You can also ignore all major, minor, or patch
slachiewicz closed pull request #176:
URL: https://github.com/apache/maven-dependency-plugin/pull/176
--
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,
[
https://issues.apache.org/jira/browse/MSHARED-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz reassigned MSHARED-687:
Assignee: (was: Guillaume Boué)
> Programmatic read-only access to
slachiewicz merged pull request #4:
URL: https://github.com/apache/maven-wrapper/pull/4
--
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:
AlexanderAshitkin opened a new pull request #633:
URL: https://github.com/apache/maven/pull/633
The idea is to replace glob section with glob/pattern based includes
excludes to form determenistic files set.
Current implementtation with glob might be not flexible and expressive
enough.
[
https://issues.apache.org/jira/browse/MWRAPPER-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456017#comment-17456017
]
Slawomir Jaranowski commented on MWRAPPER-33:
-
I'm not sure if support for java < 8 is
AlexanderAshitkin commented on a change in pull request #631:
URL: https://github.com/apache/maven/pull/631#discussion_r765269522
##
File path: maven-caching-extension/src/site/markdown/GETTING-STARTED.md
##
@@ -0,0 +1,69 @@
+
+
+## Getting Started
+
+To on-board incremental
Herve Boutemy created MWRAPPER-34:
-
Summary: use Java 7 for maven-wrapper-plugin and maven-wrapper.jar
Key: MWRAPPER-34
URL: https://issues.apache.org/jira/browse/MWRAPPER-34
Project: Maven Wrapper
[
https://issues.apache.org/jira/browse/MWRAPPER-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17455993#comment-17455993
]
Herve Boutemy commented on MWRAPPER-33:
---
I'll do a first step with plugin in Java 7 and wrapper in
[
https://issues.apache.org/jira/browse/MWRAPPER-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MWRAPPER-33:
--
Fix Version/s: 3.2.0
> Use java 8 in maven-wrapper
> ---
>
>
[
https://issues.apache.org/jira/browse/MWRAPPER-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MWRAPPER-33:
--
Affects Version/s: 3.1.0
> Use java 8 in maven-wrapper
> ---
>
>
slachiewicz merged pull request #3:
URL: https://github.com/apache/maven-wrapper/pull/3
--
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/MWRAPPER-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated MWRAPPER-33:
Description:
Currently {{maven-wrapper}} use java {*}5{*}.
It blocks build
[
https://issues.apache.org/jira/browse/MWRAPPER-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated MWRAPPER-32:
Component/s: Maven Wrapper Plugin
> Use Maven core component in provided scope
>
hiljusti edited a comment on pull request #72:
URL: https://github.com/apache/maven-wagon/pull/72#issuecomment-989117811
As a note: My (minor) issue could have benefited from this:
https://issues.apache.org/jira/browse/MDEPLOY-289
The summary is our enterprise (amazon) used custom
hiljusti commented on pull request #72:
URL: https://github.com/apache/maven-wagon/pull/72#issuecomment-989117811
As a note: My (minor) issue could have benefited from this:
https://issues.apache.org/jira/browse/MDEPLOY-289
The summary is a custom maven repository proxy, where it
Slawomir Jaranowski created MWRAPPER-33:
---
Summary: Use java 8 in maven-wrapper
Key: MWRAPPER-33
URL: https://issues.apache.org/jira/browse/MWRAPPER-33
Project: Maven Wrapper
Issue
Slawomir Jaranowski created MWRAPPER-32:
---
Summary: Use Maven core component in provided scope
Key: MWRAPPER-32
URL: https://issues.apache.org/jira/browse/MWRAPPER-32
Project: Maven Wrapper
[
https://issues.apache.org/jira/browse/MSITE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSITE-876:
-
Fix Version/s: (was: 3.10.0)
> Execution default-deploy of goal ...deploy failed: An API
[
https://issues.apache.org/jira/browse/MSITE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MSITE-876:
Assignee: (was: Michael Osipov)
> Execution default-deploy of goal ...deploy failed:
[
https://issues.apache.org/jira/browse/MWRAPPER-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17455924#comment-17455924
]
Slawomir Jaranowski commented on MWRAPPER-31:
-
I will do it.
> Get rid of
Slawomir Jaranowski created MWRAPPER-31:
---
Summary: Get rid of maven-artifact-transfer
Key: MWRAPPER-31
URL: https://issues.apache.org/jira/browse/MWRAPPER-31
Project: Maven Wrapper
slawekjaranowski commented on pull request #1:
URL: https://github.com/apache/maven-wrapper/pull/1#issuecomment-989039486
your welcome
--
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
[
https://issues.apache.org/jira/browse/MWRAPPER-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MWRAPPER-27:
--
Priority: Minor (was: Major)
> rework mvnw* scripts to better match mvn* from Maven 3.8
>
[
https://issues.apache.org/jira/browse/MWRAPPER-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MWRAPPER-25:
--
Priority: Minor (was: Major)
> fix installer messages
> --
>
>
[
https://issues.apache.org/jira/browse/MWRAPPER-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MWRAPPER-24:
--
Priority: Minor (was: Major)
> mvnw calls which(1) which is an external command
>
[
https://issues.apache.org/jira/browse/MWRAPPER-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MWRAPPER-30.
-
Fix Version/s: 3.1.0
Assignee: Herve Boutemy
Resolution: Fixed
merged in
[
https://issues.apache.org/jira/browse/MWRAPPER-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MWRAPPER-30:
--
Priority: Minor (was: Major)
> Add help mojo
> -
>
> Key:
[
https://issues.apache.org/jira/browse/MWRAPPER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MWRAPPER-29.
-
Fix Version/s: 3.1.0
Assignee: Herve Boutemy
Resolution: Fixed
merged in
hboutemy merged pull request #2:
URL: https://github.com/apache/maven-wrapper/pull/2
--
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:
hboutemy commented on pull request #1:
URL: https://github.com/apache/maven-wrapper/pull/1#issuecomment-989029965
nice fix: thanks a lot
--
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
hboutemy merged pull request #1:
URL: https://github.com/apache/maven-wrapper/pull/1
--
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:
dependabot[bot] opened a new pull request #25:
URL: https://github.com/apache/maven-filtering/pull/25
Bumps [plexus-utils](https://github.com/codehaus-plexus/plexus-utils) from
3.3.0 to 3.4.1.
Release notes
Sourced from
[
https://issues.apache.org/jira/browse/MWRAPPER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated MWRAPPER-29:
Summary: Project should build successfully with verify lifecycle (was:
Project
dependabot[bot] opened a new pull request #129:
URL: https://github.com/apache/maven-enforcer/pull/129
Bumps [mrm-maven-plugin](https://github.com/mojohaus/mrm) from 1.2.0 to
1.3.0.
Release notes
Sourced from https://github.com/mojohaus/mrm/releases;>mrm-maven-plugin's
releases.
[
https://issues.apache.org/jira/browse/MWRAPPER-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17455305#comment-17455305
]
Slawomir Jaranowski commented on MWRAPPER-30:
-
PR:
[
https://issues.apache.org/jira/browse/MWRAPPER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17455301#comment-17455301
]
Slawomir Jaranowski commented on MWRAPPER-29:
-
PR:
[
https://issues.apache.org/jira/browse/MRESOURCES-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17454788#comment-17454788
]
Jimisola Laursen edited comment on MRESOURCES-237 at 12/8/21, 1:22 PM:
[
https://issues.apache.org/jira/browse/MRESOURCES-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17455231#comment-17455231
]
Jimisola Laursen commented on MRESOURCES-269:
-
[~slachiewicz] It does not work for me.
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17455216#comment-17455216
]
Patrick Ruckstuhl commented on MDEP-753:
Do I see this correct that the actual issue would be fixed
rmannibucau commented on pull request #632:
URL: https://github.com/apache/maven/pull/632#issuecomment-988696241
@kwin not sure, `--fail-never` will ignore the exception and `--fail-at-end`
will stack it to fail after other modules build so MojoXXXExceptons never bring
anything in this
kwin commented on pull request #632:
URL: https://github.com/apache/maven/pull/632#issuecomment-988694442
> Overall the need of these exception is that mojo don't throw an
Exception/Throwable but there is no technical reason
I think the reason is to throw an exception which would
rmannibucau commented on pull request #632:
URL: https://github.com/apache/maven/pull/632#issuecomment-988675286
My understanding was that MojoExecutionException is a wrapper around another
exception as primary usage whereas MojoFailureException is a root exception by
itself (and previous
gnodet edited a comment on pull request #632:
URL: https://github.com/apache/maven/pull/632#issuecomment-988654452
> Dug a bit deeper and found
>
>
gnodet commented on pull request #632:
URL: https://github.com/apache/maven/pull/632#issuecomment-988654452
> Dug a bit deeper and found
>
>
kwin commented on pull request #632:
URL: https://github.com/apache/maven/pull/632#issuecomment-988638938
Dug a bit deeper and found
https://github.com/apache/maven/blob/ed370a6382ee4e431d36ae38454174b94d4f33aa/maven-core/src/main/java/org/apache/maven/DefaultMaven.java#L235-L255
for the
kwin edited a comment on pull request #632:
URL: https://github.com/apache/maven/pull/632#issuecomment-988618617
I tried it out with a dummy mojo and both exceptions behave exactly the
same, i.e. both emit "BUILD FAILURE". I couldn't influence the build outcome
with any of the
kwin edited a comment on pull request #632:
URL: https://github.com/apache/maven/pull/632#issuecomment-988618617
I tried it out with a dummy mojo and both exceptions behave exactly the
same, i.e. both emit "BUILD FAILURE". I couldn't influence the build outcome
with any of the
kwin commented on pull request #632:
URL: https://github.com/apache/maven/pull/632#issuecomment-988624535
Given that, I would recommend to either reestablish the different semantics
or deprecate one exception class of the two. In any case right now it is highly
confusing why there are two
kwin commented on pull request #632:
URL: https://github.com/apache/maven/pull/632#issuecomment-988618617
I tried it out with a dummy mojo and both exceptions behave exactly the
same, i.e. both emit "BUILD FAILURE". I couldn't influence the build outcome
with any of the `--fail-xxx`
[
https://issues.apache.org/jira/browse/MNG-7354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17455049#comment-17455049
]
Michael Osipov commented on MNG-7354:
-
I am excited to see what exactly needs to be done...
> Refactor
kwin commented on pull request #632:
URL: https://github.com/apache/maven/pull/632#issuecomment-988594671
@gnodet Indeed I couldn't find anything either yet. TBH I have just taken
the information from
65 matches
Mail list logo
