date:20240315



dependabot[bot] opened a new pull request, #366:
URL: https://github.com/apache/maven-dependency-plugin/pull/366

   Bumps 
[org.codehaus.plexus:plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver)
 from 4.9.1 to 4.9.2.
   
   Release notes
   Sourced from https://github.com/codehaus-plexus/plexus-archiver/releases;>org.codehaus.plexus:plexus-archiver's
 releases.
   
   4.9.2
   
    Dependency updates
   
   Bump org.apache.commons:commons-compress from 1.26.0 to 1.26.1 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/325;>#325)
 https://github.com/dependabot;>@dependabot
   Bump org.codehaus.plexus:plexus from 16 to 17 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/324;>#324)
 https://github.com/dependabot;>@dependabot
   Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.0 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/323;>#323)
 https://github.com/dependabot;>@dependabot
   Bump org.assertj:assertj-core from 3.25.2 to 3.25.3 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/322;>#322)
 https://github.com/dependabot;>@dependabot
   Bump org.assertj:assertj-core from 3.25.1 to 3.25.2 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/320;>#320)
 https://github.com/dependabot;>@dependabot
   Bump org.assertj:assertj-core from 3.24.2 to 3.25.1 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/319;>#319)
 https://github.com/dependabot;>@dependabot
   Bump org.codehaus.plexus:plexus-io from 3.4.1 to 3.4.2 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/317;>#317)
 https://github.com/dependabot;>@dependabot
   
    Maintenance
   
   Bump release-drafter/release-drafter from 5 to 6 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/321;>#321)
 https://github.com/dependabot;>@dependabot
   
   
   
   
   Commits
   
   https://github.com/codehaus-plexus/plexus-archiver/commit/30e3a058ff1a68ad934c105e097a137e05743111;>30e3a05
 [maven-release-plugin] prepare release plexus-archiver-4.9.2
   https://github.com/codehaus-plexus/plexus-archiver/commit/0d2bedcfd3798fee20aa81676a4f02147d530cff;>0d2bedc
 Bump org.apache.commons:commons-compress from 1.26.0 to 1.26.1
   https://github.com/codehaus-plexus/plexus-archiver/commit/caeb7d83a1806288419cf12b72174574b0fc4268;>caeb7d8
 Bump org.codehaus.plexus:plexus from 16 to 17
   https://github.com/codehaus-plexus/plexus-archiver/commit/6077fd7385965710ed8dd5918acf6c2079497e9d;>6077fd7
 Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.0
   https://github.com/codehaus-plexus/plexus-archiver/commit/728627506af607073b4986d4189b2dba46fc189e;>7286275
 Bump org.assertj:assertj-core from 3.25.2 to 3.25.3
   https://github.com/codehaus-plexus/plexus-archiver/commit/41d252e71612a6680612d557d0339c9f880f41a7;>41d252e
 Bump release-drafter/release-drafter from 5 to 6
   https://github.com/codehaus-plexus/plexus-archiver/commit/d8fb23364bf90e0c3e74f09ef67b2bccfc889a4a;>d8fb233
 Bump org.assertj:assertj-core from 3.25.1 to 3.25.2
   https://github.com/codehaus-plexus/plexus-archiver/commit/661e428a223815d8210485a7bd093c05f240c495;>661e428
 Bump org.assertj:assertj-core from 3.24.2 to 3.25.1
   https://github.com/codehaus-plexus/plexus-archiver/commit/2e891e5a71f7478f9a34e2d2825a23b297c25101;>2e891e5
 Bump org.codehaus.plexus:plexus-io from 3.4.1 to 3.4.2
   https://github.com/codehaus-plexus/plexus-archiver/commit/a61668c862ada70482d0f30770d7b5f8c1390c63;>a61668c
 [maven-release-plugin] prepare for next development iteration
   See full diff in https://github.com/codehaus-plexus/plexus-archiver/compare/plexus-archiver-4.9.1...plexus-archiver-4.9.2;>compare
 view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.codehaus.plexus:plexus-archiver=maven=4.9.1=4.9.2)](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

Re: [PR] Update README.adoc [maven-mvnd]



ppalaga commented on code in PR #925:
URL: https://github.com/apache/maven-mvnd/pull/925#discussion_r1526928896


##
README.adoc:
##
@@ -70,7 +69,7 @@ $ brew install mvndaemon/homebrew-mvnd/mvnd
 
 We're looking for contribution to support https://www.macports.org[MacPorts],
 https://community.chocolatey.org/packages/mvndaemon/[Chocolatey], 
https://scoop.sh/[Scoop] or
-https://github.com/joschi/asdf-mvnd#install[asdf].  If you're fancy helping 
us...
+https://github.com/joschi/asdf-mvnd#install[asdf].  If you fancy helping us...

Review Comment:
   Thanks for pointing to an evidence, gentlemen. I did not know "fancy" was 
also a verb. 



-- 
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] (MTOOLCHAINS-49) Automatic discovery of JDK toolchains



[ 
https://issues.apache.org/jira/browse/MTOOLCHAINS-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827606#comment-17827606
 ] 

ASF GitHub Bot commented on MTOOLCHAINS-49:
---

slawekjaranowski commented on code in PR #14:
URL: 
https://github.com/apache/maven-toolchains-plugin/pull/14#discussion_r1526841943


