[GitHub] [maven-release] pzygielo commented on pull request #88: Remove unused formal parameters
pzygielo commented on pull request #88: URL: https://github.com/apache/maven-release/pull/88#issuecomment-991855296 Rebased to benefit from change in cb55288a:pom.xml. -- 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-release] slachiewicz merged pull request #88: Remove unused formal parameters
slachiewicz merged pull request #88: URL: https://github.com/apache/maven-release/pull/88 -- 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] [Updated] (ARCHETYPE-603) archetype:create-from-project is not copying .gitignore file to archetype
[
https://issues.apache.org/jira/browse/ARCHETYPE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated ARCHETYPE-603:
Summary: archetype:create-from-project is not copying .gitignore file to
archetype (was: on archetype:create-from-project does not copying .gitignore
file to archetype)
> archetype:create-from-project is not copying .gitignore file to archetype
> -
>
> Key: ARCHETYPE-603
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-603
> Project: Maven Archetype
> Issue Type: Bug
>Affects Versions: 3.0.0, 3.0.1
>Reporter: Ebuzer taha kanat
>Priority: Major
>
> {code:xml}false{code}
> or
> {code:xml}
>
>
>
>
> .*ignore
>
>
>
> {code}
> not solving the problem either
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (ARCHETYPE-603) archetype:create-from-project is not copying .gitignore file to archetype
[
https://issues.apache.org/jira/browse/ARCHETYPE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457873#comment-17457873
]
Herve Boutemy commented on ARCHETYPE-603:
-
IIUC, it's the same than ARCHETYPE-605, isn't it?
> archetype:create-from-project is not copying .gitignore file to archetype
> -
>
> Key: ARCHETYPE-603
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-603
> Project: Maven Archetype
> Issue Type: Bug
>Affects Versions: 3.0.0, 3.0.1
>Reporter: Ebuzer taha kanat
>Priority: Major
>
> {code:xml}false{code}
> or
> {code:xml}
>
>
>
>
> .*ignore
>
>
>
> {code}
> not solving the problem either
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (ARCHETYPE-603) archetype:create-from-project is not copying .gitignore file to archetype
[ https://issues.apache.org/jira/browse/ARCHETYPE-603 ]
Herve Boutemy deleted comment on ARCHETYPE-603:
-
was (Author: hboutemy):
IIUC, it's the same than ARCHETYPE-605, isn't it?
> archetype:create-from-project is not copying .gitignore file to archetype
> -
>
> Key: ARCHETYPE-603
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-603
> Project: Maven Archetype
> Issue Type: Bug
>Affects Versions: 3.0.0, 3.0.1
>Reporter: Ebuzer taha kanat
>Priority: Major
>
> {code:xml}false{code}
> or
> {code:xml}
>
>
>
>
> .*ignore
>
>
>
> {code}
> not solving the problem either
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (ARCHETYPE-605) Allow .gitignore file in archetype resources
[
https://issues.apache.org/jira/browse/ARCHETYPE-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457875#comment-17457875
]
Herve Boutemy commented on ARCHETYPE-605:
-
can you confirm it's the same as ARCHETYPE-606, please?
> Allow .gitignore file in archetype resources
>
>
> Key: ARCHETYPE-605
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-605
> Project: Maven Archetype
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 3.2.0
>Reporter: Piotr Lewandowski
>Priority: Major
> Fix For: backlog
>
>
> Since 3.2.0 (and plexus-archiver:4.2.2) JAR archive with archetype does not
> include {{.gitignore}} file, despite of fact that this file is located in
> {{archetype-resources}} directory.
> In {{JarMojo}} Plexus' {{addDirectory(File)}} method is called.
> {code:java}
> archiver.getArchiver().addDirectory( archetypeDirectory );{code}
> This method does not configure default excludes, that are enabled by default.
> {code:java}
> @Override
> public void addDirectory( @Nonnull final File directory )
> throws ArchiverException
> {
> addFileSet(
> fileSet( directory ).prefixed( "" ).includeExclude( null, null
> ).includeEmptyDirs( includeEmptyDirs ) );
> }{code}
> {{setUsingDefaultExcludes}} method is not called on fileSet here.
> Later on, this fileSet is used to create {{PlexusIoFileResourceCollection}}
> object. On this object, {{getResources}} method is called that uses Plexus'
> {{DirectoryScanner}} to find out all resources that should be included into
> final artifact. This scanner uses {{usingDefaultExcludes}} configuration and
> excludes [among the
> others|https://github.com/sonatype/plexus-utils/blob/master/src/main/java/org/codehaus/plexus/util/AbstractScanner.java#L92],
> {{.gitignore}} file.
> I have not found any way to configure archetype-archiver to disable default
> excludes. In my opinion current behavior is a regression - custom
> {{.gitignore}} is useful feature in archetypes.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-archetype] hboutemy commented on pull request #56: [ARCHETYPE-605] Allow .gitignore file in archetype resources
hboutemy commented on pull request #56: URL: https://github.com/apache/maven-archetype/pull/56#issuecomment-991864908 isn't it fixed by #59 ? -- 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-archetype] acanda closed pull request #56: [ARCHETYPE-605] Allow .gitignore file in archetype resources
acanda closed pull request #56: URL: https://github.com/apache/maven-archetype/pull/56 -- 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-archetype] acanda commented on pull request #56: [ARCHETYPE-605] Allow .gitignore file in archetype resources
acanda commented on pull request #56: URL: https://github.com/apache/maven-archetype/pull/56#issuecomment-991872621 Yes, this is fixed by #59. Someone else submitted the same fix so I'm closing this issue. -- 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] (MNG-7357) All Maven Core JARs have unusual entry order
[
https://issues.apache.org/jira/browse/MNG-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457915#comment-17457915
]
Michael Osipov commented on MNG-7357:
-
You mean the JAR spec. The JAR Spec does *not* mandate them to be first, *but*
if you look into the Java code you'll see it tries to scan for {{META-INF/}},
followed by {{META-INF/MANIFEST.MF}} *or* {{META-INF/MANIFEST.MF}} to make
proper decision how to proceed with this JAR. If those entries are at the end
It would take time to arrive at the end of the file. If you put
{{META-INF/MANIFEST.MF}} then there is zero reason to put {{META-INF/}} after
it. Since we create empy dirs first I would expect the same approach here.
Impl in Java:
https://github.com/AdoptOpenJDK/openjdk-jdk11/blob/19fb8f93c59dfd791f62d41f332db9e306bc1422/src/java.base/share/classes/java/util/jar/JarInputStream.java#L79-L87
> All Maven Core JARs have unusual entry order
>
>
> Key: MNG-7357
> URL: https://issues.apache.org/jira/browse/MNG-7357
> Project: Maven
> Issue Type: Bug
>Reporter: Michael Osipov
>Priority: Minor
>
> Built from 3a06530dbce82e2054afa3cc4c81631910474bd0 I receive this:
> {noformat}
> mosipov@bsd1srv:/usr/home/mosipov/var/Projekte/maven (master *=)
> $ find . -name maven-\*4.0.0-alpha-1-SNAPSHOT.jar -type f -exec sh -c
> 'zipinfo {} | head -4' \; 2>&1 | less
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:04 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 20-Jan-26 09:04 META-INF/
> Archive:
> ./maven-model-builder/target/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 217583 bytes, number of entries: 173
> -rw-r--r-- 2.0 unx 352 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive: ./maven-model/target/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 203201 bytes, number of entries: 76
> -rw-r--r-- 2.0 unx 336 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive:
> ./maven-slf4j-provider/target/maven-slf4j-provider-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 25315 bytes, number of entries: 26
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:04 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 20-Jan-26 09:04 META-INF/
> Archive:
> ./maven-model-builder/target/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 217583 bytes, number of entries: 173
> -rw-r--r-- 2.0 unx 352 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive: ./maven-model/target/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 203201 bytes, number of entries: 76
> -rw-r--r-- 2.0 unx 336 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive:
> ./maven-slf4j-provider/target/maven-slf4j-provider-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 25315 bytes, number of entries: 26
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:04 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 20-Jan-26 09:04 META-INF/
> Archive:
> ./maven-model-builder/target/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 217583 bytes, number of entries: 173
> -rw-r--r-- 2.0 unx 352 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive: ./maven-model/target/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 203201 bytes, number of entries: 76
> -rw-r--r-- 2.0 unx 336 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive:
> ./maven-slf4j-provider/target/maven-slf4j-provider-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 25315 bytes, number of entries: 26
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:04 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 20-Jan-26 09:04 META-INF/
> Archive:
> ./maven-model-builder/target/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 217583 bytes, number of entries: 173
> -rw-r--r-- 2.0 unx 352 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive: ./maven-model/target/
[jira] [Commented] (MTOOLCHAINS-39) Can't unzip/unjar maven-toolchain-1.0.jar that is available at Maven Central
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457921#comment-17457921 ] Michael Osipov commented on MTOOLCHAINS-39: --- [~hboutemy]: Does Sonatype perform some kind of analysis on all ZIP format artifacts whether they are readable with jar(1)? Appearantly there is a fraction which is broken and cannot be fixed. If there is such a list can we make it available publically for the community? > Can't unzip/unjar maven-toolchain-1.0.jar that is available at Maven Central > > > Key: MTOOLCHAINS-39 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-39 > Project: Maven Toolchains Plugin > Issue Type: Bug >Affects Versions: 1.0 >Reporter: Thomas Cunningham >Priority: Major > > jar tvf maven-toolchain-1.0.jar that is available from maven central reports > reasonable results > However > jar xvf doesn't work > ❯ jar xvf maven-toolchain-1.0.jar > inflated: META-INF > java.io.IOException: META-INF : could not create directory > at jdk.jartool/sun.tools.jar.Main.extractFile(Main.java:1449) > at jdk.jartool/sun.tools.jar.Main.extract(Main.java:1364) > at jdk.jartool/sun.tools.jar.Main.run(Main.java:409) > at jdk.jartool/sun.tools.jar.Main.main(Main.java:1681) > unzip doesn't work > ❯ unzip maven-toolchain-1.0.jar > Archive: maven-toolchain-1.0.jar > replace META-INF? [y]es, [n]o, [A]ll, [N]one, [r]ename: A > inflating: META-INF > checkdir error: META-INF exists but is not directory > unable to process META-INF/MANIFEST.MF. > inflating: org > checkdir error: org exists but is not directory > unable to process org/apache. > checkdir error: org exists but is not directory > unable to process org/apache/maven. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/java. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/java/DefaultJavaToolchainFactory.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/java/JavaToolChain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/java/DefaultJavaToolChain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainManagerPrivate.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/DefaultToolchain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainPrivate.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/MisconfiguredToolchainException.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainManager.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainFactory$1.class. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/model. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/ToolchainModel.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/PersistedToolchains.class. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/model/io. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/model/io/xpp3. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/io/xpp3/MavenToolchainsXpp3Reader.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/io/xpp3/MavenToolchainsXpp3Writer.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/RequirementMatcherFactory$ExactMatcher.class. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/Toolchain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain
[jira] [Commented] (MWRAPPER-21) Arbitrary file write during archive extraction ("Zip Slip") in wrapper
[
https://issues.apache.org/jira/browse/MWRAPPER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457922#comment-17457922
]
Michael Osipov commented on MWRAPPER-21:
If this is fixed, why is this issue not closed?
> Arbitrary file write during archive extraction ("Zip Slip") in wrapper
> --
>
> Key: MWRAPPER-21
> URL: https://issues.apache.org/jira/browse/MWRAPPER-21
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Jar
>Affects Versions: 0.5.6
>Reporter: Sylwester Lachiewicz
>Assignee: Robert Scholte
>Priority: Major
>
> In Maven Wrapper Installer
> [https://github.com/apache/maven/blob/ef8c95eb397651e10f677763dfcd9c8cea7c27b0/maven-wrapper/src/main/java/org/apache/maven/wrapper/Installer.java]
>
> {code:java}
> ZipEntry entry = entries.nextElement();
> if ( entry.isDirectory() )
> {
> continue;
> }
> Path targetFile = dest.resolve( entry.getName() );
> // Unsanitized archive entry, which may contain '..', is used in a file
> system operation.
> // prevent Zip Slip
> if ( targetFile.startsWith( dest ) )
> {
>Files.createDirectories( targetFile.getParent() );
>Files.copy( zipFile.getInputStream( entry ), targetFile );
> }
> {code}
>
> Found via LGTM.com scan
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7357) All Maven Core JARs have unusual entry order
[
https://issues.apache.org/jira/browse/MNG-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457930#comment-17457930
]
Herve Boutemy commented on MNG-7357:
{quote}The JAR Spec does not mandate them to be first{quote}
I see we think at the same discussion we already had :)
the question is to find where it happened and if we did a change or not
> All Maven Core JARs have unusual entry order
>
>
> Key: MNG-7357
> URL: https://issues.apache.org/jira/browse/MNG-7357
> Project: Maven
> Issue Type: Bug
>Reporter: Michael Osipov
>Priority: Minor
>
> Built from 3a06530dbce82e2054afa3cc4c81631910474bd0 I receive this:
> {noformat}
> mosipov@bsd1srv:/usr/home/mosipov/var/Projekte/maven (master *=)
> $ find . -name maven-\*4.0.0-alpha-1-SNAPSHOT.jar -type f -exec sh -c
> 'zipinfo {} | head -4' \; 2>&1 | less
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:04 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 20-Jan-26 09:04 META-INF/
> Archive:
> ./maven-model-builder/target/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 217583 bytes, number of entries: 173
> -rw-r--r-- 2.0 unx 352 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive: ./maven-model/target/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 203201 bytes, number of entries: 76
> -rw-r--r-- 2.0 unx 336 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive:
> ./maven-slf4j-provider/target/maven-slf4j-provider-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 25315 bytes, number of entries: 26
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:04 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 20-Jan-26 09:04 META-INF/
> Archive:
> ./maven-model-builder/target/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 217583 bytes, number of entries: 173
> -rw-r--r-- 2.0 unx 352 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive: ./maven-model/target/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 203201 bytes, number of entries: 76
> -rw-r--r-- 2.0 unx 336 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive:
> ./maven-slf4j-provider/target/maven-slf4j-provider-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 25315 bytes, number of entries: 26
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:04 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 20-Jan-26 09:04 META-INF/
> Archive:
> ./maven-model-builder/target/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 217583 bytes, number of entries: 173
> -rw-r--r-- 2.0 unx 352 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive: ./maven-model/target/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 203201 bytes, number of entries: 76
> -rw-r--r-- 2.0 unx 336 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive:
> ./maven-slf4j-provider/target/maven-slf4j-provider-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 25315 bytes, number of entries: 26
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:04 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 20-Jan-26 09:04 META-INF/
> Archive:
> ./maven-model-builder/target/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 217583 bytes, number of entries: 173
> -rw-r--r-- 2.0 unx 352 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive: ./maven-model/target/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 203201 bytes, number of entries: 76
> -rw-r--r-- 2.0 unx 336 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive:
> ./maven-slf4j-provider/target/maven-slf4j-provider-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 25315 bytes, number of entries: 26
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx
[jira] [Commented] (MTOOLCHAINS-39) Can't unzip/unjar maven-toolchain-1.0.jar that is available at Maven Central
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457931#comment-17457931 ] Herve Boutemy commented on MTOOLCHAINS-39: -- no idea: please open a MVNCENTRAL issue https://issues.sonatype.org/projects/MVNCENTRAL > Can't unzip/unjar maven-toolchain-1.0.jar that is available at Maven Central > > > Key: MTOOLCHAINS-39 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-39 > Project: Maven Toolchains Plugin > Issue Type: Bug >Affects Versions: 1.0 >Reporter: Thomas Cunningham >Priority: Major > > jar tvf maven-toolchain-1.0.jar that is available from maven central reports > reasonable results > However > jar xvf doesn't work > ❯ jar xvf maven-toolchain-1.0.jar > inflated: META-INF > java.io.IOException: META-INF : could not create directory > at jdk.jartool/sun.tools.jar.Main.extractFile(Main.java:1449) > at jdk.jartool/sun.tools.jar.Main.extract(Main.java:1364) > at jdk.jartool/sun.tools.jar.Main.run(Main.java:409) > at jdk.jartool/sun.tools.jar.Main.main(Main.java:1681) > unzip doesn't work > ❯ unzip maven-toolchain-1.0.jar > Archive: maven-toolchain-1.0.jar > replace META-INF? [y]es, [n]o, [A]ll, [N]one, [r]ename: A > inflating: META-INF > checkdir error: META-INF exists but is not directory > unable to process META-INF/MANIFEST.MF. > inflating: org > checkdir error: org exists but is not directory > unable to process org/apache. > checkdir error: org exists but is not directory > unable to process org/apache/maven. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/java. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/java/DefaultJavaToolchainFactory.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/java/JavaToolChain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/java/DefaultJavaToolChain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainManagerPrivate.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/DefaultToolchain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainPrivate.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/MisconfiguredToolchainException.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainManager.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainFactory$1.class. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/model. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/ToolchainModel.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/PersistedToolchains.class. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/model/io. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/model/io/xpp3. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/io/xpp3/MavenToolchainsXpp3Reader.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/io/xpp3/MavenToolchainsXpp3Writer.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/RequirementMatcherFactory$ExactMatcher.class. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/Toolchain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/RequirementMatcherFactory.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/RequirementMatcherFactory$1.class.
[jira] [Updated] (MTOOLCHAINS-39) Can't unzip/unjar maven-toolchain-1.0.jar that is available at Maven Central
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MTOOLCHAINS-39: - Description: jar tvf maven-toolchain-1.0.jar that is available from maven central reports reasonable results https://repo.maven.apache.org/maven2/org/apache/maven/maven-toolchain/ However jar xvf doesn't work ❯ jar xvf maven-toolchain-1.0.jar inflated: META-INF java.io.IOException: META-INF : could not create directory at jdk.jartool/sun.tools.jar.Main.extractFile(Main.java:1449) at jdk.jartool/sun.tools.jar.Main.extract(Main.java:1364) at jdk.jartool/sun.tools.jar.Main.run(Main.java:409) at jdk.jartool/sun.tools.jar.Main.main(Main.java:1681) unzip doesn't work ❯ unzip maven-toolchain-1.0.jar Archive: maven-toolchain-1.0.jar replace META-INF? [y]es, [n]o, [A]ll, [N]one, [r]ename: A inflating: META-INF checkdir error: META-INF exists but is not directory unable to process META-INF/MANIFEST.MF. inflating: org checkdir error: org exists but is not directory unable to process org/apache. checkdir error: org exists but is not directory unable to process org/apache/maven. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/java. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/java/DefaultJavaToolchainFactory.class. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/java/JavaToolChain.class. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/java/DefaultJavaToolChain.class. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/ToolchainManagerPrivate.class. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/DefaultToolchain.class. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/ToolchainPrivate.class. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/MisconfiguredToolchainException.class. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/ToolchainManager.class. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/ToolchainFactory$1.class. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/model. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/model/ToolchainModel.class. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/model/PersistedToolchains.class. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/model/io. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/model/io/xpp3. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/model/io/xpp3/MavenToolchainsXpp3Reader.class. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/model/io/xpp3/MavenToolchainsXpp3Writer.class. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/RequirementMatcherFactory$ExactMatcher.class. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/Toolchain.class. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/RequirementMatcherFactory.class. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/RequirementMatcherFactory$1.class. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/ToolchainManagerPrivate$1.class. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/DefaultToolchainManager.class. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/ToolchainFactory.class. checkdir error: org exists but is not directory unable to process org/apache/maven/toolchain/ToolchainManager$1.class. checkdir error: org exists but is not directory unable to process org/apache/maven/too
[jira] [Commented] (MTOOLCHAINS-39) Can't unzip/unjar maven-toolchain-1.0.jar that is available at Maven Central
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457932#comment-17457932 ] Herve Boutemy commented on MTOOLCHAINS-39: -- notice that this artifact has been released with Maven 2.0.6 parent, even if its version is 1.0, before being integrated in Maven 2.0.9 to 3.0-alpha-2 it really looks like an old artifact that does not deserve to loose too much time on researching... > Can't unzip/unjar maven-toolchain-1.0.jar that is available at Maven Central > > > Key: MTOOLCHAINS-39 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-39 > Project: Maven Toolchains Plugin > Issue Type: Bug >Affects Versions: 1.0 >Reporter: Thomas Cunningham >Priority: Major > > jar tvf maven-toolchain-1.0.jar that is available from maven central reports > reasonable results > https://repo.maven.apache.org/maven2/org/apache/maven/maven-toolchain/ > However > jar xvf doesn't work > ❯ jar xvf maven-toolchain-1.0.jar > inflated: META-INF > java.io.IOException: META-INF : could not create directory > at jdk.jartool/sun.tools.jar.Main.extractFile(Main.java:1449) > at jdk.jartool/sun.tools.jar.Main.extract(Main.java:1364) > at jdk.jartool/sun.tools.jar.Main.run(Main.java:409) > at jdk.jartool/sun.tools.jar.Main.main(Main.java:1681) > unzip doesn't work > ❯ unzip maven-toolchain-1.0.jar > Archive: maven-toolchain-1.0.jar > replace META-INF? [y]es, [n]o, [A]ll, [N]one, [r]ename: A > inflating: META-INF > checkdir error: META-INF exists but is not directory > unable to process META-INF/MANIFEST.MF. > inflating: org > checkdir error: org exists but is not directory > unable to process org/apache. > checkdir error: org exists but is not directory > unable to process org/apache/maven. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/java. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/java/DefaultJavaToolchainFactory.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/java/JavaToolChain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/java/DefaultJavaToolChain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainManagerPrivate.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/DefaultToolchain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainPrivate.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/MisconfiguredToolchainException.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainManager.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainFactory$1.class. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/model. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/ToolchainModel.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/PersistedToolchains.class. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/model/io. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/model/io/xpp3. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/io/xpp3/MavenToolchainsXpp3Reader.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/io/xpp3/MavenToolchainsXpp3Writer.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/RequirementMatcherFactory$ExactMatcher.class. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/Toolchain.class. > checkdir error: org exists but is not directory >
[jira] [Comment Edited] (MTOOLCHAINS-39) Can't unzip/unjar maven-toolchain-1.0.jar that is available at Maven Central
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457932#comment-17457932 ] Herve Boutemy edited comment on MTOOLCHAINS-39 at 12/12/21, 12:08 PM: -- notice that this artifact has been released with Maven 2.0.6 parent, even if its version is 1.0, before being integrated in Maven 2.0.9 to 3.0-alpha-2 https://repo.maven.apache.org/maven2/org/apache/maven/maven-toolchain/ it really looks like an old artifact that does not deserve to loose too much time on researching... was (Author: hboutemy): notice that this artifact has been released with Maven 2.0.6 parent, even if its version is 1.0, before being integrated in Maven 2.0.9 to 3.0-alpha-2 it really looks like an old artifact that does not deserve to loose too much time on researching... > Can't unzip/unjar maven-toolchain-1.0.jar that is available at Maven Central > > > Key: MTOOLCHAINS-39 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-39 > Project: Maven Toolchains Plugin > Issue Type: Bug >Affects Versions: 1.0 >Reporter: Thomas Cunningham >Priority: Major > > jar tvf maven-toolchain-1.0.jar that is available from maven central reports > reasonable results > https://repo.maven.apache.org/maven2/org/apache/maven/maven-toolchain/ > However > jar xvf doesn't work > ❯ jar xvf maven-toolchain-1.0.jar > inflated: META-INF > java.io.IOException: META-INF : could not create directory > at jdk.jartool/sun.tools.jar.Main.extractFile(Main.java:1449) > at jdk.jartool/sun.tools.jar.Main.extract(Main.java:1364) > at jdk.jartool/sun.tools.jar.Main.run(Main.java:409) > at jdk.jartool/sun.tools.jar.Main.main(Main.java:1681) > unzip doesn't work > ❯ unzip maven-toolchain-1.0.jar > Archive: maven-toolchain-1.0.jar > replace META-INF? [y]es, [n]o, [A]ll, [N]one, [r]ename: A > inflating: META-INF > checkdir error: META-INF exists but is not directory > unable to process META-INF/MANIFEST.MF. > inflating: org > checkdir error: org exists but is not directory > unable to process org/apache. > checkdir error: org exists but is not directory > unable to process org/apache/maven. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/java. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/java/DefaultJavaToolchainFactory.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/java/JavaToolChain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/java/DefaultJavaToolChain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainManagerPrivate.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/DefaultToolchain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainPrivate.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/MisconfiguredToolchainException.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainManager.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainFactory$1.class. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/model. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/ToolchainModel.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/PersistedToolchains.class. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/model/io. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/model/io/xpp3. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/io/xpp3/MavenToolchainsXpp3Reader.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/mo
[jira] [Commented] (MNG-7357) All Maven Core JARs have unusual entry order
[
https://issues.apache.org/jira/browse/MNG-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457934#comment-17457934
]
Michael Osipov commented on MNG-7357:
-
I checked Plexus Archiver and it does add {{META-INF/}} first and *then* then
manifest.
> All Maven Core JARs have unusual entry order
>
>
> Key: MNG-7357
> URL: https://issues.apache.org/jira/browse/MNG-7357
> Project: Maven
> Issue Type: Bug
>Reporter: Michael Osipov
>Priority: Minor
>
> Built from 3a06530dbce82e2054afa3cc4c81631910474bd0 I receive this:
> {noformat}
> mosipov@bsd1srv:/usr/home/mosipov/var/Projekte/maven (master *=)
> $ find . -name maven-\*4.0.0-alpha-1-SNAPSHOT.jar -type f -exec sh -c
> 'zipinfo {} | head -4' \; 2>&1 | less
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:04 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 20-Jan-26 09:04 META-INF/
> Archive:
> ./maven-model-builder/target/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 217583 bytes, number of entries: 173
> -rw-r--r-- 2.0 unx 352 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive: ./maven-model/target/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 203201 bytes, number of entries: 76
> -rw-r--r-- 2.0 unx 336 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive:
> ./maven-slf4j-provider/target/maven-slf4j-provider-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 25315 bytes, number of entries: 26
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:04 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 20-Jan-26 09:04 META-INF/
> Archive:
> ./maven-model-builder/target/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 217583 bytes, number of entries: 173
> -rw-r--r-- 2.0 unx 352 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive: ./maven-model/target/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 203201 bytes, number of entries: 76
> -rw-r--r-- 2.0 unx 336 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive:
> ./maven-slf4j-provider/target/maven-slf4j-provider-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 25315 bytes, number of entries: 26
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:04 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 20-Jan-26 09:04 META-INF/
> Archive:
> ./maven-model-builder/target/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 217583 bytes, number of entries: 173
> -rw-r--r-- 2.0 unx 352 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive: ./maven-model/target/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 203201 bytes, number of entries: 76
> -rw-r--r-- 2.0 unx 336 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive:
> ./maven-slf4j-provider/target/maven-slf4j-provider-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 25315 bytes, number of entries: 26
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:04 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 20-Jan-26 09:04 META-INF/
> Archive:
> ./maven-model-builder/target/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 217583 bytes, number of entries: 173
> -rw-r--r-- 2.0 unx 352 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive: ./maven-model/target/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 203201 bytes, number of entries: 76
> -rw-r--r-- 2.0 unx 336 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive:
> ./maven-slf4j-provider/target/maven-slf4j-provider-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 25315 bytes, number of entries: 26
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:04 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 20-Jan-26
[jira] [Commented] (MTOOLCHAINS-39) Can't unzip/unjar maven-toolchain-1.0.jar that is available at Maven Central
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457938#comment-17457938 ] Michael Osipov commented on MTOOLCHAINS-39: --- I am not just focused on this one, but there are likely many of them. This is just an example for it. Yes, it is old, but none the less. More surprisingly, It worked somehow back then?! > Can't unzip/unjar maven-toolchain-1.0.jar that is available at Maven Central > > > Key: MTOOLCHAINS-39 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-39 > Project: Maven Toolchains Plugin > Issue Type: Bug >Affects Versions: 1.0 >Reporter: Thomas Cunningham >Priority: Major > > jar tvf maven-toolchain-1.0.jar that is available from maven central reports > reasonable results > https://repo.maven.apache.org/maven2/org/apache/maven/maven-toolchain/ > However > jar xvf doesn't work > ❯ jar xvf maven-toolchain-1.0.jar > inflated: META-INF > java.io.IOException: META-INF : could not create directory > at jdk.jartool/sun.tools.jar.Main.extractFile(Main.java:1449) > at jdk.jartool/sun.tools.jar.Main.extract(Main.java:1364) > at jdk.jartool/sun.tools.jar.Main.run(Main.java:409) > at jdk.jartool/sun.tools.jar.Main.main(Main.java:1681) > unzip doesn't work > ❯ unzip maven-toolchain-1.0.jar > Archive: maven-toolchain-1.0.jar > replace META-INF? [y]es, [n]o, [A]ll, [N]one, [r]ename: A > inflating: META-INF > checkdir error: META-INF exists but is not directory > unable to process META-INF/MANIFEST.MF. > inflating: org > checkdir error: org exists but is not directory > unable to process org/apache. > checkdir error: org exists but is not directory > unable to process org/apache/maven. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/java. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/java/DefaultJavaToolchainFactory.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/java/JavaToolChain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/java/DefaultJavaToolChain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainManagerPrivate.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/DefaultToolchain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainPrivate.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/MisconfiguredToolchainException.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainManager.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainFactory$1.class. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/model. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/ToolchainModel.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/PersistedToolchains.class. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/model/io. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/model/io/xpp3. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/io/xpp3/MavenToolchainsXpp3Reader.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/io/xpp3/MavenToolchainsXpp3Writer.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/RequirementMatcherFactory$ExactMatcher.class. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/Toolchain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/RequirementM
[jira] [Commented] (MTOOLCHAINS-39) Can't unzip/unjar maven-toolchain-1.0.jar that is available at Maven Central
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457953#comment-17457953 ] Herve Boutemy commented on MTOOLCHAINS-39: -- bq. More surprisingly, It worked somehow back then?! yes, this one was a release done by Apache Maven team, with as serious as possible review: I don't know if at that time, native tools versions worked and there is a global shift in last 10 years, or if it was just an issue not seen imagine what we can find in Central with artifacts less reviewed... and imagine what we'll do when we find artifacts we know we don't understand: who can judge/decide if they are wrong? I think it's another aspect of "it's up to the user to know if he trusts artifact providers: hoster is just hoster" (I'm not sure my frenglish can be understood ;) ) > Can't unzip/unjar maven-toolchain-1.0.jar that is available at Maven Central > > > Key: MTOOLCHAINS-39 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-39 > Project: Maven Toolchains Plugin > Issue Type: Bug >Affects Versions: 1.0 >Reporter: Thomas Cunningham >Priority: Major > > jar tvf maven-toolchain-1.0.jar that is available from maven central reports > reasonable results > https://repo.maven.apache.org/maven2/org/apache/maven/maven-toolchain/ > However > jar xvf doesn't work > ❯ jar xvf maven-toolchain-1.0.jar > inflated: META-INF > java.io.IOException: META-INF : could not create directory > at jdk.jartool/sun.tools.jar.Main.extractFile(Main.java:1449) > at jdk.jartool/sun.tools.jar.Main.extract(Main.java:1364) > at jdk.jartool/sun.tools.jar.Main.run(Main.java:409) > at jdk.jartool/sun.tools.jar.Main.main(Main.java:1681) > unzip doesn't work > ❯ unzip maven-toolchain-1.0.jar > Archive: maven-toolchain-1.0.jar > replace META-INF? [y]es, [n]o, [A]ll, [N]one, [r]ename: A > inflating: META-INF > checkdir error: META-INF exists but is not directory > unable to process META-INF/MANIFEST.MF. > inflating: org > checkdir error: org exists but is not directory > unable to process org/apache. > checkdir error: org exists but is not directory > unable to process org/apache/maven. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/java. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/java/DefaultJavaToolchainFactory.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/java/JavaToolChain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/java/DefaultJavaToolChain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainManagerPrivate.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/DefaultToolchain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainPrivate.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/MisconfiguredToolchainException.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainManager.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainFactory$1.class. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/model. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/ToolchainModel.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/PersistedToolchains.class. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/model/io. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/model/io/xpp3. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/io/xpp3/MavenToolchainsXpp3Reader.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/io/xpp3/Mav
[jira] [Commented] (MTOOLCHAINS-39) Can't unzip/unjar maven-toolchain-1.0.jar that is available at Maven Central
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457956#comment-17457956 ] Michael Osipov commented on MTOOLCHAINS-39: --- Well, it's not OHV. > Can't unzip/unjar maven-toolchain-1.0.jar that is available at Maven Central > > > Key: MTOOLCHAINS-39 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-39 > Project: Maven Toolchains Plugin > Issue Type: Bug >Affects Versions: 1.0 >Reporter: Thomas Cunningham >Priority: Major > > jar tvf maven-toolchain-1.0.jar that is available from maven central reports > reasonable results > https://repo.maven.apache.org/maven2/org/apache/maven/maven-toolchain/ > However > jar xvf doesn't work > ❯ jar xvf maven-toolchain-1.0.jar > inflated: META-INF > java.io.IOException: META-INF : could not create directory > at jdk.jartool/sun.tools.jar.Main.extractFile(Main.java:1449) > at jdk.jartool/sun.tools.jar.Main.extract(Main.java:1364) > at jdk.jartool/sun.tools.jar.Main.run(Main.java:409) > at jdk.jartool/sun.tools.jar.Main.main(Main.java:1681) > unzip doesn't work > ❯ unzip maven-toolchain-1.0.jar > Archive: maven-toolchain-1.0.jar > replace META-INF? [y]es, [n]o, [A]ll, [N]one, [r]ename: A > inflating: META-INF > checkdir error: META-INF exists but is not directory > unable to process META-INF/MANIFEST.MF. > inflating: org > checkdir error: org exists but is not directory > unable to process org/apache. > checkdir error: org exists but is not directory > unable to process org/apache/maven. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/java. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/java/DefaultJavaToolchainFactory.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/java/JavaToolChain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/java/DefaultJavaToolChain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainManagerPrivate.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/DefaultToolchain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainPrivate.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/MisconfiguredToolchainException.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainManager.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/ToolchainFactory$1.class. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/model. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/ToolchainModel.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/PersistedToolchains.class. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/model/io. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/model/io/xpp3. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/io/xpp3/MavenToolchainsXpp3Reader.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/model/io/xpp3/MavenToolchainsXpp3Writer.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/RequirementMatcherFactory$ExactMatcher.class. > checkdir error: org exists but is not directory > unable to process org/apache/maven/toolchain/Toolchain.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/RequirementMatcherFactory.class. > checkdir error: org exists but is not directory > unable to process > org/apache/maven/toolchain/RequirementMatcherFactory$1.c
[jira] [Updated] (MSITE-876) Execution default-deploy of goal ...deploy failed: An API incompatibility was encountered while executing ....deploy: java.lang.NoSuchMethodError: org.apache.maven.wagon.s
[
https://issues.apache.org/jira/browse/MSITE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated MSITE-876:
---
Priority: Blocker (was: Major)
> Execution default-deploy of goal ...deploy failed: An API incompatibility was
> encountered while executing deploy: java.lang.NoSuchMethodError:
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
> --
>
> Key: MSITE-876
> URL: https://issues.apache.org/jira/browse/MSITE-876
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.9.1
>Reporter: Konrad Windszus
>Priority: Blocker
>
> When using maven-site-plugin 3.9.1 with the additional plugin dependency
> {{org.apache.maven.wagon:wagon-webdav-jackrabbit:3.3.1}} I experience the
> following error
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy (default-deploy) on
> project ...: Execution default-deploy of goal
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy:
> java.lang.NoSuchMethodError:
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.9.1
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/plugins/maven-site-plugin/3.9.1/maven-site-plugin-3.9.1.jar
> [ERROR] urls[1] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/wagon/wagon-webdav-jackrabbit/3.3.1/wagon-webdav-jackrabbit-3.3.1.jar
> [ERROR] urls[2] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/wagon/wagon-http-shared/3.3.1/wagon-http-shared-3.3.1.jar
> [ERROR] urls[3] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/jsoup/jsoup/1.11.2/jsoup-1.11.2.jar
> [ERROR] urls[4] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/jackrabbit/jackrabbit-webdav/2.14.4/jackrabbit-webdav-2.14.4.jar
> [ERROR] urls[5] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/commons-codec/commons-codec/1.10/commons-codec-1.10.jar
> [ERROR] urls[6] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/slf4j/jcl-over-slf4j/1.7.25/jcl-over-slf4j-1.7.25.jar
> [ERROR] urls[7] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/httpcomponents/httpclient/4.5.6/httpclient-4.5.6.jar
> [ERROR] urls[8] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/httpcomponents/httpcore/4.4.10/httpcore-4.4.10.jar
> [ERROR] urls[9] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar
> [ERROR] urls[10] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/reporting/maven-reporting-exec/1.5.1/maven-reporting-exec-1.5.1.jar
> [ERROR] urls[11] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> [ERROR] urls[12] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/eclipse/aether/aether-util/0.9.0.M2/aether-util-0.9.0.M2.jar
> [ERROR] urls[13] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/shared/maven-shared-utils/3.1.0/maven-shared-utils-3.1.0.jar
> [ERROR] urls[14] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> [ERROR] urls[15] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/codehaus/plexus/plexus-component-annotations/2.0.0/plexus-component-annotations-2.0.0.jar
> [ERROR] urls[16] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> [ERROR] urls[17] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> [ERROR] urls[18] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/maven-archiver/3.5.0/maven-archiver-3.5.0.jar
> [ERROR] urls[19] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/sisu/sisu-inject-bean/1.4.2
[jira] [Commented] (MSITE-876) Execution default-deploy of goal ...deploy failed: An API incompatibility was encountered while executing ....deploy: java.lang.NoSuchMethodError: org.apache.maven.wagon
[
https://issues.apache.org/jira/browse/MSITE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457957#comment-17457957
]
Michael Osipov commented on MSITE-876:
--
[~slachiewicz], this is a not a blocker because I have provided multiple ways
to address this issue. It's not hopeless.
> Execution default-deploy of goal ...deploy failed: An API incompatibility was
> encountered while executing deploy: java.lang.NoSuchMethodError:
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
> --
>
> Key: MSITE-876
> URL: https://issues.apache.org/jira/browse/MSITE-876
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.9.1
>Reporter: Konrad Windszus
>Priority: Blocker
>
> When using maven-site-plugin 3.9.1 with the additional plugin dependency
> {{org.apache.maven.wagon:wagon-webdav-jackrabbit:3.3.1}} I experience the
> following error
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy (default-deploy) on
> project ...: Execution default-deploy of goal
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy:
> java.lang.NoSuchMethodError:
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.9.1
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/plugins/maven-site-plugin/3.9.1/maven-site-plugin-3.9.1.jar
> [ERROR] urls[1] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/wagon/wagon-webdav-jackrabbit/3.3.1/wagon-webdav-jackrabbit-3.3.1.jar
> [ERROR] urls[2] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/wagon/wagon-http-shared/3.3.1/wagon-http-shared-3.3.1.jar
> [ERROR] urls[3] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/jsoup/jsoup/1.11.2/jsoup-1.11.2.jar
> [ERROR] urls[4] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/jackrabbit/jackrabbit-webdav/2.14.4/jackrabbit-webdav-2.14.4.jar
> [ERROR] urls[5] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/commons-codec/commons-codec/1.10/commons-codec-1.10.jar
> [ERROR] urls[6] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/slf4j/jcl-over-slf4j/1.7.25/jcl-over-slf4j-1.7.25.jar
> [ERROR] urls[7] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/httpcomponents/httpclient/4.5.6/httpclient-4.5.6.jar
> [ERROR] urls[8] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/httpcomponents/httpcore/4.4.10/httpcore-4.4.10.jar
> [ERROR] urls[9] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar
> [ERROR] urls[10] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/reporting/maven-reporting-exec/1.5.1/maven-reporting-exec-1.5.1.jar
> [ERROR] urls[11] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> [ERROR] urls[12] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/eclipse/aether/aether-util/0.9.0.M2/aether-util-0.9.0.M2.jar
> [ERROR] urls[13] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/shared/maven-shared-utils/3.1.0/maven-shared-utils-3.1.0.jar
> [ERROR] urls[14] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> [ERROR] urls[15] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/codehaus/plexus/plexus-component-annotations/2.0.0/plexus-component-annotations-2.0.0.jar
> [ERROR] urls[16] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> [ERROR] urls[17] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> [ERROR] urls[18] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/maven-archiver/3.5.0/maven-archiver-3.5.0.j
[jira] [Commented] (DOXIASITETOOLS-148) Remove SiteRenderingContext#publishDate (undo DOXIASITETOOLS-63)
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457959#comment-17457959
]
Sylwester Lachiewicz commented on DOXIASITETOOLS-148:
-
[~michael-o] may be goo candidate if we plan to deprecate something soon
> Remove SiteRenderingContext#publishDate (undo DOXIASITETOOLS-63)
>
>
> Key: DOXIASITETOOLS-148
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-148
> Project: Maven Doxia Sitetools
> Issue Type: Task
> Components: Site renderer
>Affects Versions: 1.6
>Reporter: Michael Osipov
>Priority: Major
>
> The field {{publishDate}} has been introduced DOXIATESITETOOLS-63 but cannot
> be set anywhere. Either provide a sane setting option including proper
> documentation or drop it completely.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (DOXIASITETOOLS-148) Remove SiteRenderingContext#publishDate (undo DOXIASITETOOLS-63)
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457960#comment-17457960
]
Michael Osipov commented on DOXIASITETOOLS-148:
---
Maybe, yes. We had some sort of dispute with Robert. Ultimately, we need to
decide how this contributes to reproducible builds and how this can be made
official.
> Remove SiteRenderingContext#publishDate (undo DOXIASITETOOLS-63)
>
>
> Key: DOXIASITETOOLS-148
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-148
> Project: Maven Doxia Sitetools
> Issue Type: Task
> Components: Site renderer
>Affects Versions: 1.6
>Reporter: Michael Osipov
>Priority: Major
>
> The field {{publishDate}} has been introduced DOXIATESITETOOLS-63 but cannot
> be set anywhere. Either provide a sane setting option including proper
> documentation or drop it completely.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (DOXIASITETOOLS-148) Remove SiteRenderingContext#publishDate (undo DOXIASITETOOLS-63)
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457960#comment-17457960
]
Michael Osipov edited comment on DOXIASITETOOLS-148 at 12/12/21, 1:07 PM:
--
Maybe, yes. We had some sort of dispute with Robert. Ultimately, we need to
decide how this contributes to reproducible builds and how this can be made
official. If we cannot agree, we should deprecate and remove since years have
passed without any traction.
was (Author: michael-o):
Maybe, yes. We had some sort of dispute with Robert. Ultimately, we need to
decide how this contributes to reproducible builds and how this can be made
official.
> Remove SiteRenderingContext#publishDate (undo DOXIASITETOOLS-63)
>
>
> Key: DOXIASITETOOLS-148
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-148
> Project: Maven Doxia Sitetools
> Issue Type: Task
> Components: Site renderer
>Affects Versions: 1.6
>Reporter: Michael Osipov
>Priority: Major
>
> The field {{publishDate}} has been introduced DOXIATESITETOOLS-63 but cannot
> be set anywhere. Either provide a sane setting option including proper
> documentation or drop it completely.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MSITE-876) Execution default-deploy of goal ...deploy failed: An API incompatibility was encountered while executing ....deploy: java.lang.NoSuchMethodError: org.apache.maven.wagon
[
https://issues.apache.org/jira/browse/MSITE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457963#comment-17457963
]
Sylwester Lachiewicz commented on MSITE-876:
All those workarounds we need to apply to all our Maven projects if we want to
keep compatibility with Maven 3.1.x
> Execution default-deploy of goal ...deploy failed: An API incompatibility was
> encountered while executing deploy: java.lang.NoSuchMethodError:
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
> --
>
> Key: MSITE-876
> URL: https://issues.apache.org/jira/browse/MSITE-876
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.9.1
>Reporter: Konrad Windszus
>Priority: Blocker
>
> When using maven-site-plugin 3.9.1 with the additional plugin dependency
> {{org.apache.maven.wagon:wagon-webdav-jackrabbit:3.3.1}} I experience the
> following error
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy (default-deploy) on
> project ...: Execution default-deploy of goal
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy:
> java.lang.NoSuchMethodError:
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.9.1
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/plugins/maven-site-plugin/3.9.1/maven-site-plugin-3.9.1.jar
> [ERROR] urls[1] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/wagon/wagon-webdav-jackrabbit/3.3.1/wagon-webdav-jackrabbit-3.3.1.jar
> [ERROR] urls[2] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/wagon/wagon-http-shared/3.3.1/wagon-http-shared-3.3.1.jar
> [ERROR] urls[3] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/jsoup/jsoup/1.11.2/jsoup-1.11.2.jar
> [ERROR] urls[4] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/jackrabbit/jackrabbit-webdav/2.14.4/jackrabbit-webdav-2.14.4.jar
> [ERROR] urls[5] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/commons-codec/commons-codec/1.10/commons-codec-1.10.jar
> [ERROR] urls[6] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/slf4j/jcl-over-slf4j/1.7.25/jcl-over-slf4j-1.7.25.jar
> [ERROR] urls[7] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/httpcomponents/httpclient/4.5.6/httpclient-4.5.6.jar
> [ERROR] urls[8] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/httpcomponents/httpcore/4.4.10/httpcore-4.4.10.jar
> [ERROR] urls[9] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar
> [ERROR] urls[10] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/reporting/maven-reporting-exec/1.5.1/maven-reporting-exec-1.5.1.jar
> [ERROR] urls[11] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> [ERROR] urls[12] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/eclipse/aether/aether-util/0.9.0.M2/aether-util-0.9.0.M2.jar
> [ERROR] urls[13] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/shared/maven-shared-utils/3.1.0/maven-shared-utils-3.1.0.jar
> [ERROR] urls[14] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> [ERROR] urls[15] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/codehaus/plexus/plexus-component-annotations/2.0.0/plexus-component-annotations-2.0.0.jar
> [ERROR] urls[16] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> [ERROR] urls[17] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> [ERROR] urls[18] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/maven-archiver/3.5.0/maven-archiver-
[jira] [Commented] (MSITE-876) Execution default-deploy of goal ...deploy failed: An API incompatibility was encountered while executing ....deploy: java.lang.NoSuchMethodError: org.apache.maven.wagon
[
https://issues.apache.org/jira/browse/MSITE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457967#comment-17457967
]
Michael Osipov commented on MSITE-876:
--
This is a special case and I believe that none of our projects is affected.
What do you explicitly have in mind.
> Execution default-deploy of goal ...deploy failed: An API incompatibility was
> encountered while executing deploy: java.lang.NoSuchMethodError:
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
> --
>
> Key: MSITE-876
> URL: https://issues.apache.org/jira/browse/MSITE-876
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.9.1
>Reporter: Konrad Windszus
>Priority: Blocker
>
> When using maven-site-plugin 3.9.1 with the additional plugin dependency
> {{org.apache.maven.wagon:wagon-webdav-jackrabbit:3.3.1}} I experience the
> following error
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy (default-deploy) on
> project ...: Execution default-deploy of goal
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy:
> java.lang.NoSuchMethodError:
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.9.1
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/plugins/maven-site-plugin/3.9.1/maven-site-plugin-3.9.1.jar
> [ERROR] urls[1] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/wagon/wagon-webdav-jackrabbit/3.3.1/wagon-webdav-jackrabbit-3.3.1.jar
> [ERROR] urls[2] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/wagon/wagon-http-shared/3.3.1/wagon-http-shared-3.3.1.jar
> [ERROR] urls[3] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/jsoup/jsoup/1.11.2/jsoup-1.11.2.jar
> [ERROR] urls[4] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/jackrabbit/jackrabbit-webdav/2.14.4/jackrabbit-webdav-2.14.4.jar
> [ERROR] urls[5] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/commons-codec/commons-codec/1.10/commons-codec-1.10.jar
> [ERROR] urls[6] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/slf4j/jcl-over-slf4j/1.7.25/jcl-over-slf4j-1.7.25.jar
> [ERROR] urls[7] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/httpcomponents/httpclient/4.5.6/httpclient-4.5.6.jar
> [ERROR] urls[8] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/httpcomponents/httpcore/4.4.10/httpcore-4.4.10.jar
> [ERROR] urls[9] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar
> [ERROR] urls[10] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/reporting/maven-reporting-exec/1.5.1/maven-reporting-exec-1.5.1.jar
> [ERROR] urls[11] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> [ERROR] urls[12] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/eclipse/aether/aether-util/0.9.0.M2/aether-util-0.9.0.M2.jar
> [ERROR] urls[13] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/shared/maven-shared-utils/3.1.0/maven-shared-utils-3.1.0.jar
> [ERROR] urls[14] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> [ERROR] urls[15] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/codehaus/plexus/plexus-component-annotations/2.0.0/plexus-component-annotations-2.0.0.jar
> [ERROR] urls[16] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> [ERROR] urls[17] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> [ERROR] urls[18] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/maven-archiver/3.5.0/maven-archiver-3.5.0.jar
> [E
[jira] [Commented] (MWRAPPER-21) Arbitrary file write during archive extraction ("Zip Slip") in wrapper
[
https://issues.apache.org/jira/browse/MWRAPPER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457973#comment-17457973
]
Herve Boutemy commented on MWRAPPER-21:
---
it was an issue found in Maven core branch, with initial MNG issue
I moved the issue to MWRAPPER (with a few other ones) to track re-doing in
maven-wrapper.git what was done initially in maven.git
and on a few issues like this one, it seems the code never went to a state
where the issue was to be fixed
then I think we can close this WRAPPER-21
> Arbitrary file write during archive extraction ("Zip Slip") in wrapper
> --
>
> Key: MWRAPPER-21
> URL: https://issues.apache.org/jira/browse/MWRAPPER-21
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Jar
>Affects Versions: 0.5.6
>Reporter: Sylwester Lachiewicz
>Assignee: Robert Scholte
>Priority: Major
>
> In Maven Wrapper Installer
> [https://github.com/apache/maven/blob/ef8c95eb397651e10f677763dfcd9c8cea7c27b0/maven-wrapper/src/main/java/org/apache/maven/wrapper/Installer.java]
>
> {code:java}
> ZipEntry entry = entries.nextElement();
> if ( entry.isDirectory() )
> {
> continue;
> }
> Path targetFile = dest.resolve( entry.getName() );
> // Unsanitized archive entry, which may contain '..', is used in a file
> system operation.
> // prevent Zip Slip
> if ( targetFile.startsWith( dest ) )
> {
>Files.createDirectories( targetFile.getParent() );
>Files.copy( zipFile.getInputStream( entry ), targetFile );
> }
> {code}
>
> Found via LGTM.com scan
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MWRAPPER-13) Unclear how to use maven-wrapper-plugin
[
https://issues.apache.org/jira/browse/MWRAPPER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MWRAPPER-13:
--
Affects Version/s: 3.0.2
> Unclear how to use maven-wrapper-plugin
> ---
>
> Key: MWRAPPER-13
> URL: https://issues.apache.org/jira/browse/MWRAPPER-13
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Plugin
>Affects Versions: 3.0.2
>Reporter: Austin Doupnik
>Priority: Major
>
> I have heavily used the takari plugin in the past and am comparing to that.
> The takari plugin documentation is very clear and easy to follow, simply run
> {code:bash}
> mvn -N io.takari:maven:0.7.7:wrapper
> {code}
> I am attempting to follow what is documented
> [here|http://maven.apache.org/plugins/maven-wrapper-plugin/usage.html], but
> running into a number of problems.
> h2. Setup
> {code:bash}
> $ ~/Applications/apache-maven-3.8.1/bin/mvn archetype:generate
> -DartifactId=example -DgroupId=example -B
>
> $ cd example
> {code}
> h2. Following the documentation
> {code:bash}
> $ ~/Applications/apache-maven-3.8.1/bin/mvn wrapper
>
> [INFO] Scanning for projects...
> [INFO]
> [INFO] --< example:example
> >---
> [INFO] Building example 1.0-SNAPSHOT
> [INFO] [ jar
> ]-
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.093 s
> [INFO] Finished at: 2021-05-02T13:52:38-07:00
> [INFO]
>
> [ERROR] Unknown lifecycle phase "wrapper". You must specify a valid lifecycle
> phase or a goal in the format : or
> :[:]:. Available
> lifecycle phases are: validate, initialize, generate-sources,
> process-sources, generate-resources, process-resources, compile,
> process-classes, generate-test-sources, process-test-sources,
> generate-test-resources, process-test-resources, test-compile,
> process-test-classes, test, prepare-package, package, pre-integration-test,
> integration-test, post-integration-test, verify, install, deploy, pre-clean,
> clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/LifecyclePhaseNotFoundException
> {code}
> h2. Trying something else
> {code:bash}
> $ ~/Applications/apache-maven-3.8.1/bin/mvn wrapper:wrapper
>
> [INFO] Scanning for projects...
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-jar-plugin/2.4/maven-jar-plugin-2.4.jar
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-jar-plugin/2.4/maven-jar-plugin-2.4.jar
> (34 kB at 76 kB/s)
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/3.1/maven-compiler-plugin-3.1.jar
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/3.1/maven-compiler-plugin-3.1.jar
> (43 kB at 682 kB/s)
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.12.4/maven-surefire-plugin-2.12.4.jar
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.12.4/maven-surefire-plugin-2.12.4.jar
> (30 kB at 725 kB/s)
> [INFO]
> [INFO] --< example:example
> >---
> [INFO] Building example 1.0-SNAPSHOT
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-wrapper-plugin:3.0.1:wrapper (default-cli) @ example ---
> [WARNING] The POM for org.apache.maven:apache-maven-wrapper:zip:script:3.8.1
> is missing, no dependency information available
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.622 s
> [INFO] Finished at: 2021-05-02T13:54:08-07:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-wrapper-plugin
[jira] [Updated] (MWRAPPER-15) Support SNAPSHOT versions
[
https://issues.apache.org/jira/browse/MWRAPPER-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MWRAPPER-15:
--
Affects Version/s: 3.0.2
> Support SNAPSHOT versions
> -
>
> Key: MWRAPPER-15
> URL: https://issues.apache.org/jira/browse/MWRAPPER-15
> Project: Maven Wrapper
> Issue Type: New Feature
>Affects Versions: 3.0.2
>Reporter: Slawomir Jaranowski
>Priority: Normal
>
> In some case I would test build with the latest snapshot maven version.
> Such possibility can help other to easy test maven version under development.
> Would be great to have possibility to provide {{mavenVersion}} like:
> {{4.0.0-alpha-1-SNAPSHOT}} or even only {{SNAPSHOT}} in this case last
> {{SNAPSHOT}} version should be used.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7357) All Maven Core JARs have unusual entry order
[
https://issues.apache.org/jira/browse/MNG-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457978#comment-17457978
]
Herve Boutemy commented on MNG-7357:
bq. checked Plexus Archiver and it does add META-INF/ first and then then
manifest
since which version?
I'm sure it has not always been the case
> All Maven Core JARs have unusual entry order
>
>
> Key: MNG-7357
> URL: https://issues.apache.org/jira/browse/MNG-7357
> Project: Maven
> Issue Type: Bug
>Reporter: Michael Osipov
>Priority: Minor
>
> Built from 3a06530dbce82e2054afa3cc4c81631910474bd0 I receive this:
> {noformat}
> mosipov@bsd1srv:/usr/home/mosipov/var/Projekte/maven (master *=)
> $ find . -name maven-\*4.0.0-alpha-1-SNAPSHOT.jar -type f -exec sh -c
> 'zipinfo {} | head -4' \; 2>&1 | less
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:04 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 20-Jan-26 09:04 META-INF/
> Archive:
> ./maven-model-builder/target/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 217583 bytes, number of entries: 173
> -rw-r--r-- 2.0 unx 352 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive: ./maven-model/target/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 203201 bytes, number of entries: 76
> -rw-r--r-- 2.0 unx 336 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive:
> ./maven-slf4j-provider/target/maven-slf4j-provider-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 25315 bytes, number of entries: 26
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:04 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 20-Jan-26 09:04 META-INF/
> Archive:
> ./maven-model-builder/target/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 217583 bytes, number of entries: 173
> -rw-r--r-- 2.0 unx 352 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive: ./maven-model/target/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 203201 bytes, number of entries: 76
> -rw-r--r-- 2.0 unx 336 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive:
> ./maven-slf4j-provider/target/maven-slf4j-provider-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 25315 bytes, number of entries: 26
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:04 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 20-Jan-26 09:04 META-INF/
> Archive:
> ./maven-model-builder/target/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 217583 bytes, number of entries: 173
> -rw-r--r-- 2.0 unx 352 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive: ./maven-model/target/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 203201 bytes, number of entries: 76
> -rw-r--r-- 2.0 unx 336 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive:
> ./maven-slf4j-provider/target/maven-slf4j-provider-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 25315 bytes, number of entries: 26
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:04 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 20-Jan-26 09:04 META-INF/
> Archive:
> ./maven-model-builder/target/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 217583 bytes, number of entries: 173
> -rw-r--r-- 2.0 unx 352 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive: ./maven-model/target/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 203201 bytes, number of entries: 76
> -rw-r--r-- 2.0 unx 336 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive:
> ./maven-slf4j-provider/target/maven-slf4j-provider-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 25315 bytes, number of entries: 26
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:04 META-INF/MANI
[jira] [Commented] (MNG-7357) All Maven Core JARs have unusual entry order
[
https://issues.apache.org/jira/browse/MNG-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457979#comment-17457979
]
Michael Osipov commented on MNG-7357:
-
I looked at the one at GitHub master. I haven't checked history of Maven JAR
Plugin which handles off to Maven ARchiver, Plexus Archiver and Commons
Compress.
> All Maven Core JARs have unusual entry order
>
>
> Key: MNG-7357
> URL: https://issues.apache.org/jira/browse/MNG-7357
> Project: Maven
> Issue Type: Bug
>Reporter: Michael Osipov
>Priority: Minor
>
> Built from 3a06530dbce82e2054afa3cc4c81631910474bd0 I receive this:
> {noformat}
> mosipov@bsd1srv:/usr/home/mosipov/var/Projekte/maven (master *=)
> $ find . -name maven-\*4.0.0-alpha-1-SNAPSHOT.jar -type f -exec sh -c
> 'zipinfo {} | head -4' \; 2>&1 | less
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:04 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 20-Jan-26 09:04 META-INF/
> Archive:
> ./maven-model-builder/target/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 217583 bytes, number of entries: 173
> -rw-r--r-- 2.0 unx 352 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive: ./maven-model/target/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 203201 bytes, number of entries: 76
> -rw-r--r-- 2.0 unx 336 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive:
> ./maven-slf4j-provider/target/maven-slf4j-provider-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 25315 bytes, number of entries: 26
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:04 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 20-Jan-26 09:04 META-INF/
> Archive:
> ./maven-model-builder/target/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 217583 bytes, number of entries: 173
> -rw-r--r-- 2.0 unx 352 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive: ./maven-model/target/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 203201 bytes, number of entries: 76
> -rw-r--r-- 2.0 unx 336 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive:
> ./maven-slf4j-provider/target/maven-slf4j-provider-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 25315 bytes, number of entries: 26
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:04 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 20-Jan-26 09:04 META-INF/
> Archive:
> ./maven-model-builder/target/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 217583 bytes, number of entries: 173
> -rw-r--r-- 2.0 unx 352 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive: ./maven-model/target/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 203201 bytes, number of entries: 76
> -rw-r--r-- 2.0 unx 336 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive:
> ./maven-slf4j-provider/target/maven-slf4j-provider-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 25315 bytes, number of entries: 26
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:04 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 20-Jan-26 09:04 META-INF/
> Archive:
> ./maven-model-builder/target/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 217583 bytes, number of entries: 173
> -rw-r--r-- 2.0 unx 352 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive: ./maven-model/target/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 203201 bytes, number of entries: 76
> -rw-r--r-- 2.0 unx 336 b- defN 21-Apr-05 08:12 META-INF/MANIFEST.MF
> drwxr-xr-x 2.0 unx0 b- stor 21-Apr-05 08:12 META-INF/
> Archive:
> ./maven-slf4j-provider/target/maven-slf4j-provider-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 25315 bytes, number of entries: 26
> Archive: ./maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Zip file size: 7277 bytes, number of entries: 10
> -rw-r--r-- 2.0 unx 358 b- defN 20-Jan-26 09:0
[jira] [Updated] (DOXIASITETOOLS-235) Upgrade Maven Doxia to 1.11
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIASITETOOLS-235: -- Summary: Upgrade Maven Doxia to 1.11 (was: Upgrade Maven Doxia to 1.11.1) > Upgrade Maven Doxia to 1.11 > --- > > Key: DOXIASITETOOLS-235 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-235 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 1.11 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (DOXIASITETOOLS-236) Deprecate Doxia Sitetools Doc Renderer
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIASITETOOLS-236: -- Fix Version/s: 1.11.1 > Deprecate Doxia Sitetools Doc Renderer > -- > > Key: DOXIASITETOOLS-236 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-236 > Project: Maven Doxia Sitetools > Issue Type: Task > Components: Doc renderer >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 1.11, 1.11.1 > > > Doxia 1.11 will deprecate all page-oriented modules, means this module will > rely on code being deprecated and marked for removal. Therefore, we cannot > support page-oriented output. Only website-oriented one will remain. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (DOXIASITETOOLS-234) improve documentation on site.xml inheritance vs interpolation
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIASITETOOLS-234: -- Fix Version/s: 1.11.1 > improve documentation on site.xml inheritance vs interpolation > -- > > Key: DOXIASITETOOLS-234 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-234 > Project: Maven Doxia Sitetools > Issue Type: Improvement > Components: Decoration model, Integration Tools >Affects Versions: 1.7, 1.7.1, 1.10 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 1.11, 1.11.1 > > > after DOXIASITETOOLS-118 and DOXIASITETOOLS-158 updates, as integrated in > Maven Site Plugin > https://maven.apache.org/plugins/maven-site-plugin/history.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (DOXIASITETOOLS-237) Upgrade Maven Doxia to 1.11.1
Michael Osipov created DOXIASITETOOLS-237: - Summary: Upgrade Maven Doxia to 1.11.1 Key: DOXIASITETOOLS-237 URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-237 Project: Maven Doxia Sitetools Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (DOXIASITETOOLS-237) Upgrade Maven Doxia to 1.11.1
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIASITETOOLS-237: -- Fix Version/s: 1.11.1 > Upgrade Maven Doxia to 1.11.1 > - > > Key: DOXIASITETOOLS-237 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-237 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 1.11.1 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-javadoc-plugin] dependabot[bot] commented on pull request #110: Bump doxia-sink-api from 1.9.1 to 1.11.1
dependabot[bot] commented on pull request #110: URL: https://github.com/apache/maven-javadoc-plugin/pull/110#issuecomment-991925503 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- 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-javadoc-plugin] slachiewicz closed pull request #110: Bump doxia-sink-api from 1.9.1 to 1.11.1
slachiewicz closed pull request #110: URL: https://github.com/apache/maven-javadoc-plugin/pull/110 -- 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] (DOXIASITETOOLS-148) Remove SiteRenderingContext#publishDate (undo DOXIASITETOOLS-63)
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457980#comment-17457980
]
Michael Osipov commented on DOXIASITETOOLS-148:
---
[~hboutemy], I think this should default to {{project.build.outputTimestamp}}
if set. The site remains reproducible. WDYT?
> Remove SiteRenderingContext#publishDate (undo DOXIASITETOOLS-63)
>
>
> Key: DOXIASITETOOLS-148
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-148
> Project: Maven Doxia Sitetools
> Issue Type: Task
> Components: Site renderer
>Affects Versions: 1.6
>Reporter: Michael Osipov
>Priority: Major
>
> The field {{publishDate}} has been introduced DOXIATESITETOOLS-63 but cannot
> be set anywhere. Either provide a sane setting option including proper
> documentation or drop it completely.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (DOXIASITETOOLS-148) Remove SiteRenderingContext#publishDate (undo DOXIASITETOOLS-63)
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457991#comment-17457991
]
Herve Boutemy commented on DOXIASITETOOLS-148:
--
this is probably a step in the right direction, yes
even if I suppose nobody will check if it is sufficient: having a reproducible
site is IMHO a huge ambition, given how having a reproducible binary is already
hard
> Remove SiteRenderingContext#publishDate (undo DOXIASITETOOLS-63)
>
>
> Key: DOXIASITETOOLS-148
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-148
> Project: Maven Doxia Sitetools
> Issue Type: Task
> Components: Site renderer
>Affects Versions: 1.6
>Reporter: Michael Osipov
>Priority: Major
>
> The field {{publishDate}} has been introduced DOXIATESITETOOLS-63 but cannot
> be set anywhere. Either provide a sane setting option including proper
> documentation or drop it completely.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (DOXIASITETOOLS-148) Remove SiteRenderingContext#publishDate (undo DOXIASITETOOLS-63)
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457998#comment-17457998
]
Michael Osipov commented on DOXIASITETOOLS-148:
---
I don't strive for it currently, but trying to grap low hanging fruits. If we
know that we have this information supply it to the generation in site,
javadoc, jxr, pmd, etc.
> Remove SiteRenderingContext#publishDate (undo DOXIASITETOOLS-63)
>
>
> Key: DOXIASITETOOLS-148
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-148
> Project: Maven Doxia Sitetools
> Issue Type: Task
> Components: Site renderer
>Affects Versions: 1.6
>Reporter: Michael Osipov
>Priority: Major
>
> The field {{publishDate}} has been introduced DOXIATESITETOOLS-63 but cannot
> be set anywhere. Either provide a sane setting option including proper
> documentation or drop it completely.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MSITE-876) Execution default-deploy of goal ...deploy failed: An API incompatibility was encountered while executing ....deploy: java.lang.NoSuchMethodError: org.apache.maven.wagon
[
https://issues.apache.org/jira/browse/MSITE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458000#comment-17458000
]
Sylwester Lachiewicz commented on MSITE-876:
Good. You know better Wagon related stuff. Let's see. Thx for explanation
> Execution default-deploy of goal ...deploy failed: An API incompatibility was
> encountered while executing deploy: java.lang.NoSuchMethodError:
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
> --
>
> Key: MSITE-876
> URL: https://issues.apache.org/jira/browse/MSITE-876
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.9.1
>Reporter: Konrad Windszus
>Priority: Major
>
> When using maven-site-plugin 3.9.1 with the additional plugin dependency
> {{org.apache.maven.wagon:wagon-webdav-jackrabbit:3.3.1}} I experience the
> following error
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy (default-deploy) on
> project ...: Execution default-deploy of goal
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy:
> java.lang.NoSuchMethodError:
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.9.1
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/plugins/maven-site-plugin/3.9.1/maven-site-plugin-3.9.1.jar
> [ERROR] urls[1] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/wagon/wagon-webdav-jackrabbit/3.3.1/wagon-webdav-jackrabbit-3.3.1.jar
> [ERROR] urls[2] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/wagon/wagon-http-shared/3.3.1/wagon-http-shared-3.3.1.jar
> [ERROR] urls[3] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/jsoup/jsoup/1.11.2/jsoup-1.11.2.jar
> [ERROR] urls[4] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/jackrabbit/jackrabbit-webdav/2.14.4/jackrabbit-webdav-2.14.4.jar
> [ERROR] urls[5] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/commons-codec/commons-codec/1.10/commons-codec-1.10.jar
> [ERROR] urls[6] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/slf4j/jcl-over-slf4j/1.7.25/jcl-over-slf4j-1.7.25.jar
> [ERROR] urls[7] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/httpcomponents/httpclient/4.5.6/httpclient-4.5.6.jar
> [ERROR] urls[8] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/httpcomponents/httpcore/4.4.10/httpcore-4.4.10.jar
> [ERROR] urls[9] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar
> [ERROR] urls[10] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/reporting/maven-reporting-exec/1.5.1/maven-reporting-exec-1.5.1.jar
> [ERROR] urls[11] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> [ERROR] urls[12] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/eclipse/aether/aether-util/0.9.0.M2/aether-util-0.9.0.M2.jar
> [ERROR] urls[13] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/shared/maven-shared-utils/3.1.0/maven-shared-utils-3.1.0.jar
> [ERROR] urls[14] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> [ERROR] urls[15] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/codehaus/plexus/plexus-component-annotations/2.0.0/plexus-component-annotations-2.0.0.jar
> [ERROR] urls[16] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> [ERROR] urls[17] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> [ERROR] urls[18] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/maven-archiver/3.5.0/maven-archiver-3.5.0.jar
> [ERROR] urls[19] =
> file:/var/
[jira] [Updated] (MSITE-876) Execution default-deploy of goal ...deploy failed: An API incompatibility was encountered while executing ....deploy: java.lang.NoSuchMethodError: org.apache.maven.wagon.s
[
https://issues.apache.org/jira/browse/MSITE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated MSITE-876:
---
Priority: Major (was: Blocker)
> Execution default-deploy of goal ...deploy failed: An API incompatibility was
> encountered while executing deploy: java.lang.NoSuchMethodError:
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
> --
>
> Key: MSITE-876
> URL: https://issues.apache.org/jira/browse/MSITE-876
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.9.1
>Reporter: Konrad Windszus
>Priority: Major
>
> When using maven-site-plugin 3.9.1 with the additional plugin dependency
> {{org.apache.maven.wagon:wagon-webdav-jackrabbit:3.3.1}} I experience the
> following error
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy (default-deploy) on
> project ...: Execution default-deploy of goal
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy:
> java.lang.NoSuchMethodError:
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.9.1
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/plugins/maven-site-plugin/3.9.1/maven-site-plugin-3.9.1.jar
> [ERROR] urls[1] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/wagon/wagon-webdav-jackrabbit/3.3.1/wagon-webdav-jackrabbit-3.3.1.jar
> [ERROR] urls[2] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/wagon/wagon-http-shared/3.3.1/wagon-http-shared-3.3.1.jar
> [ERROR] urls[3] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/jsoup/jsoup/1.11.2/jsoup-1.11.2.jar
> [ERROR] urls[4] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/jackrabbit/jackrabbit-webdav/2.14.4/jackrabbit-webdav-2.14.4.jar
> [ERROR] urls[5] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/commons-codec/commons-codec/1.10/commons-codec-1.10.jar
> [ERROR] urls[6] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/slf4j/jcl-over-slf4j/1.7.25/jcl-over-slf4j-1.7.25.jar
> [ERROR] urls[7] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/httpcomponents/httpclient/4.5.6/httpclient-4.5.6.jar
> [ERROR] urls[8] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/httpcomponents/httpcore/4.4.10/httpcore-4.4.10.jar
> [ERROR] urls[9] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar
> [ERROR] urls[10] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/reporting/maven-reporting-exec/1.5.1/maven-reporting-exec-1.5.1.jar
> [ERROR] urls[11] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> [ERROR] urls[12] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/eclipse/aether/aether-util/0.9.0.M2/aether-util-0.9.0.M2.jar
> [ERROR] urls[13] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/shared/maven-shared-utils/3.1.0/maven-shared-utils-3.1.0.jar
> [ERROR] urls[14] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> [ERROR] urls[15] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/codehaus/plexus/plexus-component-annotations/2.0.0/plexus-component-annotations-2.0.0.jar
> [ERROR] urls[16] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> [ERROR] urls[17] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> [ERROR] urls[18] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/maven-archiver/3.5.0/maven-archiver-3.5.0.jar
> [ERROR] urls[19] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/s
[jira] [Closed] (DOXIASITETOOLS-237) Upgrade Maven Doxia to 1.11.1
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIASITETOOLS-237. - Resolution: Fixed Fixed with [49319f4574ccd28691a03e96a26242927262aaad|https://gitbox.apache.org/repos/asf?p=maven-doxia-sitetools.git;a=commit;h=49319f4574ccd28691a03e96a26242927262aaad]. > Upgrade Maven Doxia to 1.11.1 > - > > Key: DOXIASITETOOLS-237 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-237 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 1.11.1 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (DOXIASITETOOLS-237) Upgrade Maven Doxia to 1.11.1
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458001#comment-17458001 ] Michael Osipov edited comment on DOXIASITETOOLS-237 at 12/12/21, 4:56 PM: -- Fixed with [a264e00c14bbc61bf710fd484a750fb6bff1f51a|https://gitbox.apache.org/repos/asf?p=maven-doxia-sitetools.git;a=commit;h=a264e00c14bbc61bf710fd484a750fb6bff1f51a]. was (Author: michael-o): Fixed with [49319f4574ccd28691a03e96a26242927262aaad|https://gitbox.apache.org/repos/asf?p=maven-doxia-sitetools.git;a=commit;h=49319f4574ccd28691a03e96a26242927262aaad]. > Upgrade Maven Doxia to 1.11.1 > - > > Key: DOXIASITETOOLS-237 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-237 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 1.11.1 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-release] slachiewicz commented on pull request #75: Bump maven-invoker from 2.2 to 3.1.0
slachiewicz commented on pull request #75: URL: https://github.com/apache/maven-release/pull/75#issuecomment-991932754 @dependabot recreate -- 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] (MSITE-876) Execution default-deploy of goal ...deploy failed: An API incompatibility was encountered while executing ....deploy: java.lang.NoSuchMethodError: org.apache.maven.wagon
[
https://issues.apache.org/jira/browse/MSITE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458002#comment-17458002
]
Michael Osipov commented on MSITE-876:
--
[~slachiewicz], most important is to verify "Downgrade WebDAV module to the
same version as in 3.5.4", but [~kwin] hasn't done yet.
> Execution default-deploy of goal ...deploy failed: An API incompatibility was
> encountered while executing deploy: java.lang.NoSuchMethodError:
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
> --
>
> Key: MSITE-876
> URL: https://issues.apache.org/jira/browse/MSITE-876
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.9.1
>Reporter: Konrad Windszus
>Priority: Major
>
> When using maven-site-plugin 3.9.1 with the additional plugin dependency
> {{org.apache.maven.wagon:wagon-webdav-jackrabbit:3.3.1}} I experience the
> following error
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy (default-deploy) on
> project ...: Execution default-deploy of goal
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy:
> java.lang.NoSuchMethodError:
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.9.1
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/plugins/maven-site-plugin/3.9.1/maven-site-plugin-3.9.1.jar
> [ERROR] urls[1] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/wagon/wagon-webdav-jackrabbit/3.3.1/wagon-webdav-jackrabbit-3.3.1.jar
> [ERROR] urls[2] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/wagon/wagon-http-shared/3.3.1/wagon-http-shared-3.3.1.jar
> [ERROR] urls[3] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/jsoup/jsoup/1.11.2/jsoup-1.11.2.jar
> [ERROR] urls[4] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/jackrabbit/jackrabbit-webdav/2.14.4/jackrabbit-webdav-2.14.4.jar
> [ERROR] urls[5] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/commons-codec/commons-codec/1.10/commons-codec-1.10.jar
> [ERROR] urls[6] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/slf4j/jcl-over-slf4j/1.7.25/jcl-over-slf4j-1.7.25.jar
> [ERROR] urls[7] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/httpcomponents/httpclient/4.5.6/httpclient-4.5.6.jar
> [ERROR] urls[8] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/httpcomponents/httpcore/4.4.10/httpcore-4.4.10.jar
> [ERROR] urls[9] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar
> [ERROR] urls[10] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/reporting/maven-reporting-exec/1.5.1/maven-reporting-exec-1.5.1.jar
> [ERROR] urls[11] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> [ERROR] urls[12] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/eclipse/aether/aether-util/0.9.0.M2/aether-util-0.9.0.M2.jar
> [ERROR] urls[13] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/shared/maven-shared-utils/3.1.0/maven-shared-utils-3.1.0.jar
> [ERROR] urls[14] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> [ERROR] urls[15] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/codehaus/plexus/plexus-component-annotations/2.0.0/plexus-component-annotations-2.0.0.jar
> [ERROR] urls[16] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> [ERROR] urls[17] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> [ERROR] urls[18] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/maven-archiver/3.5.0/maven-archiv
[GitHub] [maven-release] slachiewicz commented on pull request #83: Bump commons-cli from 1.2 to 1.5.0
slachiewicz commented on pull request #83: URL: https://github.com/apache/maven-release/pull/83#issuecomment-991932896 @dependabot rebase -- 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-release] slachiewicz commented on pull request #81: Bump maven-scm-manager-plexus from 1.8 to 1.12.0
slachiewicz commented on pull request #81: URL: https://github.com/apache/maven-release/pull/81#issuecomment-991932928 @dependabot rebase -- 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-release] slachiewicz commented on pull request #80: Bump plexus-utils from 3.0.15 to 3.4.1
slachiewicz commented on pull request #80: URL: https://github.com/apache/maven-release/pull/80#issuecomment-991932953 @dependabot rebase -- 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-release] slachiewicz commented on pull request #79: Bump scmVersion from 1.11.3 to 1.12.0
slachiewicz commented on pull request #79: URL: https://github.com/apache/maven-release/pull/79#issuecomment-991932990 @dependabot rebase -- 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] (MNG-7358) Can't debug with mvnDebug with version 4
[
https://issues.apache.org/jira/browse/MNG-7358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458013#comment-17458013
]
Michael Osipov commented on MNG-7358:
-
Well, works for me:
!screenshot-1.png!
Version: Photon Release (4.8.0)
Build id: 20180619-1200
> Can't debug with mvnDebug with version 4
>
>
> Key: MNG-7358
> URL: https://issues.apache.org/jira/browse/MNG-7358
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 4.0.x-candidate
> Environment: Linux
> 3.8.3
> $ mvn --version
> Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
> Apache Maven 3.8.3 (NON_CANONICAL)
> Maven home: /opt/maven
> Java version: 1.8.0_292, vendor: Oracle Corporation, runtime:
> /usr/lib/jvm/java-8-openjdk/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "5.15.5-arch1-1", arch: "amd64", family: "unix"
> 4.0.0
> Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
> Apache Maven 4.0.0-alpha-1-SNAPSHOT (3a06530dbce82e2054afa3cc4c81631910474bd0)
> Maven home: /opt/maven-git
> Java version: 1.8.0_292, vendor: Oracle Corporation, runtime:
> /usr/lib/jvm/java-8-openjdk/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "5.15.5-arch1-1", arch: "amd64", family: "unix"
>Reporter: Odne Hellebø
>Priority: Minor
> Attachments: image-2021-12-11-21-55-46-230.png, intellijDebug.png,
> mvnDebugGit.zip, screenshot-1.png
>
>
> When using mvnDebug at version 4, it just skips all the breakpoints in
> intellij.
> These are the settings in intellij
> !intellijDebug.png!
> To reproduce just set some breakpoints in test, and then run
> {code:bash}mvnDebug test{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-7358) Can't debug with mvnDebug with version 4
[
https://issues.apache.org/jira/browse/MNG-7358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7358:
Attachment: screenshot-1.png
> Can't debug with mvnDebug with version 4
>
>
> Key: MNG-7358
> URL: https://issues.apache.org/jira/browse/MNG-7358
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 4.0.x-candidate
> Environment: Linux
> 3.8.3
> $ mvn --version
> Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
> Apache Maven 3.8.3 (NON_CANONICAL)
> Maven home: /opt/maven
> Java version: 1.8.0_292, vendor: Oracle Corporation, runtime:
> /usr/lib/jvm/java-8-openjdk/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "5.15.5-arch1-1", arch: "amd64", family: "unix"
> 4.0.0
> Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
> Apache Maven 4.0.0-alpha-1-SNAPSHOT (3a06530dbce82e2054afa3cc4c81631910474bd0)
> Maven home: /opt/maven-git
> Java version: 1.8.0_292, vendor: Oracle Corporation, runtime:
> /usr/lib/jvm/java-8-openjdk/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "5.15.5-arch1-1", arch: "amd64", family: "unix"
>Reporter: Odne Hellebø
>Priority: Minor
> Attachments: image-2021-12-11-21-55-46-230.png, intellijDebug.png,
> mvnDebugGit.zip, screenshot-1.png
>
>
> When using mvnDebug at version 4, it just skips all the breakpoints in
> intellij.
> These are the settings in intellij
> !intellijDebug.png!
> To reproduce just set some breakpoints in test, and then run
> {code:bash}mvnDebug test{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-clean-plugin] dependabot[bot] opened a new pull request #3: Bump maven-shared-utils from 3.2.1 to 3.3.4
dependabot[bot] opened a new pull request #3: URL: https://github.com/apache/maven-clean-plugin/pull/3 Bumps [maven-shared-utils](https://github.com/apache/maven-shared-utils) from 3.2.1 to 3.3.4. Commits https://github.com/apache/maven-shared-utils/commit/17091d82508deb9b7067f3434ba16f660ffc5023";>17091d8 [maven-release-plugin] prepare release maven-shared-utils-3.3.4 https://github.com/apache/maven-shared-utils/commit/9f40037bfb04d54dd997a9ab837390045c9a4348";>9f40037 [NOJIRA] Javadoc cleanup in preparation of release https://github.com/apache/maven-shared-utils/commit/4e93c5621ef45c7cf6a03d96ca7a3c45ac4e2062";>4e93c56 [SUREFIRE-1556] fail fast on empty element names (https://github-redirect.dependabot.com/apache/maven-shared-utils/issues/11";>#11) https://github.com/apache/maven-shared-utils/commit/1461e4de42c324a71decfefe0c51a6f80f05f9e2";>1461e4d Revert "remove unused plexus dependency" https://github.com/apache/maven-shared-utils/commit/8f31df7af9383d278fc5513729e1bdcf254fd997";>8f31df7 update to JUnit 4.13.2 https://github.com/apache/maven-shared-utils/commit/5097ceefd24fc83e005bdfa4e254975b025733ad";>5097cee remove unused plexus dependency https://github.com/apache/maven-shared-utils/commit/b4577c968a84be979e31347d0525f3714724bcd5";>b4577c9 Merge pull request https://github-redirect.dependabot.com/apache/maven-shared-utils/issues/70";>#70 from gnodet/MSHARED-965-help https://github.com/apache/maven-shared-utils/commit/eb4f6355d772739094bcf8edce5d7da894ca8be5";>eb4f635 Merge pull request https://github-redirect.dependabot.com/apache/maven-shared-utils/issues/67";>#67 from gnodet/MNG-6380 https://github.com/apache/maven-shared-utils/commit/0bb44cdc9541beeb9c78927c663d16b6d737eb09";>0bb44cd [MNG-6380] Use the new jansi AnsiMode to control the whether ansi sequences a... https://github.com/apache/maven-shared-utils/commit/f94bb250dcddcddadc610aa7cc28d7b07a9697ed";>f94bb25 [MNG-6915] Add a helper method to get the terminal width Additional commits viewable in https://github.com/apache/maven-shared-utils/compare/maven-shared-utils-3.2.1...maven-shared-utils-3.3.4";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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-install-plugin] cstamas merged pull request #17: [MINSTALL-171] Update plugin (requires Maven 3.2.5+)
cstamas merged pull request #17: URL: https://github.com/apache/maven-install-plugin/pull/17 -- 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] (MINSTALL-171) Update plugin (requires Maven 3.2.5+)
[ https://issues.apache.org/jira/browse/MINSTALL-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák closed MINSTALL-171. > Update plugin (requires Maven 3.2.5+) > - > > Key: MINSTALL-171 > URL: https://issues.apache.org/jira/browse/MINSTALL-171 > Project: Maven Install Plugin > Issue Type: Task >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák >Priority: Major > Fix For: 3.0.0-M2 > > > Update plugin source and dependencies: > * update Maven requirement to 3.2.5+ > * drop org.sonatype resolver, use org.eclipse > * set maven bits to provided > * drop legacy dependencies, use current ones -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (MINSTALL-171) Update plugin (requires Maven 3.2.5+)
[ https://issues.apache.org/jira/browse/MINSTALL-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák resolved MINSTALL-171. -- Resolution: Fixed > Update plugin (requires Maven 3.2.5+) > - > > Key: MINSTALL-171 > URL: https://issues.apache.org/jira/browse/MINSTALL-171 > Project: Maven Install Plugin > Issue Type: Task >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák >Priority: Major > Fix For: 3.0.0-M2 > > > Update plugin source and dependencies: > * update Maven requirement to 3.2.5+ > * drop org.sonatype resolver, use org.eclipse > * set maven bits to provided > * drop legacy dependencies, use current ones -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MNG-7355) Error with minify
[
https://issues.apache.org/jira/browse/MNG-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458027#comment-17458027
]
Odne Hellebø commented on MNG-7355:
---
I've reported it upstream, but I'm doubting that anyone will do anything.
https://github.com/samaxes/minify-maven-plugin/issues/174
> Error with minify
> -
>
> Key: MNG-7355
> URL: https://issues.apache.org/jira/browse/MNG-7355
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 4.0.0-alpha-1
> Environment: Linux ITPC118 5.15.5-arch1-1 #1 SMP PREEMPT Thu, 25 Nov
> 2021 22:09:33 + x86_64 GNU/Linux
> (Maven 4 version)
> $ /home/plitter/.build/maven4/target/bin/mvn --version
> Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
> Apache Maven 4.0.0-alpha-1-SNAPSHOT (3a06530dbce82e2054afa3cc4c81631910474bd0)
> Maven home: /home/plitter/.build/maven4/target
> Java version: 1.8.0_292, vendor: Oracle Corporation, runtime:
> /usr/lib/jvm/java-8-openjdk/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "5.15.5-arch1-1", arch: "amd64", family: "unix"
> (Maven 3 version)
> $ mvn --version
> Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
> Apache Maven 3.8.3 (NON_CANONICAL)
> Maven home: /opt/maven
> Java version: 1.8.0_292, vendor: Oracle Corporation, runtime:
> /usr/lib/jvm/java-8-openjdk/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "5.15.5-arch1-1", arch: "amd64", family: "unix"
>Reporter: Odne Hellebø
>Assignee: Michael Osipov
>Priority: Minor
> Attachments: foobar.zip, image (15).png, image (16).png,
> wholeBuild.log
>
>
> I'm trying to build a large project with maven 4, and have gotten an error
> {code:sh}
> Failed to execute goal com.samaxes.maven:minify-maven-plugin:1.7.4:minify
> (default-minify) on project core: java.lang.NoClassDefFoundError:
> org/codehaus/plexus/util/IOUtil: org.codehaus.plexus.util.IOUtil -> [Help
> 1]{code}
> I tried deleting my {code:sh}.m2{code} folder and build with -U. Still same
> error. Then I checked that I have org/codehaus... were in the .m2 folder, and
> that it had org.codehaus.plexus.util.IOUtil in the jar (see pictures).
> {code:pom}
>
> com.samaxes.maven
> minify-maven-plugin
> 1.7.4
>
>
> default-minify
>
> UTF-8
> .
>
>
> surveillance/style.css
>
> style.demo.css
> .
>
>
> surveillance/index.js
>
> surveillance/stats.js
>
> script.demo.js
> CLOSURE
>
>
> minify
>
>
>
>
> {code}
> Am I doing something wrong? It was working in maven 3.8.3.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7355) Error with minify
[
https://issues.apache.org/jira/browse/MNG-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458029#comment-17458029
]
Michael Osipov commented on MNG-7355:
-
Then go for the second approach I have sketched.
> Error with minify
> -
>
> Key: MNG-7355
> URL: https://issues.apache.org/jira/browse/MNG-7355
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 4.0.0-alpha-1
> Environment: Linux ITPC118 5.15.5-arch1-1 #1 SMP PREEMPT Thu, 25 Nov
> 2021 22:09:33 + x86_64 GNU/Linux
> (Maven 4 version)
> $ /home/plitter/.build/maven4/target/bin/mvn --version
> Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
> Apache Maven 4.0.0-alpha-1-SNAPSHOT (3a06530dbce82e2054afa3cc4c81631910474bd0)
> Maven home: /home/plitter/.build/maven4/target
> Java version: 1.8.0_292, vendor: Oracle Corporation, runtime:
> /usr/lib/jvm/java-8-openjdk/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "5.15.5-arch1-1", arch: "amd64", family: "unix"
> (Maven 3 version)
> $ mvn --version
> Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
> Apache Maven 3.8.3 (NON_CANONICAL)
> Maven home: /opt/maven
> Java version: 1.8.0_292, vendor: Oracle Corporation, runtime:
> /usr/lib/jvm/java-8-openjdk/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "5.15.5-arch1-1", arch: "amd64", family: "unix"
>Reporter: Odne Hellebø
>Assignee: Michael Osipov
>Priority: Minor
> Attachments: foobar.zip, image (15).png, image (16).png,
> wholeBuild.log
>
>
> I'm trying to build a large project with maven 4, and have gotten an error
> {code:sh}
> Failed to execute goal com.samaxes.maven:minify-maven-plugin:1.7.4:minify
> (default-minify) on project core: java.lang.NoClassDefFoundError:
> org/codehaus/plexus/util/IOUtil: org.codehaus.plexus.util.IOUtil -> [Help
> 1]{code}
> I tried deleting my {code:sh}.m2{code} folder and build with -U. Still same
> error. Then I checked that I have org/codehaus... were in the .m2 folder, and
> that it had org.codehaus.plexus.util.IOUtil in the jar (see pictures).
> {code:pom}
>
> com.samaxes.maven
> minify-maven-plugin
> 1.7.4
>
>
> default-minify
>
> UTF-8
> .
>
>
> surveillance/style.css
>
> style.demo.css
> .
>
>
> surveillance/index.js
>
> surveillance/stats.js
>
> script.demo.js
> CLOSURE
>
>
> minify
>
>
>
>
> {code}
> Am I doing something wrong? It was working in maven 3.8.3.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-release] slachiewicz commented on pull request #89: Change interface implemented by MavenArtifactVersion
slachiewicz commented on pull request #89: URL: https://github.com/apache/maven-release/pull/89#issuecomment-991964929 Nice finding. Thx -- 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-release] slachiewicz merged pull request #89: Change interface implemented by MavenArtifactVersion
slachiewicz merged pull request #89: URL: https://github.com/apache/maven-release/pull/89 -- 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] (MNG-7332) Remove --define CLI option
[
https://issues.apache.org/jira/browse/MNG-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458035#comment-17458035
]
Hudson commented on MNG-7332:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7129 #10
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7129/10/
> Remove --define CLI option
> --
>
> Key: MNG-7332
> URL: https://issues.apache.org/jira/browse/MNG-7332
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Remove support for the {{--define}} option.
> Rationale:
> # We can't get that to work properly with Commons CLI 1.5
> # Most likely, most of our users use {{-D}} as they think they're setting
> system properties (which happens to be a side effect of {{-D}}, not its goal)
> Not only remove code, also update website/docs for it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7332) Remove --define CLI option
[
https://issues.apache.org/jira/browse/MNG-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458037#comment-17458037
]
Hudson commented on MNG-7332:
-
Build unstable in Jenkins: Maven » Maven TLP » maven »
maven.config-from-start-scripts #3
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven.config-from-start-scripts/3/
> Remove --define CLI option
> --
>
> Key: MNG-7332
> URL: https://issues.apache.org/jira/browse/MNG-7332
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Remove support for the {{--define}} option.
> Rationale:
> # We can't get that to work properly with Commons CLI 1.5
> # Most likely, most of our users use {{-D}} as they think they're setting
> system properties (which happens to be a side effect of {{-D}}, not its goal)
> Not only remove code, also update website/docs for it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7332) Remove --define CLI option
[
https://issues.apache.org/jira/browse/MNG-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458038#comment-17458038
]
Hudson commented on MNG-7332:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7273 #8
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7273/8/
> Remove --define CLI option
> --
>
> Key: MNG-7332
> URL: https://issues.apache.org/jira/browse/MNG-7332
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Remove support for the {{--define}} option.
> Rationale:
> # We can't get that to work properly with Commons CLI 1.5
> # Most likely, most of our users use {{-D}} as they think they're setting
> system properties (which happens to be a side effect of {{-D}}, not its goal)
> Not only remove code, also update website/docs for it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7332) Remove --define CLI option
[
https://issues.apache.org/jira/browse/MNG-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458040#comment-17458040
]
Hudson commented on MNG-7332:
-
Build unstable in Jenkins: Maven » Maven TLP » maven »
MNG-7173-resolver-guice-module #12
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7173-resolver-guice-module/12/
> Remove --define CLI option
> --
>
> Key: MNG-7332
> URL: https://issues.apache.org/jira/browse/MNG-7332
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Remove support for the {{--define}} option.
> Rationale:
> # We can't get that to work properly with Commons CLI 1.5
> # Most likely, most of our users use {{-D}} as they think they're setting
> system properties (which happens to be a side effect of {{-D}}, not its goal)
> Not only remove code, also update website/docs for it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-resolver] asfgit closed pull request #131: [MRESOLVER-219] File advisory locking based NamedLocks
asfgit closed pull request #131: URL: https://github.com/apache/maven-resolver/pull/131 -- 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] (MRESOLVER-219) Implement NamedLock with advisory file locking
[ https://issues.apache.org/jira/browse/MRESOLVER-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MRESOLVER-219. Resolution: Fixed Fixed with [50df10dca354445f2f93356f08b21a6ee5143d0c|https://gitbox.apache.org/repos/asf?p=maven-resolver.git;a=commit;h=50df10dca354445f2f93356f08b21a6ee5143d0c]. > Implement NamedLock with advisory file locking > -- > > Key: MRESOLVER-219 > URL: https://issues.apache.org/jira/browse/MRESOLVER-219 > Project: Maven Resolver > Issue Type: Task > Components: Resolver >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák >Priority: Major > Fix For: 1.7.3 > > > To enable MT/MP builds on same FS. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MRESOLVER-133) Improve resolver performance by using breadth-first search
[ https://issues.apache.org/jira/browse/MRESOLVER-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458042#comment-17458042 ] Michael Osipov commented on MRESOLVER-133: -- [~wecai], can you take a look at this and how this intersects with your issue/PR? > Improve resolver performance by using breadth-first search > -- > > Key: MRESOLVER-133 > URL: https://issues.apache.org/jira/browse/MRESOLVER-133 > Project: Maven Resolver > Issue Type: Improvement > Components: Resolver >Affects Versions: 1.4.2 >Reporter: Gregory Ducharme >Priority: Major > Attachments: mvnbaddeps.zip > > > > I believe the maven resolver is unnecessarily inefficient because it performs > a depth-first search of components to resolve dependencies. Consider the case > when dependencies use version ranges, the user intent is for maven to resolve > with the highest versions of dependencies that satisfy all constraints. If > maven were to use a breadth-first search (and terminate searching as soon as > a solution is found) then in many cases a valid set of dependencies can be > resolved (at the top of the version ranges) without requiring that all > historical versions are resolvable. One should get the same answer with both > depth-first and breadth first strategies, but with the breadth-first approach > not being vulnerable to a missing parent POM somewhere in history making it > impossible to build the head of code. Additionally, I suspect that > breadth-first would be faster and use less memory than depth first. > > Additionally the depth-first approach has a weakness that when ny version of > a parent pom of a component referenced in a dependency tree of another > component is missing maven fails to resolve dependencies. One get a message > of the form: > Failed to execute goal on project module: Could not resolve dependencies for > project baddepdemo.project2:module:jar:1: Failed to collect dependencies ... > > Currently the only way to resolve this issue is one of three ways: > 1) restore a missing parent POM into the repository history, or > 2) delete all modules associated with the missing parent POM from the > repository > 3) manually adjust version ranges in consumer dependencies to exclude the > bad versions of dependencies that refer to the missing parent POM. > > What I would like is a configuration switch that would allow one to select > between the two search strategies So that the manual interventions described > above are not required. > > I have include a zip file that include the minimal projects needed to > demonstrate the dependency resolution problem: > project 1 has a module and parent pom. > project 2 is a single pom that has a dependency on the module in project 1. > Project 2 uses a dependency range [1,) that indicates that the latest version > of project1's module is to be used. > If one builds two versions (1 and 2) of project 1, project2 will resolve to > use version 2 as expected. However if you delete the parent pom of project1 > from the repository maven cannot resolve dependencies and fails. If the > version range in project 2 is changed to [2,) then the expected behavior is > observed. > The zip file contains a shell script (demo.sh) that can be run without > parameters to demonstrate the behavior when all versions are present in the > repository. Run it with 1 as a parameter (the lower end of the version range > used in project2) and the script will delete the parent pom from project 1 > and the error condition will be demonstrated. Run it with 2 and maven will > resolve dependencies as version1 of project1 is explicitly excluded from the > dependency resolution process. > > I am also willing to look at the source and propose a patch, but I would need > guidance on which modules/source I should look at. > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MNG-7332) Remove --define CLI option
[
https://issues.apache.org/jira/browse/MNG-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458044#comment-17458044
]
Hudson commented on MNG-7332:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » logger-levels-config #3
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/logger-levels-config/3/
> Remove --define CLI option
> --
>
> Key: MNG-7332
> URL: https://issues.apache.org/jira/browse/MNG-7332
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Remove support for the {{--define}} option.
> Rationale:
> # We can't get that to work properly with Commons CLI 1.5
> # Most likely, most of our users use {{-D}} as they think they're setting
> system properties (which happens to be a side effect of {{-D}}, not its goal)
> Not only remove code, also update website/docs for it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MRESOLVER-224) DefaultVersionResolver is inflicting ArtifactNotFoundException for classifiers with SNAPSHOT version
[
https://issues.apache.org/jira/browse/MRESOLVER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458043#comment-17458043
]
Michael Osipov commented on MRESOLVER-224:
--
[~tuomas_kiviaho], can you provide a sample project for this?
> DefaultVersionResolver is inflicting ArtifactNotFoundException for
> classifiers with SNAPSHOT version
>
>
> Key: MRESOLVER-224
> URL: https://issues.apache.org/jira/browse/MRESOLVER-224
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Affects Versions: 1.6.3
>Reporter: Tuomas Kiviaho
>Priority: Major
>
> I use classifier artifact along with the artifact itself as a dependency in a
> Maven Invoker Plugin project. The project that calls the invoker has the
> artifact itself as a dependency, but no reference to the classifier.
> This causes resolving of the maven-metadata.xml for the project itself plus
> downloading of the dependency artifact.When invoker is called the artifact is
> already downloaded to the local repo and cached with SNAPSHOT key.
> This causes the DefaultVersionResolver to merge the version information of
> the SNAPSHOT:jar artifact that is now being resolved with the
> already downloaded SNAPSHOT key. Since the local version is newer than the
> repo version the DefaultVersionResolver thinks SNAPSHOT:jar to
> be outdated thus overriding it with local repo.
> Since the SNAPSHOT:jar doesn't exist in the local repo there
> are no remote report left to try the DefaultArtifactResolver fails ultimately
> to ArtifactNotFoundException since there was no download task.
> {code:java}
> [INFO] [DEBUG] Resolving artifact
> .:jar::-SNAPSHOT from
> []{code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7332) Remove --define CLI option
[
https://issues.apache.org/jira/browse/MNG-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458045#comment-17458045
]
Hudson commented on MNG-7332:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » mojo-logging #16
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/mojo-logging/16/
> Remove --define CLI option
> --
>
> Key: MNG-7332
> URL: https://issues.apache.org/jira/browse/MNG-7332
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Remove support for the {{--define}} option.
> Rationale:
> # We can't get that to work properly with Commons CLI 1.5
> # Most likely, most of our users use {{-D}} as they think they're setting
> system properties (which happens to be a side effect of {{-D}}, not its goal)
> Not only remove code, also update website/docs for it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7332) Remove --define CLI option
[
https://issues.apache.org/jira/browse/MNG-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458046#comment-17458046
]
Hudson commented on MNG-7332:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7270 #3
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7270/3/
> Remove --define CLI option
> --
>
> Key: MNG-7332
> URL: https://issues.apache.org/jira/browse/MNG-7332
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Remove support for the {{--define}} option.
> Rationale:
> # We can't get that to work properly with Commons CLI 1.5
> # Most likely, most of our users use {{-D}} as they think they're setting
> system properties (which happens to be a side effect of {{-D}}, not its goal)
> Not only remove code, also update website/docs for it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-resolver] cstamas opened a new pull request #138: Refactor selector
cstamas opened a new pull request #138: URL: https://github.com/apache/maven-resolver/pull/138 To make it more extensible -- 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-resolver] michael-o commented on pull request #138: Refactor selector
michael-o commented on pull request #138: URL: https://github.com/apache/maven-resolver/pull/138#issuecomment-991976670 Need to take a look at this with a sober mind. -- 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-resolver] michael-o commented on pull request #138: Refactor selector
michael-o commented on pull request #138: URL: https://github.com/apache/maven-resolver/pull/138#issuecomment-991977202 Maybe this will be simpler when service locator will be gone? -- 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-resolver] cstamas commented on pull request #138: Refactor selector
cstamas commented on pull request #138: URL: https://github.com/apache/maven-resolver/pull/138#issuecomment-991977655 > Maybe this will be simpler when service locator will be gone? Def, so can't wait to drop SL -- 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] (MNG-7332) Remove --define CLI option
[
https://issues.apache.org/jira/browse/MNG-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458052#comment-17458052
]
Hudson commented on MNG-7332:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7270-maven-3.8.x #3
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7270-maven-3.8.x/3/
> Remove --define CLI option
> --
>
> Key: MNG-7332
> URL: https://issues.apache.org/jira/browse/MNG-7332
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Remove support for the {{--define}} option.
> Rationale:
> # We can't get that to work properly with Commons CLI 1.5
> # Most likely, most of our users use {{-D}} as they think they're setting
> system properties (which happens to be a side effect of {{-D}}, not its goal)
> Not only remove code, also update website/docs for it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-resolver] michael-o commented on pull request #138: Refactor selector
michael-o commented on pull request #138: URL: https://github.com/apache/maven-resolver/pull/138#issuecomment-991977883 > > Maybe this will be simpler when service locator will be gone? > > Def, so can't wait to drop SL Does this make sense while SL is still there? -- 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] (MNG-7332) Remove --define CLI option
[
https://issues.apache.org/jira/browse/MNG-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458055#comment-17458055
]
Hudson commented on MNG-7332:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6846 #32
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6846/32/
> Remove --define CLI option
> --
>
> Key: MNG-7332
> URL: https://issues.apache.org/jira/browse/MNG-7332
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Remove support for the {{--define}} option.
> Rationale:
> # We can't get that to work properly with Commons CLI 1.5
> # Most likely, most of our users use {{-D}} as they think they're setting
> system properties (which happens to be a side effect of {{-D}}, not its goal)
> Not only remove code, also update website/docs for it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7332) Remove --define CLI option
[
https://issues.apache.org/jira/browse/MNG-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458057#comment-17458057
]
Hudson commented on MNG-7332:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7166 #12
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7166/12/
> Remove --define CLI option
> --
>
> Key: MNG-7332
> URL: https://issues.apache.org/jira/browse/MNG-7332
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Remove support for the {{--define}} option.
> Rationale:
> # We can't get that to work properly with Commons CLI 1.5
> # Most likely, most of our users use {{-D}} as they think they're setting
> system properties (which happens to be a side effect of {{-D}}, not its goal)
> Not only remove code, also update website/docs for it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7332) Remove --define CLI option
[
https://issues.apache.org/jira/browse/MNG-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458058#comment-17458058
]
Hudson commented on MNG-7332:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7122 #18
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7122/18/
> Remove --define CLI option
> --
>
> Key: MNG-7332
> URL: https://issues.apache.org/jira/browse/MNG-7332
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Remove support for the {{--define}} option.
> Rationale:
> # We can't get that to work properly with Commons CLI 1.5
> # Most likely, most of our users use {{-D}} as they think they're setting
> system properties (which happens to be a side effect of {{-D}}, not its goal)
> Not only remove code, also update website/docs for it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7332) Remove --define CLI option
[
https://issues.apache.org/jira/browse/MNG-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458084#comment-17458084
]
Hudson commented on MNG-7332:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6727 #19
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6727/19/
> Remove --define CLI option
> --
>
> Key: MNG-7332
> URL: https://issues.apache.org/jira/browse/MNG-7332
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Remove support for the {{--define}} option.
> Rationale:
> # We can't get that to work properly with Commons CLI 1.5
> # Most likely, most of our users use {{-D}} as they think they're setting
> system properties (which happens to be a side effect of {{-D}}, not its goal)
> Not only remove code, also update website/docs for it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7332) Remove --define CLI option
[
https://issues.apache.org/jira/browse/MNG-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458087#comment-17458087
]
Hudson commented on MNG-7332:
-
Build unstable in Jenkins: Maven » Maven TLP » maven »
maven-3.8.x-resolver-1.7.x #5
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.8.x-resolver-1.7.x/5/
> Remove --define CLI option
> --
>
> Key: MNG-7332
> URL: https://issues.apache.org/jira/browse/MNG-7332
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Remove support for the {{--define}} option.
> Rationale:
> # We can't get that to work properly with Commons CLI 1.5
> # Most likely, most of our users use {{-D}} as they think they're setting
> system properties (which happens to be a side effect of {{-D}}, not its goal)
> Not only remove code, also update website/docs for it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7332) Remove --define CLI option
[
https://issues.apache.org/jira/browse/MNG-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458088#comment-17458088
]
Hudson commented on MNG-7332:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-5222 #35
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-5222/35/
> Remove --define CLI option
> --
>
> Key: MNG-7332
> URL: https://issues.apache.org/jira/browse/MNG-7332
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Remove support for the {{--define}} option.
> Rationale:
> # We can't get that to work properly with Commons CLI 1.5
> # Most likely, most of our users use {{-D}} as they think they're setting
> system properties (which happens to be a side effect of {{-D}}, not its goal)
> Not only remove code, also update website/docs for it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7332) Remove --define CLI option
[
https://issues.apache.org/jira/browse/MNG-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458089#comment-17458089
]
Hudson commented on MNG-7332:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7287 #3
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7287/3/
> Remove --define CLI option
> --
>
> Key: MNG-7332
> URL: https://issues.apache.org/jira/browse/MNG-7332
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Remove support for the {{--define}} option.
> Rationale:
> # We can't get that to work properly with Commons CLI 1.5
> # Most likely, most of our users use {{-D}} as they think they're setting
> system properties (which happens to be a side effect of {{-D}}, not its goal)
> Not only remove code, also update website/docs for it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MSHARED-844) Upgrade to Doxia 1.11.1
[ https://issues.apache.org/jira/browse/MSHARED-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MSHARED-844: - Summary: Upgrade to Doxia 1.11.1 (was: Upgrade to Doxia 1.9) > Upgrade to Doxia 1.11.1 > --- > > Key: MSHARED-844 > URL: https://issues.apache.org/jira/browse/MSHARED-844 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-api >Reporter: Sylwester Lachiewicz >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MSHARED-844) Upgrade to Doxia 1.11.1
[ https://issues.apache.org/jira/browse/MSHARED-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MSHARED-844: - Fix Version/s: maven-reporting-api-3.1.0 > Upgrade to Doxia 1.11.1 > --- > > Key: MSHARED-844 > URL: https://issues.apache.org/jira/browse/MSHARED-844 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-api >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: maven-reporting-api-3.1.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Reopened] (MSHARED-844) Upgrade to Doxia 1.11.1
[ https://issues.apache.org/jira/browse/MSHARED-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reopened MSHARED-844: -- Assignee: Sylwester Lachiewicz > Upgrade to Doxia 1.11.1 > --- > > Key: MSHARED-844 > URL: https://issues.apache.org/jira/browse/MSHARED-844 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-api >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MNG-7332) Remove --define CLI option
[
https://issues.apache.org/jira/browse/MNG-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458090#comment-17458090
]
Hudson commented on MNG-7332:
-
Build unstable in Jenkins: Maven » Maven TLP » maven »
maven-3.8.x_mavenProject_use_InheritableThreadLocal #7
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.8.x_mavenProject_use_InheritableThreadLocal/7/
> Remove --define CLI option
> --
>
> Key: MNG-7332
> URL: https://issues.apache.org/jira/browse/MNG-7332
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Remove support for the {{--define}} option.
> Rationale:
> # We can't get that to work properly with Commons CLI 1.5
> # Most likely, most of our users use {{-D}} as they think they're setting
> system properties (which happens to be a side effect of {{-D}}, not its goal)
> Not only remove code, also update website/docs for it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7332) Remove --define CLI option
[
https://issues.apache.org/jira/browse/MNG-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458091#comment-17458091
]
Hudson commented on MNG-7332:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-4645 #24
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-4645/24/
> Remove --define CLI option
> --
>
> Key: MNG-7332
> URL: https://issues.apache.org/jira/browse/MNG-7332
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Remove support for the {{--define}} option.
> Rationale:
> # We can't get that to work properly with Commons CLI 1.5
> # Most likely, most of our users use {{-D}} as they think they're setting
> system properties (which happens to be a side effect of {{-D}}, not its goal)
> Not only remove code, also update website/docs for it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7332) Remove --define CLI option
[
https://issues.apache.org/jira/browse/MNG-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458095#comment-17458095
]
Hudson commented on MNG-7332:
-
Build unstable in Jenkins: Maven » Maven TLP » maven »
collapse-mvnDebug-into-mvn #13
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/collapse-mvnDebug-into-mvn/13/
> Remove --define CLI option
> --
>
> Key: MNG-7332
> URL: https://issues.apache.org/jira/browse/MNG-7332
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Remove support for the {{--define}} option.
> Rationale:
> # We can't get that to work properly with Commons CLI 1.5
> # Most likely, most of our users use {{-D}} as they think they're setting
> system properties (which happens to be a side effect of {{-D}}, not its goal)
> Not only remove code, also update website/docs for it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7332) Remove --define CLI option
[
https://issues.apache.org/jira/browse/MNG-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458099#comment-17458099
]
Hudson commented on MNG-7332:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6471 #19
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6471/19/
> Remove --define CLI option
> --
>
> Key: MNG-7332
> URL: https://issues.apache.org/jira/browse/MNG-7332
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Remove support for the {{--define}} option.
> Rationale:
> # We can't get that to work properly with Commons CLI 1.5
> # Most likely, most of our users use {{-D}} as they think they're setting
> system properties (which happens to be a side effect of {{-D}}, not its goal)
> Not only remove code, also update website/docs for it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7332) Remove --define CLI option
[
https://issues.apache.org/jira/browse/MNG-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458107#comment-17458107
]
Hudson commented on MNG-7332:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7177 #12
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7177/12/
> Remove --define CLI option
> --
>
> Key: MNG-7332
> URL: https://issues.apache.org/jira/browse/MNG-7332
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Remove support for the {{--define}} option.
> Rationale:
> # We can't get that to work properly with Commons CLI 1.5
> # Most likely, most of our users use {{-D}} as they think they're setting
> system properties (which happens to be a side effect of {{-D}}, not its goal)
> Not only remove code, also update website/docs for it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MENFORCER-399) requireVariable = requireProperty or requireEnvironmentVariable
[
https://issues.apache.org/jira/browse/MENFORCER-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hüseyin Kartal updated MENFORCER-399:
-
Attachment: pom.xml
> requireVariable = requireProperty or requireEnvironmentVariable
> ---
>
> Key: MENFORCER-399
> URL: https://issues.apache.org/jira/browse/MENFORCER-399
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
> Components: Standard Rules
>Affects Versions: 3.0.0
>Reporter: Hüseyin Kartal
>Priority: Major
> Attachments: pom.xml
>
>
> As far a i know maven doesn't care where a value for ${variable} comes from.
> In a pom you can access a env.variable or a property by ${variable}.
> Also in some system the value is provided by an environment variable like
> CICD or by a property maybe a dev environment.
> I would suggest a new standard rule "requireVariable" which just look like
> maven for a value for this variable by property or environment.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7332) Remove --define CLI option
[
https://issues.apache.org/jira/browse/MNG-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458117#comment-17458117
]
Hudson commented on MNG-7332:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-4645+MNG-6772 #20
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-4645+MNG-6772/20/
> Remove --define CLI option
> --
>
> Key: MNG-7332
> URL: https://issues.apache.org/jira/browse/MNG-7332
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Remove support for the {{--define}} option.
> Rationale:
> # We can't get that to work properly with Commons CLI 1.5
> # Most likely, most of our users use {{-D}} as they think they're setting
> system properties (which happens to be a side effect of {{-D}}, not its goal)
> Not only remove code, also update website/docs for it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MENFORCER-399) requireVariable = requireProperty or requireEnvironmentVariable
[
https://issues.apache.org/jira/browse/MENFORCER-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458119#comment-17458119
]
Hüseyin Kartal commented on MENFORCER-399:
--
I created a pom for demo.
You can define an environment variable and/or pass a property to that and the
value will be used for the property "variable".
{quote}{{${VAR}}}
{quote}
But it's not possible to enforce this behaviour. That ${VAR} is set.
To test just define envioronment like:
{quote}export VAR=environment
{quote}
Or pass the property like:
{quote}{{mvn install -DVAR=property}}
{quote}
> requireVariable = requireProperty or requireEnvironmentVariable
> ---
>
> Key: MENFORCER-399
> URL: https://issues.apache.org/jira/browse/MENFORCER-399
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
> Components: Standard Rules
>Affects Versions: 3.0.0
>Reporter: Hüseyin Kartal
>Priority: Major
> Attachments: pom.xml
>
>
> As far a i know maven doesn't care where a value for ${variable} comes from.
> In a pom you can access a env.variable or a property by ${variable}.
> Also in some system the value is provided by an environment variable like
> CICD or by a property maybe a dev environment.
> I would suggest a new standard rule "requireVariable" which just look like
> maven for a value for this variable by property or environment.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-javadoc-plugin] dependabot[bot] opened a new pull request #112: Bump plexus-archiver from 4.2.5 to 4.2.6
dependabot[bot] opened a new pull request #112: URL: https://github.com/apache/maven-javadoc-plugin/pull/112 Bumps [plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver) from 4.2.5 to 4.2.6. Release notes Sourced from https://github.com/codehaus-plexus/plexus-archiver/releases";>plexus-archiver's releases. Plexus Archiver 4.2.6 This release updates commons-compress to 1.21 which contains security fixed for https://github.com/advisories/GHSA-xqfj-vm6h-2x34";>CVE-2021-35517 https://github.com/advisories/GHSA-crv7-7245-f45f";>CVE-2021-35516 https://github.com/advisories/GHSA-7hfm-57qf-j43q";>CVE-2021-35515 https://github.com/advisories/GHSA-mc84-pj99-q6hh";>CVE-2021-36090 🚀 New features and improvements FileInputStream, FileOutputStream, FileReader and FileWriter are no longer used (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/183";>#183) https://github.com/jorsol";>@jorsol Code cleanup (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/172";>#172) https://github.com/olamy";>@olamy 📦 Dependency updates Bump plexus from 7 to 8 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/179";>#179) https://github.com/dependabot";>@dependabot Bump plexus-utils from 3.3.0 to 3.4.1 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/181";>#181) https://github.com/dependabot";>@dependabot Bump commons-compress from 1.20 to 1.21 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/177";>#177) https://github.com/dependabot";>@dependabot Commits https://github.com/codehaus-plexus/plexus-archiver/commit/539719ef7c606bfd9aeec31c9fa719748532bd48";>539719e [maven-release-plugin] prepare release plexus-archiver-4.2.6 https://github.com/codehaus-plexus/plexus-archiver/commit/b045a276fa98004b0a35b35559c62a01e9f3948f";>b045a27 ci: Add JDK 17 (Final) and JDK 18-ea to build matrix https://github.com/codehaus-plexus/plexus-archiver/commit/0177bc355c1495d0c6b48d5ce59b86655ba535f7";>0177bc3 Bump plexus from 7 to 8 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/179";>#179) https://github.com/codehaus-plexus/plexus-archiver/commit/6aae5406b599c8ad9467e4d9f63dded6cc83894a";>6aae540 Bump plexus-utils from 3.3.0 to 3.4.1 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/181";>#181) https://github.com/codehaus-plexus/plexus-archiver/commit/37d604b5b34e9c79cf7d3086db3eb8f69c5aaf4b";>37d604b Avoid FileInputStream, FileOutputStream, FileReader and FileWriter (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/183";>#183) https://github.com/codehaus-plexus/plexus-archiver/commit/06e3a95d5dbc9a929732bef08a61b0974219060f";>06e3a95 Update maven.yml https://github.com/codehaus-plexus/plexus-archiver/commit/bd64c12470b0d216885130749d9e53c7064dec9c";>bd64c12 Delete .travis.yml https://github.com/codehaus-plexus/plexus-archiver/commit/cf0f9c6e12e46c84bf8616c364db9535a9226286";>cf0f9c6 Bump commons-compress from 1.20 to 1.21 https://github.com/codehaus-plexus/plexus-archiver/commit/768bf7ab4e4b4af0e9873c62c3e37dc9d04dac95";>768bf7a update search.maven.org url https://github.com/codehaus-plexus/plexus-archiver/commit/bc66255c51b9c8fc405b5d475b35e75f2557b039";>bc66255 Bump actions/checkout from 2 to 2.3.4 Additional commits viewable in https://github.com/codehaus-plexus/plexus-archiver/compare/plexus-archiver-4.2.5...plexus-archiver-4.2.6";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it ma
[GitHub] [maven-help-plugin] dependabot[bot] opened a new pull request #41: Bump jdom2 from 2.0.6 to 2.0.6.1
dependabot[bot] opened a new pull request #41: URL: https://github.com/apache/maven-help-plugin/pull/41 Bumps [jdom2](https://github.com:/hunterhacker/jdom) from 2.0.6 to 2.0.6.1. Release notes Sourced from https://github.com:/hunterhacker/jdom/releases";>jdom2's releases. JDOM 2.0.6.1 Fix for CVE-2021-33813 Commits https://github.com/hunterhacker/jdom/commit/c6065f684bdff5cebf5f23b2859c5e4c89fd89db";>c6065f6 Merge pull request https://github.com:/hunterhacker/jdom/issues/194";>#194 from schwehr/codespell https://github.com/hunterhacker/jdom/commit/b7cb36b2305a894355c092ebb698fcdd50b1d67d";>b7cb36b codespell https://github.com/hunterhacker/jdom/commit/aa6f028f8ddbfebcf69380f984c6c1461f8bf85c";>aa6f028 Merge pull request https://github.com:/hunterhacker/jdom/issues/192";>#192 from hunterhacker/tmp-cleanup https://github.com/hunterhacker/jdom/commit/25cf24eeb65e3231109915132cb34be08884fde1";>25cf24e Fixes https://github.com:/hunterhacker/jdom/issues/186";>#186 - update to Jaxen 1.2.0 https://github.com/hunterhacker/jdom/commit/03a391ad6f5a10b3f6f13e5a620412d0e60351c5";>03a391a Merge pull request https://github.com:/hunterhacker/jdom/issues/191";>#191 from hunterhacker/tmp-cleanup https://github.com/hunterhacker/jdom/commit/4f9af12b2612b6114756472b5b28d5226cb2";>4f9af12 Resolve as many StAX unit test fails as possible https://github.com/hunterhacker/jdom/commit/118853b185914527f13d606f9c650f5efac75f39";>118853b Addresses https://github.com:/hunterhacker/jdom/issues/189";>#189 again - use just the features for entity expansion tracking https://github.com/hunterhacker/jdom/commit/37c20d8359ed355d23d1ceb8c953e95d96a456d1";>37c20d8 Merge pull request https://github.com:/hunterhacker/jdom/issues/162";>#162 from seberget/master https://github.com/hunterhacker/jdom/commit/e3788905ace4c5df5ed528d732681f6f400daad0";>e378890 Merge pull request https://github.com:/hunterhacker/jdom/issues/185";>#185 from yagee-de/Automatic-Module-Name https://github.com/hunterhacker/jdom/commit/768c7e8b125ea79518a8642b10677a2e80b222d0";>768c7e8 Merge pull request https://github.com:/hunterhacker/jdom/issues/190";>#190 from hunterhacker/tmp-cleanup Additional commits viewable in https://github.com:/hunterhacker/jdom/compare/JDOM-2.0.6...JDOM-2.0.6.1";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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
