[GitHub] [maven-source-plugin] slawekjaranowski merged pull request #7: Add pull request template
slawekjaranowski merged PR #7: URL: https://github.com/apache/maven-source-plugin/pull/7 -- 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...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-integration-testing] gnodet commented on a diff in pull request #178: Use a plugin to download all dependencies to bypass conflict resolution
gnodet commented on code in PR #178: URL: https://github.com/apache/maven-integration-testing/pull/178#discussion_r910721755 ## core-it-support/core-it-bootstrap/pom.xml: ## @@ -19,45 +19,58 @@ specific language governing permissions and limitations under the License. --> - +http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";> 4.0.0 -org.apache.maven.its.bootstrap -maven-it-boostrap -1.0 +org.apache.maven.its +core-it-support +2.1-SNAPSHOT - org.apache.maven.its.bootstrap - group-13 - 1.0 - jar - - Maven Integration Test :: Boostrap :: Group-13 - - - + core-it-bootstrap + maven-plugin + Bootstrap plugin - - org.codehaus.plexus - plexus-utils - 2.0.5 - org.apache.maven maven-plugin-api - 3.1.0 + 3.8.6 org.apache.maven maven-core - 3.1.0 + 3.8.6 - org.apache.maven.plugins - maven-plugin-plugin - 3.6.0 + org.apache.maven.plugin-tools + maven-plugin-annotations + + + org.apache.maven.resolver + maven-resolver-impl + 1.8.0 + + + org.codehaus.plexus + plexus-component-annotations + + + + +org.codehaus.plexus +plexus-component-metadata Review Comment: No need for sisu actually. -- 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...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-integration-testing] michael-o commented on a diff in pull request #178: Use a plugin to download all dependencies to bypass conflict resolution
michael-o commented on code in PR #178: URL: https://github.com/apache/maven-integration-testing/pull/178#discussion_r910744382 ## core-it-support/maven-it-plugin-bootstrap/pom.xml: ## @@ -28,20 +28,25 @@ under the License. 2.1-SNAPSHOT - core-it-bootstrap + maven-it-plugin-bootstrap maven-plugin Bootstrap plugin + +3.8.6 Review Comment: Don't use this pattern. There is an official property `maven.version` which contains the version of the currently running Maven environment. Use, as we do now everywhere for versions camel case: `mavenVersion`. -- 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...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-integration-testing] gnodet commented on a diff in pull request #178: Use a plugin to download all dependencies to bypass conflict resolution
gnodet commented on code in PR #178: URL: https://github.com/apache/maven-integration-testing/pull/178#discussion_r910790998 ## core-it-suite/pom.xml: ## @@ -159,6 +161,42 @@ under the License. + +org.apache.maven.its +core-it-bootstrap Review Comment: Renamed -- 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...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-integration-testing] gnodet commented on a diff in pull request #178: Use a plugin to download all dependencies to bypass conflict resolution
gnodet commented on code in PR #178: URL: https://github.com/apache/maven-integration-testing/pull/178#discussion_r910790998 ## core-it-suite/pom.xml: ## @@ -159,6 +161,42 @@ under the License. + +org.apache.maven.its +core-it-bootstrap Review Comment: Renamed to `maven-it-plugin-bootstrap` as `maven-XXX-plugin` is reserved for plugins in the `org.apache.maven.plugins` groupId. -- 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...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-integration-testing] gnodet commented on a diff in pull request #178: Use a plugin to download all dependencies to bypass conflict resolution
gnodet commented on code in PR #178: URL: https://github.com/apache/maven-integration-testing/pull/178#discussion_r910791967 ## core-it-suite/pom.xml: ## @@ -159,6 +161,42 @@ under the License. + +org.apache.maven.its +core-it-bootstrap +2.1-SNAPSHOT + + +boostrap +process-test-classes Review Comment: Fixed -- 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...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-integration-testing] gnodet commented on a diff in pull request #178: Use a plugin to download all dependencies to bypass conflict resolution
gnodet commented on code in PR #178: URL: https://github.com/apache/maven-integration-testing/pull/178#discussion_r910793570 ## core-it-support/maven-it-plugin-bootstrap/pom.xml: ## @@ -28,20 +28,25 @@ under the License. 2.1-SNAPSHOT - core-it-bootstrap + maven-it-plugin-bootstrap maven-plugin Bootstrap plugin + +3.8.6 Review Comment: Fixed -- 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...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (ARCHETYPE-633) A required class was missing while executing org.apache.maven.plugins:maven-archetype-plugin:3.1.1:generate: org/apache/commons/lang/StringUtils
[ https://issues.apache.org/jira/browse/ARCHETYPE-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17560943#comment-17560943 ] Michael Osipov commented on ARCHETYPE-633: -- Which version? > A required class was missing while executing > org.apache.maven.plugins:maven-archetype-plugin:3.1.1:generate: > org/apache/commons/lang/StringUtils > > > Key: ARCHETYPE-633 > URL: https://issues.apache.org/jira/browse/ARCHETYPE-633 > Project: Maven Archetype > Issue Type: Bug > Environment: any >Reporter: Stefano Fornari >Priority: Major > > This issue seems to be still there. As described in [this SO > article|https://stackoverflow.com/questions/56993067/maven-archetype-plugin-fails-with-classnotfoundexception], > the pom misses a dependency on commons-lang... -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-pmd-plugin] adangel merged pull request #73: [MPMD-345] - Upgrade to PMD 6.47.0
adangel merged PR #73: URL: https://github.com/apache/maven-pmd-plugin/pull/73 -- 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...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MPMD-345) Upgrade to PMD 6.47.0
[ https://issues.apache.org/jira/browse/MPMD-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-345. --- Resolution: Fixed > Upgrade to PMD 6.47.0 > - > > Key: MPMD-345 > URL: https://issues.apache.org/jira/browse/MPMD-345 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.18.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-345) Upgrade to PMD 6.47.0
[ https://issues.apache.org/jira/browse/MPMD-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17560954#comment-17560954 ] Hudson commented on MPMD-345: - Build succeeded in Jenkins: Maven » Maven TLP » maven-pmd-plugin » master #40 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-pmd-plugin/job/master/40/ > Upgrade to PMD 6.47.0 > - > > Key: MPMD-345 > URL: https://issues.apache.org/jira/browse/MPMD-345 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.18.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-integration-testing] michael-o commented on pull request #178: Use a plugin to download all dependencies to bypass conflict resolution
michael-o commented on PR #178: URL: https://github.com/apache/maven-integration-testing/pull/178#issuecomment-1171101155 I digged a little deeper. Basically, those 162 failed projects are require exactly those dependencies which old bootstrap has provided. Change to new bootstrap, run: 162 failures. Remove bootstrap.txt: 162 failures, as if those deps aren't present evaluated. Change to master, disable the Bootstrap test project in the integration suite: 162 failures. I don't understand this. There must be some fundemantal difference which worked before. -- 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...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MPOM-334) Upgrade fluido skin to 1.11.1
Slawomir Jaranowski created MPOM-334: Summary: Upgrade fluido skin to 1.11.1 Key: MPOM-334 URL: https://issues.apache.org/jira/browse/MPOM-334 Project: Maven POMs Issue Type: Dependency upgrade Components: asf Reporter: Slawomir Jaranowski Assignee: Slawomir Jaranowski Fix For: ASF-27 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPOM-334) Upgrade fluido skin to 1.11.1
[ https://issues.apache.org/jira/browse/MPOM-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski updated MPOM-334: - Fix Version/s: MAVEN-37 > Upgrade fluido skin to 1.11.1 > - > > Key: MPOM-334 > URL: https://issues.apache.org/jira/browse/MPOM-334 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: ASF-27, MAVEN-37 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-apache-parent] michael-o commented on pull request #90: [MPOM-334] Upgrade fluido skin to 1.11.1
michael-o commented on PR #90: URL: https://github.com/apache/maven-apache-parent/pull/90#issuecomment-1171167048 Somewhere custom code needs to be removed -- 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...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-integration-testing] michael-o commented on pull request #178: Use a plugin to download all dependencies to bypass conflict resolution
michael-o commented on PR #178: URL: https://github.com/apache/maven-integration-testing/pull/178#issuecomment-1171176532 Yes, it does: https://github.com/apache/maven-integration-testing/blob/0b8a1d613193d73aa02cd703ed59d0e468a8bc6f/core-it-suite/src/test/java/org/apache/maven/it/MavenITBootstrapTest.java#L51 So you need to reinstantiate that IT, but with a single module using you new plugin and the issue should be solved. -- 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...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-mvnd] jglick commented on pull request #616: Maven385
jglick commented on PR #616: URL: https://github.com/apache/maven-mvnd/pull/616#issuecomment-1171203577 Could we get a patch release with 3.8.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-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-apache-parent] slawekjaranowski commented on pull request #90: [MPOM-334] Upgrade fluido skin to 1.11.1
slawekjaranowski commented on PR #90: URL: https://github.com/apache/maven-apache-parent/pull/90#issuecomment-1171299720 Custom code was removed in https://github.com/apache/maven-apache-parent/commit/f1790e455abdba4d781257a192e9e9ec74cd7f06 -- 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...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MWRAPPER-69) MVNW_REPOURL path not considered
Carsten Rohde created MWRAPPER-69:
-
Summary: MVNW_REPOURL path not considered
Key: MWRAPPER-69
URL: https://issues.apache.org/jira/browse/MWRAPPER-69
Project: Maven Wrapper
Issue Type: Bug
Components: Maven Wrapper Jar
Affects Versions: 3.1.1
Environment: Microsoft Windows 10
Reporter: Carsten Rohde
As far as I can see, this is a new bug introduced in 3.1.1
running the plugin with said environment variable set, the plugin correctly
writes the repository url into the maven-wrapper.properties.
using the maven wrapper however, the path part from the url is ignored and just
the protocol://host:port part is used.
Version 3.1.1 (fails)
{code:java}
SET MVNW_REPOURL=http://myrepository.mine/base/path
[INFO] Apache Maven Wrapper 3.1.1
[INFO] Detected MVNW_REPOURL environment variable
http://myrepository.mine/base/path
[INFO] Installing Maven distribution
C:\Users\developer\.m2\wrapper\dists\apache-maven-3.8.1-bin\726df79b
[INFO] Downloading
http://myrepository.mine/org/apache/maven/apache-maven/3.8.1/apache-maven-3.8.1-bin.zip
[WARNING] Using an insecure connection to download the Maven distribution.
Please consider using HTTPS.
Exception in thread "main" java.io.FileNotFoundException:
http://myrepository.mine/org/apache/maven/apache-maven/3.8.1/apache-maven-3.8.1-bin.zip
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1890)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
at
org.apache.maven.wrapper.DefaultDownloader.downloadInternal(DefaultDownloader.java:109)
at
org.apache.maven.wrapper.DefaultDownloader.download(DefaultDownloader.java:97)
at org.apache.maven.wrapper.Installer.createDist(Installer.java:94)
at
org.apache.maven.wrapper.WrapperExecutor.execute(WrapperExecutor.java:151)
at
org.apache.maven.wrapper.MavenWrapperMain.main(MavenWrapperMain.java:76)
{code}
Version 3.1.0 (working)
{code:java}
SET MVNW_REPOURL=http://myrepository.mine/base/path
Found
"C:\_dev\workspaces\git\PickApp\build\deploy\.mvn\wrapper\maven-wrapper.jar"
Apache Maven Wrapper 3.1.0
Detected MVNW_REPOURL environment variable http://myrepository.mine/base/path
Installing Maven distribution
C:\Users\developer\.m2\wrapper\dists\apache-maven-3.8.1-bin\5rncivls3ihmmbfjma6p3gsnss
Downloading
http://myrepository.mine/base/path/org/apache/maven/apache-maven/3.8.1/apache-maven-3.8.1-bin.zip
WARNING Using HTTP Basic Authentication over an insecure connection to download
the Maven distribution. Please consider using HTTPS.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.Unzipping
C:\Users\developer\.m2\wrapper\dists\apache-maven-3.8.1-bin\5rncivls3ihmmbfjma6p3gsnss\apache-maven-3.8.1-bin.zip
to
C:\Users\developer\.m2\wrapper\dists\apache-maven-3.8.1-bin\5rncivls3ihmmbfjma6p3gsnss
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MWRAPPER-69) MVNW_REPOURL path not considered
[
https://issues.apache.org/jira/browse/MWRAPPER-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Rohde updated MWRAPPER-69:
--
Description:
As far as I can see, this is a new bug introduced in 3.1.1
running the plugin with said environment variable set, the plugin correctly
writes the repository url into the maven-wrapper.properties.
using the maven wrapper however, the path part from the url is ignored and just
the protocol://host:port part is used.
Version 3.1.1 (fails)
{code:java}
SET MVNW_REPOURL=http://myrepository.mine/base/path
[INFO] Apache Maven Wrapper 3.1.1
[INFO] Detected MVNW_REPOURL environment variable
http://myrepository.mine/base/path
[INFO] Installing Maven distribution
C:\Users\developer\.m2\wrapper\dists\apache-maven-3.8.1-bin\726df79b
[INFO] Downloading
http://myrepository.mine/org/apache/maven/apache-maven/3.8.1/apache-maven-3.8.1-bin.zip
[WARNING] Using an insecure connection to download the Maven distribution.
Please consider using HTTPS.
Exception in thread "main" java.io.FileNotFoundException:
http://myrepository.mine/org/apache/maven/apache-maven/3.8.1/apache-maven-3.8.1-bin.zip
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1890)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
at
org.apache.maven.wrapper.DefaultDownloader.downloadInternal(DefaultDownloader.java:109)
at
org.apache.maven.wrapper.DefaultDownloader.download(DefaultDownloader.java:97)
at org.apache.maven.wrapper.Installer.createDist(Installer.java:94)
at
org.apache.maven.wrapper.WrapperExecutor.execute(WrapperExecutor.java:151)
at
org.apache.maven.wrapper.MavenWrapperMain.main(MavenWrapperMain.java:76)
{code}
Version 3.1.0 (working)
{code:java}
SET MVNW_REPOURL=http://myrepository.mine/base/path
Apache Maven Wrapper 3.1.0
Detected MVNW_REPOURL environment variable http://myrepository.mine/base/path
Installing Maven distribution
C:\Users\developer\.m2\wrapper\dists\apache-maven-3.8.1-bin\5rncivls3ihmmbfjma6p3gsnss
Downloading
http://myrepository.mine/base/path/org/apache/maven/apache-maven/3.8.1/apache-maven-3.8.1-bin.zip
WARNING Using HTTP Basic Authentication over an insecure connection to download
the Maven distribution. Please consider using HTTPS.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.Unzipping
C:\Users\developer\.m2\wrapper\dists\apache-maven-3.8.1-bin\5rncivls3ihmmbfjma6p3gsnss\apache-maven-3.8.1-bin.zip
to
C:\Users\developer\.m2\wrapper\dists\apache-maven-3.8.1-bin\5rncivls3ihmmbfjma6p3gsnss
{code}
was:
As far as I can see, this is a new bug introduced in 3.1.1
running the plugin with said environment variable set, the plugin correctly
writes the repository url into the maven-wrapper.properties.
using the maven wrapper however, the path part from the url is ignored and just
the protocol://host:port part is used.
Version 3.1.1 (fails)
{code:java}
SET MVNW_REPOURL=http://myrepository.mine/base/path
[INFO] Apache Maven Wrapper 3.1.1
[INFO] Detected MVNW_REPOURL environment variable
http://myrepository.mine/base/path
[INFO] Installing Maven distribution
C:\Users\developer\.m2\wrapper\dists\apache-maven-3.8.1-bin\726df79b
[INFO] Downloading
http://myrepository.mine/org/apache/maven/apache-maven/3.8.1/apache-maven-3.8.1-bin.zip
[WARNING] Using an insecure connection to download the Maven distribution.
Please consider using HTTPS.
Exception in thread "main" java.io.FileNotFoundException:
http://myrepository.mine/org/apache/maven/apache-maven/3.8.1/apache-maven-3.8.1-bin.zip
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1890)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
at
org.apache.maven.wrapper.DefaultDownloader.downloadInternal(DefaultDownloader.java:109)
at
org.apache.maven.wrapper.DefaultDownloader.download(DefaultDownloader.java:97)
at org.apache.maven.wrapper.Installer.createDist(Installer.java:94)
at
org.apache.maven.wrapper.WrapperExecutor.execute(WrapperExecutor.java:151)
at
org.apache.maven.wrapper.MavenWrapperMain.main(MavenWrapperMain.java:76)
{code}
Version 3.1.0 (working)
{code:java}
SET MVNW_REPOURL=http://myrepository.mine/base/path
Found
"C:\_dev\workspaces\git\PickApp\build\deploy\.mvn\wrapper\maven-wrapper.jar"
Apache Maven Wrapper 3.1.0
Detected MVNW_REPOURL environment variable http://myrepository.mine/base/path
Installing Maven distribution
C:\Users\developer\.m2\wrapper\dists\apache-maven-3.8.1-bin\5rncivls3ihmmbfjma6p3gsnss
Downloading
http://myrepository.mine/base/path/org/apache/maven/apache-maven/3.8.1/apache-maven-3.8.1-bin.zip
WARNING Using HTTP Basic Authentication over an insecure connection to download
the Maven distribution. Please consider using HTTPS.
.
.
.
[jira] [Commented] (MWRAPPER-69) MVNW_REPOURL path not considered
[
https://issues.apache.org/jira/browse/MWRAPPER-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561081#comment-17561081
]
Slawomir Jaranowski commented on MWRAPPER-69:
-
I suppose that is the same problem as in MWRAPPER-68
> MVNW_REPOURL path not considered
>
>
> Key: MWRAPPER-69
> URL: https://issues.apache.org/jira/browse/MWRAPPER-69
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Jar
>Affects Versions: 3.1.1
> Environment: Microsoft Windows 10
>Reporter: Carsten Rohde
>Priority: Major
>
> As far as I can see, this is a new bug introduced in 3.1.1
> running the plugin with said environment variable set, the plugin correctly
> writes the repository url into the maven-wrapper.properties.
> using the maven wrapper however, the path part from the url is ignored and
> just the protocol://host:port part is used.
> Version 3.1.1 (fails)
> {code:java}
> SET MVNW_REPOURL=http://myrepository.mine/base/path
> [INFO] Apache Maven Wrapper 3.1.1
> [INFO] Detected MVNW_REPOURL environment variable
> http://myrepository.mine/base/path
> [INFO] Installing Maven distribution
> C:\Users\developer\.m2\wrapper\dists\apache-maven-3.8.1-bin\726df79b
> [INFO] Downloading
> http://myrepository.mine/org/apache/maven/apache-maven/3.8.1/apache-maven-3.8.1-bin.zip
> [WARNING] Using an insecure connection to download the Maven distribution.
> Please consider using HTTPS.
> Exception in thread "main" java.io.FileNotFoundException:
> http://myrepository.mine/org/apache/maven/apache-maven/3.8.1/apache-maven-3.8.1-bin.zip
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1890)
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
> at
> org.apache.maven.wrapper.DefaultDownloader.downloadInternal(DefaultDownloader.java:109)
> at
> org.apache.maven.wrapper.DefaultDownloader.download(DefaultDownloader.java:97)
> at org.apache.maven.wrapper.Installer.createDist(Installer.java:94)
> at
> org.apache.maven.wrapper.WrapperExecutor.execute(WrapperExecutor.java:151)
> at
> org.apache.maven.wrapper.MavenWrapperMain.main(MavenWrapperMain.java:76)
> {code}
>
> Version 3.1.0 (working)
> {code:java}
> SET MVNW_REPOURL=http://myrepository.mine/base/path
> Apache Maven Wrapper 3.1.0
> Detected MVNW_REPOURL environment variable http://myrepository.mine/base/path
> Installing Maven distribution
> C:\Users\developer\.m2\wrapper\dists\apache-maven-3.8.1-bin\5rncivls3ihmmbfjma6p3gsnss
> Downloading
> http://myrepository.mine/base/path/org/apache/maven/apache-maven/3.8.1/apache-maven-3.8.1-bin.zip
> WARNING Using HTTP Basic Authentication over an insecure connection to
> download the Maven distribution. Please consider using HTTPS.
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .Unzipping
> C:\Users\developer\.m2\wrapper\dists\apache-maven-3.8.1-bin\5rncivls3ihmmbfjma6p3gsnss\apache-maven-3.8.1-bin.zip
> to
> C:\Users\developer\.m2\wrapper\dists\apache-maven-3.8.1-bin\5rncivls3ihmmbfjma6p3gsnss
> {code}
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MWRAPPER-69) MVNW_REPOURL path not considered
[
https://issues.apache.org/jira/browse/MWRAPPER-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561084#comment-17561084
]
Carsten Rohde commented on MWRAPPER-69:
---
I agree. Somehow I didn't find MWRAPPER-68 before, sorry!
> MVNW_REPOURL path not considered
>
>
> Key: MWRAPPER-69
> URL: https://issues.apache.org/jira/browse/MWRAPPER-69
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Jar
>Affects Versions: 3.1.1
> Environment: Microsoft Windows 10
>Reporter: Carsten Rohde
>Priority: Major
>
> As far as I can see, this is a new bug introduced in 3.1.1
> running the plugin with said environment variable set, the plugin correctly
> writes the repository url into the maven-wrapper.properties.
> using the maven wrapper however, the path part from the url is ignored and
> just the protocol://host:port part is used.
> Version 3.1.1 (fails)
> {code:java}
> SET MVNW_REPOURL=http://myrepository.mine/base/path
> [INFO] Apache Maven Wrapper 3.1.1
> [INFO] Detected MVNW_REPOURL environment variable
> http://myrepository.mine/base/path
> [INFO] Installing Maven distribution
> C:\Users\developer\.m2\wrapper\dists\apache-maven-3.8.1-bin\726df79b
> [INFO] Downloading
> http://myrepository.mine/org/apache/maven/apache-maven/3.8.1/apache-maven-3.8.1-bin.zip
> [WARNING] Using an insecure connection to download the Maven distribution.
> Please consider using HTTPS.
> Exception in thread "main" java.io.FileNotFoundException:
> http://myrepository.mine/org/apache/maven/apache-maven/3.8.1/apache-maven-3.8.1-bin.zip
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1890)
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
> at
> org.apache.maven.wrapper.DefaultDownloader.downloadInternal(DefaultDownloader.java:109)
> at
> org.apache.maven.wrapper.DefaultDownloader.download(DefaultDownloader.java:97)
> at org.apache.maven.wrapper.Installer.createDist(Installer.java:94)
> at
> org.apache.maven.wrapper.WrapperExecutor.execute(WrapperExecutor.java:151)
> at
> org.apache.maven.wrapper.MavenWrapperMain.main(MavenWrapperMain.java:76)
> {code}
>
> Version 3.1.0 (working)
> {code:java}
> SET MVNW_REPOURL=http://myrepository.mine/base/path
> Apache Maven Wrapper 3.1.0
> Detected MVNW_REPOURL environment variable http://myrepository.mine/base/path
> Installing Maven distribution
> C:\Users\developer\.m2\wrapper\dists\apache-maven-3.8.1-bin\5rncivls3ihmmbfjma6p3gsnss
> Downloading
> http://myrepository.mine/base/path/org/apache/maven/apache-maven/3.8.1/apache-maven-3.8.1-bin.zip
> WARNING Using HTTP Basic Authentication over an insecure connection to
> download the Maven distribution. Please consider using HTTPS.
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .Unzipping
> C:\Users\developer\.m2\wrapper\dists\apache-maven-3.8.1-bin\5rncivls3ihmmbfjma6p3gsnss\apache-maven-3.8.1-bin.zip
> to
> C:\Users\developer\.m2\wrapper\dists\apache-maven-3.8.1-bin\5rncivls3ihmmbfjma6p3gsnss
> {code}
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-apache-parent] slawekjaranowski merged pull request #90: [MPOM-334] Upgrade fluido skin to 1.11.1
slawekjaranowski merged PR #90: URL: https://github.com/apache/maven-apache-parent/pull/90 -- 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...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-parent] slawekjaranowski merged pull request #70: [MPOM-334] Upgrade fluido skin to 1.11.1
slawekjaranowski merged PR #70: URL: https://github.com/apache/maven-parent/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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MPOM-334) Upgrade fluido skin to 1.11.1
[ https://issues.apache.org/jira/browse/MPOM-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MPOM-334. Resolution: Fixed > Upgrade fluido skin to 1.11.1 > - > > Key: MPOM-334 > URL: https://issues.apache.org/jira/browse/MPOM-334 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: ASF-27, MAVEN-37 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPOM-334) Upgrade fluido skin to 1.11.1
[ https://issues.apache.org/jira/browse/MPOM-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561087#comment-17561087 ] Hudson commented on MPOM-334: - Build succeeded in Jenkins: Maven » Maven TLP » maven-parent » master #38 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-parent/job/master/38/ > Upgrade fluido skin to 1.11.1 > - > > Key: MPOM-334 > URL: https://issues.apache.org/jira/browse/MPOM-334 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: ASF-27, MAVEN-37 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPOM-334) Upgrade fluido skin to 1.11.1
[ https://issues.apache.org/jira/browse/MPOM-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561088#comment-17561088 ] Hudson commented on MPOM-334: - Build succeeded in Jenkins: Maven » Maven TLP » maven-apache-parent » master #41 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-apache-parent/job/master/41/ > Upgrade fluido skin to 1.11.1 > - > > Key: MPOM-334 > URL: https://issues.apache.org/jira/browse/MPOM-334 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: ASF-27, MAVEN-37 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-archiver] dependabot[bot] opened a new pull request, #26: Bump plexus-archiver from 1.0-alpha-7 to 3.6.0 in /src/test/resources
dependabot[bot] opened a new pull request, #26: URL: https://github.com/apache/maven-archiver/pull/26 Bumps [plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver) from 1.0-alpha-7 to 3.6.0. Release notes Sourced from https://github.com/codehaus-plexus/plexus-archiver/releases";>plexus-archiver's releases. Plexus Archiver 3.6.0 requires Java 7. :rocket: New features and improvements https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/84";>#84, https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/57";>#57 - Added Archiver implementation (JarToolModularJarArchiver) that creates modular JAR files using the JDK jar tool. The implementation uses java.util.spi.ToolProvider introduced in Java 9, so if it is run on Java 7 or 8 the resulting archive will be identical to a one created by JarArchiver - the module descriptor is not going to be validated and no additional information (such as version, main class and packages) is going to be added. https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/67";>#67 - Added ability to set the module version and main class of a modular JAR file https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/83";>#83 - Added new protected method (postCreateArchive) to AbstractArchiver that is called after the archive is created successfully https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/87";>#87 - of Levan Giguashvili (https://github.com/odinn1984";>@odinn1984) Snyk eng team to fix a possible security issue. (See https://gist.github.com/grnd/eafd7dab7c4cc6197d817a07fa46b2df";>https://gist.github.com/grnd/eafd7dab7c4cc6197d817a07fa46b2df) :bug: Bug Fixes https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/73";>#73 - Symbolic links not properly encoded in ZIP archives https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/57";>#57 - ZipArchiver creates archives with inconsistent central directory entries https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/79";>#79 - JarArchiver and PlexusIoZipFileResourceCollection leak file descriptors :toolbox: Maintenance https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/77";>#77 - Fixed the way unit tests modify the timestamp of a file :package: Dependency updates https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/71";>#71, https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/72";>#72, https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/76";>#76, https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/78";>#78, https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/85";>#85, https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/86";>#86 - Updated dependencies: commons-compress to 1.16.1, plexus-utils to 3.1.0, org.tukaani:xz to 1.8 and plexus-io to 3.0.1 Plexus Archiver 3.5 requires Java 7. Now Plexus Archiver uses pure Java implementations to deal with file attributes so the useJvmChmod is no longer used and it is just ignored. Archiver#setUseJvmChmod, Archiver#isUseJvmChmod(), UnArchiver#setUseJvmChmod, UnArchiver#isUseJvmChmod(), ArchiveEntryUtils#chmod( File, int, Logger, boolean ) and ArchiveEntryUtils#chmod( File, int, Logger ) are deprecated and are subject to removal in a future version. :rocket: New features and improvements https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/51";>#51 - More specific exception for cases when there are no files to archive. Now EmptyArchiveException is thrown when you try to create empty archive. Previously the more generic ArchiverException was thrown. :bug: Bug Fixes https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/47";>#47 - Archiver follows symlinks on Windows https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/53";>#53 - AbstractZipArchiver no longer respects recompressAddedZips https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/58";>#58 - Creates corrupt JARs :package: Dependency updates https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/56";>#56 - Upgrade the minimum required Java version to 7 and Plexus IO to 3.0.0 https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/60";>#60 - Upgrade dependencies. plexus-container-default to 1.0-alpha-30, commons-compress to 1.14, org.tukaani.xz to 1.6 and com.google.code.findbugs.jsr305 to 3.0.2 Plexus Archiver 3.4.1 :rocket: New features and improvements https://github-redirect.dependabot.com/codehaus-plexus/plexu
[GitHub] [maven-integration-testing] gnodet commented on pull request #178: Use a plugin to download all dependencies to bypass conflict resolution
gnodet commented on PR #178: URL: https://github.com/apache/maven-integration-testing/pull/178#issuecomment-1171427649 > Yes, it does: > > https://github.com/apache/maven-integration-testing/blob/0b8a1d613193d73aa02cd703ed59d0e468a8bc6f/core-it-suite/src/test/java/org/apache/maven/it/MavenITBootstrapTest.java#L51 > > So you need to reinstantiate that IT, but with a single module using you new plugin and the issue should be solved. I really don't like the idea of wrapping the download in a fake test. I've pushed a change to force the download from maven central. -- 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...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MNG-7507) Upgrade commons io to 2.7
Peter Bower created MNG-7507: Summary: Upgrade commons io to 2.7 Key: MNG-7507 URL: https://issues.apache.org/jira/browse/MNG-7507 Project: Maven Issue Type: Dependency upgrade Components: Dependencies Affects Versions: 3.8.6 Reporter: Peter Bower Maven 3.8.6 distributes ./apache-maven-3.8.6/lib/commons-io-2.6.jar. This jar is vulnerable to CVE-2021-29425. Are there plans to upgrade to commons io 2.7 in the next version of maven ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-7507) Upgrade commons io to 2.7
[ https://issues.apache.org/jira/browse/MNG-7507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-7507. --- Resolution: Won't Fix Upgrade won't happen. Maven 3.8.x uses Java 7 while Commons IO 2.7 requires Java 8. > Upgrade commons io to 2.7 > - > > Key: MNG-7507 > URL: https://issues.apache.org/jira/browse/MNG-7507 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 3.8.6 >Reporter: Peter Bower >Priority: Major > > Maven 3.8.6 distributes ./apache-maven-3.8.6/lib/commons-io-2.6.jar. This > jar is vulnerable to CVE-2021-29425. > Are there plans to upgrade to commons io 2.7 in the next version of maven ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-integration-testing] gnodet commented on pull request #178: Use a plugin to download all dependencies to bypass conflict resolution
gnodet commented on PR #178: URL: https://github.com/apache/maven-integration-testing/pull/178#issuecomment-1171447619 > > Yes, it does: > > https://github.com/apache/maven-integration-testing/blob/0b8a1d613193d73aa02cd703ed59d0e468a8bc6f/core-it-suite/src/test/java/org/apache/maven/it/MavenITBootstrapTest.java#L51 > > > > So you need to reinstantiate that IT, but with a single module using you new plugin and the issue should be solved. > > I really don't like the idea of wrapping the download in a fake test. I've pushed a change to force the download from maven central. Note that there are quite a few tests that do use the `remote-settings.xml` config, which kinda defeat the original purpose. I can try to update the bootstrap list so that they use the bootstrapped dependencies, but I'd rather merge that one asap. -- 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...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-integration-testing] michael-o commented on pull request #178: Use a plugin to download all dependencies to bypass conflict resolution
michael-o commented on PR #178: URL: https://github.com/apache/maven-integration-testing/pull/178#issuecomment-1171449291 > > > > Yes, it does: > > > https://github.com/apache/maven-integration-testing/blob/0b8a1d613193d73aa02cd703ed59d0e468a8bc6f/core-it-suite/src/test/java/org/apache/maven/it/MavenITBootstrapTest.java#L51 > > > > > > So you need to reinstantiate that IT, but with a single module using you new plugin and the issue should be solved. > > > > > > I really don't like the idea of wrapping the download in a fake test. I've pushed a change to force the download from maven central. > > Note that there are quite a few tests that do use the `remote-settings.xml` config, which kinda defeat the original purpose. I can try to update the bootstrap list so that they use the bootstrapped dependencies, but I'd rather merge that one asap. Don't fiddle with stuff which isn't related. For those there is a separate ticket. Let's focus on this solely on this problem. -- 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...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MWRAPPER-69) MVNW_REPOURL path not considered
[
https://issues.apache.org/jira/browse/MWRAPPER-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski closed MWRAPPER-69.
---
Resolution: Duplicate
> MVNW_REPOURL path not considered
>
>
> Key: MWRAPPER-69
> URL: https://issues.apache.org/jira/browse/MWRAPPER-69
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Jar
>Affects Versions: 3.1.1
> Environment: Microsoft Windows 10
>Reporter: Carsten Rohde
>Priority: Major
>
> As far as I can see, this is a new bug introduced in 3.1.1
> running the plugin with said environment variable set, the plugin correctly
> writes the repository url into the maven-wrapper.properties.
> using the maven wrapper however, the path part from the url is ignored and
> just the protocol://host:port part is used.
> Version 3.1.1 (fails)
> {code:java}
> SET MVNW_REPOURL=http://myrepository.mine/base/path
> [INFO] Apache Maven Wrapper 3.1.1
> [INFO] Detected MVNW_REPOURL environment variable
> http://myrepository.mine/base/path
> [INFO] Installing Maven distribution
> C:\Users\developer\.m2\wrapper\dists\apache-maven-3.8.1-bin\726df79b
> [INFO] Downloading
> http://myrepository.mine/org/apache/maven/apache-maven/3.8.1/apache-maven-3.8.1-bin.zip
> [WARNING] Using an insecure connection to download the Maven distribution.
> Please consider using HTTPS.
> Exception in thread "main" java.io.FileNotFoundException:
> http://myrepository.mine/org/apache/maven/apache-maven/3.8.1/apache-maven-3.8.1-bin.zip
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1890)
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
> at
> org.apache.maven.wrapper.DefaultDownloader.downloadInternal(DefaultDownloader.java:109)
> at
> org.apache.maven.wrapper.DefaultDownloader.download(DefaultDownloader.java:97)
> at org.apache.maven.wrapper.Installer.createDist(Installer.java:94)
> at
> org.apache.maven.wrapper.WrapperExecutor.execute(WrapperExecutor.java:151)
> at
> org.apache.maven.wrapper.MavenWrapperMain.main(MavenWrapperMain.java:76)
> {code}
>
> Version 3.1.0 (working)
> {code:java}
> SET MVNW_REPOURL=http://myrepository.mine/base/path
> Apache Maven Wrapper 3.1.0
> Detected MVNW_REPOURL environment variable http://myrepository.mine/base/path
> Installing Maven distribution
> C:\Users\developer\.m2\wrapper\dists\apache-maven-3.8.1-bin\5rncivls3ihmmbfjma6p3gsnss
> Downloading
> http://myrepository.mine/base/path/org/apache/maven/apache-maven/3.8.1/apache-maven-3.8.1-bin.zip
> WARNING Using HTTP Basic Authentication over an insecure connection to
> download the Maven distribution. Please consider using HTTPS.
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .Unzipping
> C:\Users\developer\.m2\wrapper\dists\apache-maven-3.8.1-bin\5rncivls3ihmmbfjma6p3gsnss\apache-maven-3.8.1-bin.zip
> to
> C:\Users\developer\.m2\wrapper\dists\apache-maven-3.8.1-bin\5rncivls3ihmmbfjma6p3gsnss
> {code}
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-integration-testing] michael-o commented on pull request #178: Use a plugin to download all dependencies to bypass conflict resolution
michael-o commented on PR #178: URL: https://github.com/apache/maven-integration-testing/pull/178#issuecomment-1171452931 > > Yes, it does: > > https://github.com/apache/maven-integration-testing/blob/0b8a1d613193d73aa02cd703ed59d0e468a8bc6f/core-it-suite/src/test/java/org/apache/maven/it/MavenITBootstrapTest.java#L51 > > > > So you need to reinstantiate that IT, but with a single module using you new plugin and the issue should be solved. > > I really don't like the idea of wrapping the download in a fake test. I've pushed a change to force the download from maven central. I am not happy with this solution because: * It completely breaks of the system * It cannot be mirrored automatically * Locked down envs will fail * Slow links will make it even slower * etc. I don't consider this solution better than before. From an IT perspective, the bootstrap must behave just the way any other IT would behave while downloading a depedency. Now, you have change the conditions. Now, I cannot just run `run-it.sh`. I will always need to filddle to inject the mirrors, credentials, etc. A drawback for fast downloads. -- 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...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-mvnd] robertk3s opened a new issue, #660: Support Maven 3.8.6
robertk3s opened a new issue, #660: URL: https://github.com/apache/maven-mvnd/issues/660 Update to latest and greatest Maven version. Reason mostly "Regression fixes from Maven 3.8.5" see https://maven.apache.org/docs/3.8.6/release-notes.html -- 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...@maven.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-install-plugin] olamy commented on pull request #31: [MINSTALL-175] Drop MAT
olamy commented on PR #31: URL: https://github.com/apache/maven-install-plugin/pull/31#issuecomment-1171955129 As an Apache project we do not own the package `org.eclipse.aether` so we cannot promote the use of such package distributed in a `org.apache.maven groupId`. This was supposed to be a temporary transitional phase. It's now almost 7 years the project has been moved here. So as a transition phase we had enough time to change this aberration from our source code. This usage should be dead already after so many years. It looks to moving backward with such change.. if the goal is remove some old dependencies we don't like (e.g the dependencies pulled by m-a-t) we can certainly exclude: ``` maven-artifact-transfer-maven-3.0.x ``` And even drop this module from our source code if we don't want to keep supporting it. But the history of the source here at Apache is remove the usage of org.eclipse as a package we distribute which again is totally wrong and we cannot keep promoting. -- 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...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MENFORCER-424) Maven enforcer rule which checks that all dependencies in dependencyManagement don't have an explicit scope set
[
https://issues.apache.org/jira/browse/MENFORCER-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561295#comment-17561295
]
Konrad Windszus commented on MENFORCER-424:
---
I provided a PR in https://github.com/apache/maven-enforcer/pull/169.
[~sjaranowski] Do you have time to review?
> Maven enforcer rule which checks that all dependencies in
> dependencyManagement don't have an explicit scope set
> ---
>
> Key: MENFORCER-424
> URL: https://issues.apache.org/jira/browse/MENFORCER-424
> Project: Maven Enforcer Plugin
> Issue Type: New Feature
> Components: Standard Rules
>Reporter: Konrad Windszus
>Priority: Major
>
> Setting the scope in the dependencyManagement is an anti-pattern and may lead
> to surprising results during classpath creation. Compare also with the
> discussion in
> https://github.com/apache/maven-apache-parent/pull/63#discussion_r788361219.
> I propose to add a new rule with name {{banDependencyManagementScope}}.
> Probably scope {{import}} should be accepted though, because it is a special
> case.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