##
src/main/java/org/apache/maven/plugins/toolchain/jdk/ToolchainDiscoverer.java:
##
@@ -0,0 +1,468 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+package org.apache.maven.plugins.toolchain.jdk;
+
+import javax.inject.Named;
+import javax.inject.Singleton;
+
+import java.io.IOException;
+import java.io.Reader;
+import java.io.Writer;
+import java.nio.file.Files;
+import java.nio.file.Path;
+import java.nio.file.Paths;
+import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.Collections;
+import java.util.Comparator;
+import java.util.HashMap;
+import java.util.LinkedHashMap;
+import java.util.List;
+import java.util.Locale;
+import java.util.Map;
+import java.util.Objects;
+import java.util.Optional;
+import java.util.Set;
+import java.util.concurrent.ConcurrentHashMap;
+import java.util.function.Function;
+import java.util.stream.Collectors;
+import java.util.stream.Stream;
+
+import org.apache.maven.toolchain.model.PersistedToolchains;
+import org.apache.maven.toolchain.model.ToolchainModel;
+import org.apache.maven.toolchain.model.io.xpp3.MavenToolchainsXpp3Reader;
+import org.apache.maven.toolchain.model.io.xpp3.MavenToolchainsXpp3Writer;
+import org.codehaus.plexus.util.xml.Xpp3Dom;
+import org.codehaus.plexus.util.xml.pull.XmlPullParserException;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import static java.util.Comparator.comparing;
+import static 
org.apache.maven.plugins.toolchain.jdk.SelectJdkToolchainMojo.TOOLCHAIN_TYPE_JDK;
+
+/**
+ * Toolchain discoverer service
+ */
+@Named
+@Singleton
+public class ToolchainDiscoverer {
+
+public static final String JAVA = "java.";
+public static final String VERSION = "version";
+public static final String RUNTIME_NAME = "runtime.name";
+public static final String RUNTIME_VERSION = "runtime.version";
+public static final String VENDOR = "vendor";
+public static final String VENDOR_VERSION = "vendor.version";
+public static final String[] PROPERTIES = {VERSION, RUNTIME_NAME, 
RUNTIME_VERSION, VENDOR, VENDOR_VERSION};
+
+public static final String CURRENT = "current";
+public static final String ENV = "env";
+public static final String LTS = "lts";
+
+public static final List SORTED_PROVIDES = 
Collections.unmodifiableList(
+Arrays.asList(VERSION, RUNTIME_NAME, RUNTIME_VERSION, VENDOR, 
VENDOR_VERSION, CURRENT, LTS, ENV));
+
+public static final String DISCOVERED_TOOLCHAINS_CACHE_XML = 
".m2/discovered-toolchains-cache.xml";
+
+public static final String JDK_HOME = "jdkHome";
+public static final String JAVA_HOME = "java.home";
+
+private static final String COMMA = ",";
+public static final String USER_HOME = "user.home";
+
+private final Logger log = LoggerFactory.getLogger(getClass());
+
+private volatile Map cache;
+private volatile boolean cacheModified;
+private volatile Set foundJdks;
+
+/**
+ * Build the model for the current JDK toolchain
+ */
+public Optional getCurrentJdkToolchain() {
+Path currentJdkHome = 
getCanonicalPath(Paths.get(System.getProperty(JAVA_HOME)));
+if (hasJavaC(currentJdkHome)) {
+// in case the current JVM is not a JDK
+return Optional.empty();
+}
+ToolchainModel model = new ToolchainModel();
+model.setType(TOOLCHAIN_TYPE_JDK);
+Stream.of(PROPERTIES).forEach(k -> {
+String v = System.getProperty(JAVA + k);
+if (v != null) {
+model.addProvide(k.substring(JAVA.length()), v);

Review Comment:
   ```
   model.addProvide(k, v);
   ```



##
src/main/java/org/apache/maven/plugins/toolchain/jdk/ToolchainDiscoverer.java:
##
@@ -0,0 +1,468 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under

Re: [PR] [MTOOLCHAINS-49] Automatic discovery of JDK toolchains [maven-toolchains-plugin]



slawekjaranowski commented on code in PR #14:
URL: 
https://github.com/apache/maven-toolchains-plugin/pull/14#discussion_r1526841943


##
src/main/java/org/apache/maven/plugins/toolchain/jdk/ToolchainDiscoverer.java:
##
@@ -0,0 +1,468 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+package org.apache.maven.plugins.toolchain.jdk;
+
+import javax.inject.Named;
+import javax.inject.Singleton;
+
+import java.io.IOException;
+import java.io.Reader;
+import java.io.Writer;
+import java.nio.file.Files;
+import java.nio.file.Path;
+import java.nio.file.Paths;
+import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.Collections;
+import java.util.Comparator;
+import java.util.HashMap;
+import java.util.LinkedHashMap;
+import java.util.List;
+import java.util.Locale;
+import java.util.Map;
+import java.util.Objects;
+import java.util.Optional;
+import java.util.Set;
+import java.util.concurrent.ConcurrentHashMap;
+import java.util.function.Function;
+import java.util.stream.Collectors;
+import java.util.stream.Stream;
+
+import org.apache.maven.toolchain.model.PersistedToolchains;
+import org.apache.maven.toolchain.model.ToolchainModel;
+import org.apache.maven.toolchain.model.io.xpp3.MavenToolchainsXpp3Reader;
+import org.apache.maven.toolchain.model.io.xpp3.MavenToolchainsXpp3Writer;
+import org.codehaus.plexus.util.xml.Xpp3Dom;
+import org.codehaus.plexus.util.xml.pull.XmlPullParserException;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import static java.util.Comparator.comparing;
+import static 
org.apache.maven.plugins.toolchain.jdk.SelectJdkToolchainMojo.TOOLCHAIN_TYPE_JDK;
+
+/**
+ * Toolchain discoverer service
+ */
+@Named
+@Singleton
+public class ToolchainDiscoverer {
+
+public static final String JAVA = "java.";
+public static final String VERSION = "version";
+public static final String RUNTIME_NAME = "runtime.name";
+public static final String RUNTIME_VERSION = "runtime.version";
+public static final String VENDOR = "vendor";
+public static final String VENDOR_VERSION = "vendor.version";
+public static final String[] PROPERTIES = {VERSION, RUNTIME_NAME, 
RUNTIME_VERSION, VENDOR, VENDOR_VERSION};
+
+public static final String CURRENT = "current";
+public static final String ENV = "env";
+public static final String LTS = "lts";
+
+public static final List SORTED_PROVIDES = 
Collections.unmodifiableList(
+Arrays.asList(VERSION, RUNTIME_NAME, RUNTIME_VERSION, VENDOR, 
VENDOR_VERSION, CURRENT, LTS, ENV));
+
+public static final String DISCOVERED_TOOLCHAINS_CACHE_XML = 
".m2/discovered-toolchains-cache.xml";
+
+public static final String JDK_HOME = "jdkHome";
+public static final String JAVA_HOME = "java.home";
+
+private static final String COMMA = ",";
+public static final String USER_HOME = "user.home";
+
+private final Logger log = LoggerFactory.getLogger(getClass());
+
+private volatile Map cache;
+private volatile boolean cacheModified;
+private volatile Set foundJdks;
+
+/**
+ * Build the model for the current JDK toolchain
+ */
+public Optional getCurrentJdkToolchain() {
+Path currentJdkHome = 
getCanonicalPath(Paths.get(System.getProperty(JAVA_HOME)));
+if (hasJavaC(currentJdkHome)) {
+// in case the current JVM is not a JDK
+return Optional.empty();
+}
+ToolchainModel model = new ToolchainModel();
+model.setType(TOOLCHAIN_TYPE_JDK);
+Stream.of(PROPERTIES).forEach(k -> {
+String v = System.getProperty(JAVA + k);
+if (v != null) {
+model.addProvide(k.substring(JAVA.length()), v);

Review Comment:
   ```
   model.addProvide(k, v);
   ```



##
src/main/java/org/apache/maven/plugins/toolchain/jdk/ToolchainDiscoverer.java:
##
@@ -0,0 +1,468 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ *

[PR] Bump org.codehaus.plexus:plexus-archiver from 4.9.1 to 4.9.2 [maven-archiver]



dependabot[bot] opened a new pull request, #55:
URL: https://github.com/apache/maven-archiver/pull/55

   Bumps 
[org.codehaus.plexus:plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver)
 from 4.9.1 to 4.9.2.
   
   Release notes
   Sourced from https://github.com/codehaus-plexus/plexus-archiver/releases;>org.codehaus.plexus:plexus-archiver's
 releases.
   
   4.9.2
   
    Dependency updates
   
   Bump org.apache.commons:commons-compress from 1.26.0 to 1.26.1 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/325;>#325)
 https://github.com/dependabot;>@dependabot
   Bump org.codehaus.plexus:plexus from 16 to 17 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/324;>#324)
 https://github.com/dependabot;>@dependabot
   Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.0 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/323;>#323)
 https://github.com/dependabot;>@dependabot
   Bump org.assertj:assertj-core from 3.25.2 to 3.25.3 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/322;>#322)
 https://github.com/dependabot;>@dependabot
   Bump org.assertj:assertj-core from 3.25.1 to 3.25.2 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/320;>#320)
 https://github.com/dependabot;>@dependabot
   Bump org.assertj:assertj-core from 3.24.2 to 3.25.1 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/319;>#319)
 https://github.com/dependabot;>@dependabot
   Bump org.codehaus.plexus:plexus-io from 3.4.1 to 3.4.2 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/317;>#317)
 https://github.com/dependabot;>@dependabot
   
    Maintenance
   
   Bump release-drafter/release-drafter from 5 to 6 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/321;>#321)
 https://github.com/dependabot;>@dependabot
   
   
   
   
   Commits
   
   https://github.com/codehaus-plexus/plexus-archiver/commit/30e3a058ff1a68ad934c105e097a137e05743111;>30e3a05
 [maven-release-plugin] prepare release plexus-archiver-4.9.2
   https://github.com/codehaus-plexus/plexus-archiver/commit/0d2bedcfd3798fee20aa81676a4f02147d530cff;>0d2bedc
 Bump org.apache.commons:commons-compress from 1.26.0 to 1.26.1
   https://github.com/codehaus-plexus/plexus-archiver/commit/caeb7d83a1806288419cf12b72174574b0fc4268;>caeb7d8
 Bump org.codehaus.plexus:plexus from 16 to 17
   https://github.com/codehaus-plexus/plexus-archiver/commit/6077fd7385965710ed8dd5918acf6c2079497e9d;>6077fd7
 Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.0
   https://github.com/codehaus-plexus/plexus-archiver/commit/728627506af607073b4986d4189b2dba46fc189e;>7286275
 Bump org.assertj:assertj-core from 3.25.2 to 3.25.3
   https://github.com/codehaus-plexus/plexus-archiver/commit/41d252e71612a6680612d557d0339c9f880f41a7;>41d252e
 Bump release-drafter/release-drafter from 5 to 6
   https://github.com/codehaus-plexus/plexus-archiver/commit/d8fb23364bf90e0c3e74f09ef67b2bccfc889a4a;>d8fb233
 Bump org.assertj:assertj-core from 3.25.1 to 3.25.2
   https://github.com/codehaus-plexus/plexus-archiver/commit/661e428a223815d8210485a7bd093c05f240c495;>661e428
 Bump org.assertj:assertj-core from 3.24.2 to 3.25.1
   https://github.com/codehaus-plexus/plexus-archiver/commit/2e891e5a71f7478f9a34e2d2825a23b297c25101;>2e891e5
 Bump org.codehaus.plexus:plexus-io from 3.4.1 to 3.4.2
   https://github.com/codehaus-plexus/plexus-archiver/commit/a61668c862ada70482d0f30770d7b5f8c1390c63;>a61668c
 [maven-release-plugin] prepare for next development iteration
   See full diff in https://github.com/codehaus-plexus/plexus-archiver/compare/plexus-archiver-4.9.1...plexus-archiver-4.9.2;>compare
 view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.codehaus.plexus:plexus-archiver=maven=4.9.1=4.9.2)](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

[jira] [Commented] (MASSEMBLY-1021) Nullpointer in assembly:single when upgrading to 3.7.0

2024-03-15 Thread Thomas Mortagne (Jira)



[ 
https://issues.apache.org/jira/browse/MASSEMBLY-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827593#comment-17827593
 ] 

Thomas Mortagne commented on MASSEMBLY-1021:


Great, thanks for the confirmation [~sjaranowski] :)

> Nullpointer in assembly:single when upgrading to 3.7.0
> --
>
> Key: MASSEMBLY-1021
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-1021
> Project: Maven Assembly Plugin
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Thomas Mortagne
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.7.1
>
>
> I just upgraded to 3.7.0 (from 3.6.0) and end up with something very similar 
> to MASSEMBLY-659.
> The assembly file is 
> https://github.com/xwiki/xwiki-rendering/blob/master/xwiki-rendering-standalone/src/assemble/zip-with-dependencies.xml
>  and when building I get:
> {noformat}
> 21:59:56,428 [INFO] [jenkins-event-spy] Generated 
> /root/workspace/XWiki_xwiki-rendering_master@tmp/withMaven50b764e5/maven-spy-20240313-215448-41518180198517015559409.log
> 21:59:56,429 [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-assembly-plugin:3.7.0:single (default) on 
> project xwiki-rendering-standalone: Execution default of goal 
> org.apache.maven.plugins:maven-assembly-plugin:3.7.0:single failed: Cannot 
> invoke "java.io.File.isFile()" because "this.inputFile" is null -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-assembly-plugin:3.7.0:single (default) on 
> project xwiki-rendering-standalone: Execution default of goal 
> org.apache.maven.plugins:maven-assembly-plugin:3.7.0:single failed: Cannot 
> invoke "java.io.File.isFile()" because "this.inputFile" is null
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:159)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:105)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:73)
> at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
>  (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:568)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
> (Launcher.java:283)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
> (Launcher.java:226)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
> (Launcher.java:407)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main 
> (Launcher.java:348)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default of goal org.apache.maven.plugins:maven-assembly-plugin:3.7.0:single 
> failed: Cannot invoke "java.io.File.isFile()" because "this.inputFile" is null
> at com.gradle.maven.scan.extension.internal.d.a.executeMojo 
> (SourceFile:121)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:212)
> at

[jira] [Commented] (MSKINS-242) Replace deprecated prettify JS library



[ 
https://issues.apache.org/jira/browse/MSKINS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827592#comment-17827592
 ] 

Konrad Windszus commented on MSKINS-242:


hightlight.js does not come with line number capabilities 
(https://highlightjs.readthedocs.io/en/latest/line-numbers.html) but there are 
plugins for that (e.g. https://github.com/wcoder/highlightjs-line-numbers.js).

> Replace deprecated prettify JS library
> --
>
> Key: MSKINS-242
> URL: https://issues.apache.org/jira/browse/MSKINS-242
> Project: Maven Skins
>  Issue Type: Improvement
>  Components: Fluido Skin
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: fluido-2.0.0
>
>
> The JS library used for code highlighting in 
> https://github.com/apache/maven-fluido-skin/blob/master/src/main/resources/js/prettify.js
>  seems to be based on the legacy library 
> https://github.com/googlearchive/code-prettify (unclear which version). As 
> that is no longer maintained since quite a while we should switch.
> One alternative is [hightlight.js|https://highlightjs.org/](compare also with 
> https://meta.stackexchange.com/questions/353983/goodbye-prettify-hello-highlight-js-swapping-out-our-syntax-highlighter).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [PR] Update README.adoc [maven-mvnd]



nathansit commented on code in PR #925:
URL: https://github.com/apache/maven-mvnd/pull/925#discussion_r1526637439


##
README.adoc:
##
@@ -70,7 +69,7 @@ $ brew install mvndaemon/homebrew-mvnd/mvnd
 
 We're looking for contribution to support https://www.macports.org[MacPorts],
 https://community.chocolatey.org/packages/mvndaemon/[Chocolatey], 
https://scoop.sh/[Scoop] or
-https://github.com/joschi/asdf-mvnd#install[asdf].  If you're fancy helping 
us...
+https://github.com/joschi/asdf-mvnd#install[asdf].  If you fancy helping us...

Review Comment:
   I can see it being written as "If you are fancy, help us" or something along 
those lines. But I haven't heard that turn of phrase too often either.



-- 
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-8075) Allow project.baseUri in repository.url



[ 
https://issues.apache.org/jira/browse/MNG-8075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827575#comment-17827575
 ] 

ASF GitHub Bot commented on MNG-8075:
-

slawekjaranowski merged PR #1438:
URL: https://github.com/apache/maven/pull/1438




> Allow project.baseUri in repository.url
> ---
>
> Key: MNG-8075
> URL: https://issues.apache.org/jira/browse/MNG-8075
> Project: Maven
>  Issue Type: Improvement
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-14
>
>
> Such we can use properties like {{{}$\{basedir{, 
> {{{}$\{project.basedir{, so we can add also {{${project.baseUri}}}
>  
> We cen use:
> {code:java}
> 
>   repo
>   ${project.baseUri}/repo
>  {code}
> instead of:
> {code:java}
> 
>   repo
>   file://${project.basedir/repo
>  {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Closed] (MNG-8075) Allow project.baseUri in repository.url

2024-03-15 Thread Slawomir Jaranowski (Jira)



 [ 
https://issues.apache.org/jira/browse/MNG-8075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Slawomir Jaranowski closed MNG-8075.

Resolution: Fixed

> Allow project.baseUri in repository.url
> ---
>
> Key: MNG-8075
> URL: https://issues.apache.org/jira/browse/MNG-8075
> Project: Maven
>  Issue Type: Improvement
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-14
>
>
> Such we can use properties like {{{}$\{basedir{, 
> {{{}$\{project.basedir{, so we can add also {{${project.baseUri}}}
>  
> We cen use:
> {code:java}
> 
>   repo
>   ${project.baseUri}/repo
>  {code}
> instead of:
> {code:java}
> 
>   repo
>   file://${project.basedir/repo
>  {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [PR] [MNG-8075] Allow project.baseUri in repository.url [maven]



slawekjaranowski merged PR #1438:
URL: https://github.com/apache/maven/pull/1438


-- 
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

Re: [PR] Update README.adoc [maven-mvnd]



nathansit commented on code in PR #925:
URL: https://github.com/apache/maven-mvnd/pull/925#discussion_r1526637439


##
README.adoc:
##
@@ -70,7 +69,7 @@ $ brew install mvndaemon/homebrew-mvnd/mvnd
 
 We're looking for contribution to support https://www.macports.org[MacPorts],
 https://community.chocolatey.org/packages/mvndaemon/[Chocolatey], 
https://scoop.sh/[Scoop] or
-https://github.com/joschi/asdf-mvnd#install[asdf].  If you're fancy helping 
us...
+https://github.com/joschi/asdf-mvnd#install[asdf].  If you fancy helping us...

Review Comment:
   I can see it being written as "If you are fancy, help us" or something along 
those lines. But I figured that the correction was your intended turn of 
phrase. It's actually the one thing that I noticed that prompted me to open 
this pr.
   
   [Another example](https://hinative.com/questions/16176373) here the answers 
seem to change the you're to you



-- 
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

Re: [PR] Update README.adoc [maven-mvnd]



nathansit commented on code in PR #925:
URL: https://github.com/apache/maven-mvnd/pull/925#discussion_r1526637439


##
README.adoc:
##
@@ -70,7 +69,7 @@ $ brew install mvndaemon/homebrew-mvnd/mvnd
 
 We're looking for contribution to support https://www.macports.org[MacPorts],
 https://community.chocolatey.org/packages/mvndaemon/[Chocolatey], 
https://scoop.sh/[Scoop] or
-https://github.com/joschi/asdf-mvnd#install[asdf].  If you're fancy helping 
us...
+https://github.com/joschi/asdf-mvnd#install[asdf].  If you fancy helping us...

Review Comment:
   I can see it being written as "If you are fancy, help us" or something along 
those lines. But I figured that the correction was your intended turn of phrase.
   
   [Another example](https://hinative.com/questions/16176373) here the answers 
seem to change the you're to you



-- 
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

Re: [PR] Update README.adoc [maven-mvnd]



nathansit closed pull request #925: Update README.adoc
URL: https://github.com/apache/maven-mvnd/pull/925


-- 
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] (MASSEMBLY-1021) Nullpointer in assembly:single when upgrading to 3.7.0

2024-03-15 Thread Slawomir Jaranowski (Jira)



[ 
https://issues.apache.org/jira/browse/MASSEMBLY-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827566#comment-17827566
 ] 

Slawomir Jaranowski commented on MASSEMBLY-1021:


Confirm with 3.7.0 build fail - with 3.7.1 it is ok

> Nullpointer in assembly:single when upgrading to 3.7.0
> --
>
> Key: MASSEMBLY-1021
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-1021
> Project: Maven Assembly Plugin
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Thomas Mortagne
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.7.1
>
>
> I just upgraded to 3.7.0 (from 3.6.0) and end up with something very similar 
> to MASSEMBLY-659.
> The assembly file is 
> https://github.com/xwiki/xwiki-rendering/blob/master/xwiki-rendering-standalone/src/assemble/zip-with-dependencies.xml
>  and when building I get:
> {noformat}
> 21:59:56,428 [INFO] [jenkins-event-spy] Generated 
> /root/workspace/XWiki_xwiki-rendering_master@tmp/withMaven50b764e5/maven-spy-20240313-215448-41518180198517015559409.log
> 21:59:56,429 [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-assembly-plugin:3.7.0:single (default) on 
> project xwiki-rendering-standalone: Execution default of goal 
> org.apache.maven.plugins:maven-assembly-plugin:3.7.0:single failed: Cannot 
> invoke "java.io.File.isFile()" because "this.inputFile" is null -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-assembly-plugin:3.7.0:single (default) on 
> project xwiki-rendering-standalone: Execution default of goal 
> org.apache.maven.plugins:maven-assembly-plugin:3.7.0:single failed: Cannot 
> invoke "java.io.File.isFile()" because "this.inputFile" is null
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:159)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:105)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:73)
> at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
>  (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:568)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
> (Launcher.java:283)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
> (Launcher.java:226)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
> (Launcher.java:407)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main 
> (Launcher.java:348)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default of goal org.apache.maven.plugins:maven-assembly-plugin:3.7.0:single 
> failed: Cannot invoke "java.io.File.isFile()" because "this.inputFile" is null
> at com.gradle.maven.scan.extension.internal.d.a.executeMojo 
> (SourceFile:121)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:212)
> at

[jira] [Created] (MSHARED-1364) AbstractMavenReportRenderer should not depend on Doxia impl classes

Konrad Windszus created MSHARED-1364:


 Summary: AbstractMavenReportRenderer should not depend on Doxia 
impl classes
 Key: MSHARED-1364
 URL: https://issues.apache.org/jira/browse/MSHARED-1364
 Project: Maven Shared Components
  Issue Type: Improvement
  Components: maven-reporting-impl
Affects Versions: maven-reporting-impl-4.0.0-M13
Reporter: Konrad Windszus


The classes in package {{o.a.m.doxia.sink.impl}} should by definition not be 
considered stable API (and therefore only consumed from Doxia classes 
internally).
However 
{{https://github.com/apache/maven-reporting-impl/blob/72181306bb0e12eed50c4ba4aec98dd76499df39/src/main/java/org/apache/maven/reporting/AbstractMavenReportRenderer.java#L47}}
 depends on some internal constants.
This is dangerous, as those constants were removed in the context of DOXIA-685. 
Although constants are inlined during compile time, the evaluation of those 
constants vanished as well, so using them has no longer any effect. Reporting 
Impl should only rely on stable Doxia API to achieve a better decoupling.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MRESOLVER-512) Scope Manager



[ 
https://issues.apache.org/jira/browse/MRESOLVER-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827555#comment-17827555
 ] 

ASF GitHub Bot commented on MRESOLVER-512:
--

cstamas commented on PR #445:
URL: https://github.com/apache/maven-resolver/pull/445#issuecomment-246152

   Well, IMO this PR goes exactly in direction of MRESOLVER-471, as:
   * scope manager is optional, in a sense, if you want to use Resolver 2.x as 
you did Resolver 1.x, go for it
   * ScopeManager solves the problem of "Resolver should be oblivious about 
scopes" (MRESOLVER-471), as Resolver 1.x implemented scope related logic 
scattered across several (dozen?) classes, and actions like "introducing new 
scope" or "removal of a scope" was impossible exactly due that (as Resolver was 
not oblivious, but had them cemented as String constants spread across dozen 
classes). Hence Resolver was "this xor that". 
   
   With ScopeManager Resolver IS really oblivious, as they are defined by 
client project, the app that is integrating Resolver 2.




> Scope Manager
> -
>
> Key: MRESOLVER-512
> URL: https://issues.apache.org/jira/browse/MRESOLVER-512
> Project: Maven Resolver
>  Issue Type: New Feature
>  Components: Resolver
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-9
>
>
> In Resolver 1.x times, resolver was unaware of "resolution scope", to get the 
> wanted resolution scope caller had to tweak and set up various nits and bits, 
> like selectors, filters, and so on. It was easy to miss. Similarly, resolver 
> had no "first class" type for "dependency scope" either, they were just 
> string labels (that everyone knew HOW should behave, but was never codified) 
> and its meaning and notion was sprinkled across several classes. Introducing 
> new scope in these conditions (or alter selector to something that would have 
> new scopes, like Maven4 plans) was nearly impossible.
> The ScopeManager aims to solve these issues: it defines "resolution scope" 
> and "dependency scope", interprets them, and allows caller to simply make a 
> call to "resolve me main-runtime" resolution scope. No hoops and loops. 
> Moreover, it is FASTER than Resolver 1.x was, that used always same selector 
> (to build dirty graph), so potentially huge graph even if you needed just a 
> bit of it, that was later chopped down to clean up the graph. ScopeManager 
> automates selector selection/setup, and goes directly for result, in most 
> cases the resulting tree is done in first pass.
> Finally, and most importantly, ScopeManager allows to be "configured": by 
> supplying the recipe for dependency and resolution scopes, hence, makes 
> Resolver 2.x versatile, in a sense, it is not "this or that" anymore, it can 
> obey Maven3 and Maven4 dependency scopes at the same time.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [PR] [MRESOLVER-512] ScopeManager [maven-resolver]



cstamas commented on PR #445:
URL: https://github.com/apache/maven-resolver/pull/445#issuecomment-246152

   Well, IMO this PR goes exactly in direction of MRESOLVER-471, as:
   * scope manager is optional, in a sense, if you want to use Resolver 2.x as 
you did Resolver 1.x, go for it
   * ScopeManager solves the problem of "Resolver should be oblivious about 
scopes" (MRESOLVER-471), as Resolver 1.x implemented scope related logic 
scattered across several (dozen?) classes, and actions like "introducing new 
scope" or "removal of a scope" was impossible exactly due that (as Resolver was 
not oblivious, but had them cemented as String constants spread across dozen 
classes). Hence Resolver was "this xor that". 
   
   With ScopeManager Resolver IS really oblivious, as they are defined by 
client project, the app that is integrating Resolver 2.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Comment Edited] (MSKINS-244) Get rid of CSS classes "table" and "verbatim"



[ 
https://issues.apache.org/jira/browse/MSKINS-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827546#comment-17827546
 ] 

Konrad Windszus edited comment on MSKINS-244 at 3/15/24 4:13 PM:
-

The class {{verbatim}} is now tackled in MSKINS-245.


was (Author: kwin):
The class `verbatim` is now tackled in MSKINS-245.

> Get rid of CSS classes "table" and "verbatim"
> -
>
> Key: MSKINS-244
> URL: https://issues.apache.org/jira/browse/MSKINS-244
> Project: Maven Skins
>  Issue Type: Improvement
>  Components: Fluido Skin
>Reporter: Konrad Windszus
>Priority: Major
>
> Both classes {{table}} and {{verbatim}} feel redundant to me, as for both we 
> do have a semantic element (with the same meaning) which is {{}} and 
> {{}}.
> Therefore the CSS referring to those should be removed: 
> https://github.com/apache/maven-fluido-skin/blob/d5eef2752bdb2e3d395438a502ab87ecbebd9e8c/src/main/resources/css/maven-base.css#L32-L33



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (MSKINS-244) Get rid of CSS classes "table" and "verbatim"



 [ 
https://issues.apache.org/jira/browse/MSKINS-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus reassigned MSKINS-244:
--

Assignee: Konrad Windszus

> Get rid of CSS classes "table" and "verbatim"
> -
>
> Key: MSKINS-244
> URL: https://issues.apache.org/jira/browse/MSKINS-244
> Project: Maven Skins
>  Issue Type: Improvement
>  Components: Fluido Skin
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>
> Both classes {{table}} and {{verbatim}} feel redundant to me, as for both we 
> do have a semantic element (with the same meaning) which is {{}} and 
> {{}}.
> Therefore the CSS referring to those should be removed: 
> https://github.com/apache/maven-fluido-skin/blob/d5eef2752bdb2e3d395438a502ab87ecbebd9e8c/src/main/resources/css/maven-base.css#L32-L33



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MSKINS-244) Get rid of CSS classes "table" and "verbatim"



[ 
https://issues.apache.org/jira/browse/MSKINS-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827546#comment-17827546
 ] 

Konrad Windszus commented on MSKINS-244:


The class `verbatim` is now tackled in MSKINS-245.

> Get rid of CSS classes "table" and "verbatim"
> -
>
> Key: MSKINS-244
> URL: https://issues.apache.org/jira/browse/MSKINS-244
> Project: Maven Skins
>  Issue Type: Improvement
>  Components: Fluido Skin
>Reporter: Konrad Windszus
>Priority: Major
>
> Both classes {{table}} and {{verbatim}} feel redundant to me, as for both we 
> do have a semantic element (with the same meaning) which is {{}} and 
> {{}}.
> Therefore the CSS referring to those should be removed: 
> https://github.com/apache/maven-fluido-skin/blob/d5eef2752bdb2e3d395438a502ab87ecbebd9e8c/src/main/resources/css/maven-base.css#L32-L33



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MSKINS-245) Maven Site 4 will break code highlight of site generated by Markdown



[ 
https://issues.apache.org/jira/browse/MSKINS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827545#comment-17827545
 ] 

ASF GitHub Bot commented on MSKINS-245:
---

kwin commented on PR #58:
URL: https://github.com/apache/maven-fluido-skin/pull/58#issuecomment-191720

   This also fixes the missing indentation for `` (broken 
in both Fluido 1.x and 2.x), which e.g. can be seen in 

   
   ![Screenshot 2024-03-15 at 17 08 
35](https://github.com/apache/maven-fluido-skin/assets/185025/f33b93f7-a3f0-404c-a90e-54c2d919ffae)
   
   




> Maven Site 4 will break code highlight of site generated by Markdown
> 
>
> Key: MSKINS-245
> URL: https://issues.apache.org/jira/browse/MSKINS-245
> Project: Maven Skins
>  Issue Type: Bug
>Reporter: Xavi Lee
>Assignee: Konrad Windszus
>Priority: Major
> Attachments: maven-site-3.png, maven-site-4.png, test-v3.html, 
> test-v4.html
>
>
> repro repo https://github.com/awxiaoxian2020/code-render-bug
> master branch is Maven Site 3 with Fluido skin 1
> v4 branch is Maven Site 4 with Fluido skin 2.
> Open their respective `target/site/test.html` files in local to see the 
> rendered result.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [PR] [MSKINS-245] Add code highlighting class to every combination [maven-fluido-skin]



kwin commented on PR #58:
URL: https://github.com/apache/maven-fluido-skin/pull/58#issuecomment-191720

   This also fixes the missing indentation for `` (broken 
in both Fluido 1.x and 2.x), which e.g. can be seen in 

   
   ![Screenshot 2024-03-15 at 17 08 
35](https://github.com/apache/maven-fluido-skin/assets/185025/f33b93f7-a3f0-404c-a90e-54c2d919ffae)
   
   


-- 
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] (DOXIA-731) Simplify HTML emitted from Sink.verbatim(...)



[ 
https://issues.apache.org/jira/browse/DOXIA-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827544#comment-17827544
 ] 

ASF GitHub Bot commented on DOXIA-731:
--

kwin commented on code in PR #202:
URL: https://github.com/apache/maven-doxia/pull/202#discussion_r1526512211


##
doxia-modules/doxia-module-markdown/src/test/java/org/apache/maven/doxia/module/markdown/MarkdownParserTest.java:
##
@@ -798,4 +800,24 @@ public void testQuoteVsApostrophe() throws Exception {
 "This apostrophe isn't a quote." + "This \u2018quoted 
text\u2019 isn't surrounded by apostrophes.",
 content.toString());
 }
+
+@Override
+protected void assertEventPrefix(Iterator eventIterator) 
{
+assertSinkStartsWith(eventIterator, "head", "head_", "body");
+}
+
+@Override
+protected void assertEventSuffix(Iterator eventIterator) 
{
+assertSinkEquals(eventIterator, "body_");
+}
+
+@Override
+protected String getVerbatimSource() {
+return null; // not supported in MD

Review Comment:
   Not sure fenced code blocks are related. There is also 
https://spec.commonmark.org/0.31.2/#indented-code-block and both really refer 
to code only as there is no verbatim without code semantics.





> Simplify HTML emitted from Sink.verbatim(...)
> -
>
> Key: DOXIA-731
> URL: https://issues.apache.org/jira/browse/DOXIA-731
> Project: Maven Doxia
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 2.0.0-M9
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>
> The XHTML markup generated from Sink.verbatim(...) should be streamlined to 
> either emit {{}} or {{}} depending on the given attribute.
> There is no need to generate an additional div nor any additional classes.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [PR] [DOXIA-731] Simplify HTML markup emitted from Sink.verbatim [maven-doxia]



kwin commented on code in PR #202:
URL: https://github.com/apache/maven-doxia/pull/202#discussion_r1526512211


##
doxia-modules/doxia-module-markdown/src/test/java/org/apache/maven/doxia/module/markdown/MarkdownParserTest.java:
##
@@ -798,4 +800,24 @@ public void testQuoteVsApostrophe() throws Exception {
 "This apostrophe isn't a quote." + "This \u2018quoted 
text\u2019 isn't surrounded by apostrophes.",
 content.toString());
 }
+
+@Override
+protected void assertEventPrefix(Iterator eventIterator) 
{
+assertSinkStartsWith(eventIterator, "head", "head_", "body");
+}
+
+@Override
+protected void assertEventSuffix(Iterator eventIterator) 
{
+assertSinkEquals(eventIterator, "body_");
+}
+
+@Override
+protected String getVerbatimSource() {
+return null; // not supported in MD

Review Comment:
   Not sure fenced code blocks are related. There is also 
https://spec.commonmark.org/0.31.2/#indented-code-block and both really refer 
to code only as there is no verbatim without code semantics.



-- 
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] (DOXIA-731) Simplify HTML emitted from Sink.verbatim(...)



[ 
https://issues.apache.org/jira/browse/DOXIA-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827542#comment-17827542
 ] 

ASF GitHub Bot commented on DOXIA-731:
--

kwin commented on PR #202:
URL: https://github.com/apache/maven-doxia/pull/202#issuecomment-180404

   > Can you test it down the line to Sitetools and Maven Site Plugin?
   
   It works fine now together with 
https://github.com/apache/maven-fluido-skin/pull/58.




> Simplify HTML emitted from Sink.verbatim(...)
> -
>
> Key: DOXIA-731
> URL: https://issues.apache.org/jira/browse/DOXIA-731
> Project: Maven Doxia
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 2.0.0-M9
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>
> The XHTML markup generated from Sink.verbatim(...) should be streamlined to 
> either emit {{}} or {{}} depending on the given attribute.
> There is no need to generate an additional div nor any additional classes.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [PR] [DOXIA-731] Simplify HTML markup emitted from Sink.verbatim [maven-doxia]



kwin commented on PR #202:
URL: https://github.com/apache/maven-doxia/pull/202#issuecomment-180404

   > Can you test it down the line to Sitetools and Maven Site Plugin?
   
   It works fine now together with 
https://github.com/apache/maven-fluido-skin/pull/58.


-- 
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] [Moved] (MSKINS-245) Maven Site 4 will break code highlight of site generated by Markdown



 [ 
https://issues.apache.org/jira/browse/MSKINS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus moved MSITE-1002 to MSKINS-245:
---

  Component/s: (was: doxia integration)
  Key: MSKINS-245  (was: MSITE-1002)
Affects Version/s: (was: 4.0.0-M13)
  Project: Maven Skins  (was: Maven Site Plugin)

> Maven Site 4 will break code highlight of site generated by Markdown
> 
>
> Key: MSKINS-245
> URL: https://issues.apache.org/jira/browse/MSKINS-245
> Project: Maven Skins
>  Issue Type: Bug
>Reporter: Xavi Lee
>Assignee: Konrad Windszus
>Priority: Major
> Attachments: maven-site-3.png, maven-site-4.png, test-v3.html, 
> test-v4.html
>
>
> repro repo https://github.com/awxiaoxian2020/code-render-bug
> master branch is Maven Site 3 with Fluido skin 1
> v4 branch is Maven Site 4 with Fluido skin 2.
> Open their respective `target/site/test.html` files in local to see the 
> rendered result.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MRESOLVER-512) Scope Manager



[ 
https://issues.apache.org/jira/browse/MRESOLVER-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827539#comment-17827539
 ] 

ASF GitHub Bot commented on MRESOLVER-512:
--

cstamas opened a new pull request, #1442:
URL: https://github.com/apache/maven/pull/1442

   This makes all the new scopes implemented out of the box
   
   Related PR https://github.com/apache/maven-resolver/pull/445
   
   ---
   
   https://issues.apache.org/jira/browse/MRESOLVER-512




> Scope Manager
> -
>
> Key: MRESOLVER-512
> URL: https://issues.apache.org/jira/browse/MRESOLVER-512
> Project: Maven Resolver
>  Issue Type: New Feature
>  Components: Resolver
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-9
>
>
> In Resolver 1.x times, resolver was unaware of "resolution scope", to get the 
> wanted resolution scope caller had to tweak and set up various nits and bits, 
> like selectors, filters, and so on. It was easy to miss. Similarly, resolver 
> had no "first class" type for "dependency scope" either, they were just 
> string labels (that everyone knew HOW should behave, but was never codified) 
> and its meaning and notion was sprinkled across several classes. Introducing 
> new scope in these conditions (or alter selector to something that would have 
> new scopes, like Maven4 plans) was nearly impossible.
> The ScopeManager aims to solve these issues: it defines "resolution scope" 
> and "dependency scope", interprets them, and allows caller to simply make a 
> call to "resolve me main-runtime" resolution scope. No hoops and loops. 
> Moreover, it is FASTER than Resolver 1.x was, that used always same selector 
> (to build dirty graph), so potentially huge graph even if you needed just a 
> bit of it, that was later chopped down to clean up the graph. ScopeManager 
> automates selector selection/setup, and goes directly for result, in most 
> cases the resulting tree is done in first pass.
> Finally, and most importantly, ScopeManager allows to be "configured": by 
> supplying the recipe for dependency and resolution scopes, hence, makes 
> Resolver 2.x versatile, in a sense, it is not "this or that" anymore, it can 
> obey Maven3 and Maven4 dependency scopes at the same time.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[PR] [EXPERIMENT] Using Resolver with MRESOLVER-512 [maven]



cstamas opened a new pull request, #1442:
URL: https://github.com/apache/maven/pull/1442

   This makes all the new scopes implemented out of the box
   
   Related PR https://github.com/apache/maven-resolver/pull/445
   
   ---
   
   https://issues.apache.org/jira/browse/MRESOLVER-512


-- 
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

[PR] Bump org.apache.activemq:apache-activemq from 5.16.0 to 5.16.6 in /integration-tests/src/test/projects/concurrent-downloads/mod1 [maven-mvnd]



dependabot[bot] opened a new pull request, #926:
URL: https://github.com/apache/maven-mvnd/pull/926

   Bumps org.apache.activemq:apache-activemq from 5.16.0 to 5.16.6.
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.apache.activemq:apache-activemq=maven=5.16.0=5.16.6)](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 show  ignore conditions` will show all of 
the ignore conditions of the specified dependency
   - `@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)
   You can disable automated security fix PRs for this repo from the [Security 
Alerts page](https://github.com/apache/maven-mvnd/network/alerts).
   
   


-- 
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

Re: [PR] Update to mvn 3.9.6 [maven-mvnd]



ppalaga commented on PR #924:
URL: https://github.com/apache/maven-mvnd/pull/924#issuecomment-1999873605

   Thanks @nathansit!


-- 
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

Re: [I] Update: Maven 3.9.6 + Resolver 1.9.18 [maven-mvnd]



ppalaga closed issue #922: Update: Maven 3.9.6 + Resolver 1.9.18
URL: https://github.com/apache/maven-mvnd/issues/922


-- 
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

Re: [PR] Update to mvn 3.9.6 [maven-mvnd]



ppalaga merged PR #924:
URL: https://github.com/apache/maven-mvnd/pull/924


-- 
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

Re: [PR] Update README.adoc [maven-mvnd]



Stephan202 commented on code in PR #925:
URL: https://github.com/apache/maven-mvnd/pull/925#discussion_r1526422691


##
README.adoc:
##
@@ -70,7 +69,7 @@ $ brew install mvndaemon/homebrew-mvnd/mvnd
 
 We're looking for contribution to support https://www.macports.org[MacPorts],
 https://community.chocolatey.org/packages/mvndaemon/[Chocolatey], 
https://scoop.sh/[Scoop] or
-https://github.com/joschi/asdf-mvnd#install[asdf].  If you're fancy helping 
us...
+https://github.com/joschi/asdf-mvnd#install[asdf].  If you fancy helping us...

Review Comment:
   I'm not a native speaker, but IIUC the original is incorrect, and the 
suggestion _is_ correct. See also examples e.g. 
[here](https://dictionary.cambridge.org/dictionary/english/fancy).



-- 
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

[PR] Bump org.codehaus.plexus:plexus-archiver from 4.9.1 to 4.9.2 [maven-plugin-tools]



dependabot[bot] opened a new pull request, #270:
URL: https://github.com/apache/maven-plugin-tools/pull/270

   Bumps 
[org.codehaus.plexus:plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver)
 from 4.9.1 to 4.9.2.
   
   Release notes
   Sourced from https://github.com/codehaus-plexus/plexus-archiver/releases;>org.codehaus.plexus:plexus-archiver's
 releases.
   
   4.9.2
   
    Dependency updates
   
   Bump org.apache.commons:commons-compress from 1.26.0 to 1.26.1 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/325;>#325)
 https://github.com/dependabot;>@dependabot
   Bump org.codehaus.plexus:plexus from 16 to 17 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/324;>#324)
 https://github.com/dependabot;>@dependabot
   Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.0 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/323;>#323)
 https://github.com/dependabot;>@dependabot
   Bump org.assertj:assertj-core from 3.25.2 to 3.25.3 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/322;>#322)
 https://github.com/dependabot;>@dependabot
   Bump org.assertj:assertj-core from 3.25.1 to 3.25.2 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/320;>#320)
 https://github.com/dependabot;>@dependabot
   Bump org.assertj:assertj-core from 3.24.2 to 3.25.1 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/319;>#319)
 https://github.com/dependabot;>@dependabot
   Bump org.codehaus.plexus:plexus-io from 3.4.1 to 3.4.2 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/317;>#317)
 https://github.com/dependabot;>@dependabot
   
    Maintenance
   
   Bump release-drafter/release-drafter from 5 to 6 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/321;>#321)
 https://github.com/dependabot;>@dependabot
   
   
   
   
   Commits
   
   https://github.com/codehaus-plexus/plexus-archiver/commit/30e3a058ff1a68ad934c105e097a137e05743111;>30e3a05
 [maven-release-plugin] prepare release plexus-archiver-4.9.2
   https://github.com/codehaus-plexus/plexus-archiver/commit/0d2bedcfd3798fee20aa81676a4f02147d530cff;>0d2bedc
 Bump org.apache.commons:commons-compress from 1.26.0 to 1.26.1
   https://github.com/codehaus-plexus/plexus-archiver/commit/caeb7d83a1806288419cf12b72174574b0fc4268;>caeb7d8
 Bump org.codehaus.plexus:plexus from 16 to 17
   https://github.com/codehaus-plexus/plexus-archiver/commit/6077fd7385965710ed8dd5918acf6c2079497e9d;>6077fd7
 Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.0
   https://github.com/codehaus-plexus/plexus-archiver/commit/728627506af607073b4986d4189b2dba46fc189e;>7286275
 Bump org.assertj:assertj-core from 3.25.2 to 3.25.3
   https://github.com/codehaus-plexus/plexus-archiver/commit/41d252e71612a6680612d557d0339c9f880f41a7;>41d252e
 Bump release-drafter/release-drafter from 5 to 6
   https://github.com/codehaus-plexus/plexus-archiver/commit/d8fb23364bf90e0c3e74f09ef67b2bccfc889a4a;>d8fb233
 Bump org.assertj:assertj-core from 3.25.1 to 3.25.2
   https://github.com/codehaus-plexus/plexus-archiver/commit/661e428a223815d8210485a7bd093c05f240c495;>661e428
 Bump org.assertj:assertj-core from 3.24.2 to 3.25.1
   https://github.com/codehaus-plexus/plexus-archiver/commit/2e891e5a71f7478f9a34e2d2825a23b297c25101;>2e891e5
 Bump org.codehaus.plexus:plexus-io from 3.4.1 to 3.4.2
   https://github.com/codehaus-plexus/plexus-archiver/commit/a61668c862ada70482d0f30770d7b5f8c1390c63;>a61668c
 [maven-release-plugin] prepare for next development iteration
   See full diff in https://github.com/codehaus-plexus/plexus-archiver/compare/plexus-archiver-4.9.1...plexus-archiver-4.9.2;>compare
 view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.codehaus.plexus:plexus-archiver=maven=4.9.1=4.9.2)](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

[jira] [Created] (SUREFIRE-2242) Plain test report does not include names of the skipped tests

2024-03-15 Thread Alexandru Popescu (Jira)

Alexandru Popescu created SUREFIRE-2242:
---

 Summary: Plain test report does not include names of the skipped 
tests
 Key: SUREFIRE-2242
 URL: https://issues.apache.org/jira/browse/SUREFIRE-2242
 Project: Maven Surefire
  Issue Type: Improvement
Affects Versions: 3.2.5
Reporter: Alexandru Popescu


When using the plain reportFormat, skipped tests using JUnit 
Assumptions/Conditions API are not including the method name in the report, 
just the class name.

 

Example output (note the last 2 lines, indicating two skipped test)

 

{{Tests run: 3, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 0.031 s -- in 
org.example.AssumptionsDemo}}
{{org.example.AssumptionsDemo.testWithAssumption -- Time elapsed: 0.015 s}}
{{org.example.AssumptionsDemo skipped}}
{{org.example.AssumptionsDemo skipped}}

 

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MRESOLVER-512) Scope Manager



[ 
https://issues.apache.org/jira/browse/MRESOLVER-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827498#comment-17827498
 ] 

ASF GitHub Bot commented on MRESOLVER-512:
--

gnodet commented on PR #445:
URL: https://github.com/apache/maven-resolver/pull/445#issuecomment-1999632591

   I'm *really* reluctant about this PR.  This goes in the exact opposite 
direction than https://issues.apache.org/jira/browse/MRESOLVER-471, which aimed 
to make the resolver agnostic about scopes and leave these bits to be defined 
by Maven.
   
   It basically replaces 250 lines of deprecated code (the 
`JavaDependencyContextRefiner`, `JavaScopeDeriver` and `JavaScopeSelector` 
which were deprecated a few weeks ago) with 3800 new lines of code, adds a 
strong tie between the resolver and maven, whereas the code could be easily 
moved into maven which already exposes those concepts.
   




> Scope Manager
> -
>
> Key: MRESOLVER-512
> URL: https://issues.apache.org/jira/browse/MRESOLVER-512
> Project: Maven Resolver
>  Issue Type: New Feature
>  Components: Resolver
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-9
>
>
> In Resolver 1.x times, resolver was unaware of "resolution scope", to get the 
> wanted resolution scope caller had to tweak and set up various nits and bits, 
> like selectors, filters, and so on. It was easy to miss. Similarly, resolver 
> had no "first class" type for "dependency scope" either, they were just 
> string labels (that everyone knew HOW should behave, but was never codified) 
> and its meaning and notion was sprinkled across several classes. Introducing 
> new scope in these conditions (or alter selector to something that would have 
> new scopes, like Maven4 plans) was nearly impossible.
> The ScopeManager aims to solve these issues: it defines "resolution scope" 
> and "dependency scope", interprets them, and allows caller to simply make a 
> call to "resolve me main-runtime" resolution scope. No hoops and loops. 
> Moreover, it is FASTER than Resolver 1.x was, that used always same selector 
> (to build dirty graph), so potentially huge graph even if you needed just a 
> bit of it, that was later chopped down to clean up the graph. ScopeManager 
> automates selector selection/setup, and goes directly for result, in most 
> cases the resulting tree is done in first pass.
> Finally, and most importantly, ScopeManager allows to be "configured": by 
> supplying the recipe for dependency and resolution scopes, hence, makes 
> Resolver 2.x versatile, in a sense, it is not "this or that" anymore, it can 
> obey Maven3 and Maven4 dependency scopes at the same time.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [PR] [MRESOLVER-512] ScopeManager [maven-resolver]



gnodet commented on PR #445:
URL: https://github.com/apache/maven-resolver/pull/445#issuecomment-1999632591

   I'm *really* reluctant about this PR.  This goes in the exact opposite 
direction than https://issues.apache.org/jira/browse/MRESOLVER-471, which aimed 
to make the resolver agnostic about scopes and leave these bits to be defined 
by Maven.
   
   It basically replaces 250 lines of deprecated code (the 
`JavaDependencyContextRefiner`, `JavaScopeDeriver` and `JavaScopeSelector` 
which were deprecated a few weeks ago) with 3800 new lines of code, adds a 
strong tie between the resolver and maven, whereas the code could be easily 
moved into maven which already exposes those concepts.
   


-- 
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

Re: [PR] Update README.adoc [maven-mvnd]



ppalaga commented on code in PR #925:
URL: https://github.com/apache/maven-mvnd/pull/925#discussion_r1526253989


##
README.adoc:
##
@@ -70,7 +69,7 @@ $ brew install mvndaemon/homebrew-mvnd/mvnd
 
 We're looking for contribution to support https://www.macports.org[MacPorts],
 https://community.chocolatey.org/packages/mvndaemon/[Chocolatey], 
https://scoop.sh/[Scoop] or
-https://github.com/joschi/asdf-mvnd#install[asdf].  If you're fancy helping 
us...
+https://github.com/joschi/asdf-mvnd#install[asdf].  If you fancy helping us...

Review Comment:
   -1 on this change. The original was correct IMO.



##
README.adoc:
##
@@ -24,8 +24,7 @@ This architecture brings the following advantages:
 * The JVM for running the actual builds does not need to get started anew for 
each build.
 * The classloaders holding classes of Maven plugins are cached over multiple 
builds. The plugin jars are thus read
   and parsed just once. SNAPSHOT versions of Maven plugins are not cached.
-* The native code produced by the Just-In-Time (JIT) compiler inside the JVM 
is kept too. Compared to stock Maven,
-  less time is spent by the JIT compilation. During the repeated builds the 
JIT-optimized code is available
+* The native code produced by the Just-In-Time (JIT) compiler inside the JVM 
is kept too. JIT compilation is faster than stock Maven. During the repeated 
builds the JIT-optimized code is available

Review Comment:
   > JIT compilation is faster than stock Maven.
   
   This changes the meaning in a wrong way. The changed sentence does not state 
anything useful. 



-- 
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

Re: [PR] Update: Maven 3.9.6 + Resolver 1.9.18 resolves #922 [maven-mvnd]



ppalaga commented on PR #923:
URL: https://github.com/apache/maven-mvnd/pull/923#issuecomment-1999603344

   Duplicate of https://github.com/apache/maven-mvnd/issues/922


-- 
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] (MRESOLVER-512) Scope Manager



 [ 
https://issues.apache.org/jira/browse/MRESOLVER-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamas Cservenak updated MRESOLVER-512:
--
Description: 
In Resolver 1.x times, resolver was unaware of "resolution scope", to get the 
wanted resolution scope caller had to tweak and set up various nits and bits, 
like selectors, filters, and so on. It was easy to miss. Similarly, resolver 
had no "first class" type for "dependency scope" either, they were just string 
labels (that everyone knew HOW should behave, but was never codified) and its 
meaning and notion was sprinkled across several classes. Introducing new scope 
in these conditions (or alter selector to something that would have new scopes, 
like Maven4 plans) was nearly impossible.

The ScopeManager aims to solve these issues: it defines "resolution scope" and 
"dependency scope", interprets them, and allows caller to simply make a call to 
"resolve me main-runtime" resolution scope. No hoops and loops. Moreover, it is 
FASTER than Resolver 1.x was, that used always same selector (to build dirty 
graph), so potentially huge graph even if you needed just a bit of it, that was 
later chopped down to clean up the graph. ScopeManager automates selector 
selection/setup, and goes directly for result, in most cases the resulting tree 
is done in first pass.

Finally, and most importantly, ScopeManager allows to be "configured": by 
supplying the recipe for dependency and resolution scopes, hence, makes 
Resolver 2.x versatile, in a sense, it is not "this or that" anymore, it can 
obey Maven3 and Maven4 dependency scopes at the same time.

  was:
In Resolver 1.x times, resolver was unaware of "resolution scope", to get the 
wanted resolution scope caller had to tweak and set up various nits and bits, 
like selectors, filters, and so on. It was easy to miss. Similarly, resolver 
had no "first class" type for "dependency scope" either, and its meaning and 
notion was sprinkled across several classes. Introducing new scope in these 
conditions (or alter selector to something that would have new scopes, like 
Maven4 plans) was nearly impossible.

The ScopeManager aims to solve these issues: it defines "resolution scope" and 
"dependency scope", interprets them, and allows caller to simply make a call to 
"resolve me main-runtime" resolution scope. No hoops and loops. Moreover, it is 
FASTER than Resolver 1.x was, that used always same selector (to build dirty 
graph), so potentially huge graph even if you needed just a bit of it, that was 
later chopped down to clean up the graph. ScopeManager automates selector 
selection/setup, and goes directly for result, in most cases the resulting tree 
is done in first pass.

Finally, and most importantly, ScopeManager allows to be "configured": by 
supplying the recipe for dependency and resolution scopes, hence, makes 
Resolver 2.x versatile, in a sense, it is not "this or that" anymore, it can 
obey Maven3 and Maven4 dependency scopes at the same time.


> Scope Manager
> -
>
> Key: MRESOLVER-512
> URL: https://issues.apache.org/jira/browse/MRESOLVER-512
> Project: Maven Resolver
>  Issue Type: New Feature
>  Components: Resolver
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-9
>
>
> In Resolver 1.x times, resolver was unaware of "resolution scope", to get the 
> wanted resolution scope caller had to tweak and set up various nits and bits, 
> like selectors, filters, and so on. It was easy to miss. Similarly, resolver 
> had no "first class" type for "dependency scope" either, they were just 
> string labels (that everyone knew HOW should behave, but was never codified) 
> and its meaning and notion was sprinkled across several classes. Introducing 
> new scope in these conditions (or alter selector to something that would have 
> new scopes, like Maven4 plans) was nearly impossible.
> The ScopeManager aims to solve these issues: it defines "resolution scope" 
> and "dependency scope", interprets them, and allows caller to simply make a 
> call to "resolve me main-runtime" resolution scope. No hoops and loops. 
> Moreover, it is FASTER than Resolver 1.x was, that used always same selector 
> (to build dirty graph), so potentially huge graph even if you needed just a 
> bit of it, that was later chopped down to clean up the graph. ScopeManager 
> automates selector selection/setup, and goes directly for result, in most 
> cases the resulting tree is done in first pass.
> Finally, and most importantly, ScopeManager allows to be "configured": by 
> supplying the recipe for dependency and resolution scopes, hence, makes 
> Resolver 2.x versatile, in a sense, it is not "this or that" anymore, it can 
> obey Maven3 and Maven4 dependency scopes at the same time.



--
This

[jira] [Updated] (MRESOLVER-512) Scope Manager



 [ 
https://issues.apache.org/jira/browse/MRESOLVER-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamas Cservenak updated MRESOLVER-512:
--
Description: 
In Resolver 1.x times, resolver was unaware of "resolution scope", to get the 
wanted resolution scope caller had to tweak and set up various nits and bits, 
like selectors, filters, and so on. It was easy to miss. Similarly, resolver 
had no "first class" type for "dependency scope" either, and its meaning and 
notion was sprinkled across several classes. Introducing new scope in these 
conditions (or alter selector to something that would have new scopes, like 
Maven4 plans) was nearly impossible.

The ScopeManager aims to solve these issues: it defines "resolution scope" and 
"dependency scope", interprets them, and allows caller to simply make a call to 
"resolve me main-runtime" resolution scope. No hoops and loops. Moreover, it is 
FASTER than Resolver 1.x was, that used always same selector (to build dirty 
graph), so potentially huge graph even if you needed just a bit of it, that was 
later chopped down to clean up the graph. ScopeManager automates selector 
selection/setup, and goes directly for result, in most cases the resulting tree 
is done in first pass.

Finally, and most importantly, ScopeManager allows to be "configured": by 
supplying the recipe for dependency and resolution scopes, hence, makes 
Resolver 2.x versatile, in a sense, it is not "this or that" anymore, it can 
obey Maven3 and Maven4 dependency scopes at the same time.

  was:Add centralized scope handling.


> Scope Manager
> -
>
> Key: MRESOLVER-512
> URL: https://issues.apache.org/jira/browse/MRESOLVER-512
> Project: Maven Resolver
>  Issue Type: New Feature
>  Components: Resolver
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-9
>
>
> In Resolver 1.x times, resolver was unaware of "resolution scope", to get the 
> wanted resolution scope caller had to tweak and set up various nits and bits, 
> like selectors, filters, and so on. It was easy to miss. Similarly, resolver 
> had no "first class" type for "dependency scope" either, and its meaning and 
> notion was sprinkled across several classes. Introducing new scope in these 
> conditions (or alter selector to something that would have new scopes, like 
> Maven4 plans) was nearly impossible.
> The ScopeManager aims to solve these issues: it defines "resolution scope" 
> and "dependency scope", interprets them, and allows caller to simply make a 
> call to "resolve me main-runtime" resolution scope. No hoops and loops. 
> Moreover, it is FASTER than Resolver 1.x was, that used always same selector 
> (to build dirty graph), so potentially huge graph even if you needed just a 
> bit of it, that was later chopped down to clean up the graph. ScopeManager 
> automates selector selection/setup, and goes directly for result, in most 
> cases the resulting tree is done in first pass.
> Finally, and most importantly, ScopeManager allows to be "configured": by 
> supplying the recipe for dependency and resolution scopes, hence, makes 
> Resolver 2.x versatile, in a sense, it is not "this or that" anymore, it can 
> obey Maven3 and Maven4 dependency scopes at the same time.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MRESOLVER-512) Scope Manager



[ 
https://issues.apache.org/jira/browse/MRESOLVER-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827486#comment-17827486
 ] 

ASF GitHub Bot commented on MRESOLVER-512:
--

cstamas opened a new pull request, #445:
URL: https://github.com/apache/maven-resolver/pull/445

   Resolver ScopeManager.
   
   ---
   
   https://issues.apache.org/jira/browse/MRESOLVER-512




> Scope Manager
> -
>
> Key: MRESOLVER-512
> URL: https://issues.apache.org/jira/browse/MRESOLVER-512
> Project: Maven Resolver
>  Issue Type: New Feature
>  Components: Resolver
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-9
>
>
> Add centralized scope handling.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[PR] [MRESOLVER-512] ScopeManager [maven-resolver]



cstamas opened a new pull request, #445:
URL: https://github.com/apache/maven-resolver/pull/445

   Resolver ScopeManager.
   
   ---
   
   https://issues.apache.org/jira/browse/MRESOLVER-512


-- 
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] (MCOMPILER-582) Automatic detection of release option for JDK < 9



 [ 
https://issues.apache.org/jira/browse/MCOMPILER-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus updated MCOMPILER-582:
--
Description: Since plexus-compiler 2.15.0 the {{release}} parameter is 
automatically disregarded for javac version < 9 
(https://github.com/codehaus-plexus/plexus-compiler/issues/140). It is no 
longer necessary to guard that parameter with a profile.  (was: Since 
plexus-compiler 2.15.0 `--release` options is automatically disregarded for 
javac version < 9 
(https://github.com/codehaus-plexus/plexus-compiler/issues/140). It is no 
longer necessary to guard that parameter with a profile.)

> Automatic detection of release option for JDK < 9
> -
>
> Key: MCOMPILER-582
> URL: https://issues.apache.org/jira/browse/MCOMPILER-582
> Project: Maven Compiler Plugin
>  Issue Type: New Feature
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.13.0
>
>
> Since plexus-compiler 2.15.0 the {{release}} parameter is automatically 
> disregarded for javac version < 9 
> (https://github.com/codehaus-plexus/plexus-compiler/issues/140). It is no 
> longer necessary to guard that parameter with a profile.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (DOXIA-734) XHTML 1 elements/attributes which are obsolete in XHTML5 no longer detected by XdocParser/FmlParser



 [ 
https://issues.apache.org/jira/browse/DOXIA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus reassigned DOXIA-734:
-

Assignee: Konrad Windszus

> XHTML 1 elements/attributes which are obsolete in XHTML5 no longer detected 
> by XdocParser/FmlParser
> ---
>
> Key: DOXIA-734
> URL: https://issues.apache.org/jira/browse/DOXIA-734
> Project: Maven Doxia
>  Issue Type: Bug
>  Components: Module - Apt, Module - Fml
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>
> Currently only {{}} is translated into a proper 
> {{Sink.anchor(...)}} call.
> The obsolete {{}} is currently not calling an according 
> {{Sink.anchor(...)}} method but may be still used in ancient markups which 
> derive from the XHtml5BaseParser.
> For example XDoc and FML both stem from the time where 
> https://www.w3.org/TR/xhtml1/ was the most recent XHTML spec and therefore 
> support {{a name}} (according to 
> https://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-xdoc/xsddoc/http___maven.apache.org_XDOC_2.0/element/a.html
>  and 
> https://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-fml/xsddoc/http___maven.apache.org_FML_1.0.1/element/a.html)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (DOXIA-734) XHTML 1 elements/attributes which are obsolete in XHTML5 no longer detected by XdocParser/FmlParser



 [ 
https://issues.apache.org/jira/browse/DOXIA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus updated DOXIA-734:
--
Summary: XHTML 1 elements/attributes which are obsolete in XHTML5 no longer 
detected by XdocParser/FmlParser  (was: anchor element with "name" attribute no 
longer detected by XdocParser/FmlParser)

> XHTML 1 elements/attributes which are obsolete in XHTML5 no longer detected 
> by XdocParser/FmlParser
> ---
>
> Key: DOXIA-734
> URL: https://issues.apache.org/jira/browse/DOXIA-734
> Project: Maven Doxia
>  Issue Type: Bug
>  Components: Module - Apt, Module - Fml
>Reporter: Konrad Windszus
>Priority: Major
>
> Currently only {{}} is translated into a proper 
> {{Sink.anchor(...)}} call.
> The obsolete {{}} is currently not calling an according 
> {{Sink.anchor(...)}} method but may be still used in ancient markups which 
> derive from the XHtml5BaseParser.
> For example XDoc and FML both stem from the time where 
> https://www.w3.org/TR/xhtml1/ was the most recent XHTML spec and therefore 
> support {{a name}} (according to 
> https://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-xdoc/xsddoc/http___maven.apache.org_XDOC_2.0/element/a.html
>  and 
> https://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-fml/xsddoc/http___maven.apache.org_FML_1.0.1/element/a.html)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[PR] Bump org.codehaus.plexus:plexus-archiver from 4.9.1 to 4.9.2 [maven-acr-plugin]



dependabot[bot] opened a new pull request, #32:
URL: https://github.com/apache/maven-acr-plugin/pull/32

   Bumps 
[org.codehaus.plexus:plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver)
 from 4.9.1 to 4.9.2.
   
   Release notes
   Sourced from https://github.com/codehaus-plexus/plexus-archiver/releases;>org.codehaus.plexus:plexus-archiver's
 releases.
   
   4.9.2
   
    Dependency updates
   
   Bump org.apache.commons:commons-compress from 1.26.0 to 1.26.1 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/325;>#325)
 https://github.com/dependabot;>@dependabot
   Bump org.codehaus.plexus:plexus from 16 to 17 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/324;>#324)
 https://github.com/dependabot;>@dependabot
   Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.0 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/323;>#323)
 https://github.com/dependabot;>@dependabot
   Bump org.assertj:assertj-core from 3.25.2 to 3.25.3 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/322;>#322)
 https://github.com/dependabot;>@dependabot
   Bump org.assertj:assertj-core from 3.25.1 to 3.25.2 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/320;>#320)
 https://github.com/dependabot;>@dependabot
   Bump org.assertj:assertj-core from 3.24.2 to 3.25.1 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/319;>#319)
 https://github.com/dependabot;>@dependabot
   Bump org.codehaus.plexus:plexus-io from 3.4.1 to 3.4.2 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/317;>#317)
 https://github.com/dependabot;>@dependabot
   
    Maintenance
   
   Bump release-drafter/release-drafter from 5 to 6 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/321;>#321)
 https://github.com/dependabot;>@dependabot
   
   
   
   
   Commits
   
   https://github.com/codehaus-plexus/plexus-archiver/commit/30e3a058ff1a68ad934c105e097a137e05743111;>30e3a05
 [maven-release-plugin] prepare release plexus-archiver-4.9.2
   https://github.com/codehaus-plexus/plexus-archiver/commit/0d2bedcfd3798fee20aa81676a4f02147d530cff;>0d2bedc
 Bump org.apache.commons:commons-compress from 1.26.0 to 1.26.1
   https://github.com/codehaus-plexus/plexus-archiver/commit/caeb7d83a1806288419cf12b72174574b0fc4268;>caeb7d8
 Bump org.codehaus.plexus:plexus from 16 to 17
   https://github.com/codehaus-plexus/plexus-archiver/commit/6077fd7385965710ed8dd5918acf6c2079497e9d;>6077fd7
 Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.0
   https://github.com/codehaus-plexus/plexus-archiver/commit/728627506af607073b4986d4189b2dba46fc189e;>7286275
 Bump org.assertj:assertj-core from 3.25.2 to 3.25.3
   https://github.com/codehaus-plexus/plexus-archiver/commit/41d252e71612a6680612d557d0339c9f880f41a7;>41d252e
 Bump release-drafter/release-drafter from 5 to 6
   https://github.com/codehaus-plexus/plexus-archiver/commit/d8fb23364bf90e0c3e74f09ef67b2bccfc889a4a;>d8fb233
 Bump org.assertj:assertj-core from 3.25.1 to 3.25.2
   https://github.com/codehaus-plexus/plexus-archiver/commit/661e428a223815d8210485a7bd093c05f240c495;>661e428
 Bump org.assertj:assertj-core from 3.24.2 to 3.25.1
   https://github.com/codehaus-plexus/plexus-archiver/commit/2e891e5a71f7478f9a34e2d2825a23b297c25101;>2e891e5
 Bump org.codehaus.plexus:plexus-io from 3.4.1 to 3.4.2
   https://github.com/codehaus-plexus/plexus-archiver/commit/a61668c862ada70482d0f30770d7b5f8c1390c63;>a61668c
 [maven-release-plugin] prepare for next development iteration
   See full diff in https://github.com/codehaus-plexus/plexus-archiver/compare/plexus-archiver-4.9.1...plexus-archiver-4.9.2;>compare
 view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.codehaus.plexus:plexus-archiver=maven=4.9.1=4.9.2)](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

[jira] [Commented] (MGPG-111) Clean up dependency declarations



[ 
https://issues.apache.org/jira/browse/MGPG-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827468#comment-17827468
 ] 

ASF GitHub Bot commented on MGPG-111:
-

elharo commented on code in PR #81:
URL: https://github.com/apache/maven-gpg-plugin/pull/81#discussion_r1526109383


##
pom.xml:
##
@@ -137,6 +149,7 @@ under the License.
   2.9.0
   pom
 
+ Clean up dependency declarations
> 
>
> Key: MGPG-111
> URL: https://issues.apache.org/jira/browse/MGPG-111
> Project: Maven GPG Plugin
>  Issue Type: Dependency upgrade
>Reporter: Elliotte Rusty Harold
>Assignee: Tamas Cservenak
>Priority: Minor
> Fix For: 3.2.1
>
>
> [WARNING] Used undeclared dependencies found:
> [WARNING]org.apache.maven:maven-artifact:jar:3.9.6:provided
> [WARNING]org.apache.maven:maven-settings:jar:3.9.6:provided
> [WARNING]com.kohlschutter.junixsocket:junixsocket-common:jar:2.9.0:compile
> [WARNING]org.apache.maven.resolver:maven-resolver-impl:jar:1.9.18:provided
> [WARNING] Unused declared dependencies found:
> [WARNING]com.kohlschutter.junixsocket:junixsocket-core:pom:2.9.0:compile
> [WARNING]org.codehaus.plexus:plexus-cipher:jar:2.0:compile



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [PR] [MGPG-111] Fix dependencies [maven-gpg-plugin]



elharo commented on code in PR #81:
URL: https://github.com/apache/maven-gpg-plugin/pull/81#discussion_r1526109383


##
pom.xml:
##
@@ -137,6 +149,7 @@ under the License.
   2.9.0
   pom
 
+

Review Comment:
   plexus-sec-dispatcher and maven-resolver-impl? That's surprising



-- 
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] (DOXIA-734) anchor element with "name" attribute no longer detected by XdocParser/FmlParser



[ 
https://issues.apache.org/jira/browse/DOXIA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827463#comment-17827463
 ] 

ASF GitHub Bot commented on DOXIA-734:
--

kwin commented on PR #204:
URL: https://github.com/apache/maven-doxia/pull/204#issuecomment-1999355773

   > Does it make sense to log a warning to tell the user that the attribute 
should be migrated?
   
   I don't think, because the user is complying with the spec while using 
XHTML5 only attributes/elements (while supported) is not specified for XDoc 
2.0. We should rather deprecate XDoc usage alltogether (but this is separate 
from this issue).




> anchor element with "name" attribute no longer detected by 
> XdocParser/FmlParser
> ---
>
> Key: DOXIA-734
> URL: https://issues.apache.org/jira/browse/DOXIA-734
> Project: Maven Doxia
>  Issue Type: Bug
>  Components: Module - Apt, Module - Fml
>Reporter: Konrad Windszus
>Priority: Major
>
> Currently only {{}} is translated into a proper 
> {{Sink.anchor(...)}} call.
> The obsolete {{}} is currently not calling an according 
> {{Sink.anchor(...)}} method but may be still used in ancient markups which 
> derive from the XHtml5BaseParser.
> For example XDoc and FML both stem from the time where 
> https://www.w3.org/TR/xhtml1/ was the most recent XHTML spec and therefore 
> support {{a name}} (according to 
> https://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-xdoc/xsddoc/http___maven.apache.org_XDOC_2.0/element/a.html
>  and 
> https://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-fml/xsddoc/http___maven.apache.org_FML_1.0.1/element/a.html)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [PR] [DOXIA-734] Restore handling of XHTML 1.0 obsolete attributes [maven-doxia]



kwin commented on PR #204:
URL: https://github.com/apache/maven-doxia/pull/204#issuecomment-1999355773

   > Does it make sense to log a warning to tell the user that the attribute 
should be migrated?
   
   I don't think, because the user is complying with the spec while using 
XHTML5 only attributes/elements (while supported) is not specified for XDoc 
2.0. We should rather deprecate XDoc usage alltogether (but this is separate 
from 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

[PR] Extract a lightweight API implementation to be used outside of maven (wip) [maven]



gnodet opened a new pull request, #1441:
URL: https://github.com/apache/maven/pull/1441

   (no comment)


-- 
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] (MGPG-112) Upgrading from 3.1.0 to 3.2.0 with no other changes causes "gpg: signing failed: No pinentry"



[ 
https://issues.apache.org/jira/browse/MGPG-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827457#comment-17827457
 ] 

Tamas Cservenak commented on MGPG-112:
--

Release 3.2.1 on vote (72h)

> Upgrading from 3.1.0 to 3.2.0 with no other changes causes "gpg: signing 
> failed: No pinentry"
> -
>
> Key: MGPG-112
> URL: https://issues.apache.org/jira/browse/MGPG-112
> Project: Maven GPG Plugin
>  Issue Type: Bug
>Affects Versions: 3.2.0
> Environment: GitHub actions, using ubuntu-22.04 (Ubuntu 22.04 LTS) 
> image. Full details can be found in the linked logs in Description.
>Reporter: Harald Kuhr
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.2.1
>
>
> After upgrading to Maven GPG plugin from 3.1.0 to 3.20, the Deploy step of my 
> projects CI failed with the message "gpg: signing failed: No pinentry". 
>  
> After upgrade to 3.2.0, the deploy step fails the build, while the relevant 
> part of the log says:
>  
> {noformat}
> [INFO] --- maven-gpg-plugin:3.2.0:sign (sign-artifacts) @ twelvemonkeys ---
> [INFO] Signer 'gpg' is signing 2 files
> gpg: signing failed: No pinentry
> gpg: signing failed: No pinentry
> ...
> Error:  Failed to execute goal 
> org.apache.maven.plugins:maven-gpg-plugin:3.2.0:sign (sign-artifacts) on 
> project twelvemonkeys: Exit code: 2 -> [Help 1]{noformat}
>  
> After reverting to the working 3.1.0, build and deploy succeeds, the relevant 
> part of the log says:
>  
> {noformat}
> [INFO] --- maven-gpg-plugin:3.1.0:sign (sign-artifacts) @ twelvemonkeys ---
> [INFO] Signing 2 files with default secret key.
> ...
> [INFO] BUILD SUCCESS
> {noformat}
>  
> Is this an expected/intended behavior with the 3.2.0 release, and does the 
> plugin need additional/different configuration? If this is the case, can you 
> provide suggestions or workarounds to get the signing working again?
> As this is a minor version change, I suspect this is a bug/regression and not 
> intended. I don't find anything in the release notes suggesting a 
> configuration change is required.
> Plugin configuration (private key and passphrase is passed using GHA secrets):
>  
> {noformat}
> 
> org.apache.maven.plugins
> maven-gpg-plugin
> 3.1.0  
> 
> 
> 
> --pinentry-mode
> loopback
> 
> 
> 
> 
> sign-artifacts
> verify
> 
> sign
> 
> 
> 
> {noformat}
>  
> Full POM for the build: 
> [https://github.com/haraldk/TwelveMonkeys/blob/878d6217d8538f05205c092c7230c8db6727d058/pom.xml]
>  
> Full logs from broken build (Dependabot PR bump 3.1.0 to 3.2.0):
> [https://github.com/haraldk/TwelveMonkeys/actions/runs/8230467333/job/22504202895]
>  
> Full logs from working build (reverted to 3.1.0): 
> [https://github.com/haraldk/TwelveMonkeys/actions/runs/8230663423/job/22504567422]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [PR] Bump org.codehaus.plexus:plexus-archiver from 4.9.0 to 4.9.1 [maven-ear-plugin]



dependabot[bot] commented on PR #106:
URL: https://github.com/apache/maven-ear-plugin/pull/106#issuecomment-1999282252

   Superseded by #109.


-- 
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

Re: [PR] Bump org.codehaus.plexus:plexus-archiver from 4.9.0 to 4.9.1 [maven-ear-plugin]



dependabot[bot] closed pull request #106: Bump 
org.codehaus.plexus:plexus-archiver from 4.9.0 to 4.9.1
URL: https://github.com/apache/maven-ear-plugin/pull/106


-- 
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

[PR] Bump org.codehaus.plexus:plexus-archiver from 4.9.0 to 4.9.2 [maven-ear-plugin]



dependabot[bot] opened a new pull request, #109:
URL: https://github.com/apache/maven-ear-plugin/pull/109

   Bumps 
[org.codehaus.plexus:plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver)
 from 4.9.0 to 4.9.2.
   
   Release notes
   Sourced from https://github.com/codehaus-plexus/plexus-archiver/releases;>org.codehaus.plexus:plexus-archiver's
 releases.
   
   4.9.2
   
    Dependency updates
   
   Bump org.apache.commons:commons-compress from 1.26.0 to 1.26.1 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/325;>#325)
 https://github.com/dependabot;>@dependabot
   Bump org.codehaus.plexus:plexus from 16 to 17 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/324;>#324)
 https://github.com/dependabot;>@dependabot
   Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.0 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/323;>#323)
 https://github.com/dependabot;>@dependabot
   Bump org.assertj:assertj-core from 3.25.2 to 3.25.3 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/322;>#322)
 https://github.com/dependabot;>@dependabot
   Bump org.assertj:assertj-core from 3.25.1 to 3.25.2 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/320;>#320)
 https://github.com/dependabot;>@dependabot
   Bump org.assertj:assertj-core from 3.24.2 to 3.25.1 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/319;>#319)
 https://github.com/dependabot;>@dependabot
   Bump org.codehaus.plexus:plexus-io from 3.4.1 to 3.4.2 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/317;>#317)
 https://github.com/dependabot;>@dependabot
   
    Maintenance
   
   Bump release-drafter/release-drafter from 5 to 6 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/321;>#321)
 https://github.com/dependabot;>@dependabot
   
   4.9.1
   
    New features and improvements
   
   https://redirect.github.com/codehaus-plexus/plexus-archiver/issues/311;>#311
 - provide fluent setter for usingDefaultExcludes flag in Abstrac… (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/312;>#312)
 https://github.com/redzi;>@redzi
   
    Dependency updates
   
   Bump org.codehaus.plexus:plexus from 15 to 16 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/316;>#316)
 https://github.com/dependabot;>@dependabot
   Bump com.github.luben:zstd-jni from 1.5.5-10 to 1.5.5-11 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/314;>#314)
 https://github.com/dependabot;>@dependabot
   Bump commons-io:commons-io from 2.15.0 to 2.15.1 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/313;>#313)
 https://github.com/dependabot;>@dependabot
   Bump org.apache.commons:commons-compress from 1.24.0 to 1.25.0 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/309;>#309)
 https://github.com/dependabot;>@dependabot
   
    Maintenance
   
   Reuse plexus-pom action for CI (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/315;>#315)
 https://github.com/slachiewicz;>@slachiewicz
   
   
   
   
   Commits
   
   https://github.com/codehaus-plexus/plexus-archiver/commit/30e3a058ff1a68ad934c105e097a137e05743111;>30e3a05
 [maven-release-plugin] prepare release plexus-archiver-4.9.2
   https://github.com/codehaus-plexus/plexus-archiver/commit/0d2bedcfd3798fee20aa81676a4f02147d530cff;>0d2bedc
 Bump org.apache.commons:commons-compress from 1.26.0 to 1.26.1
   https://github.com/codehaus-plexus/plexus-archiver/commit/caeb7d83a1806288419cf12b72174574b0fc4268;>caeb7d8
 Bump org.codehaus.plexus:plexus from 16 to 17
   https://github.com/codehaus-plexus/plexus-archiver/commit/6077fd7385965710ed8dd5918acf6c2079497e9d;>6077fd7
 Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.0
   https://github.com/codehaus-plexus/plexus-archiver/commit/728627506af607073b4986d4189b2dba46fc189e;>7286275
 Bump org.assertj:assertj-core from 3.25.2 to 3.25.3
   https://github.com/codehaus-plexus/plexus-archiver/commit/41d252e71612a6680612d557d0339c9f880f41a7;>41d252e
 Bump release-drafter/release-drafter from 5 to 6
   https://github.com/codehaus-plexus/plexus-archiver/commit/d8fb23364bf90e0c3e74f09ef67b2bccfc889a4a;>d8fb233
 Bump org.assertj:assertj-core from 3.25.1 to 3.25.2
   https://github.com/codehaus-plexus/plexus-archiver/commit/661e428a223815d8210485a7bd093c05f240c495;>661e428
 Bump org.assertj:assertj-core from 3.24.2 to 3.25.1
   https://github.com/codehaus-plexus/plexus-archiver/commit/2e891e5a71f7478f9a34e2d2825a23b297c25101;>2e891e5
 Bump org.codehaus.plexus:plexus-io from 3.4.1 to 3.4.2
   https://github.com/codehaus-plexus/plexus-archiver/commit/a61668c862ada70482d0f30770d7b5f8c1390c63;>a61668c
 [maven-release-plugin] prepare for next development iteration
   Additional commits viewable in https://github.com/codehaus-plexus/plexus-archiver/compare/plexus-archiver-4.9.0...plexus-archiver-4.9.2;>compare
 view

[PR] Remove unneeded dependencies in maven-di [maven]



gnodet opened a new pull request, #1440:
URL: https://github.com/apache/maven/pull/1440

   (no comment)


-- 
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-514) Update to Commons Codec 1.16.1



 [ 
https://issues.apache.org/jira/browse/MRESOLVER-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamas Cservenak closed MRESOLVER-514.
-
  Assignee: Tamas Cservenak
Resolution: Fixed

> Update to Commons Codec 1.16.1
> --
>
> Key: MRESOLVER-514
> URL: https://issues.apache.org/jira/browse/MRESOLVER-514
> Project: Maven Resolver
>  Issue Type: Dependency upgrade
>  Components: Resolver
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-9
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [PR] Bump commons-codec:commons-codec from 1.16.0 to 1.16.1 [maven-resolver]



cstamas merged PR #440:
URL: https://github.com/apache/maven-resolver/pull/440


-- 
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-513) Update to Slf4j 2.0.12



 [ 
https://issues.apache.org/jira/browse/MRESOLVER-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamas Cservenak closed MRESOLVER-513.
-
  Assignee: Tamas Cservenak
Resolution: Fixed

> Update to Slf4j 2.0.12
> --
>
> Key: MRESOLVER-513
> URL: https://issues.apache.org/jira/browse/MRESOLVER-513
> Project: Maven Resolver
>  Issue Type: Dependency upgrade
>  Components: Resolver
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-9
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [PR] Bump slf4jVersion from 2.0.11 to 2.0.12 [maven-resolver]



cstamas merged PR #441:
URL: https://github.com/apache/maven-resolver/pull/441


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Created] (MRESOLVER-513) Update to Slf4j 2.0.12

Tamas Cservenak created MRESOLVER-513:
-

 Summary: Update to Slf4j 2.0.12
 Key: MRESOLVER-513
 URL: https://issues.apache.org/jira/browse/MRESOLVER-513
 Project: Maven Resolver
  Issue Type: Dependency upgrade
  Components: Resolver
Reporter: Tamas Cservenak
 Fix For: 2.0.0, 2.0.0-alpha-9






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (MRESOLVER-514) Update to Commons Codec 1.16.1

Tamas Cservenak created MRESOLVER-514:
-

 Summary: Update to Commons Codec 1.16.1
 Key: MRESOLVER-514
 URL: https://issues.apache.org/jira/browse/MRESOLVER-514
 Project: Maven Resolver
  Issue Type: Dependency upgrade
  Components: Resolver
Reporter: Tamas Cservenak
 Fix For: 2.0.0, 2.0.0-alpha-9






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [PR] Bump com.google.inject:guice from 6.0.0 to 7.0.0 [maven-resolver]



dependabot[bot] closed pull request #444: Bump com.google.inject:guice from 
6.0.0 to 7.0.0
URL: https://github.com/apache/maven-resolver/pull/444


-- 
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

Re: [PR] Bump com.google.inject:guice from 6.0.0 to 7.0.0 [maven-resolver]



cstamas commented on PR #444:
URL: https://github.com/apache/maven-resolver/pull/444#issuecomment-1999228951

   @dependabot close


-- 
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

Re: [PR] Bump org.eclipse.jetty:jetty-bom from 10.0.20 to 12.0.7 [maven-resolver]



dependabot[bot] closed pull request #443: Bump org.eclipse.jetty:jetty-bom from 
10.0.20 to 12.0.7
URL: https://github.com/apache/maven-resolver/pull/443


-- 
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

Re: [PR] Bump org.eclipse.jetty:jetty-bom from 10.0.20 to 12.0.7 [maven-resolver]



cstamas commented on PR #443:
URL: https://github.com/apache/maven-resolver/pull/443#issuecomment-1999228560

   @dependabot close


-- 
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-510) Update to Redisson 3.27.2



 [ 
https://issues.apache.org/jira/browse/MRESOLVER-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamas Cservenak closed MRESOLVER-510.
-
  Assignee: Tamas Cservenak
Resolution: Fixed

> Update to Redisson 3.27.2
> -
>
> Key: MRESOLVER-510
> URL: https://issues.apache.org/jira/browse/MRESOLVER-510
> Project: Maven Resolver
>  Issue Type: Dependency upgrade
>  Components: Resolver
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-9
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (MRESOLVER-512) Scope Manager



 [ 
https://issues.apache.org/jira/browse/MRESOLVER-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamas Cservenak reassigned MRESOLVER-512:
-

Assignee: Tamas Cservenak

> Scope Manager
> -
>
> Key: MRESOLVER-512
> URL: https://issues.apache.org/jira/browse/MRESOLVER-512
> Project: Maven Resolver
>  Issue Type: New Feature
>  Components: Resolver
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-9
>
>
> Add centralized scope handling.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Closed] (MRESOLVER-508) Update to Junit 5.10.2



 [ 
https://issues.apache.org/jira/browse/MRESOLVER-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamas Cservenak closed MRESOLVER-508.
-
  Assignee: Tamas Cservenak
Resolution: Fixed

> Update to Junit 5.10.2
> --
>
> Key: MRESOLVER-508
> URL: https://issues.apache.org/jira/browse/MRESOLVER-508
> Project: Maven Resolver
>  Issue Type: Dependency upgrade
>  Components: Resolver
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-9
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Closed] (MRESOLVER-509) Update to mockito 5.11.0



 [ 
https://issues.apache.org/jira/browse/MRESOLVER-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamas Cservenak closed MRESOLVER-509.
-
  Assignee: Tamas Cservenak
Resolution: Fixed

> Update to mockito 5.11.0
> 
>
> Key: MRESOLVER-509
> URL: https://issues.apache.org/jira/browse/MRESOLVER-509
> Project: Maven Resolver
>  Issue Type: Dependency upgrade
>  Components: Resolver
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-9
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Closed] (MRESOLVER-511) Update testcontainers to 1.19.7



 [ 
https://issues.apache.org/jira/browse/MRESOLVER-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamas Cservenak closed MRESOLVER-511.
-
  Assignee: Tamas Cservenak
Resolution: Fixed

> Update testcontainers to 1.19.7
> ---
>
> Key: MRESOLVER-511
> URL: https://issues.apache.org/jira/browse/MRESOLVER-511
> Project: Maven Resolver
>  Issue Type: Dependency upgrade
>  Components: Resolver
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-9
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (MRESOLVER-509) Update to mockito 5.11.0



 [ 
https://issues.apache.org/jira/browse/MRESOLVER-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamas Cservenak updated MRESOLVER-509:
--
Component/s: Resolver

> Update to mockito 5.11.0
> 
>
> Key: MRESOLVER-509
> URL: https://issues.apache.org/jira/browse/MRESOLVER-509
> Project: Maven Resolver
>  Issue Type: Dependency upgrade
>  Components: Resolver
>Reporter: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-9
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (MRESOLVER-511) Update testcontainers to 1.19.7



 [ 
https://issues.apache.org/jira/browse/MRESOLVER-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamas Cservenak updated MRESOLVER-511:
--
Component/s: Resolver

> Update testcontainers to 1.19.7
> ---
>
> Key: MRESOLVER-511
> URL: https://issues.apache.org/jira/browse/MRESOLVER-511
> Project: Maven Resolver
>  Issue Type: Dependency upgrade
>  Components: Resolver
>Reporter: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-9
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (MRESOLVER-508) Update to Junit 5.10.2



 [ 
https://issues.apache.org/jira/browse/MRESOLVER-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamas Cservenak updated MRESOLVER-508:
--
Component/s: Resolver

> Update to Junit 5.10.2
> --
>
> Key: MRESOLVER-508
> URL: https://issues.apache.org/jira/browse/MRESOLVER-508
> Project: Maven Resolver
>  Issue Type: Dependency upgrade
>  Components: Resolver
>Reporter: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-9
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (MRESOLVER-512) Scope Manager

Tamas Cservenak created MRESOLVER-512:
-

 Summary: Scope Manager
 Key: MRESOLVER-512
 URL: https://issues.apache.org/jira/browse/MRESOLVER-512
 Project: Maven Resolver
  Issue Type: New Feature
  Components: Resolver
Reporter: Tamas Cservenak
 Fix For: 2.0.0, 2.0.0-alpha-9


Add centralized scope handling.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (MRESOLVER-510) Update to Redisson 3.27.2



 [ 
https://issues.apache.org/jira/browse/MRESOLVER-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamas Cservenak updated MRESOLVER-510:
--
Component/s: Resolver

> Update to Redisson 3.27.2
> -
>
> Key: MRESOLVER-510
> URL: https://issues.apache.org/jira/browse/MRESOLVER-510
> Project: Maven Resolver
>  Issue Type: Dependency upgrade
>  Components: Resolver
>Reporter: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-9
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[PR] Bump com.google.inject:guice from 6.0.0 to 7.0.0 [maven-resolver]



dependabot[bot] opened a new pull request, #444:
URL: https://github.com/apache/maven-resolver/pull/444

   Bumps [com.google.inject:guice](https://github.com/google/guice) from 6.0.0 
to 7.0.0.
   
   Release notes
   Sourced from https://github.com/google/guice/releases;>com.google.inject:guice's 
releases.
   
   Guice 7.0.0
   See https://github.com/google/guice/wiki/Guice700;>https://github.com/google/guice/wiki/Guice700
 for release notes.
   Guice 7.0.0-rc1
   See https://github.com/google/guice/wiki/Guice700;>https://github.com/google/guice/wiki/Guice700
 for release notes.
   
   
   
   Commits
   
   https://github.com/google/guice/commit/b0e1d0fab0167cd555ab8d262333c1a32db7d492;>b0e1d0f
 set 7.0.0 release #s.
   https://github.com/google/guice/commit/f4a66b797ecc05d80406d6c8fb11e6cc0e5c6d21;>f4a66b7
 Make error_prone_annotations dependency optional
   https://github.com/google/guice/commit/654032a954d55a00fc5ee90da815da98cb6676a1;>654032a
 Internal change.
   https://github.com/google/guice/commit/bee813b7cc15e46695ca1baf5041a00e0a612f91;>bee813b
 Improve MissingImplementationError to lazily calculate suggestions and 
standa...
   https://github.com/google/guice/commit/2d64067e99401e50404c6e05a819bce891b725de;>2d64067
 Use linked bindings for MapBinder/Multibinder/OptionalBinder aliases, 
instead...
   https://github.com/google/guice/commit/be0141cc0d01763a13ec0b2fcd32ddbe0748ad6d;>be0141c
 Internal change
   https://github.com/google/guice/commit/40a5bcfab5cfe45c3b6c5ffc9309b310df82775b;>40a5bcf
 Avoid re-initializing factories that are already initialized. This is 
necessa...
   https://github.com/google/guice/commit/9ac476784e88f4481f8211dcb19ac536f5f2b32d;>9ac4767
 Change the way we reference what 6.0 supports in the README, so it doesn't 
ge...
   https://github.com/google/guice/commit/24324ca6c61f64872376ed7f4ed22a3f1f0724f1;>24324ca
 Prepare for the Guice 6.0  7.0 releases.  This change does the 
following:
   https://github.com/google/guice/commit/49b1a33c594fd92ad0d1d013fa91d689e8814a6c;>49b1a33
 Remove redundant references to javax.{inject,persistence,servlet} and 
replace...
   See full diff in https://github.com/google/guice/compare/6.0.0...7.0.0;>compare 
view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=com.google.inject:guice=maven=6.0.0=7.0.0)](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 show  ignore conditions` will show all of 
the ignore conditions of the specified dependency
   - `@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

[PR] Bump org.eclipse.jetty:jetty-bom from 10.0.20 to 12.0.7 [maven-resolver]



dependabot[bot] opened a new pull request, #443:
URL: https://github.com/apache/maven-resolver/pull/443

   Bumps [org.eclipse.jetty:jetty-bom](https://github.com/jetty/jetty.project) 
from 10.0.20 to 12.0.7.
   
   Release notes
   Sourced from https://github.com/jetty/jetty.project/releases;>org.eclipse.jetty:jetty-bom's
 releases.
   
   12.0.7
   Special Thanks to the following Eclipse Jetty community members
   
   https://github.com/hboutemy;>@hboutemy (Hervé 
Boutemy)
   https://github.com/danishnawab;>@danishnawab 
(Danish Nawab)
   
   Changelog
   
   https://redirect.github.com/jetty/jetty.project/issues/11465;>#11465 
- HttpURI.toURI() sets userInfo to null
   https://redirect.github.com/jetty/jetty.project/issues/11455;>#11455 
- Improve DEBUG during WebInfConfiguration.unpack
   https://redirect.github.com/jetty/jetty.project/issues/11448;>#11448 
- UriCompliance.Violation ignored despite being set
   https://redirect.github.com/jetty/jetty.project/issues/11443;>#11443 
- Fix NPE in HttpReceiverOverHTTP2.read() when the channel's stream is null
   https://redirect.github.com/jetty/jetty.project/issues/11435;>#11435 
- Add suppressed failures in Callback failed
   https://redirect.github.com/jetty/jetty.project/issues/11432;>#11432 
- Change default number of acceptor threads
   https://redirect.github.com/jetty/jetty.project/issues/11426;>#11426 
- Experiment with ArrayByteBufferPool performance
   https://redirect.github.com/jetty/jetty.project/issues/11424;>#11424 
- What is the jetty.deploy.scanInterval default?  module, ini, 
code, and documentation do not agree.
   https://redirect.github.com/jetty/jetty.project/issues/11414;>#11414 
- When producing URI/URL strings follow spec and produce lowercase schemes and 
drop default ports
   https://redirect.github.com/jetty/jetty.project/issues/11410;>#11410 
- PathMappingsHandler does not start ResourceHandler properly
   https://redirect.github.com/jetty/jetty.project/issues/11401;>#11401 
- Replace StringBuffer with StringBuilder
   https://redirect.github.com/jetty/jetty.project/issues/11398;>#11398 
- WebSocket ClosedChannelException when demanding frames in onOpen
   https://redirect.github.com/jetty/jetty.project/issues/11397;>#11397 
- Jetty 12: ContextHandler.getTempDirectory() does not respect the 
Context.getTempDirectory() contract
   https://redirect.github.com/jetty/jetty.project/issues/11387;>#11387 
- Reintroduce MultiPartCompliance.LEGACY (not as default) too allow for parsing 
of non-compliant multipart/form-data
   https://redirect.github.com/jetty/jetty.project/issues/11386;>#11386 
- Making FormFields get defaults from Context, not Request
   https://redirect.github.com/jetty/jetty.project/issues/11383;>#11383 
- Added documentation about SslHandshakeListener.
   https://redirect.github.com/jetty/jetty.project/issues/11377;>#11377 
- Jetty 12 fails to start WebApp Bundle with OSGi Boot bundle (or when 
packaged)
   https://redirect.github.com/jetty/jetty.project/issues/11371;>#11371 
- Review ArrayByteBufferPool eviction
   https://redirect.github.com/jetty/jetty.project/issues/11370;>#11370 
- IllegalStateException when last write fails
   https://redirect.github.com/jetty/jetty.project/issues/11363;>#11363 
- ContentSourcePublisher throws from request
   https://redirect.github.com/jetty/jetty.project/issues/11361;>#11361 
- Updates to UriCompliance.checkUriCompliance
   https://redirect.github.com/jetty/jetty.project/issues/11360;>#11360 
- drop buildnumber:create already executed by jetty-util (https://github.com/hboutemy;>@hboutemy)
   https://redirect.github.com/jetty/jetty.project/issues/11356;>#11356 
- Allow ServerWebSocketContainer to be created without ContextHandler
   https://redirect.github.com/jetty/jetty.project/issues/11353;>#11353 
- The default virtual thread executor should created named threads (https://github.com/danishnawab;>@danishnawab)
   https://redirect.github.com/jetty/jetty.project/issues/11310;>#11310 
- Uploading big multipart files via jetty 12.0.5 with spring boot 3.2.1 cause 
problems
   https://redirect.github.com/jetty/jetty.project/issues/11279;>#11279 
- fix use of AliasCheckers with CombinedResource
   https://redirect.github.com/jetty/jetty.project/issues/11278;>#11278 
- 500 response when trying to display symlinked directory
   https://redirect.github.com/jetty/jetty.project/issues/11270;>#11270 
- Windows 11 pro - problem launching Jetty with  
${jetty.home}\etc\jetty-ee10-deploy.xml 
   https://redirect.github.com/jetty/jetty.project/issues/10432;>#10432 
- Fix buffer leaks in FCGI and H3 HttpClientIdleTimeoutTest
   https://redirect.github.com/jetty/jetty.project/issues/8979;>#8979 - 
Jetty 12 - HttpClientTransport network modes
   https://redirect.github.com/jetty/jetty.project/issues/8887;>#8887 - 
Jetty-12 client calls onDataAvailable with producing thread
   
   12.0.6
   Security Updates
   This release addresses:
   
   CVE-2024-22201 - HTTP/2 connection not closed

[PR] Bump mavenVersion from 4.0.0-alpha-12 to 4.0.0-alpha-13 [maven-resolver]



dependabot[bot] opened a new pull request, #442:
URL: https://github.com/apache/maven-resolver/pull/442

   Bumps `mavenVersion` from 4.0.0-alpha-12 to 4.0.0-alpha-13.
   Updates `org.apache.maven:maven-resolver-provider` from 4.0.0-alpha-12 to 
4.0.0-alpha-13
   
   Commits
   
   https://github.com/apache/maven/commit/0a6a5617fe5ef65c44f05903491e170d92cf37fc;>0a6a561
 [maven-release-plugin] prepare release maven-4.0.0-alpha-13
   https://github.com/apache/maven/commit/2bfa3a8fae6cc2eaca39a717bc2d9fbed55afbdd;>2bfa3a8
 [MNG-8061] Maven: Require Java 17 (https://redirect.github.com/apache/maven/issues/1430;>#1430)
   https://github.com/apache/maven/commit/5029cc238ce5ce03b0fb431a278889f8b788c0a7;>5029cc2
 [MNG-8012] Warn if in-reactor BOM import happens (https://redirect.github.com/apache/maven/issues/1434;>#1434)
   https://github.com/apache/maven/commit/9780ca1baff15e977d41da4687abc7e4f355bd77;>9780ca1
 [MNG-8015] Control the type of path where each dependency can be placed (https://redirect.github.com/apache/maven/issues/1401;>#1401)
   https://github.com/apache/maven/commit/a27873629f94174bbcaa345c81abb204e4357ce5;>a278736
 [MNG-8024] Make WrapperProperties and WrapperList serializable (https://redirect.github.com/apache/maven/issues/1433;>#1433)
   https://github.com/apache/maven/commit/a3e8da805c7e8d743700f13924bd2aafe3fe6783;>a3e8da8
 Make LifecycleStarter pluggable (https://redirect.github.com/apache/maven/issues/1424;>#1424)
   https://github.com/apache/maven/commit/456890d40bd63af5036b8db31c4e5b50532f48ee;>456890d
 Missing annotations on api (https://redirect.github.com/apache/maven/issues/1428;>#1428)
   https://github.com/apache/maven/commit/24eee1f8e66a3c8e9baaceb2d83edfeb14a6d121;>24eee1f
 Add a SpiService marker interface (https://redirect.github.com/apache/maven/issues/1427;>#1427)
   https://github.com/apache/maven/commit/a9934f91fd0808e55f1b08ada91b0d2fcdf59f4a;>a9934f9
 Extract JLine support into its own module (https://redirect.github.com/apache/maven/issues/1426;>#1426)
   https://github.com/apache/maven/commit/ce151933949ab39eca78b8374531d39bc8c76b0f;>ce15193
 Fix concurrent cache access (https://redirect.github.com/apache/maven/issues/1425;>#1425)
   Additional commits viewable in https://github.com/apache/maven/compare/maven-4.0.0-alpha-12...maven-4.0.0-alpha-13;>compare
 view
   
   
   
   
   Updates `org.apache.maven:maven-model-builder` from 4.0.0-alpha-12 to 
4.0.0-alpha-13
   
   Commits
   
   https://github.com/apache/maven/commit/0a6a5617fe5ef65c44f05903491e170d92cf37fc;>0a6a561
 [maven-release-plugin] prepare release maven-4.0.0-alpha-13
   https://github.com/apache/maven/commit/2bfa3a8fae6cc2eaca39a717bc2d9fbed55afbdd;>2bfa3a8
 [MNG-8061] Maven: Require Java 17 (https://redirect.github.com/apache/maven/issues/1430;>#1430)
   https://github.com/apache/maven/commit/5029cc238ce5ce03b0fb431a278889f8b788c0a7;>5029cc2
 [MNG-8012] Warn if in-reactor BOM import happens (https://redirect.github.com/apache/maven/issues/1434;>#1434)
   https://github.com/apache/maven/commit/9780ca1baff15e977d41da4687abc7e4f355bd77;>9780ca1
 [MNG-8015] Control the type of path where each dependency can be placed (https://redirect.github.com/apache/maven/issues/1401;>#1401)
   https://github.com/apache/maven/commit/a27873629f94174bbcaa345c81abb204e4357ce5;>a278736
 [MNG-8024] Make WrapperProperties and WrapperList serializable (https://redirect.github.com/apache/maven/issues/1433;>#1433)
   https://github.com/apache/maven/commit/a3e8da805c7e8d743700f13924bd2aafe3fe6783;>a3e8da8
 Make LifecycleStarter pluggable (https://redirect.github.com/apache/maven/issues/1424;>#1424)
   https://github.com/apache/maven/commit/456890d40bd63af5036b8db31c4e5b50532f48ee;>456890d
 Missing annotations on api (https://redirect.github.com/apache/maven/issues/1428;>#1428)
   https://github.com/apache/maven/commit/24eee1f8e66a3c8e9baaceb2d83edfeb14a6d121;>24eee1f
 Add a SpiService marker interface (https://redirect.github.com/apache/maven/issues/1427;>#1427)
   https://github.com/apache/maven/commit/a9934f91fd0808e55f1b08ada91b0d2fcdf59f4a;>a9934f9
 Extract JLine support into its own module (https://redirect.github.com/apache/maven/issues/1426;>#1426)
   https://github.com/apache/maven/commit/ce151933949ab39eca78b8374531d39bc8c76b0f;>ce15193
 Fix concurrent cache access (https://redirect.github.com/apache/maven/issues/1425;>#1425)
   Additional commits viewable in https://github.com/apache/maven/compare/maven-4.0.0-alpha-12...maven-4.0.0-alpha-13;>compare
 view
   
   
   
   
   Updates `org.apache.maven:maven-plugin-api` from 4.0.0-alpha-12 to 
4.0.0-alpha-13
   
   Commits
   
   https://github.com/apache/maven/commit/0a6a5617fe5ef65c44f05903491e170d92cf37fc;>0a6a561
 [maven-release-plugin] prepare release maven-4.0.0-alpha-13
   https://github.com/apache/maven/commit/2bfa3a8fae6cc2eaca39a717bc2d9fbed55afbdd;>2bfa3a8
 [MNG-8061] Maven: Require Java 17 (https://redirect.github.com/apache/maven/issues/1430;>#1430)

[PR] Bump slf4jVersion from 2.0.11 to 2.0.12 [maven-resolver]



dependabot[bot] opened a new pull request, #441:
URL: https://github.com/apache/maven-resolver/pull/441

   Bumps `slf4jVersion` from 2.0.11 to 2.0.12.
   Updates `org.slf4j:slf4j-api` from 2.0.11 to 2.0.12
   
   Updates `org.slf4j:slf4j-simple` from 2.0.11 to 2.0.12
   
   Updates `org.slf4j:jcl-over-slf4j` from 2.0.11 to 2.0.12
   
   
   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 show  ignore conditions` will show all of 
the ignore conditions of the specified dependency
   - `@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

[PR] Bump commons-codec:commons-codec from 1.16.0 to 1.16.1 [maven-resolver]

dependabot[bot] opened a new pull request, #440:
URL: https://github.com/apache/maven-resolver/pull/440

Bumps [commons-codec:commons-codec](https://github.com/apache/commons-codec)
from 1.16.0 to 1.16.1.

Changelog
Sourced from https://github.com/apache/commons-codec/blob/master/RELEASE-NOTES.txt;>commons-codec:commons-codec's
changelog.

Apache Commons Codec 1.16.1
RELEASE NOTES
The Apache Commons Codec component contains encoder and decoders for
various formats such as Base16, Base32, Base64, digest, and Hexadecimal. In
addition to these
widely used encoders and decoders, the codec package also maintains a
collection of phonetic encoding utilities.
Feature and fix release. Requires a minimum of Java 8.
Changes in this version include:
New features:
o Add Maven property project.build.outputTimestamp for build
reproducibility. Thanks to Gary Gregory.
Fixed Bugs:
o CODEC-295: Test clean ups. Thanks to Gary Gregory.
o [StepSecurity] ci: Harden GitHub Actions https://redirect.github.com/apache/commons-codec/issues/187;>#187.
Thanks to step-security-bot, Gary Gregory.
o CODEC-295: Correct error in Base64 Javadoc https://redirect.github.com/apache/commons-codec/issues/188;>#188.
Thanks to Evan Saulpaugh.
o CODEC-295: Add minimum Java version in changes.xml https://redirect.github.com/apache/commons-codec/issues/186;>#186.
Thanks to Olivier Jaquemet, Gary Gregory.
o CODEC-310: Documentation update for the org.apache.commons.codec.digest.*
package https://redirect.github.com/apache/commons-codec/issues/208;>#208.
Thanks to Yakov Shafranovich.
o Precompile regular expression in UnixCrypt.crypt(byte[],
String). Thanks to Gary Gregory.
o CODEC-315: Fix possible IndexOutOfBoundException in PhoneticEngine.encode
method https://redirect.github.com/apache/commons-codec/issues/223;>#223.
Thanks to Arthur Chan, Gary Gregory.
o CODEC-313: Fix possible ArrayIndexOutOfBoundsException in
QuotedPrintableCodec.encodeQuotedPrintable() method https://redirect.github.com/apache/commons-codec/issues/221;>#221.
Thanks to Arthur Chan, Gary Gregory.
o CODEC-312: Fix possible StringIndexOutOfBoundException in
MatchRatingApproachEncoder.encode() method https://redirect.github.com/apache/commons-codec/issues/220;>#220.
Thanks to Arthur Chan, Gary Gregory.
o CODEC-311: Fix possible ArrayIndexOutOfBoundException in
RefinedSoundex.getMappingCode() https://redirect.github.com/apache/commons-codec/issues/219;>#219.
Thanks to Arthur Chan, Gary Gregory.
o CODEC-314: Fix possible IndexOutOfBoundsException in
PercentCodec.insertAlwaysEncodeChars() method https://redirect.github.com/apache/commons-codec/issues/222;>#222.
Thanks to Arthur Chan, Gary Gregory.
o Deprecate UnixCrypt 0-argument constructor. Thanks to Gary
Gregory.
o Deprecate Md5Crypt 0-argument constructor. Thanks to Gary
Gregory.
o Deprecate Crypt 0-argument constructor. Thanks to Gary Gregory.
o Deprecate StringUtils 0-argument constructor. Thanks to Gary
Gregory.
o Deprecate Resources 0-argument constructor. Thanks to Gary
Gregory.
o Deprecate Charsets 0-argument constructor. Thanks to Gary
Gregory.
o Deprecate CharEncoding 0-argument constructor. Thanks to Gary
Gregory.
o Add missing version for animal-sniffer-maven-plugin. Thanks to
Gary Gregory.
Changes:
o Bump commons-parent from 58 to 66. Thanks to Dependabot, Gary
Gregory.
o Bump commons-lang3 from 3.12.0 to 3.14.0. Thanks to Gary
Gregory.
o Bump commons-io from 2.13.0 to 2.15.1. Thanks to Gary
Gregory.
For complete information on Apache Commons Codec, including instructions
on how to submit bug reports,
patches, or suggestions for improvement, see the Apache Commons Codec
website:
https://commons.apache.org/proper/commons-codec/;>https://commons.apache.org/proper/commons-codec/
Download page: https://commons.apache.org/proper/commons-codec/download_codec.cgi;>https://commons.apache.org/proper/commons-codec/download_codec.cgi

... (truncated)

Commits

https://github.com/apache/commons-codec/commit/e59fc76531141cb4a36f3031457b9d5f07e5e43f;>e59fc76
Prepare release candidate
https://github.com/apache/commons-codec/commit/90c8023be911b42bab20b31b0e325174df0ee452;>90c8023
Prepare for the next release candidate
https://github.com/apache/commons-codec/commit/05714adcf957e7a7644a71cd82de30145288ff38;>05714ad
Prepare release candidate
https://github.com/apache/commons-codec/commit/060be1a1ca4b229ab348618ecae506a65543356f;>060be1a
Add missing version for animal-sniffer-maven-plugin
https://github.com/apache/commons-codec/commit/0fd7b59fb1dbd67260429e1d75789fca92ab8a6f;>0fd7b59
Remove variable assignment just before returning it

[jira] [Commented] (MRESOLVER-511) Update testcontainers to 1.19.7



[ 
https://issues.apache.org/jira/browse/MRESOLVER-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827454#comment-17827454
 ] 

ASF GitHub Bot commented on MRESOLVER-511:
--

cstamas merged PR #439:
URL: https://github.com/apache/maven-resolver/pull/439




> Update testcontainers to 1.19.7
> ---
>
> Key: MRESOLVER-511
> URL: https://issues.apache.org/jira/browse/MRESOLVER-511
> Project: Maven Resolver
>  Issue Type: Dependency upgrade
>Reporter: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-9
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [PR] [MRESOLVER-511][MRESOLVER-501][MRESOLVER-509][MRESOLVER-508] Dep updates [maven-resolver]



cstamas merged PR #439:
URL: https://github.com/apache/maven-resolver/pull/439


-- 
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] (MRESOLVER-511) Update testcontainers to 1.19.7



[ 
https://issues.apache.org/jira/browse/MRESOLVER-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827452#comment-17827452
 ] 

ASF GitHub Bot commented on MRESOLVER-511:
--

cstamas opened a new pull request, #439:
URL: https://github.com/apache/maven-resolver/pull/439

   Changes:
   * junit 5.10.2
   * mockito 5.11.0
   * redisson 3.27.2
   * testcontainers 1.19.7
   
   ---
   
   https://issues.apache.org/jira/browse/MRESOLVER-511 
   https://issues.apache.org/jira/browse/MRESOLVER-510 
   https://issues.apache.org/jira/browse/MRESOLVER-509 
   https://issues.apache.org/jira/browse/MRESOLVER-508




> Update testcontainers to 1.19.7
> ---
>
> Key: MRESOLVER-511
> URL: https://issues.apache.org/jira/browse/MRESOLVER-511
> Project: Maven Resolver
>  Issue Type: Dependency upgrade
>Reporter: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-9
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[PR] [MRESOLVER-511][MRESOLVER-501][MRESOLVER-509][MRESOLVER-508] Dep updates [maven-resolver]



cstamas opened a new pull request, #439:
URL: https://github.com/apache/maven-resolver/pull/439

   Changes:
   * junit 5.10.2
   * mockito 5.11.0
   * redisson 3.27.2
   * testcontainers 1.19.7
   
   ---
   
   https://issues.apache.org/jira/browse/MRESOLVER-511 
   https://issues.apache.org/jira/browse/MRESOLVER-510 
   https://issues.apache.org/jira/browse/MRESOLVER-509 
   https://issues.apache.org/jira/browse/MRESOLVER-508


-- 
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] (MRESOLVER-510) Update to Redisson 3.27.2



[ 
https://issues.apache.org/jira/browse/MRESOLVER-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827449#comment-17827449
 ] 

Tamas Cservenak commented on MRESOLVER-510:
---

Also testcontainers-redis to 2.2.0

> Update to Redisson 3.27.2
> -
>
> Key: MRESOLVER-510
> URL: https://issues.apache.org/jira/browse/MRESOLVER-510
> Project: Maven Resolver
>  Issue Type: Dependency upgrade
>Reporter: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-9
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (MRESOLVER-510) Update to Redisson 3.27.2

Tamas Cservenak created MRESOLVER-510:
-

 Summary: Update to Redisson 3.27.2
 Key: MRESOLVER-510
 URL: https://issues.apache.org/jira/browse/MRESOLVER-510
 Project: Maven Resolver
  Issue Type: Dependency upgrade
Reporter: Tamas Cservenak
 Fix For: 2.0.0, 2.0.0-alpha-9






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (MRESOLVER-511) Update testcontainers to 1.19.7

Tamas Cservenak created MRESOLVER-511:
-

 Summary: Update testcontainers to 1.19.7
 Key: MRESOLVER-511
 URL: https://issues.apache.org/jira/browse/MRESOLVER-511
 Project: Maven Resolver
  Issue Type: Dependency upgrade
Reporter: Tamas Cservenak
 Fix For: 2.0.0, 2.0.0-alpha-9






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (MRESOLVER-508) Update to Junit 5.10.2

Tamas Cservenak created MRESOLVER-508:
-

 Summary: Update to Junit 5.10.2
 Key: MRESOLVER-508
 URL: https://issues.apache.org/jira/browse/MRESOLVER-508
 Project: Maven Resolver
  Issue Type: Dependency upgrade
Reporter: Tamas Cservenak
 Fix For: 2.0.0, 2.0.0-alpha-9






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (MRESOLVER-509) Update to mockito 5.11.0

Tamas Cservenak created MRESOLVER-509:
-

 Summary: Update to mockito 5.11.0
 Key: MRESOLVER-509
 URL: https://issues.apache.org/jira/browse/MRESOLVER-509
 Project: Maven Resolver
  Issue Type: Dependency upgrade
Reporter: Tamas Cservenak
 Fix For: 2.0.0, 2.0.0-alpha-9






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (DOXIA-734) anchor element with "name" attribute no longer detected by XdocParser/FmlParser

2024-03-15 Thread Herve Boutemy (Jira)



[ 
https://issues.apache.org/jira/browse/DOXIA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827437#comment-17827437
 ] 

Herve Boutemy commented on DOXIA-734:
-

{quote}Herve Boutemy, I do remember that you told me that there is no effort in 
keeping FML, and there is basically none. Now you think it is time to remove? 
If so, we should deprecate in this milestone and drop in the next one.{quote}

Yes, I confirm what I told: I'm just ok to drop if some people want to drop 
something, I don't want to fight on every tiny front, and FML looks like a tiny 
front
on FML, I'll follow what you decide: very small impact on users, very small 
impact on maintenance, just choose

The xdoc discussion is much more important: I need more time to review your 
discussions, because now I understand it is more about xdoc 2 vs xdoc 3, not 
really about fully dropping xdoc
I don't have serious time to read for now, but I hope I'll do this WE
xdoc is a serious front where we need to measure the impacts of any choice we 
do: yes, maybe we'll have hard choice to do

> anchor element with "name" attribute no longer detected by 
> XdocParser/FmlParser
> ---
>
> Key: DOXIA-734
> URL: https://issues.apache.org/jira/browse/DOXIA-734
> Project: Maven Doxia
>  Issue Type: Bug
>  Components: Module - Apt, Module - Fml
>Reporter: Konrad Windszus
>Priority: Major
>
> Currently only {{}} is translated into a proper 
> {{Sink.anchor(...)}} call.
> The obsolete {{}} is currently not calling an according 
> {{Sink.anchor(...)}} method but may be still used in ancient markups which 
> derive from the XHtml5BaseParser.
> For example XDoc and FML both stem from the time where 
> https://www.w3.org/TR/xhtml1/ was the most recent XHTML spec and therefore 
> support {{a name}} (according to 
> https://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-xdoc/xsddoc/http___maven.apache.org_XDOC_2.0/element/a.html
>  and 
> https://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-fml/xsddoc/http___maven.apache.org_FML_1.0.1/element/a.html)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (MGPG-111) Clean up dependency declarations



 [ 
https://issues.apache.org/jira/browse/MGPG-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamas Cservenak updated MGPG-111:
-
Summary: Clean up dependency declarations  (was: Clean upn dependency 
declarations)

> Clean up dependency declarations
> 
>
> Key: MGPG-111
> URL: https://issues.apache.org/jira/browse/MGPG-111
> Project: Maven GPG Plugin
>  Issue Type: Dependency upgrade
>Reporter: Elliotte Rusty Harold
>Assignee: Tamas Cservenak
>Priority: Minor
> Fix For: 3.2.1
>
>
> [WARNING] Used undeclared dependencies found:
> [WARNING]org.apache.maven:maven-artifact:jar:3.9.6:provided
> [WARNING]org.apache.maven:maven-settings:jar:3.9.6:provided
> [WARNING]com.kohlschutter.junixsocket:junixsocket-common:jar:2.9.0:compile
> [WARNING]org.apache.maven.resolver:maven-resolver-impl:jar:1.9.18:provided
> [WARNING] Unused declared dependencies found:
> [WARNING]com.kohlschutter.junixsocket:junixsocket-core:pom:2.9.0:compile
> [WARNING]org.codehaus.plexus:plexus-cipher:jar:2.0:compile



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Closed] (MGPG-112) Upgrading from 3.1.0 to 3.2.0 with no other changes causes "gpg: signing failed: No pinentry"



 [ 
https://issues.apache.org/jira/browse/MGPG-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamas Cservenak closed MGPG-112.


> Upgrading from 3.1.0 to 3.2.0 with no other changes causes "gpg: signing 
> failed: No pinentry"
> -
>
> Key: MGPG-112
> URL: https://issues.apache.org/jira/browse/MGPG-112
> Project: Maven GPG Plugin
>  Issue Type: Bug
>Affects Versions: 3.2.0
> Environment: GitHub actions, using ubuntu-22.04 (Ubuntu 22.04 LTS) 
> image. Full details can be found in the linked logs in Description.
>Reporter: Harald Kuhr
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.2.1
>
>
> After upgrading to Maven GPG plugin from 3.1.0 to 3.20, the Deploy step of my 
> projects CI failed with the message "gpg: signing failed: No pinentry". 
>  
> After upgrade to 3.2.0, the deploy step fails the build, while the relevant 
> part of the log says:
>  
> {noformat}
> [INFO] --- maven-gpg-plugin:3.2.0:sign (sign-artifacts) @ twelvemonkeys ---
> [INFO] Signer 'gpg' is signing 2 files
> gpg: signing failed: No pinentry
> gpg: signing failed: No pinentry
> ...
> Error:  Failed to execute goal 
> org.apache.maven.plugins:maven-gpg-plugin:3.2.0:sign (sign-artifacts) on 
> project twelvemonkeys: Exit code: 2 -> [Help 1]{noformat}
>  
> After reverting to the working 3.1.0, build and deploy succeeds, the relevant 
> part of the log says:
>  
> {noformat}
> [INFO] --- maven-gpg-plugin:3.1.0:sign (sign-artifacts) @ twelvemonkeys ---
> [INFO] Signing 2 files with default secret key.
> ...
> [INFO] BUILD SUCCESS
> {noformat}
>  
> Is this an expected/intended behavior with the 3.2.0 release, and does the 
> plugin need additional/different configuration? If this is the case, can you 
> provide suggestions or workarounds to get the signing working again?
> As this is a minor version change, I suspect this is a bug/regression and not 
> intended. I don't find anything in the release notes suggesting a 
> configuration change is required.
> Plugin configuration (private key and passphrase is passed using GHA secrets):
>  
> {noformat}
> 
> org.apache.maven.plugins
> maven-gpg-plugin
> 3.1.0  
> 
> 
> 
> --pinentry-mode
> loopback
> 
> 
> 
> 
> sign-artifacts
> verify
> 
> sign
> 
> 
> 
> {noformat}
>  
> Full POM for the build: 
> [https://github.com/haraldk/TwelveMonkeys/blob/878d6217d8538f05205c092c7230c8db6727d058/pom.xml]
>  
> Full logs from broken build (Dependabot PR bump 3.1.0 to 3.2.0):
> [https://github.com/haraldk/TwelveMonkeys/actions/runs/8230467333/job/22504202895]
>  
> Full logs from working build (reverted to 3.1.0): 
> [https://github.com/haraldk/TwelveMonkeys/actions/runs/8230663423/job/22504567422]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Closed] (MGPG-111) Clean upn dependency declarations



 [ 
https://issues.apache.org/jira/browse/MGPG-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamas Cservenak closed MGPG-111.


> Clean upn dependency declarations
> -
>
> Key: MGPG-111
> URL: https://issues.apache.org/jira/browse/MGPG-111
> Project: Maven GPG Plugin
>  Issue Type: Dependency upgrade
>Reporter: Elliotte Rusty Harold
>Assignee: Tamas Cservenak
>Priority: Minor
> Fix For: 3.2.1
>
>
> [WARNING] Used undeclared dependencies found:
> [WARNING]org.apache.maven:maven-artifact:jar:3.9.6:provided
> [WARNING]org.apache.maven:maven-settings:jar:3.9.6:provided
> [WARNING]com.kohlschutter.junixsocket:junixsocket-common:jar:2.9.0:compile
> [WARNING]org.apache.maven.resolver:maven-resolver-impl:jar:1.9.18:provided
> [WARNING] Unused declared dependencies found:
> [WARNING]com.kohlschutter.junixsocket:junixsocket-core:pom:2.9.0:compile
> [WARNING]org.codehaus.plexus:plexus-cipher:jar:2.0:compile



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (MASSEMBLY-1021) Nullpointer in assembly:single when upgrading to 3.7.0

2024-03-15 Thread Thomas Mortagne (Jira)



[ 
https://issues.apache.org/jira/browse/MASSEMBLY-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827432#comment-17827432
 ] 

Thomas Mortagne edited comment on MASSEMBLY-1021 at 3/15/24 8:10 AM:
-

{quote}
I tried to reproduce with your project, my steps

* remove gradle extension from .mvn
* set version to 16.1.0 in xwiki-rendering-standalone
* execute mvn package -f xwiki-rendering-standalone

but I can build project without issues
{quote}

I did pretty much the same as you (except that you don't mention setting 
maven-assembly-plugin to 3.7.0), and I get the same error:

   * go to xwiki-rendering-standalone
* set parent  to 16.1.0
* add in  a  to set maven-assembly-plugin to 3.7.0
{noformat}

  

  org.apache.maven.plugins
  maven-assembly-plugin
  
  3.7.0

  

{noformat}
* execute mvn clean package -e

here is my mvn -v in case is has an impact:

{noformat}
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /media/DATA/utils/mvn
Java version: 17.0.10, vendor: Private Build, runtime: 
/usr/lib/jvm/java-17-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "6.5.0-25-generic", arch: "amd64", family: "unix"
{noformat}

bq. Should be fixed by MASSEMBLY-1022 

Thanks for the fix.


was (Author: tmortagne):
{quote}
I tried to reproduce with your project, my steps

* remove gradle extension from .mvn
* set version to 16.1.0 in xwiki-rendering-standalone
* execute mvn package -f xwiki-rendering-standalone

but I can build project without issues
{quote}

I did pretty much the same as you (except that you don't mention setting 
maven-assembly-plugin to 3.7.0), and I get the same error:

   * go to xwiki-rendering-standalone
* set parent  to 16.1.0
* add in  a  to set maven-assembly-plugin to 3.7.0
{noformat}

  

  org.apache.maven.plugins
  maven-assembly-plugin
  
  3.7.0

  

{noformat}
* execute mvn clean package -e

bq. Should be fixed by MASSEMBLY-1022 

Thanks for the fix.

> Nullpointer in assembly:single when upgrading to 3.7.0
> --
>
> Key: MASSEMBLY-1021
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-1021
> Project: Maven Assembly Plugin
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Thomas Mortagne
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.7.1
>
>
> I just upgraded to 3.7.0 (from 3.6.0) and end up with something very similar 
> to MASSEMBLY-659.
> The assembly file is 
> https://github.com/xwiki/xwiki-rendering/blob/master/xwiki-rendering-standalone/src/assemble/zip-with-dependencies.xml
>  and when building I get:
> {noformat}
> 21:59:56,428 [INFO] [jenkins-event-spy] Generated 
> /root/workspace/XWiki_xwiki-rendering_master@tmp/withMaven50b764e5/maven-spy-20240313-215448-41518180198517015559409.log
> 21:59:56,429 [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-assembly-plugin:3.7.0:single (default) on 
> project xwiki-rendering-standalone: Execution default of goal 
> org.apache.maven.plugins:maven-assembly-plugin:3.7.0:single failed: Cannot 
> invoke "java.io.File.isFile()" because "this.inputFile" is null -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-assembly-plugin:3.7.0:single (default) on 
> project xwiki-rendering-standalone: Execution default of goal 
> org.apache.maven.plugins:maven-assembly-plugin:3.7.0:single failed: Cannot 
> invoke "java.io.File.isFile()" because "this.inputFile" is null
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:159)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:105)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:73)
> at 
>

[jira] [Commented] (MASSEMBLY-1021) Nullpointer in assembly:single when upgrading to 3.7.0

2024-03-15 Thread Thomas Mortagne (Jira)



[ 
https://issues.apache.org/jira/browse/MASSEMBLY-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827432#comment-17827432
 ] 

Thomas Mortagne commented on MASSEMBLY-1021:


{quote}
I tried to reproduce with your project, my steps

* remove gradle extension from .mvn
* set version to 16.1.0 in xwiki-rendering-standalone
* execute mvn package -f xwiki-rendering-standalone

but I can build project without issues
{quote}

I did pretty much the same as you (except that you don't mention setting 
maven-assembly-plugin to 3.7.0), and I get the same error:

   * go to xwiki-rendering-standalone
* set parent  to 16.1.0
* add in  a  to set maven-assembly-plugin to 3.7.0
{noformat}

  

  org.apache.maven.plugins
  maven-assembly-plugin
  
  3.7.0

  

{noformat}
* execute mvn clean package -e

bq. Should be fixed by MASSEMBLY-1022 

Thanks for the fix.

> Nullpointer in assembly:single when upgrading to 3.7.0
> --
>
> Key: MASSEMBLY-1021
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-1021
> Project: Maven Assembly Plugin
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Thomas Mortagne
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.7.1
>
>
> I just upgraded to 3.7.0 (from 3.6.0) and end up with something very similar 
> to MASSEMBLY-659.
> The assembly file is 
> https://github.com/xwiki/xwiki-rendering/blob/master/xwiki-rendering-standalone/src/assemble/zip-with-dependencies.xml
>  and when building I get:
> {noformat}
> 21:59:56,428 [INFO] [jenkins-event-spy] Generated 
> /root/workspace/XWiki_xwiki-rendering_master@tmp/withMaven50b764e5/maven-spy-20240313-215448-41518180198517015559409.log
> 21:59:56,429 [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-assembly-plugin:3.7.0:single (default) on 
> project xwiki-rendering-standalone: Execution default of goal 
> org.apache.maven.plugins:maven-assembly-plugin:3.7.0:single failed: Cannot 
> invoke "java.io.File.isFile()" because "this.inputFile" is null -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-assembly-plugin:3.7.0:single (default) on 
> project xwiki-rendering-standalone: Execution default of goal 
> org.apache.maven.plugins:maven-assembly-plugin:3.7.0:single failed: Cannot 
> invoke "java.io.File.isFile()" because "this.inputFile" is null
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:159)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:105)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:73)
> at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
>  (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:568)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
> (Launcher.java:283)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
> (Launcher.java:226)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
> (Launcher.java:407)
> at

[jira] [Commented] (MGPG-90) Signing fails with 3.0.1: "no pinentry"