[jira] [Commented] (MSHARED-604) Honor none default localRepository
[
https://issues.apache.org/jira/browse/MSHARED-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276586#comment-16276586
]
Andreas Sewe commented on MSHARED-604:
--
FYI, I also came across this issue today.
My use case: Resolve an artifact to some analysis and delete it afterwards. If
it its downloaded to the default local repository ({{~/.m2/repository}}) it
cannot be safely deleted, as others may use it. Hence, I want my own, temporary
local repository.
> Honor none default localRepository
> ---
>
> Key: MSHARED-604
> URL: https://issues.apache.org/jira/browse/MSHARED-604
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.9.0
>Reporter: Dan Tran
>
> ArtifactResolver ignores localRepository settings in the request
> ProjectBuildingRequest. It always use the default location when maven starts
> Use case: I have a use case to resolve a maven artifact with local repo is
> under maven 'target' directory
> maven-compat does work my case.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (DOXIA-566) Update dependences and default plugins to latest version
[ https://issues.apache.org/jira/browse/DOXIA-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276654#comment-16276654 ] ASF GitHub Bot commented on DOXIA-566: -- slachiewicz commented on issue #6: [DOXIA-566] Upgrade dependences and plugin versions URL: https://github.com/apache/maven-doxia/pull/6#issuecomment-348937905 ok, plugin updates removed This is an automated message from the Apache Git Service. To respond to the message, please log on 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 > Update dependences and default plugins to latest version > > > Key: DOXIA-566 > URL: https://issues.apache.org/jira/browse/DOXIA-566 > Project: Maven Doxia > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MRESOLVER-38) StackOverflowError in DefaultDependencyNode.accept
Andreas Sewe created MRESOLVER-38:
-
Summary: StackOverflowError in DefaultDependencyNode.accept
Key: MRESOLVER-38
URL: https://issues.apache.org/jira/browse/MRESOLVER-38
Project: Maven Resolver
Issue Type: Bug
Components: resolver
Affects Versions: Maven Artifact Resolver 1.1.0
Reporter: Andreas Sewe
Attachments: maven-resolver-demos.patch
I noticed a {StackOverflowErrror}} when trying to build the classpath for
{{org.webjars.npm:n3-charts:2.0.17}} using Maven Resolver 1.1.0.
I’ve managed to produce a minimal example based on the {{maven-resolver-demos}}
from the {{master-with-demos}} branch. To reproduce, just apply the attached
patch to the branch (tried this with commit
[{{84a32a86}}|https://github.com/apache/maven-resolver/commit/84a32a866ff27d4df75124074fd925588f4a574d])
and run the {{GetDependencyTree}} example:
{noformat}
GetDependencyTree
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
Resolving artifact org.webjars.npm:n3-charts:pom:2.0.17
Resolved artifact org.webjars.npm:n3-charts:pom:2.0.17 from central
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
…
Resolving metadata org.webjars.npm:uglifycss/maven-metadata.xml from central
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
Resolved metadata org.webjars.npm:uglifycss/maven-metadata.xml from central
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
Resolving artifact org.webjars.npm:uglifycss:pom:0.0.18
Resolved artifact org.webjars.npm:uglifycss:pom:0.0.18 from central
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
Exception in thread "main" java.lang.StackOverflowError
at
org.eclipse.aether.util.graph.visitor.PathRecordingDependencyVisitor.visitEnter(PathRecordingDependencyVisitor.java:102)
at
org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:341)
at
org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
at
org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
at
org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
{noformat}
(Note: The patch changes the {{plexus-utils}} version as well, as I was getting
a {{ClassNotFoundException}} for
{{org.codehaus.plexus.util.xml.pull.EntityReplacementMap}} otherwise.)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MRESOLVER-38) StackOverflowError in DefaultDependencyNode.accept
[
https://issues.apache.org/jira/browse/MRESOLVER-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276712#comment-16276712
]
Andreas Sewe commented on MRESOLVER-38:
---
Other artifacts from {{org.webjars}} exhibiting the same symptoms:
{{org.webjars.npm:systemjs-builder:0.15.7}}, {{org.webjars.npm:radium:0.16.5}},
{{org.webjars.npm:babel-register:6.5.1}}.
Maybe this helps in analyzing the situation, although I am afraid all four
artifacts presumably have a rather large dependency tree, based on the number
of POMs downloaded during the {{collectDependencies}} call.
> StackOverflowError in DefaultDependencyNode.accept
> --
>
> Key: MRESOLVER-38
> URL: https://issues.apache.org/jira/browse/MRESOLVER-38
> Project: Maven Resolver
> Issue Type: Bug
> Components: resolver
>Affects Versions: Maven Artifact Resolver 1.1.0
>Reporter: Andreas Sewe
> Attachments: maven-resolver-demos.patch
>
>
> I noticed a {StackOverflowErrror}} when trying to build the classpath for
> {{org.webjars.npm:n3-charts:2.0.17}} using Maven Resolver 1.1.0.
> I’ve managed to produce a minimal example based on the
> {{maven-resolver-demos}} from the {{master-with-demos}} branch. To reproduce,
> just apply the attached patch to the branch (tried this with commit
> [{{84a32a86}}|https://github.com/apache/maven-resolver/commit/84a32a866ff27d4df75124074fd925588f4a574d])
> and run the {{GetDependencyTree}} example:
> {noformat}
>
> GetDependencyTree
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
> details.
> Resolving artifact org.webjars.npm:n3-charts:pom:2.0.17
> Resolved artifact org.webjars.npm:n3-charts:pom:2.0.17 from central
> (https://repo.maven.apache.org/maven2/, default, releases+snapshots)
> …
> Resolving metadata org.webjars.npm:uglifycss/maven-metadata.xml from central
> (https://repo.maven.apache.org/maven2/, default, releases+snapshots)
> Resolved metadata org.webjars.npm:uglifycss/maven-metadata.xml from central
> (https://repo.maven.apache.org/maven2/, default, releases+snapshots)
> Resolving artifact org.webjars.npm:uglifycss:pom:0.0.18
> Resolved artifact org.webjars.npm:uglifycss:pom:0.0.18 from central
> (https://repo.maven.apache.org/maven2/, default, releases+snapshots)
> Exception in thread "main" java.lang.StackOverflowError
> at
> org.eclipse.aether.util.graph.visitor.PathRecordingDependencyVisitor.visitEnter(PathRecordingDependencyVisitor.java:102)
> at
> org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:341)
> at
> org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
> at
> org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
> at
> org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
> {noformat}
> (Note: The patch changes the {{plexus-utils}} version as well, as I was
> getting a {{ClassNotFoundException}} for
> {{org.codehaus.plexus.util.xml.pull.EntityReplacementMap}} otherwise.)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (MRESOLVER-38) SOE/OOME in DefaultDependencyNode.accept
[
https://issues.apache.org/jira/browse/MRESOLVER-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Sewe updated MRESOLVER-38:
--
Summary: SOE/OOME in DefaultDependencyNode.accept (was: StackOverflowError
in DefaultDependencyNode.accept)
> SOE/OOME in DefaultDependencyNode.accept
>
>
> Key: MRESOLVER-38
> URL: https://issues.apache.org/jira/browse/MRESOLVER-38
> Project: Maven Resolver
> Issue Type: Bug
> Components: resolver
>Affects Versions: Maven Artifact Resolver 1.1.0
>Reporter: Andreas Sewe
> Attachments: maven-resolver-demos.patch
>
>
> I noticed a {StackOverflowErrror}} when trying to build the classpath for
> {{org.webjars.npm:n3-charts:2.0.17}} using Maven Resolver 1.1.0.
> I’ve managed to produce a minimal example based on the
> {{maven-resolver-demos}} from the {{master-with-demos}} branch. To reproduce,
> just apply the attached patch to the branch (tried this with commit
> [{{84a32a86}}|https://github.com/apache/maven-resolver/commit/84a32a866ff27d4df75124074fd925588f4a574d])
> and run the {{GetDependencyTree}} example:
> {noformat}
>
> GetDependencyTree
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
> details.
> Resolving artifact org.webjars.npm:n3-charts:pom:2.0.17
> Resolved artifact org.webjars.npm:n3-charts:pom:2.0.17 from central
> (https://repo.maven.apache.org/maven2/, default, releases+snapshots)
> …
> Resolving metadata org.webjars.npm:uglifycss/maven-metadata.xml from central
> (https://repo.maven.apache.org/maven2/, default, releases+snapshots)
> Resolved metadata org.webjars.npm:uglifycss/maven-metadata.xml from central
> (https://repo.maven.apache.org/maven2/, default, releases+snapshots)
> Resolving artifact org.webjars.npm:uglifycss:pom:0.0.18
> Resolved artifact org.webjars.npm:uglifycss:pom:0.0.18 from central
> (https://repo.maven.apache.org/maven2/, default, releases+snapshots)
> Exception in thread "main" java.lang.StackOverflowError
> at
> org.eclipse.aether.util.graph.visitor.PathRecordingDependencyVisitor.visitEnter(PathRecordingDependencyVisitor.java:102)
> at
> org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:341)
> at
> org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
> at
> org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
> at
> org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
> {noformat}
> (Note: The patch changes the {{plexus-utils}} version as well, as I was
> getting a {{ClassNotFoundException}} for
> {{org.codehaus.plexus.util.xml.pull.EntityReplacementMap}} otherwise.)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (MRESOLVER-38) SOE/OOME in DefaultDependencyNode.accept
[
https://issues.apache.org/jira/browse/MRESOLVER-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Sewe updated MRESOLVER-38:
--
Description:
I noticed a {{StackOverflowErrror}} when trying to build the classpath for
{{org.webjars.npm:n3-charts:2.0.17}} using Maven Resolver 1.1.0.
I’ve managed to produce a minimal example based on the {{maven-resolver-demos}}
from the {{master-with-demos}} branch. To reproduce, just apply the attached
patch to the branch (tried this with commit
[{{84a32a86}}|https://github.com/apache/maven-resolver/commit/84a32a866ff27d4df75124074fd925588f4a574d])
and run the {{GetDependencyTree}} example:
{noformat}
GetDependencyTree
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
Resolving artifact org.webjars.npm:n3-charts:pom:2.0.17
Resolved artifact org.webjars.npm:n3-charts:pom:2.0.17 from central
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
…
Resolving metadata org.webjars.npm:uglifycss/maven-metadata.xml from central
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
Resolved metadata org.webjars.npm:uglifycss/maven-metadata.xml from central
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
Resolving artifact org.webjars.npm:uglifycss:pom:0.0.18
Resolved artifact org.webjars.npm:uglifycss:pom:0.0.18 from central
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
Exception in thread "main" java.lang.StackOverflowError
at
org.eclipse.aether.util.graph.visitor.PathRecordingDependencyVisitor.visitEnter(PathRecordingDependencyVisitor.java:102)
at
org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:341)
at
org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
at
org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
at
org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
{noformat}
(Note: The patch changes the {{plexus-utils}} version as well, as I was getting
a {{ClassNotFoundException}} for
{{org.codehaus.plexus.util.xml.pull.EntityReplacementMap}} otherwise.)
was:
I noticed a {StackOverflowErrror}} when trying to build the classpath for
{{org.webjars.npm:n3-charts:2.0.17}} using Maven Resolver 1.1.0.
I’ve managed to produce a minimal example based on the {{maven-resolver-demos}}
from the {{master-with-demos}} branch. To reproduce, just apply the attached
patch to the branch (tried this with commit
[{{84a32a86}}|https://github.com/apache/maven-resolver/commit/84a32a866ff27d4df75124074fd925588f4a574d])
and run the {{GetDependencyTree}} example:
{noformat}
GetDependencyTree
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
Resolving artifact org.webjars.npm:n3-charts:pom:2.0.17
Resolved artifact org.webjars.npm:n3-charts:pom:2.0.17 from central
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
…
Resolving metadata org.webjars.npm:uglifycss/maven-metadata.xml from central
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
Resolved metadata org.webjars.npm:uglifycss/maven-metadata.xml from central
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
Resolving artifact org.webjars.npm:uglifycss:pom:0.0.18
Resolved artifact org.webjars.npm:uglifycss:pom:0.0.18 from central
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
Exception in thread "main" java.lang.StackOverflowError
at
org.eclipse.aether.util.graph.visitor.PathRecordingDependencyVisitor.visitEnter(PathRecordingDependencyVisitor.java:102)
at
org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:341)
at
org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
at
org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
at
org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
{noformat}
(Note: The patch changes the {{plexus-utils}} version as well, as I was getting
a {{ClassNotFoundException}} for
{{org.codehaus.plexus.util.xml.pull.EntityReplacementMap}} otherwise.)
> SOE/OOME in DefaultDependencyNode.accept
>
>
> Key: MRESOLVER-38
> URL: https://issues.apache.org/jira/browse/MRESOLVER-38
> Project: Maven Resolver
> Issue T
[jira] [Updated] (MRESOLVER-38) SOE/OOME in DefaultDependencyNode.accept
[
https://issues.apache.org/jira/browse/MRESOLVER-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Sewe updated MRESOLVER-38:
--
Priority: Critical (was: Major)
> SOE/OOME in DefaultDependencyNode.accept
>
>
> Key: MRESOLVER-38
> URL: https://issues.apache.org/jira/browse/MRESOLVER-38
> Project: Maven Resolver
> Issue Type: Bug
> Components: resolver
>Affects Versions: Maven Artifact Resolver 1.1.0
>Reporter: Andreas Sewe
>Priority: Critical
> Attachments: maven-resolver-demos.patch
>
>
> I noticed a {{StackOverflowErrror}} when trying to build the classpath for
> {{org.webjars.npm:n3-charts:2.0.17}} using Maven Resolver 1.1.0.
> I’ve managed to produce a minimal example based on the
> {{maven-resolver-demos}} from the {{master-with-demos}} branch. To reproduce,
> just apply the attached patch to the branch (tried this with commit
> [{{84a32a86}}|https://github.com/apache/maven-resolver/commit/84a32a866ff27d4df75124074fd925588f4a574d])
> and run the {{GetDependencyTree}} example:
> {noformat}
>
> GetDependencyTree
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
> details.
> Resolving artifact org.webjars.npm:n3-charts:pom:2.0.17
> Resolved artifact org.webjars.npm:n3-charts:pom:2.0.17 from central
> (https://repo.maven.apache.org/maven2/, default, releases+snapshots)
> …
> Resolving metadata org.webjars.npm:uglifycss/maven-metadata.xml from central
> (https://repo.maven.apache.org/maven2/, default, releases+snapshots)
> Resolved metadata org.webjars.npm:uglifycss/maven-metadata.xml from central
> (https://repo.maven.apache.org/maven2/, default, releases+snapshots)
> Resolving artifact org.webjars.npm:uglifycss:pom:0.0.18
> Resolved artifact org.webjars.npm:uglifycss:pom:0.0.18 from central
> (https://repo.maven.apache.org/maven2/, default, releases+snapshots)
> Exception in thread "main" java.lang.StackOverflowError
> at
> org.eclipse.aether.util.graph.visitor.PathRecordingDependencyVisitor.visitEnter(PathRecordingDependencyVisitor.java:102)
> at
> org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:341)
> at
> org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
> at
> org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
> at
> org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
> {noformat}
> (Note: The patch changes the {{plexus-utils}} version as well, as I was
> getting a {{ClassNotFoundException}} for
> {{org.codehaus.plexus.util.xml.pull.EntityReplacementMap}} otherwise.)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MRESOLVER-38) SOE/OOME in DefaultDependencyNode.accept
[
https://issues.apache.org/jira/browse/MRESOLVER-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276894#comment-16276894
]
Andreas Sewe commented on MRESOLVER-38:
---
What’s *worse*: There exist artifacts for which doing a simple
{{collectDependencies}} does not result in {{StackOverflowError}} but in an
{{OutOfMemoryError}}; thus, this can kill not just one but all threads.
Using {{GetDependencyTree}} on
{{org.webjars.npm:babel-plugin-transform-class-constructor-call:6.3.13}} again
produces a huge stack of {{DefaultDependencyNode.accept}}, but with the
additional problem that the constructs a huge (160k entries!) {{paths}}
{{List>}} (counted using Eclipse MAT on a heap dump.)
{noformat}
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
at
org.eclipse.aether.util.graph.visitor.PathRecordingDependencyVisitor.visitEnter(PathRecordingDependencyVisitor.java:108)
at
org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:341)
at
org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
at
org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
at
org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
at
org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
…
{noformat}
> SOE/OOME in DefaultDependencyNode.accept
>
>
> Key: MRESOLVER-38
> URL: https://issues.apache.org/jira/browse/MRESOLVER-38
> Project: Maven Resolver
> Issue Type: Bug
> Components: resolver
>Affects Versions: Maven Artifact Resolver 1.1.0
>Reporter: Andreas Sewe
>Priority: Critical
> Attachments: maven-resolver-demos.patch
>
>
> I noticed a {{StackOverflowErrror}} when trying to build the classpath for
> {{org.webjars.npm:n3-charts:2.0.17}} using Maven Resolver 1.1.0.
> I’ve managed to produce a minimal example based on the
> {{maven-resolver-demos}} from the {{master-with-demos}} branch. To reproduce,
> just apply the attached patch to the branch (tried this with commit
> [{{84a32a86}}|https://github.com/apache/maven-resolver/commit/84a32a866ff27d4df75124074fd925588f4a574d])
> and run the {{GetDependencyTree}} example:
> {noformat}
>
> GetDependencyTree
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
> details.
> Resolving artifact org.webjars.npm:n3-charts:pom:2.0.17
> Resolved artifact org.webjars.npm:n3-charts:pom:2.0.17 from central
> (https://repo.maven.apache.org/maven2/, default, releases+snapshots)
> …
> Resolving metadata org.webjars.npm:uglifycss/maven-metadata.xml from central
> (https://repo.maven.apache.org/maven2/, default, releases+snapshots)
> Resolved metadata org.webjars.npm:uglifycss/maven-metadata.xml from central
> (https://repo.maven.apache.org/maven2/, default, releases+snapshots)
> Resolving artifact org.webjars.npm:uglifycss:pom:0.0.18
> Resolved artifact org.webjars.npm:uglifycss:pom:0.0.18 from central
> (https://repo.maven.apache.org/maven2/, default, releases+snapshots)
> Exception in thread "main" java.lang.StackOverflowError
> at
> org.eclipse.aether.util.graph.visitor.PathRecordingDependencyVisitor.visitEnter(PathRecordingDependencyVisitor.java:102)
> at
> org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:341)
> at
> org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
> at
> org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
> at
> org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
> {noformat}
> (Note: The patch changes the {{plexus-utils}} version as well, as I was
> getting a {{ClassNotFoundException}} for
> {{org.codehaus.plexus.util.xml.pull.EntityReplacementMap}} otherwise.)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MPLUGIN-247) Allow getting mojo/parameter description/since/deprecated from annotations
[
https://issues.apache.org/jira/browse/MPLUGIN-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277145#comment-16277145
]
Andrei Pozolotin commented on MPLUGIN-247:
--
There are multitude of ways, from writing custom extractor with scala-meta to
adding annotation/description.
The annotation/description approach seems minimal-effort to me. Plus, it will
work in "any other java" context.
Am I wrong? What would you recommend? Will you accept a patch for
annotation/description support in java-extractor?
> Allow getting mojo/parameter description/since/deprecated from annotations
> --
>
> Key: MPLUGIN-247
> URL: https://issues.apache.org/jira/browse/MPLUGIN-247
> Project: Maven Plugin Tools
> Issue Type: Improvement
> Components: maven-plugin-annotations
>Affects Versions: 3.2
>Reporter: Alex Hvostov
>Priority: Minor
> Attachments: extra-annotations.diff
>
>
> The attached patch adds annotations {{@Description}}, {{@Since}}, and
> {{@DeprecatedBecause}}, which can be used instead of Javadoc comments for
> describing a Mojo and its parameters.
> My use-case for this feature is writing Maven plugins in Scala. This language
> supports annotations, but a Java parser will obviously not be able to extract
> description/since/deprecated information from Scala source files. (There is
> another {{plugin-tools}} implementation specifically for writing Scala
> plugins, which has its own set of annotations, but it is buggy, incomplete,
> and not under active development.)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MNG-5842) java.lang.NoClassDefFoundError: org/slf4j/helpers/MessageFormatter with jetty plugin
[
https://issues.apache.org/jira/browse/MNG-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277257#comment-16277257
]
ASF GitHub Bot commented on MNG-5842:
-
GitHub user dconneely opened a pull request:
https://github.com/apache/maven/pull/140
Add org.slf4j.event to exported packages
maven-core should export org.slf4j.event.* from slf4j-api 1.7.15 or later.
For example, this package is where the `Level` class is located.
Otherwise, issues similar to MNG-5842 and MNG-5845 will arise with plugins
that use Slf4j themselves (or more likely plugins that use libraries that use
Slf4j).
Discovered while working on in-house Maven plugin that failed with
`java.lang.NoClassDefFoundError: org/slf4j/event/Level`.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dconneely/maven patch-1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven/pull/140.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #140
commit 34bb114b7dbd80380e3d10c6dcffcf08e1ffaf50
Author: David Conneely
Date: 2017-12-04T18:42:18Z
Add org.slf4j.event to exported packages
maven-core should export org.slf4j.event.* from slf4j-api 1.7.15 or later.
For example, this package is where the `Level` class is located.
> java.lang.NoClassDefFoundError: org/slf4j/helpers/MessageFormatter with jetty
> plugin
>
>
> Key: MNG-5842
> URL: https://issues.apache.org/jira/browse/MNG-5842
> Project: Maven
> Issue Type: Bug
> Components: Class Loading
>Affects Versions: 3.3.1, 3.3.3
>Reporter: Jean-Christophe Gay
>Assignee: Arnaud HERITIER
>
> When Maven is used with a different SLF4J implementation than slf4j-simple
> (in my case logback to have colored logs), running jetty-maven-plugin fails.
> {code}
> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
> 2015-04-22T13:57:37+02:00)
> Maven home: /usr/local/Cellar/maven/3.3.3/libexec
> Java version: 1.8.0_40, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home/jre
> Default locale: fr_FR, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.3", arch: "x86_64", family: "mac"
> {code}
> {code}
> [WARNING] FAILED org.mortbay.jetty.plugin.JettyServer@66c4005:
> java.lang.NoClassDefFoundError: org/slf4j/helpers/MessageFormatter
> java.lang.ClassNotFoundException: org.slf4j.helpers.MessageFormatter
> at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> ~[plexus-classworlds-2.5.2.jar:na]
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
> ~[plexus-classworlds-2.5.2.jar:na]
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
> ~[plexus-classworlds-2.5.2.jar:na]
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
> ~[plexus-classworlds-2.5.2.jar:na]
> ... 21 common frames omitted
> Wrapped by: java.lang.NoClassDefFoundError: org/slf4j/helpers/MessageFormatter
> at
> org.eclipse.jetty.util.log.JettyAwareLogger.log(JettyAwareLogger.java:619)
> ~[jetty-util-7.6.16.v20140903.jar:7.6.16.v20140903]
> at
> org.eclipse.jetty.util.log.JettyAwareLogger.info(JettyAwareLogger.java:314)
> ~[jetty-util-7.6.16.v20140903.jar:7.6.16.v20140903]
> at org.eclipse.jetty.util.log.Slf4jLog.info(Slf4jLog.java:74)
> ~[jetty-util-7.6.16.v20140903.jar:7.6.16.v20140903]
> at org.eclipse.jetty.server.Server.doStart(Server.java:271)
> ~[jetty-server-7.6.16.v20140903.jar:7.6.16.v20140903]
> at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:65)
> ~[jetty-maven-plugin-7.6.16.v20140903.jar:7.6.16.v20140903]
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> ~[jetty-util-7.6.16.v20140903.jar:7.6.16.v20140903]
> at
> org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:520)
> [jetty-maven-plugin-7.6.16.v20140903.jar:7.6.16.v20140903]
> at
> org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:365)
> [jetty-maven-plugin-7.6.16.v20140903.jar:7.6.16.v20140903]
> at org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:521)
> [jetty-maven-plugin-7.6.16.v20140903.jar:7.6.16.v20140903]
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> [maven-core-3.3.1.jar:3.3.1]
> at
> org.apache.maven.lifecycle.internal.
[jira] [Commented] (MNG-6298) 3.5.2: ClassNotFoundException: javax.annotation.security.RolesAllowed
[
https://issues.apache.org/jira/browse/MNG-6298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277334#comment-16277334
]
ASF GitHub Bot commented on MNG-6298:
-
GitHub user bengtsod opened a pull request:
https://github.com/apache/maven-integration-testing/pull/26
[MNG-6298] 3.5.2: ClassNotFoundException
Test for https://github.com/apache/maven/pull/139
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bengtsod/maven-integration-testing master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven-integration-testing/pull/26.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #26
commit 01be66f166b2fe61cf9935cc1e5b1fc65e5e729e
Author: Bengt Söderberg
Date: 2017-12-04T18:49:17Z
[MNG-6298] 3.5.2: ClassNotFoundException
Test for https://github.com/apache/maven/pull/139
> 3.5.2: ClassNotFoundException: javax.annotation.security.RolesAllowed
> -
>
> Key: MNG-6298
> URL: https://issues.apache.org/jira/browse/MNG-6298
> Project: Maven
> Issue Type: Bug
> Components: Class Loading
>Affects Versions: 3.5.2
> Environment: Mac OS X 10.12.6, Ubuntu 15.10 64 bit, and Windows is
> presumed.
>Reporter: Ryan Heaton
>Priority: Critical
> Fix For: 3.5.3-candidate
>
>
> Maven 3.5.2 appears to have introduces some kind of a class loading error,
> manifesting itself like this:
> {noformat}
> Caused by: java.lang.ClassNotFoundException:
> javax.annotation.security.RolesAllowed
> at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
> ... 184 more
> {noformat}
> Previous versions of Maven do not manifest this.
> To reproduce this:
> * Clone [the Enunciate sample
> project|https://github.com/stoicflame/enunciate-sample].
> * Build the project (mvn clean package) with 3.5.0 and note the success.
> * Build the project with 3.5.2 and note the failure.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1430) Parallel parameterized JUnit test hangs on Linux
[ https://issues.apache.org/jira/browse/SUREFIRE-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277460#comment-16277460 ] Christian Beikov commented on SUREFIRE-1430: As I wrote before, the problem is specifically on Linux. It works without problems on Windows. > Parallel parameterized JUnit test hangs on Linux > > > Key: SUREFIRE-1430 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1430 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.18, 2.18.1, 2.19, 2.19.1, 2.20, 2.20.1 > Environment: Linux/Ubuntu >Reporter: Christian Beikov >Assignee: Tibor Digana > Fix For: 2.21.1 > > > This is a follow up of SUREFIRE-1264. The test case is here: > https://github.com/beikov/surefire-test > The problem is, that a simple parameterized JUnit test hangs when running in > parallel mode on Linux. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
