[GitHub] [maven-surefire] kriegaex commented on pull request #343: SUREFIRE-1881 Adds additional debug log and fork connection timeout
kriegaex commented on pull request #343: URL: https://github.com/apache/maven-surefire/pull/343#issuecomment-857386035 Ping! _(Sorry to get on your nerves, but I really would like to have this in the next milestone.)_ -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-dependency-plugin] dependabot[bot] opened a new pull request #137: Bump jettyVersion from 9.2.28.v20190418 to 11.0.4
dependabot[bot] opened a new pull request #137: URL: https://github.com/apache/maven-dependency-plugin/pull/137 Bumps `jettyVersion` from 9.2.28.v20190418 to 11.0.4. Updates `jetty-server` from 9.2.28.v20190418 to 11.0.4 Release notes Sourced from https://github.com/eclipse/jetty.project/releases;>jetty-server's releases. 11.0.3 Changelog https://github-redirect.dependabot.com/eclipse/jetty.project/issues/3764;>#3764 DeprecationWarning Decorator https://github-redirect.dependabot.com/eclipse/jetty.project/issues/5684;>#5684 Review disabled tests https://github-redirect.dependabot.com/eclipse/jetty.project/issues/5798;>#5798 jetty-runner startup error with jetty-10 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/5817;>#5817 Provide more filtering for CustomRequestLog https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6049;>#6049 Default provider [files] section always executed https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6084;>#6084 GzipHandler: NPE in setDeflaterPoolCapacity and setInflaterPoolCapacity https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6098;>#6098 jetty-cdi is missing from jetty-bom https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6099;>#6099 Cipher preference may break SNI if certificates have different key types https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6105;>#6105 HttpConnection.getBytesIn() incorrect for requests with chunked content https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6106;>#6106 WebSocket/CDI integration is broken in Jetty 10 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6125;>#6125 Do not allow override of jakarta.* container classes by webapps per Servlet 5.0 Section 15.2.1 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6132;>#6132 Ambiguous segment in URI in DELETE /a/projects/foo/branches/refs%2Fheads%2Ftest request after upgrade from 10.0.0 to 10.0.2 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6153;>#6153 jetty-maven-plugin does not correctly pass JVM arguments for external deployMode https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6159;>#6159 Jetty with Conscrypt unable to handle any HTTPS requests when connected by IP rather than hostname. https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6166;>#6166 WebSocket MessageInputStream.read() spends a lot of time in ByteBuffer.compact() https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6205;>#6205 OpenIdAuthenticator may use incorrect redirect https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6208;>#6208 HTTP/2 max local stream count exceeded https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6224;>#6224 make jetty-jspc-maven-plugin @threadsafe https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6227;>#6227 Better resolve race between AsyncListener.onTimeout and AsyncContext.dispatch https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6238;>#6238 jetty-keystore Invalid manifest header Bundle-SymbolicName: https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6250;>#6250 Lazily allocate HTTP2Stream data queue https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6251;>#6251 Use CyclicTimeout for HTTP2Streams https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6254;>#6254 Total timeout not enforced for queued requests https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6263;>#6263 Review URI encoding in ConcatServlet WelcomeFilter https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6277;>#6277 Better handle exceptions thrown from session destroy listener https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6280;>#6280 Copy ServletHolder class/instance properly during startWebapp https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6287;>#6287 Class loading broken for WebSocketClient used inside webapp 11.0.2 Changelog :warning: Important Security related Changes https://github.com/eclipse/jetty.project/security/advisories/GHSA-26vr-8j45-3r4w;>CVE-2021-28165 - https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6072;>#6072 - jetty server high CPU when client send data length 17408 https://github.com/eclipse/jetty.project/security/advisories/GHSA-v7ff-8wcx-gmc5;>CVE-2021-28164 - https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6101;>#6101 - Normalize ambiguous URIs https://github.com/eclipse/jetty.project/security/advisories/GHSA-j6qj-j888-vvgq;>CVE-2021-28163 - https://github-redirect.dependabot.com/eclipse/jetty.project/issues/6102;>#6102 - Exclude webapps directory from
[jira] [Commented] (MSHARED-788) Add functionality to collect raw dependencies in Maven 3+
[
https://issues.apache.org/jira/browse/MSHARED-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17359734#comment-17359734
]
Gabriel Belingueres commented on MSHARED-788:
-
Another issue: I can't run ITs using maven 3.1.1 or maven 3.0.5:
{color:#00}mvn -Dinvoker.mavenHome=/path/to/apache-maven-3.1.1 clean
verify{color}
it fails since it mixes up the local repos.
> Add functionality to collect raw dependencies in Maven 3+
> -
>
> Key: MSHARED-788
> URL: https://issues.apache.org/jira/browse/MSHARED-788
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-dependency-tree
>Affects Versions: maven-dependency-tree-3.0, maven-dependency-tree-3.0.1
>Reporter: Gabriel Belingueres
>Assignee: Robert Scholte
>Priority: Major
> Fix For: maven-dependency-tree-3.1.0
>
> Time Spent: 10m
>
> Add funcionality allowing to collect raw project dependencies. Add a layer to
> hide against Maven 3's sonatype aether and Maven 3.1+ eclipse aether.
> This could be used to implement dependencyConvergence and
> requireUpperBoundDeps enforcer rules.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MINDEXER-127) Maven repository indexing error: java.nio.channels.OverlappingFileLockException
[ https://issues.apache.org/jira/browse/MINDEXER-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17359647#comment-17359647 ] Hudson commented on MINDEXER-127: - Build succeeded in Jenkins: Maven » Maven TLP » maven-indexer » master #50 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-indexer/job/master/50/ > Maven repository indexing error: > java.nio.channels.OverlappingFileLockException > --- > > Key: MINDEXER-127 > URL: https://issues.apache.org/jira/browse/MINDEXER-127 > Project: Maven Indexer > Issue Type: Bug >Affects Versions: 6.0.0 >Reporter: Victor Rubezhny >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 6.0.1 > > > The `openAndWarmup()` method is invoked twice from `purge()` method of > `org.apache.maven.index.context.DefaultIndexingContext` which results into > `OverlappingFileLockException` during the index re-indexing, because the > `openAndWarmup()` method call creates a `FileLock` for an index and the > second call tries to create and add the second `FileLock` for the same index > which is erroneous: > ``` > java.nio.channels.OverlappingFileLockException > at java.base/sun.nio.ch.FileLockTable.checkList(FileLockTable.java:229) > at java.base/sun.nio.ch.FileLockTable.add(FileLockTable.java:123) > at java.base/sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:1154) > at java.base/java.nio.channels.FileChannel.tryLock(FileChannel.java:1165) > at > org.apache.maven.index.context.DefaultIndexingContext.unlockForcibly(DefaultIndexingContext.java:927) > at > org.apache.maven.index.context.DefaultIndexingContext.prepareIndex(DefaultIndexingContext.java:244) > at > org.apache.maven.index.context.DefaultIndexingContext.purge(DefaultIndexingContext.java:612) > at > org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.purgeCurrentIndex(NexusIndexManager.java:529) > at > org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.reindexWorkspace(NexusIndexManager.java:561) > at > org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.updateIndex(NexusIndexManager.java:1072) > at > org.eclipse.m2e.core.internal.index.nexus.NexusIndex.updateIndex(NexusIndex.java:147) > at > org.eclipse.m2e.core.ui.internal.preferences.MavenSettingsPreferencePage$2.runInWorkspace(MavenSettingsPreferencePage.java:263) > at > org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:42) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > ``` > The referencing issue is reported at: > https://github.com/eclipse-m2e/m2e-core/issues/169 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MINDEXER-127) Maven repository indexing error: java.nio.channels.OverlappingFileLockException
[ https://issues.apache.org/jira/browse/MINDEXER-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MINDEXER-127: - Assignee: Sylwester Lachiewicz > Maven repository indexing error: > java.nio.channels.OverlappingFileLockException > --- > > Key: MINDEXER-127 > URL: https://issues.apache.org/jira/browse/MINDEXER-127 > Project: Maven Indexer > Issue Type: Bug >Affects Versions: 6.0.0 >Reporter: Victor Rubezhny >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 6.0.1 > > > The `openAndWarmup()` method is invoked twice from `purge()` method of > `org.apache.maven.index.context.DefaultIndexingContext` which results into > `OverlappingFileLockException` during the index re-indexing, because the > `openAndWarmup()` method call creates a `FileLock` for an index and the > second call tries to create and add the second `FileLock` for the same index > which is erroneous: > ``` > java.nio.channels.OverlappingFileLockException > at java.base/sun.nio.ch.FileLockTable.checkList(FileLockTable.java:229) > at java.base/sun.nio.ch.FileLockTable.add(FileLockTable.java:123) > at java.base/sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:1154) > at java.base/java.nio.channels.FileChannel.tryLock(FileChannel.java:1165) > at > org.apache.maven.index.context.DefaultIndexingContext.unlockForcibly(DefaultIndexingContext.java:927) > at > org.apache.maven.index.context.DefaultIndexingContext.prepareIndex(DefaultIndexingContext.java:244) > at > org.apache.maven.index.context.DefaultIndexingContext.purge(DefaultIndexingContext.java:612) > at > org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.purgeCurrentIndex(NexusIndexManager.java:529) > at > org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.reindexWorkspace(NexusIndexManager.java:561) > at > org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.updateIndex(NexusIndexManager.java:1072) > at > org.eclipse.m2e.core.internal.index.nexus.NexusIndex.updateIndex(NexusIndex.java:147) > at > org.eclipse.m2e.core.ui.internal.preferences.MavenSettingsPreferencePage$2.runInWorkspace(MavenSettingsPreferencePage.java:263) > at > org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:42) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > ``` > The referencing issue is reported at: > https://github.com/eclipse-m2e/m2e-core/issues/169 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINDEXER-127) Maven repository indexing error: java.nio.channels.OverlappingFileLockException
[ https://issues.apache.org/jira/browse/MINDEXER-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MINDEXER-127: -- Fix Version/s: 6.0.1 > Maven repository indexing error: > java.nio.channels.OverlappingFileLockException > --- > > Key: MINDEXER-127 > URL: https://issues.apache.org/jira/browse/MINDEXER-127 > Project: Maven Indexer > Issue Type: Bug >Affects Versions: 6.0.0 >Reporter: Victor Rubezhny >Priority: Major > Fix For: 6.0.1 > > > The `openAndWarmup()` method is invoked twice from `purge()` method of > `org.apache.maven.index.context.DefaultIndexingContext` which results into > `OverlappingFileLockException` during the index re-indexing, because the > `openAndWarmup()` method call creates a `FileLock` for an index and the > second call tries to create and add the second `FileLock` for the same index > which is erroneous: > ``` > java.nio.channels.OverlappingFileLockException > at java.base/sun.nio.ch.FileLockTable.checkList(FileLockTable.java:229) > at java.base/sun.nio.ch.FileLockTable.add(FileLockTable.java:123) > at java.base/sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:1154) > at java.base/java.nio.channels.FileChannel.tryLock(FileChannel.java:1165) > at > org.apache.maven.index.context.DefaultIndexingContext.unlockForcibly(DefaultIndexingContext.java:927) > at > org.apache.maven.index.context.DefaultIndexingContext.prepareIndex(DefaultIndexingContext.java:244) > at > org.apache.maven.index.context.DefaultIndexingContext.purge(DefaultIndexingContext.java:612) > at > org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.purgeCurrentIndex(NexusIndexManager.java:529) > at > org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.reindexWorkspace(NexusIndexManager.java:561) > at > org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.updateIndex(NexusIndexManager.java:1072) > at > org.eclipse.m2e.core.internal.index.nexus.NexusIndex.updateIndex(NexusIndex.java:147) > at > org.eclipse.m2e.core.ui.internal.preferences.MavenSettingsPreferencePage$2.runInWorkspace(MavenSettingsPreferencePage.java:263) > at > org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:42) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > ``` > The referencing issue is reported at: > https://github.com/eclipse-m2e/m2e-core/issues/169 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-indexer] slachiewicz merged pull request #105: MINDEXER-127: Maven repository indexing error: java.nio.channels.Over…
slachiewicz merged pull request #105: URL: https://github.com/apache/maven-indexer/pull/105 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MPOM-247) Make minimum enforced Maven version configurable via property
[ https://issues.apache.org/jira/browse/MPOM-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MPOM-247: -- Fix Version/s: ASF-24 > Make minimum enforced Maven version configurable via property > - > > Key: MPOM-247 > URL: https://issues.apache.org/jira/browse/MPOM-247 > Project: Maven POMs > Issue Type: Improvement > Components: asf >Affects Versions: ASF-23 >Reporter: Konrad Windszus >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: ASF-24 > > > Although enforcing at least 3.0.5 in > [https://github.com/apache/maven-apache-parent/blob/cea7e87e91dd143c9ecc13517361e7d9b5c18c81/pom.xml#L358] > is reasonable very often ASF projects require a newer version. To reduce pom > overhead it would be nice if the minimum enforced Maven version could be > overwritten via a property. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPOM-247) Make minimum enforced Maven version configurable via property
[ https://issues.apache.org/jira/browse/MPOM-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17359583#comment-17359583 ] Hudson commented on MPOM-247: - Build succeeded in Jenkins: Maven » Maven TLP » maven-apache-parent » master #45 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-apache-parent/job/master/45/ > Make minimum enforced Maven version configurable via property > - > > Key: MPOM-247 > URL: https://issues.apache.org/jira/browse/MPOM-247 > Project: Maven POMs > Issue Type: Improvement > Components: asf >Affects Versions: ASF-23 >Reporter: Konrad Windszus >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: ASF-24 > > > Although enforcing at least 3.0.5 in > [https://github.com/apache/maven-apache-parent/blob/cea7e87e91dd143c9ecc13517361e7d9b5c18c81/pom.xml#L358] > is reasonable very often ASF projects require a newer version. To reduce pom > overhead it would be nice if the minimum enforced Maven version could be > overwritten via a property. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MPOM-247) Make minimum enforced Maven version configurable via property
[ https://issues.apache.org/jira/browse/MPOM-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MPOM-247: - Assignee: Sylwester Lachiewicz > Make minimum enforced Maven version configurable via property > - > > Key: MPOM-247 > URL: https://issues.apache.org/jira/browse/MPOM-247 > Project: Maven POMs > Issue Type: Improvement > Components: asf >Affects Versions: ASF-23 >Reporter: Konrad Windszus >Assignee: Sylwester Lachiewicz >Priority: Major > > Although enforcing at least 3.0.5 in > [https://github.com/apache/maven-apache-parent/blob/cea7e87e91dd143c9ecc13517361e7d9b5c18c81/pom.xml#L358] > is reasonable very often ASF projects require a newer version. To reduce pom > overhead it would be nice if the minimum enforced Maven version could be > overwritten via a property. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-apache-parent] asfgit closed pull request #29: [MPOM-247] make minimum Maven version configurable via property
asfgit closed pull request #29: URL: https://github.com/apache/maven-apache-parent/pull/29 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Comment Edited] (MNG-7161) Error thrown during uninstalling of JAnsi
[
https://issues.apache.org/jira/browse/MNG-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17359413#comment-17359413
]
Victor edited comment on MNG-7161 at 6/8/21, 3:35 PM:
--
This is also affecting the maven release plugin, as a workaround we have
reverted to the latest 3.8 version:
- [https://github.com/elastic/apm-pipeline-library/pull/1145]
What command did I ran to see the above error?
{code:java}
./mvnw release:prepare release:perform -V --batch-mode
'-Darguments=-DskipTests=true --batch-mode'
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
Apache Maven 4.0.0-alpha-1-SNAPSHOT (12f3e7e878e3a22a696f7ba9b5c615d520807afb)
Maven home:
/var/lib/jenkins/.m2/wrapper/dists/apache-maven-4.0.0-alpha-1-SNAPSHOT-bin/s0m0e7mg6h9hr8umuisf0sdq9/apache-maven
Java version: 1.8.0_292, vendor: Private Build, runtime:
/usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en, platform encoding: UTF8
OS name: "linux", version: "5.4.0-1044-gcp", arch: "amd64", family: "unix"
{code}
was (Author: victormartinezrubio):
This is also affecting the maven release plugin, as a workaround we have
reverted to the latest 3.8 version:
- [https://github.com/elastic/apm-pipeline-library/pull/1145]
What command did I ran to see the above error?
{code:java}
[2021-06-07T14:59:19.751Z] + ./mvnw release:prepare release:perform -V
--batch-mode '-Darguments=-DskipTests=true --batch-mode'
[2021-06-07T14:59:19.751Z] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
[2021-06-07T14:59:20.011Z] Apache Maven 4.0.0-alpha-1-SNAPSHOT
(12f3e7e878e3a22a696f7ba9b5c615d520807afb)
[2021-06-07T14:59:20.011Z] Maven home:
/var/lib/jenkins/.m2/wrapper/dists/apache-maven-4.0.0-alpha-1-SNAPSHOT-bin/s0m0e7mg6h9hr8umuisf0sdq9/apache-maven
[2021-06-07T14:59:20.011Z] Java version: 1.8.0_292, vendor: Private Build,
runtime: /usr/lib/jvm/java-8-openjdk-amd64/jre
[2021-06-07T14:59:20.011Z] Default locale: en, platform encoding: UTF8
[2021-06-07T14:59:20.011Z] OS name: "linux", version: "5.4.0-1044-gcp", arch:
"amd64", family: "unix"
{code}
> Error thrown during uninstalling of JAnsi
> -
>
> Key: MNG-7161
> URL: https://issues.apache.org/jira/browse/MNG-7161
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.x-candidate, 4.0.0, 4.0.0-alpha-1
>Reporter: Guy Brand
>Priority: Critical
>
> Our integration tests stopped working after we started to test with a Maven
> {{4.0.0-alpha-1}} nightly which included this commit:
> [https://github.com/apache/maven/commit/195fb626a9a4e5a0774f779b6d8da1cb9ef38468#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8R310-R317]
> In this commit the {{maven-shared-utils}} and the {{jansi}} dependencies are
> being upgraded. When we then run our integration tests we get the following
> null pointer exception:
> {code:java}
> java.lang.NullPointerException
> at org.fusesource.jansi.AnsiPrintStream.uninstall(AnsiPrintStream.java:79)
> at org.fusesource.jansi.AnsiConsole.systemUninstall(AnsiConsole.java:524)
> at
> org.apache.maven.shared.utils.logging.MessageUtils.doSystemUninstall(MessageUtils.java:101)
> at
> org.apache.maven.shared.utils.logging.MessageUtils.systemUninstall(MessageUtils.java:80)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:203)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
> {code}
>
> We debugged this and [these
> changes|https://github.com/fusesource/jansi/commit/63bd892b2bdfc253ec119a57bdd42df5e80fd859#diff-d59db8655d9ae2d11948e2b411c34fc9e8513f29065d82c978d7128dafbe3bafR414-R420]
> in JAnsi introduced in the above upgraded version, is the source of the
> exception. The NPE is caused because the {{out}} reference is {{null}} at the
> time it wants to uninstall the {{AnsiOutputStream}}. This reference is nulled
> because we use the Plexus interactivity library which [disposes the
> {{DefaultOutputHandler}}|https://github.com/codehaus-plexus/plexus-interactivity/blob/master/plexus-interactivity-api/src/main/java/org/codehaus/plexus/components/interactivity/DefaultOutputHandler.java#L51-L54]
> on the tear down of Plexus, in
[jira] [Commented] (MDEP-751) Publish `maven-dependency-plugin:3.2.0` artifacts to the Central Maven repository
[
https://issues.apache.org/jira/browse/MDEP-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17359418#comment-17359418
]
Sergey Vyacheslavovich Brunov commented on MDEP-751:
Hi, [~mthmulders]!
Thank you very much for the prompt reply!
Best regards,
Sergey Vyacheslavovich Brunov.
> Publish `maven-dependency-plugin:3.2.0` artifacts to the Central Maven
> repository
> -
>
> Key: MDEP-751
> URL: https://issues.apache.org/jira/browse/MDEP-751
> Project: Maven Dependency Plugin
> Issue Type: Improvement
>Reporter: Sergey Vyacheslavovich Brunov
>Priority: Minor
>
> To whom it may concern,
> It seems the {{maven-dependency-plugin:3.2.0}} artifacts have not been
> published to the Central Maven repository.
> But, at the same time, the development of a new version seems to have
> started: note {{3.2.1-SNAPSHOT}} in the
> [pom.xml|https://github.com/apache/maven-dependency-plugin/blob/1ac708df7ccf0245f8c91a6f57db9468670f11a1/pom.xml].
> Therefore, could you please publish `maven-dependency-plugin:3.2.0` artifacts
> to the Central Maven repository?
> Best regards,
> Sergey Vyacheslavovich Brunov.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7161) Error thrown during uninstalling of JAnsi
[
https://issues.apache.org/jira/browse/MNG-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17359413#comment-17359413
]
Victor commented on MNG-7161:
-
This is also affecting the maven release plugin, as a workaround we have
reverted to the latest 3.8 version:
- [https://github.com/elastic/apm-pipeline-library/pull/1145]
What command did I ran to see the above error?
{code:java}
[2021-06-07T14:59:19.751Z] + ./mvnw release:prepare release:perform -V
--batch-mode '-Darguments=-DskipTests=true --batch-mode'
[2021-06-07T14:59:19.751Z] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
[2021-06-07T14:59:20.011Z] Apache Maven 4.0.0-alpha-1-SNAPSHOT
(12f3e7e878e3a22a696f7ba9b5c615d520807afb)
[2021-06-07T14:59:20.011Z] Maven home:
/var/lib/jenkins/.m2/wrapper/dists/apache-maven-4.0.0-alpha-1-SNAPSHOT-bin/s0m0e7mg6h9hr8umuisf0sdq9/apache-maven
[2021-06-07T14:59:20.011Z] Java version: 1.8.0_292, vendor: Private Build,
runtime: /usr/lib/jvm/java-8-openjdk-amd64/jre
[2021-06-07T14:59:20.011Z] Default locale: en, platform encoding: UTF8
[2021-06-07T14:59:20.011Z] OS name: "linux", version: "5.4.0-1044-gcp", arch:
"amd64", family: "unix"
{code}
> Error thrown during uninstalling of JAnsi
> -
>
> Key: MNG-7161
> URL: https://issues.apache.org/jira/browse/MNG-7161
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.x-candidate, 4.0.0, 4.0.0-alpha-1
>Reporter: Guy Brand
>Priority: Critical
>
> Our integration tests stopped working after we started to test with a Maven
> {{4.0.0-alpha-1}} nightly which included this commit:
> [https://github.com/apache/maven/commit/195fb626a9a4e5a0774f779b6d8da1cb9ef38468#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8R310-R317]
> In this commit the {{maven-shared-utils}} and the {{jansi}} dependencies are
> being upgraded. When we then run our integration tests we get the following
> null pointer exception:
> {code:java}
> java.lang.NullPointerException
> at org.fusesource.jansi.AnsiPrintStream.uninstall(AnsiPrintStream.java:79)
> at org.fusesource.jansi.AnsiConsole.systemUninstall(AnsiConsole.java:524)
> at
> org.apache.maven.shared.utils.logging.MessageUtils.doSystemUninstall(MessageUtils.java:101)
> at
> org.apache.maven.shared.utils.logging.MessageUtils.systemUninstall(MessageUtils.java:80)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:203)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
> {code}
>
> We debugged this and [these
> changes|https://github.com/fusesource/jansi/commit/63bd892b2bdfc253ec119a57bdd42df5e80fd859#diff-d59db8655d9ae2d11948e2b411c34fc9e8513f29065d82c978d7128dafbe3bafR414-R420]
> in JAnsi introduced in the above upgraded version, is the source of the
> exception. The NPE is caused because the {{out}} reference is {{null}} at the
> time it wants to uninstall the {{AnsiOutputStream}}. This reference is nulled
> because we use the Plexus interactivity library which [disposes the
> {{DefaultOutputHandler}}|https://github.com/codehaus-plexus/plexus-interactivity/blob/master/plexus-interactivity-api/src/main/java/org/codehaus/plexus/components/interactivity/DefaultOutputHandler.java#L51-L54]
> on the tear down of Plexus, in which the {{System.out}} reference will be
> closed which is in fact the {{out}} reference of the {{AnsiConsole}} JAnsi
> will be [initialized
> before|https://github.com/apache/maven/blob/3e917677e484067b853eaa4a6de44ebcf5a988de/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L200]
> the Plexus container). This happens
> [here|https://github.com/apache/maven/blob/3e917677e484067b853eaa4a6de44ebcf5a988de/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L202],
> so before JAnsi will be uninstalled in
> [here|https://github.com/apache/maven/blob/3e917677e484067b853eaa4a6de44ebcf5a988de/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L203].
> There are two options to solve this:
> 1. Report this to JAnsi such that they catch this valid use case and do not
> throw as this worked without any exceptions in older versions.
> 2. Fix the
[jira] [Closed] (MDEP-751) Publish `maven-dependency-plugin:3.2.0` artifacts to the Central Maven repository
[
https://issues.apache.org/jira/browse/MDEP-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maarten Mulders closed MDEP-751.
Resolution: Invalid
The tag is already published in SCM, but [the vote on whether or not to
release|https://www.apache.org/foundation/voting.html#ReleaseVotes] the package
to the public has not yet ended.
Once the vote has ended with a positive result, the release process continues,
and eventually, the package will be deployed to Maven Central. That is also
when the release is formally announced on the [Maven Announcements
List|http://maven.apache.org/mailing-lists.html].
To summarise, you're a bit early. Give it a few more days time.
> Publish `maven-dependency-plugin:3.2.0` artifacts to the Central Maven
> repository
> -
>
> Key: MDEP-751
> URL: https://issues.apache.org/jira/browse/MDEP-751
> Project: Maven Dependency Plugin
> Issue Type: Improvement
>Reporter: Sergey Vyacheslavovich Brunov
>Priority: Critical
>
> To whom it may concern,
> It seems the {{maven-dependency-plugin:3.2.0}} artifacts have not been
> published to the Central Maven repository.
> But, at the same time, the development of a new version seems to have
> started: note {{3.2.1-SNAPSHOT}} in the
> [pom.xml|https://github.com/apache/maven-dependency-plugin/blob/1ac708df7ccf0245f8c91a6f57db9468670f11a1/pom.xml].
> Therefore, could you please publish `maven-dependency-plugin:3.2.0` artifacts
> to the Central Maven repository?
> Best regards,
> Sergey Vyacheslavovich Brunov.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MDEP-751) Publish `maven-dependency-plugin:3.2.0` artifacts to the Central Maven repository
[
https://issues.apache.org/jira/browse/MDEP-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maarten Mulders updated MDEP-751:
-
Priority: Minor (was: Critical)
> Publish `maven-dependency-plugin:3.2.0` artifacts to the Central Maven
> repository
> -
>
> Key: MDEP-751
> URL: https://issues.apache.org/jira/browse/MDEP-751
> Project: Maven Dependency Plugin
> Issue Type: Improvement
>Reporter: Sergey Vyacheslavovich Brunov
>Priority: Minor
>
> To whom it may concern,
> It seems the {{maven-dependency-plugin:3.2.0}} artifacts have not been
> published to the Central Maven repository.
> But, at the same time, the development of a new version seems to have
> started: note {{3.2.1-SNAPSHOT}} in the
> [pom.xml|https://github.com/apache/maven-dependency-plugin/blob/1ac708df7ccf0245f8c91a6f57db9468670f11a1/pom.xml].
> Therefore, could you please publish `maven-dependency-plugin:3.2.0` artifacts
> to the Central Maven repository?
> Best regards,
> Sergey Vyacheslavovich Brunov.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MDEP-751) Publish `maven-dependency-plugin:3.2.0` artifacts to the Central Maven repository
Sergey Brunov created MDEP-751:
--
Summary: Publish `maven-dependency-plugin:3.2.0` artifacts to the
Central Maven repository
Key: MDEP-751
URL: https://issues.apache.org/jira/browse/MDEP-751
Project: Maven Dependency Plugin
Issue Type: Improvement
Reporter: Sergey Brunov
To whom it may concern,
It seems the {{maven-dependency-plugin:3.2.0}} artifacts have not been
published to the Central Maven repository.
But, at the same time, the development of a new version seems to have started:
note {{3.2.1-SNAPSHOT}} in the
[pom.xml|https://github.com/apache/maven-dependency-plugin/blob/1ac708df7ccf0245f8c91a6f57db9468670f11a1/pom.xml].
Therefore, could you please publish `maven-dependency-plugin:3.2.0` artifacts
to the Central Maven repository?
Best regards,
Sergey Vyacheslavovich Brunov.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7162) Problem compiling, packaging or installing multimodule project with CI friendly
[
https://issues.apache.org/jira/browse/MNG-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17359323#comment-17359323
]
Michael Osipov commented on MNG-7162:
-
See [here|https://letmegooglethat.com/?q=git+bisect+how].
> Problem compiling, packaging or installing multimodule project with CI
> friendly
> ---
>
> Key: MNG-7162
> URL: https://issues.apache.org/jira/browse/MNG-7162
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.6.3
> Environment: Windows 10
>Reporter: Mario Jauvin
>Priority: Major
>
> When using CI friendly properties if I try to compile (or even run the verify
> phase) on a module that does not include all of the dependencies in the
> reactor build, maven will attempt to resolve the dependencies not in the
> reactor build and fail. If you take the branch ci-friendlies from project
> https://github.com/marioja/maven-ear-example and cd into module-ear and type
> {noformat}mvn verify{noformat} you will get this error:
> {noformat}
> [ERROR] Failed to execute goal on project module-ear: Could not resolve
> dependencies for project com.example:module-ear:ear:2.0.0-SNAPSHOT: Failed to
> collect dependencies at com.example:module-web:war:2.0.0-SNAPSHOT: Failed to
> read artifact descriptor for com.example:module-web:war:2.0.0-SNAPSHOT: Could
> not transfer artifact
> com.example:application:pom:${revision}.${sha1}${changelist} from/to
> company.repository-
> (http://company-maven.company.net:8081/repository/maven-public): Failed to
> transfer
> http://company-maven.company.net:8081/repository/maven-public/com/example/application/${revision}.${sha1}${changelist}/application-${revision}.${sha1}${changelist}.pom.
> Error code 400, Invalid repository path -> [Help 1]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-compiler-plugin] jkuhn1 commented on a change in pull request #40: [MCOMPILER-272] - When annotationProcessorPaths has multiple entries,…
jkuhn1 commented on a change in pull request #40:
URL:
https://github.com/apache/maven-compiler-plugin/pull/40#discussion_r647402009
##
File path:
src/main/java/org/apache/maven/plugin/compiler/AbstractCompilerMojo.java
##
@@ -1660,26 +1660,27 @@ private boolean hasNewFile( File classPathEntry, Date
buildStartTime )
requiredArtifacts.add( artifact );
}
-ArtifactResolutionRequest request = new ArtifactResolutionRequest()
-.setArtifact( requiredArtifacts.iterator().next() )
-.setResolveRoot( true )
-.setResolveTransitively( true )
-.setArtifactDependencies( requiredArtifacts )
-.setLocalRepository( session.getLocalRepository() )
-.setRemoteRepositories(
project.getRemoteArtifactRepositories() );
+Set elements = new HashSet<>( );
-ArtifactResolutionResult resolutionResult =
repositorySystem.resolve( request );
+for ( Artifact artifact : requiredArtifacts )
+{
+ArtifactResolutionRequest request = new
ArtifactResolutionRequest()
+.setArtifact( artifact )
+.setResolveRoot( true )
+.setResolveTransitively( true )
+.setLocalRepository(
session.getLocalRepository() )
+.setRemoteRepositories(
project.getRemoteArtifactRepositories() );
-resolutionErrorHandler.throwErrors( request, resolutionResult );
+ArtifactResolutionResult resolutionResult =
repositorySystem.resolve( request );
Review comment:
Hi, it's been a while since I get into it and I managed to bypass the
issue with some configuration and dependency refactoring, so please go ahead if
you can fix it once and for all.
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-indexer] mickaelistria commented on pull request #105: MINDEXER-127: Maven repository indexing error: java.nio.channels.Over…
mickaelistria commented on pull request #105: URL: https://github.com/apache/maven-indexer/pull/105#issuecomment-856726613 @slachiewicz Is there anything missing to this PR before it can be considered for a merge? -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MPOM-243) WARNING: release:perform issues [WARNING] The requested profile "pom.xml" could not be activated because it does not exist.
[
https://issues.apache.org/jira/browse/MPOM-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17359315#comment-17359315
]
Hudson commented on MPOM-243:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven-apache-parent » master #44
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-apache-parent/job/master/44/
> WARNING: release:perform issues [WARNING] The requested profile "pom.xml"
> could not be activated because it does not exist.
> ---
>
> Key: MPOM-243
> URL: https://issues.apache.org/jira/browse/MPOM-243
> Project: Maven POMs
> Issue Type: Bug
> Components: asf
>Affects Versions: ASF-23
>Reporter: Konrad Windszus
>Priority: Minor
>
> Since version 23 the following log output is emitted with every
> release-perform:
> {code}
> [INFO] [INFO]
>
> [INFO] [INFO] BUILD SUCCESS
> [INFO] [INFO]
>
> [INFO] [INFO] Total time: 25.851 s
> [INFO] [INFO] Finished at: 2020-03-09T19:59:04+01:00
> [INFO] [INFO]
>
> [INFO] [WARNING] The requested profile "pom.xml" could not be activated
> because it does not exist.
> [INFO] phase cleanup
> [INFO] Cleaning up after release...
> [INFO]
>
> [INFO] BUILD SUCCESS
> {code}
> Although it doesn't seem to have functional impact the warning is annoying.
> Most probably this is related to the profile activation in
> https://github.com/apache/maven-apache-parent/blob/591f84284d4bce53ca2ee686c1d84b16e8029716/pom.xml#L234
> Compare also with
> https://issues.apache.org/jira/browse/MRELEASE-1038?focusedCommentId=17024760=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17024760.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (MPOM-243) WARNING: release:perform issues [WARNING] The requested profile "pom.xml" could not be activated because it does not exist.
[
https://issues.apache.org/jira/browse/MPOM-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold closed MPOM-243.
--
> WARNING: release:perform issues [WARNING] The requested profile "pom.xml"
> could not be activated because it does not exist.
> ---
>
> Key: MPOM-243
> URL: https://issues.apache.org/jira/browse/MPOM-243
> Project: Maven POMs
> Issue Type: Bug
> Components: asf
>Affects Versions: ASF-23
>Reporter: Konrad Windszus
>Priority: Minor
>
> Since version 23 the following log output is emitted with every
> release-perform:
> {code}
> [INFO] [INFO]
>
> [INFO] [INFO] BUILD SUCCESS
> [INFO] [INFO]
>
> [INFO] [INFO] Total time: 25.851 s
> [INFO] [INFO] Finished at: 2020-03-09T19:59:04+01:00
> [INFO] [INFO]
>
> [INFO] [WARNING] The requested profile "pom.xml" could not be activated
> because it does not exist.
> [INFO] phase cleanup
> [INFO] Cleaning up after release...
> [INFO]
>
> [INFO] BUILD SUCCESS
> {code}
> Although it doesn't seem to have functional impact the warning is annoying.
> Most probably this is related to the profile activation in
> https://github.com/apache/maven-apache-parent/blob/591f84284d4bce53ca2ee686c1d84b16e8029716/pom.xml#L234
> Compare also with
> https://issues.apache.org/jira/browse/MRELEASE-1038?focusedCommentId=17024760=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17024760.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (MPOM-243) WARNING: release:perform issues [WARNING] The requested profile "pom.xml" could not be activated because it does not exist.
[
https://issues.apache.org/jira/browse/MPOM-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold resolved MPOM-243.
Resolution: Fixed
> WARNING: release:perform issues [WARNING] The requested profile "pom.xml"
> could not be activated because it does not exist.
> ---
>
> Key: MPOM-243
> URL: https://issues.apache.org/jira/browse/MPOM-243
> Project: Maven POMs
> Issue Type: Bug
> Components: asf
>Affects Versions: ASF-23
>Reporter: Konrad Windszus
>Priority: Minor
>
> Since version 23 the following log output is emitted with every
> release-perform:
> {code}
> [INFO] [INFO]
>
> [INFO] [INFO] BUILD SUCCESS
> [INFO] [INFO]
>
> [INFO] [INFO] Total time: 25.851 s
> [INFO] [INFO] Finished at: 2020-03-09T19:59:04+01:00
> [INFO] [INFO]
>
> [INFO] [WARNING] The requested profile "pom.xml" could not be activated
> because it does not exist.
> [INFO] phase cleanup
> [INFO] Cleaning up after release...
> [INFO]
>
> [INFO] BUILD SUCCESS
> {code}
> Although it doesn't seem to have functional impact the warning is annoying.
> Most probably this is related to the profile activation in
> https://github.com/apache/maven-apache-parent/blob/591f84284d4bce53ca2ee686c1d84b16e8029716/pom.xml#L234
> Compare also with
> https://issues.apache.org/jira/browse/MRELEASE-1038?focusedCommentId=17024760=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17024760.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-apache-parent] elharo merged pull request #42: [MPOM-243] configure release profile with dedicated parameter
elharo merged pull request #42: URL: https://github.com/apache/maven-apache-parent/pull/42 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-apache-parent] michael-o commented on pull request #42: [MPOM-243] configure release profile with dedicated parameter
michael-o commented on pull request #42: URL: https://github.com/apache/maven-apache-parent/pull/42#issuecomment-856716828 I wonder whether this is semantically equivalent... @rfscholte -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-apache-parent] elharo merged pull request #37: Bump maven-release-plugin from 3.0.0-M1 to 3.0.0-M4
elharo merged pull request #37: URL: https://github.com/apache/maven-apache-parent/pull/37 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-apache-parent] elharo merged pull request #38: Bump maven-plugin-plugin from 3.6.0 to 3.6.1
elharo merged pull request #38: URL: https://github.com/apache/maven-apache-parent/pull/38 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-apache-parent] dependabot[bot] commented on pull request #41: Bump checksum-maven-plugin from 1.9 to 1.10
dependabot[bot] commented on pull request #41: URL: https://github.com/apache/maven-apache-parent/pull/41#issuecomment-856669662 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-apache-parent] elharo closed pull request #41: Bump checksum-maven-plugin from 1.9 to 1.10
elharo closed pull request #41: URL: https://github.com/apache/maven-apache-parent/pull/41 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-apache-parent] elharo merged pull request #43: Bump maven-gpg-plugin from 1.6 to 3.0.1
elharo merged pull request #43: URL: https://github.com/apache/maven-apache-parent/pull/43 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-apache-parent] elharo merged pull request #44: Bump maven-javadoc-plugin from 3.2.0 to 3.3.0
elharo merged pull request #44: URL: https://github.com/apache/maven-apache-parent/pull/44 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MNG-7170) Allow to associate pomFile/${basedir} with DefaultProjectBuilder.build(ModelSource, ...)
Mickael Istria created MNG-7170:
---
Summary: Allow to associate pomFile/${basedir} with
DefaultProjectBuilder.build(ModelSource, ...)
Key: MNG-7170
URL: https://issues.apache.org/jira/browse/MNG-7170
Project: Maven
Issue Type: Improvement
Components: core
Affects Versions: 3.8.1
Reporter: Mickael Istria
In LemMinX-Maven Language Server for pom.xml files, we're building models from
"working copy" (unsaved) pom files. We do so by invoking
{code}DefaultProjectBuilder.build( ModelSource modelSource,
ProjectBuildingRequest request ){code}
One pitfall is that this cascades to pomFile being null for the Model, and as a
result {code}${basedir}{code} is not resolved.
One could expect that the {code}ModelSource2.getLocationURI(){code} could be
used to derive the pomFile when possible. LemMinX-Maven happens to properly set
this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
