[jira] [Commented] (SUREFIRE-1453) Allow to specify non existant classes as "groups"
[
https://issues.apache.org/jira/browse/SUREFIRE-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296227#comment-16296227
]
ASF GitHub Bot commented on SUREFIRE-1453:
--
Github user eolivelli commented on the issue:
https://github.com/apache/maven-surefire/pull/172
You are welcome!
> Allow to specify non existant classes as "groups"
> -
>
> Key: SUREFIRE-1453
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1453
> Project: Maven Surefire
> Issue Type: Improvement
> Components: classloading, Junit 4.7+ (parallel) support, Junit 4.x
> support, Maven Failsafe Plugin, Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Enrico Olivelli
>Assignee: Tibor Digana
>Priority: Critical
> Fix For: 2.21.0.Jigsaw
>
>
> In a reactor project I would like to run only a subset of JUnit (4.12) tests
> tagged with @Category
> But the class which defines the category is not present in the dependency
> tree of every module.
> I get this error.
> I would like to simply skip these modules, maybe in conjunction with the
> failIfNoTest=false option
> {code:java}
> rg.apache.maven.surefire.util.SurefireReflectionException:
> java.lang.reflect.InvocationTargetException; nested exception is
> java.lang.reflect.InvocationTargetException: null
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Caused by: java.lang.RuntimeException: Unable to load category:
> magnews.testgroups.MinimumAcceptance
> at
> org.apache.maven.surefire.group.match.SingleGroupMatcher.loadGroupClasses(SingleGroupMatcher.java:134)
> at
> org.apache.maven.surefire.common.junit48.FilterFactory.createGroupFilter(FilterFactory.java:92)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreProvider.createJUnit48Filter(JUnitCoreProvider.java:183)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:115)
> ... 9 more
> Caused by: java.lang.ClassNotFoundException:
> magnews.testgroups.MinimumAcceptance
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.maven.surefire.group.match.SingleGroupMatcher.loadGroupClasses(SingleGroupMatcher.java:130)
> ... 12 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1453) Allow to specify non existant classes as "groups"
[
https://issues.apache.org/jira/browse/SUREFIRE-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296228#comment-16296228
]
ASF GitHub Bot commented on SUREFIRE-1453:
--
Github user eolivelli closed the pull request at:
https://github.com/apache/maven-surefire/pull/172
> Allow to specify non existant classes as "groups"
> -
>
> Key: SUREFIRE-1453
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1453
> Project: Maven Surefire
> Issue Type: Improvement
> Components: classloading, Junit 4.7+ (parallel) support, Junit 4.x
> support, Maven Failsafe Plugin, Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Enrico Olivelli
>Assignee: Tibor Digana
>Priority: Critical
> Fix For: 2.21.0.Jigsaw
>
>
> In a reactor project I would like to run only a subset of JUnit (4.12) tests
> tagged with @Category
> But the class which defines the category is not present in the dependency
> tree of every module.
> I get this error.
> I would like to simply skip these modules, maybe in conjunction with the
> failIfNoTest=false option
> {code:java}
> rg.apache.maven.surefire.util.SurefireReflectionException:
> java.lang.reflect.InvocationTargetException; nested exception is
> java.lang.reflect.InvocationTargetException: null
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Caused by: java.lang.RuntimeException: Unable to load category:
> magnews.testgroups.MinimumAcceptance
> at
> org.apache.maven.surefire.group.match.SingleGroupMatcher.loadGroupClasses(SingleGroupMatcher.java:134)
> at
> org.apache.maven.surefire.common.junit48.FilterFactory.createGroupFilter(FilterFactory.java:92)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreProvider.createJUnit48Filter(JUnitCoreProvider.java:183)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:115)
> ... 9 more
> Caused by: java.lang.ClassNotFoundException:
> magnews.testgroups.MinimumAcceptance
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.maven.surefire.group.match.SingleGroupMatcher.loadGroupClasses(SingleGroupMatcher.java:130)
> ... 12 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[GitHub] maven-surefire issue #172: [SUREFIRE-1453] Allow to specify non existant cla...
Github user eolivelli commented on the issue: https://github.com/apache/maven-surefire/pull/172 You are welcome! ---
[GitHub] maven-surefire pull request #172: [SUREFIRE-1453] Allow to specify non exist...
Github user eolivelli closed the pull request at: https://github.com/apache/maven-surefire/pull/172 ---
[jira] [Commented] (SUREFIRE-1453) Allow to specify non existant classes as "groups"
[
https://issues.apache.org/jira/browse/SUREFIRE-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296083#comment-16296083
]
Hudson commented on SUREFIRE-1453:
--
SUCCESS: Integrated in Jenkins build maven-surefire #1814 (See
[https://builds.apache.org/job/maven-surefire/1814/])
[SUREFIRE-1453] Allow to specify non existant classes as groups (tibor17:
[http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git=commit=9826145dfea0e23894e2df48f64dd20a5d465c85])
* (edit)
surefire-grouper/src/main/java/org/apache/maven/surefire/group/match/SingleGroupMatcher.java
* (edit)
surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/JUnit48TestCategoriesIT.java
* (edit)
surefire-grouper/src/test/java/org/apache/maven/surefire/group/match/SingleGroupMatcherTest.java
> Allow to specify non existant classes as "groups"
> -
>
> Key: SUREFIRE-1453
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1453
> Project: Maven Surefire
> Issue Type: Improvement
> Components: classloading, Junit 4.7+ (parallel) support, Junit 4.x
> support, Maven Failsafe Plugin, Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Enrico Olivelli
>Assignee: Tibor Digana
>Priority: Critical
> Fix For: 2.21.0.Jigsaw
>
>
> In a reactor project I would like to run only a subset of JUnit (4.12) tests
> tagged with @Category
> But the class which defines the category is not present in the dependency
> tree of every module.
> I get this error.
> I would like to simply skip these modules, maybe in conjunction with the
> failIfNoTest=false option
> {code:java}
> rg.apache.maven.surefire.util.SurefireReflectionException:
> java.lang.reflect.InvocationTargetException; nested exception is
> java.lang.reflect.InvocationTargetException: null
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Caused by: java.lang.RuntimeException: Unable to load category:
> magnews.testgroups.MinimumAcceptance
> at
> org.apache.maven.surefire.group.match.SingleGroupMatcher.loadGroupClasses(SingleGroupMatcher.java:134)
> at
> org.apache.maven.surefire.common.junit48.FilterFactory.createGroupFilter(FilterFactory.java:92)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreProvider.createJUnit48Filter(JUnitCoreProvider.java:183)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:115)
> ... 9 more
> Caused by: java.lang.ClassNotFoundException:
> magnews.testgroups.MinimumAcceptance
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.maven.surefire.group.match.SingleGroupMatcher.loadGroupClasses(SingleGroupMatcher.java:130)
> ... 12 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1453) Allow to specify non existant classes as "groups"
[
https://issues.apache.org/jira/browse/SUREFIRE-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296054#comment-16296054
]
ASF GitHub Bot commented on SUREFIRE-1453:
--
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/172
@eolivelli
Thx for contributing. The PR was pushed to master and now it can be closed.
> Allow to specify non existant classes as "groups"
> -
>
> Key: SUREFIRE-1453
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1453
> Project: Maven Surefire
> Issue Type: Improvement
> Components: classloading, Junit 4.7+ (parallel) support, Junit 4.x
> support, Maven Failsafe Plugin, Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Enrico Olivelli
>Assignee: Tibor Digana
>Priority: Critical
> Fix For: 2.21.0.Jigsaw
>
>
> In a reactor project I would like to run only a subset of JUnit (4.12) tests
> tagged with @Category
> But the class which defines the category is not present in the dependency
> tree of every module.
> I get this error.
> I would like to simply skip these modules, maybe in conjunction with the
> failIfNoTest=false option
> {code:java}
> rg.apache.maven.surefire.util.SurefireReflectionException:
> java.lang.reflect.InvocationTargetException; nested exception is
> java.lang.reflect.InvocationTargetException: null
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Caused by: java.lang.RuntimeException: Unable to load category:
> magnews.testgroups.MinimumAcceptance
> at
> org.apache.maven.surefire.group.match.SingleGroupMatcher.loadGroupClasses(SingleGroupMatcher.java:134)
> at
> org.apache.maven.surefire.common.junit48.FilterFactory.createGroupFilter(FilterFactory.java:92)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreProvider.createJUnit48Filter(JUnitCoreProvider.java:183)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:115)
> ... 9 more
> Caused by: java.lang.ClassNotFoundException:
> magnews.testgroups.MinimumAcceptance
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.maven.surefire.group.match.SingleGroupMatcher.loadGroupClasses(SingleGroupMatcher.java:130)
> ... 12 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[GitHub] maven-surefire issue #172: [SUREFIRE-1453] Allow to specify non existant cla...
Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/172 @eolivelli Thx for contributing. The PR was pushed to master and now it can be closed. ---
[jira] [Closed] (SUREFIRE-1453) Allow to specify non existant classes as "groups"
[
https://issues.apache.org/jira/browse/SUREFIRE-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1453.
--
Resolution: Fixed
https://git1-us-west.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=9826145dfea0e23894e2df48f64dd20a5d465c85
> Allow to specify non existant classes as "groups"
> -
>
> Key: SUREFIRE-1453
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1453
> Project: Maven Surefire
> Issue Type: Improvement
> Components: classloading, Junit 4.7+ (parallel) support, Junit 4.x
> support, Maven Failsafe Plugin, Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Enrico Olivelli
>Assignee: Tibor Digana
>Priority: Critical
> Fix For: 2.21.0.Jigsaw
>
>
> In a reactor project I would like to run only a subset of JUnit (4.12) tests
> tagged with @Category
> But the class which defines the category is not present in the dependency
> tree of every module.
> I get this error.
> I would like to simply skip these modules, maybe in conjunction with the
> failIfNoTest=false option
> {code:java}
> rg.apache.maven.surefire.util.SurefireReflectionException:
> java.lang.reflect.InvocationTargetException; nested exception is
> java.lang.reflect.InvocationTargetException: null
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Caused by: java.lang.RuntimeException: Unable to load category:
> magnews.testgroups.MinimumAcceptance
> at
> org.apache.maven.surefire.group.match.SingleGroupMatcher.loadGroupClasses(SingleGroupMatcher.java:134)
> at
> org.apache.maven.surefire.common.junit48.FilterFactory.createGroupFilter(FilterFactory.java:92)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreProvider.createJUnit48Filter(JUnitCoreProvider.java:183)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:115)
> ... 9 more
> Caused by: java.lang.ClassNotFoundException:
> magnews.testgroups.MinimumAcceptance
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.maven.surefire.group.match.SingleGroupMatcher.loadGroupClasses(SingleGroupMatcher.java:130)
> ... 12 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SUREFIRE-1453) Allow to specify non existant classes as "groups"
[
https://issues.apache.org/jira/browse/SUREFIRE-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1453:
---
Component/s: Maven Failsafe Plugin
Junit 4.7+ (parallel) support
> Allow to specify non existant classes as "groups"
> -
>
> Key: SUREFIRE-1453
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1453
> Project: Maven Surefire
> Issue Type: Improvement
> Components: classloading, Junit 4.7+ (parallel) support, Junit 4.x
> support, Maven Failsafe Plugin, Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Enrico Olivelli
>Assignee: Tibor Digana
>Priority: Critical
> Fix For: 2.21.0.Jigsaw
>
>
> In a reactor project I would like to run only a subset of JUnit (4.12) tests
> tagged with @Category
> But the class which defines the category is not present in the dependency
> tree of every module.
> I get this error.
> I would like to simply skip these modules, maybe in conjunction with the
> failIfNoTest=false option
> {code:java}
> rg.apache.maven.surefire.util.SurefireReflectionException:
> java.lang.reflect.InvocationTargetException; nested exception is
> java.lang.reflect.InvocationTargetException: null
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Caused by: java.lang.RuntimeException: Unable to load category:
> magnews.testgroups.MinimumAcceptance
> at
> org.apache.maven.surefire.group.match.SingleGroupMatcher.loadGroupClasses(SingleGroupMatcher.java:134)
> at
> org.apache.maven.surefire.common.junit48.FilterFactory.createGroupFilter(FilterFactory.java:92)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreProvider.createJUnit48Filter(JUnitCoreProvider.java:183)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:115)
> ... 9 more
> Caused by: java.lang.ClassNotFoundException:
> magnews.testgroups.MinimumAcceptance
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.maven.surefire.group.match.SingleGroupMatcher.loadGroupClasses(SingleGroupMatcher.java:130)
> ... 12 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (MNGSITE-324) Broken links on https://maven.apache.org/archetypes/
Geoff Macartney created MNGSITE-324: --- Summary: Broken links on https://maven.apache.org/archetypes/ Key: MNGSITE-324 URL: https://issues.apache.org/jira/browse/MNGSITE-324 Project: Maven Project Web Site Issue Type: Bug Reporter: Geoff Macartney Priority: Trivial Page https://maven.apache.org/archetypes/ contains a table of links such as https://maven.apache.org/archetypes/maven-archetype-site/ https://maven.apache.org/archetypes/maven-archetype-site-simple/ https://maven.apache.org/archetypes/maven-archetype-webapp/ that give a 404 response. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MPMD-246) Output details of processing errors
[ https://issues.apache.org/jira/browse/MPMD-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel resolved MPMD-246. - Resolution: Fixed With 3.9.0 a new parameter has been added for PMD, which is by default enabled: Name: *renderProcessingErrors* (property = "pmd.renderProcessingErrors") Also render processing errors into the HTML report. Processing errors are problems, that PMD encountered while executing the rules. It can be parsing errors or exceptions during rule execution. Processing errors indicate a bug in PMD and the information provided help in reporting and fixing bugs in PMD. > Output details of processing errors > --- > > Key: MPMD-246 > URL: https://issues.apache.org/jira/browse/MPMD-246 > Project: Maven PMD Plugin > Issue Type: Improvement > Components: PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel > Fix For: 3.9.0 > > > To help debugging processing errors (or any error in PMD), maven should be > able to output the processing errors with exception stacktraces. > Currently, only the number of the problematic files are displayed. > Furthermore, PMD usually adds the processing errors to the XML report. But > the XML report that is generated with the maven pmd plugin doesn't contain > the errors. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MNG-6323) Deadlock in multithreaded dependency resolution
[
https://issues.apache.org/jira/browse/MNG-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Caradoc-Davies updated MNG-6323:
Description:
Maven 3.5.2 multithreaded builds experience a deadlock not seen with Maven
3.5.0.
To reproduce the issue, clone GeoServer:
{noformat}
git clone https://github.com/geoserver/geoserver.git
cd geoserver
{noformat}
Build GeoServer community modules with:
{noformat}
mvn -f src/community/pom.xml -B -T4 -U -Prelease -PcommunityRelease -DskipTests
clean install
{noformat}
Builds that normally take 2-4 minutes instead experience long hangs. {{jstack}}
output (attached) suggests a deadlock (two different hangs attached). Some of
the locks are in {{TIME_WAIT}} and eventually the build completes after 30-45
minutes, but this is enough to cause builds on Travis to be killed for their
failure to output for ten minutes. (Travis upgraded to Maven 3.5.2 a week ago.)
I have only seen the failures with -U. The hang does not occur in
single-threaded builds. There are no "*.lock" files in the local repository
during the hang so the deadlocks are not mediated by the filesystem. CPU
utilisation is zero suggesting a deadlock not a livelock.
See also discussion on the geoserver-devel mailing list:
http://osgeo-org.1560.x6.nabble.com/Travis-failures-started-with-new-trusty-images-td5346836.html
was:
Maven 3.5.2 multithreaded builds experience a deadlock not seen with Maven
3.5.0.
To reproduce the issue, clone GeoServer:
{noformat}
git clone https://github.com/geoserver/geoserver.git
cd geoserver
{noformat}
Build GeoServer community modules with:
{noformat}
mvn -f src/community/pom.xml -B -T4 -U -Prelease -PcommunityRelease -DskipTests
clean install
{noformat}
Builds that normally take 2-4 minutes instead experience long hangs. {{jstack}}
output (attached) suggests a deadlock (two different hangs attached). Some of
the locks are in {{TIME_WAIT}} and eventually the build completes after 30-45
minutes, but this is enough to cause builds on Travis to be killed for their
failure to output for ten minutes. (Travis upgraded to Maven 3.5.2 a week ago.)
I have only seen the failures with -U. The hang does not occur in
single-threaded builds. There are no "*.lock" files in the local repository
during the hang so the locks are not mediated by the filesystem. CPU
utilisation is zero suggesting a deadlock not a livelock.
See also discussion on the geoserver-devel mailing list:
http://osgeo-org.1560.x6.nabble.com/Travis-failures-started-with-new-trusty-images-td5346836.html
> Deadlock in multithreaded dependency resolution
> ---
>
> Key: MNG-6323
> URL: https://issues.apache.org/jira/browse/MNG-6323
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.2
>Reporter: Ben Caradoc-Davies
> Attachments: geoserver-community-maven-hang-jstack-2.txt,
> geoserver-community-maven-hang-jstack.txt
>
>
> Maven 3.5.2 multithreaded builds experience a deadlock not seen with Maven
> 3.5.0.
> To reproduce the issue, clone GeoServer:
> {noformat}
> git clone https://github.com/geoserver/geoserver.git
> cd geoserver
> {noformat}
> Build GeoServer community modules with:
> {noformat}
> mvn -f src/community/pom.xml -B -T4 -U -Prelease -PcommunityRelease
> -DskipTests clean install
> {noformat}
> Builds that normally take 2-4 minutes instead experience long hangs.
> {{jstack}} output (attached) suggests a deadlock (two different hangs
> attached). Some of the locks are in {{TIME_WAIT}} and eventually the build
> completes after 30-45 minutes, but this is enough to cause builds on Travis
> to be killed for their failure to output for ten minutes. (Travis upgraded to
> Maven 3.5.2 a week ago.)
> I have only seen the failures with -U. The hang does not occur in
> single-threaded builds. There are no "*.lock" files in the local repository
> during the hang so the deadlocks are not mediated by the filesystem. CPU
> utilisation is zero suggesting a deadlock not a livelock.
> See also discussion on the geoserver-devel mailing list:
> http://osgeo-org.1560.x6.nabble.com/Travis-failures-started-with-new-trusty-images-td5346836.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (MPMD-244) Maven PMD plugin fails but no reason is given for the failure
[
https://issues.apache.org/jira/browse/MPMD-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel resolved MPMD-244.
-
Resolution: Fixed
With 3.9.0 a new parameter has been added for both PMD and CPD, which is
enabled by default:
Name: *showPmdLog* (property = "pmd.showPmdLog")
When enabled, the PMD log output is redirected to maven, so that
it is visible in the console together with all the other log output.
Also, if maven is started with the debug flag ({{-X}} or {{--debug}})
the PMD logger is also configured for debug.
> Maven PMD plugin fails but no reason is given for the failure
> -
>
> Key: MPMD-244
> URL: https://issues.apache.org/jira/browse/MPMD-244
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.8
> Environment: Maven 3.5.0
> PMD 5.8.1
> OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode)
> Fedora 23
>Reporter: Goldstein Lyor
>Assignee: Andreas Dangel
>Priority: Blocker
> Fix For: 3.9.0
>
>
> After upgrading used PMD version from 5.6.1 to 5.8.1, Maven PMD plugin fails
> with no specific reason except {{Failed to process...}}. Furthermore, there
> is no PMD report or other file that indicates what is wrong.
> P.S. The file that it complains about passes without a problem for version
> 5.6.1
> {noformat}
> $ mvn -X -Dpmd.verbose=true clean install
> Maven home: /home/lyor/Software/apache-maven-3.5.0
> Java version: 1.8.0_91, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-2.b14.fc22.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.4.14-200.fc22.x86_64", arch: "amd64", family:
> "unix"
> .
> ..
> [INFO] --- maven-pmd-plugin:3.8:pmd (pmd) @ cb4-common-util ---
> [DEBUG] Dependency collection stats: {ConflictMarker.analyzeTime=1,
> ConflictMarker.markTime=0, ConflictMarker.nodeCount=280,
> ConflictIdSorter.graphTime=0, ConflictIdSorter.topsortTime=0,
> ConflictIdSorter.conflictIdCount=70, ConflictIdSorter.conflictIdCycleCount=0,
> ConflictResolver.totalTime=2, ConflictResolver.conflictItemCount=152,
> DefaultDependencyCollector.collectTime=38,
> DefaultDependencyCollector.transformTime=3}
> [DEBUG] org.apache.maven.plugins:maven-pmd-plugin:jar:3.8:
> [DEBUG]net.sourceforge.pmd:pmd-core:jar:5.8.1:runtime
> [DEBUG] com.beust:jcommander:jar:1.48:runtime
> [DEBUG] jaxen:jaxen:jar:1.1.6:runtime
> [DEBUG] net.java.dev.javacc:javacc:jar:5.0:runtime
> [DEBUG] net.sourceforge.saxon:saxon:jar:9.1.0.8:runtime
> [DEBUG] org.apache.commons:commons-lang3:jar:3.4:runtime
> [DEBUG] org.ow2.asm:asm:jar:5.0.4:runtime
> [DEBUG] com.google.code.gson:gson:jar:2.5:runtime
> [DEBUG] net.sourceforge.saxon:saxon:jar:dom:9.1.0.8:runtime
> [DEBUG]net.sourceforge.pmd:pmd-java:jar:5.8.1:runtime
> [DEBUG]net.sourceforge.pmd:pmd-javascript:jar:5.8.1:runtime
> [DEBUG] org.mozilla:rhino:jar:1.7.7:runtime
> [DEBUG]net.sourceforge.pmd:pmd-jsp:jar:5.8.1:runtime
> [DEBUG]org.apache.maven:maven-artifact:jar:2.2.1:compile
> [DEBUG]org.apache.maven:maven-model:jar:2.2.1:compile
> [DEBUG]org.apache.maven:maven-plugin-api:jar:2.2.1:compile
> [DEBUG]org.apache.maven:maven-project:jar:2.2.1:compile
> [DEBUG] org.apache.maven:maven-settings:jar:2.2.1:compile
> [DEBUG] org.apache.maven:maven-profile:jar:2.2.1:compile
> [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.2.1:compile
> [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.2.1:compile
> [DEBUG]
> backport-util-concurrent:backport-util-concurrent:jar:3.1:compile
> [DEBUG] org.apache.maven:maven-plugin-registry:jar:2.2.1:compile
> [DEBUG] org.codehaus.plexus:plexus-interpolation:jar:1.11:compile
> [DEBUG]
> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:compile
> [DEBUG] junit:junit:jar:3.8.1:compile
> [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:compile
> [DEBUG]org.apache.maven.doxia:doxia-sink-api:jar:1.4:compile
> [DEBUG] org.apache.maven.doxia:doxia-logging-api:jar:1.4:compile
> [DEBUG]org.apache.maven.doxia:doxia-decoration-model:jar:1.4:compile
> [DEBUG] org.codehaus.plexus:plexus-component-annotations:jar:1.6:compile
> [DEBUG]org.apache.maven.doxia:doxia-site-renderer:jar:1.4:compile
> [DEBUG] org.apache.maven.doxia:doxia-core:jar:1.4:compile
> [DEBUG] xerces:xercesImpl:jar:2.9.1:compile
> [DEBUG] commons-lang:commons-lang:jar:2.4:compile
> [DEBUG] org.apache.maven.doxia:doxia-module-xhtml:jar:1.4:compile
> [DEBUG] org.apache.maven.doxia:doxia-module-fml:jar:1.4:compile
> [DEBUG]
[jira] [Commented] (MNG-6323) Deadlock in multithreaded dependency resolution
[
https://issues.apache.org/jira/browse/MNG-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16295523#comment-16295523
]
Ben Caradoc-Davies commented on MNG-6323:
-
By the way, reverting MNG-6025 (be223808939d75152d7157db33d45f230114555e) did
not fix. I did not try reverting the upgrade to Resolver 1.1.0 (MNG-6258).
> Deadlock in multithreaded dependency resolution
> ---
>
> Key: MNG-6323
> URL: https://issues.apache.org/jira/browse/MNG-6323
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.2
>Reporter: Ben Caradoc-Davies
> Attachments: geoserver-community-maven-hang-jstack-2.txt,
> geoserver-community-maven-hang-jstack.txt
>
>
> Maven 3.5.2 multithreaded builds experience a deadlock not seen with Maven
> 3.5.0.
> To reproduce the issue, clone GeoServer:
> {noformat}
> git clone https://github.com/geoserver/geoserver.git
> cd geoserver
> {noformat}
> Build GeoServer community modules with:
> {noformat}
> mvn -f src/community/pom.xml -B -T4 -U -Prelease -PcommunityRelease
> -DskipTests clean install
> {noformat}
> Builds that normally take 2-4 minutes instead experience long hangs.
> {{jstack}} output (attached) suggests a deadlock (two different hangs
> attached). Some of the locks are in {{TIME_WAIT}} and eventually the build
> completes after 30-45 minutes, but this is enough to cause builds on Travis
> to be killed for their failure to output for ten minutes. (Travis upgraded to
> Maven 3.5.2 a week ago.)
> I have only seen the failures with -U. The hang does not occur in
> single-threaded builds. There are no "*.lock" files in the local repository
> during the hang so the locks are not mediated by the filesystem. CPU
> utilisation is zero suggesting a deadlock not a livelock.
> See also discussion on the geoserver-devel mailing list:
> http://osgeo-org.1560.x6.nabble.com/Travis-failures-started-with-new-trusty-images-td5346836.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (MNG-6323) Deadlock in multithreaded dependency resolution
[
https://issues.apache.org/jira/browse/MNG-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Caradoc-Davies updated MNG-6323:
Description:
Maven 3.5.2 multithreaded builds experience a deadlock not seen with Maven
3.5.0.
To reproduce the issue, clone GeoServer:
{noformat}
git clone https://github.com/geoserver/geoserver.git
cd geoserver
{noformat}
Build GeoServer community modules with:
{noformat}
mvn -f src/community/pom.xml -B -T4 -U -Prelease -PcommunityRelease -DskipTests
clean install
{noformat}
Builds that normally take 2-4 minutes instead experience long hangs. {{jstack}}
output (attached) suggests a deadlock (two different hangs attached). Some of
the locks are in {{TIME_WAIT}} and eventually the build completes after 30-45
minutes, but this is enough to cause builds on Travis to be killed for their
failure to output for ten minutes. (Travis upgraded to Maven 3.5.2 a week ago.)
I have only seen the failures with -U. The hang does not occur in
single-threaded builds. There are no "*.lock" files in the local repository
during the hang so the locks are not mediated by the filesystem. CPU
utilisation is zero suggesting a deadlock not a livelock.
See also discussion on the geoserver-devel mailing list:
http://osgeo-org.1560.x6.nabble.com/Travis-failures-started-with-new-trusty-images-td5346836.html
was:
Maven 3.5.2 multithreaded builds experience a deadlock not seen with Maven
3.5.0.
To reproduce the issue, clone GeoServer:
{noformat}
git clone https://github.com/geoserver/geoserver.git
cd geoserver
{noformat}
Build GeoServer community modules with:
{noformat}
mvn -f src/community/pom.xml -B -T4 -U -Prelease -PcommunityRelease -DskipTests
clean install
{noformat}
Builds that normally take 2-4 minutes instead experience long hangs. {{jstack}}
output (attached) suggests a deadlock (two different hangs attached). Some of
the locks are in {{TIME_WAIT}} and eventually the build completes after 30-45
minutes, but this is enough to cause builds on Travis to be killed for their
failure to output for ten minutes. (Travis upgraded to Maven 3.5.2 a week ago.)
I have only seen the failures with -U. The hang does not occur in
single-threaded builds.
See also discussion on the geoserver-devel mailing list:
http://osgeo-org.1560.x6.nabble.com/Travis-failures-started-with-new-trusty-images-td5346836.html
> Deadlock in multithreaded dependency resolution
> ---
>
> Key: MNG-6323
> URL: https://issues.apache.org/jira/browse/MNG-6323
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.2
>Reporter: Ben Caradoc-Davies
> Attachments: geoserver-community-maven-hang-jstack-2.txt,
> geoserver-community-maven-hang-jstack.txt
>
>
> Maven 3.5.2 multithreaded builds experience a deadlock not seen with Maven
> 3.5.0.
> To reproduce the issue, clone GeoServer:
> {noformat}
> git clone https://github.com/geoserver/geoserver.git
> cd geoserver
> {noformat}
> Build GeoServer community modules with:
> {noformat}
> mvn -f src/community/pom.xml -B -T4 -U -Prelease -PcommunityRelease
> -DskipTests clean install
> {noformat}
> Builds that normally take 2-4 minutes instead experience long hangs.
> {{jstack}} output (attached) suggests a deadlock (two different hangs
> attached). Some of the locks are in {{TIME_WAIT}} and eventually the build
> completes after 30-45 minutes, but this is enough to cause builds on Travis
> to be killed for their failure to output for ten minutes. (Travis upgraded to
> Maven 3.5.2 a week ago.)
> I have only seen the failures with -U. The hang does not occur in
> single-threaded builds. There are no "*.lock" files in the local repository
> during the hang so the locks are not mediated by the filesystem. CPU
> utilisation is zero suggesting a deadlock not a livelock.
> See also discussion on the geoserver-devel mailing list:
> http://osgeo-org.1560.x6.nabble.com/Travis-failures-started-with-new-trusty-images-td5346836.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MPMD-244) Maven PMD plugin fails but no reason is given for the failure
[
https://issues.apache.org/jira/browse/MPMD-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16295509#comment-16295509
]
Hudson commented on MPMD-244:
-
Build succeeded in Jenkins: Maven TLP » maven-pmd-plugin » master #9
See https://builds.apache.org/job/maven-box/job/maven-pmd-plugin/job/master/9/
> Maven PMD plugin fails but no reason is given for the failure
> -
>
> Key: MPMD-244
> URL: https://issues.apache.org/jira/browse/MPMD-244
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.8
> Environment: Maven 3.5.0
> PMD 5.8.1
> OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode)
> Fedora 23
>Reporter: Goldstein Lyor
>Assignee: Andreas Dangel
>Priority: Blocker
> Fix For: 3.9.0
>
>
> After upgrading used PMD version from 5.6.1 to 5.8.1, Maven PMD plugin fails
> with no specific reason except {{Failed to process...}}. Furthermore, there
> is no PMD report or other file that indicates what is wrong.
> P.S. The file that it complains about passes without a problem for version
> 5.6.1
> {noformat}
> $ mvn -X -Dpmd.verbose=true clean install
> Maven home: /home/lyor/Software/apache-maven-3.5.0
> Java version: 1.8.0_91, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-2.b14.fc22.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.4.14-200.fc22.x86_64", arch: "amd64", family:
> "unix"
> .
> ..
> [INFO] --- maven-pmd-plugin:3.8:pmd (pmd) @ cb4-common-util ---
> [DEBUG] Dependency collection stats: {ConflictMarker.analyzeTime=1,
> ConflictMarker.markTime=0, ConflictMarker.nodeCount=280,
> ConflictIdSorter.graphTime=0, ConflictIdSorter.topsortTime=0,
> ConflictIdSorter.conflictIdCount=70, ConflictIdSorter.conflictIdCycleCount=0,
> ConflictResolver.totalTime=2, ConflictResolver.conflictItemCount=152,
> DefaultDependencyCollector.collectTime=38,
> DefaultDependencyCollector.transformTime=3}
> [DEBUG] org.apache.maven.plugins:maven-pmd-plugin:jar:3.8:
> [DEBUG]net.sourceforge.pmd:pmd-core:jar:5.8.1:runtime
> [DEBUG] com.beust:jcommander:jar:1.48:runtime
> [DEBUG] jaxen:jaxen:jar:1.1.6:runtime
> [DEBUG] net.java.dev.javacc:javacc:jar:5.0:runtime
> [DEBUG] net.sourceforge.saxon:saxon:jar:9.1.0.8:runtime
> [DEBUG] org.apache.commons:commons-lang3:jar:3.4:runtime
> [DEBUG] org.ow2.asm:asm:jar:5.0.4:runtime
> [DEBUG] com.google.code.gson:gson:jar:2.5:runtime
> [DEBUG] net.sourceforge.saxon:saxon:jar:dom:9.1.0.8:runtime
> [DEBUG]net.sourceforge.pmd:pmd-java:jar:5.8.1:runtime
> [DEBUG]net.sourceforge.pmd:pmd-javascript:jar:5.8.1:runtime
> [DEBUG] org.mozilla:rhino:jar:1.7.7:runtime
> [DEBUG]net.sourceforge.pmd:pmd-jsp:jar:5.8.1:runtime
> [DEBUG]org.apache.maven:maven-artifact:jar:2.2.1:compile
> [DEBUG]org.apache.maven:maven-model:jar:2.2.1:compile
> [DEBUG]org.apache.maven:maven-plugin-api:jar:2.2.1:compile
> [DEBUG]org.apache.maven:maven-project:jar:2.2.1:compile
> [DEBUG] org.apache.maven:maven-settings:jar:2.2.1:compile
> [DEBUG] org.apache.maven:maven-profile:jar:2.2.1:compile
> [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.2.1:compile
> [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.2.1:compile
> [DEBUG]
> backport-util-concurrent:backport-util-concurrent:jar:3.1:compile
> [DEBUG] org.apache.maven:maven-plugin-registry:jar:2.2.1:compile
> [DEBUG] org.codehaus.plexus:plexus-interpolation:jar:1.11:compile
> [DEBUG]
> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:compile
> [DEBUG] junit:junit:jar:3.8.1:compile
> [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:compile
> [DEBUG]org.apache.maven.doxia:doxia-sink-api:jar:1.4:compile
> [DEBUG] org.apache.maven.doxia:doxia-logging-api:jar:1.4:compile
> [DEBUG]org.apache.maven.doxia:doxia-decoration-model:jar:1.4:compile
> [DEBUG] org.codehaus.plexus:plexus-component-annotations:jar:1.6:compile
> [DEBUG]org.apache.maven.doxia:doxia-site-renderer:jar:1.4:compile
> [DEBUG] org.apache.maven.doxia:doxia-core:jar:1.4:compile
> [DEBUG] xerces:xercesImpl:jar:2.9.1:compile
> [DEBUG] commons-lang:commons-lang:jar:2.4:compile
> [DEBUG] org.apache.maven.doxia:doxia-module-xhtml:jar:1.4:compile
> [DEBUG] org.apache.maven.doxia:doxia-module-fml:jar:1.4:compile
> [DEBUG] org.codehaus.plexus:plexus-i18n:jar:1.0-beta-7:compile
> [DEBUG] org.codehaus.plexus:plexus-velocity:jar:1.1.7:compile
> [DEBUG] org.apache.velocity:velocity:jar:1.5:compile
> [DEBUG] oro:oro:jar:2.0.8:compile
> [DEBUG]
[jira] [Commented] (MPMD-246) Output details of processing errors
[ https://issues.apache.org/jira/browse/MPMD-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16295510#comment-16295510 ] Hudson commented on MPMD-246: - Build succeeded in Jenkins: Maven TLP » maven-pmd-plugin » master #9 See https://builds.apache.org/job/maven-box/job/maven-pmd-plugin/job/master/9/ > Output details of processing errors > --- > > Key: MPMD-246 > URL: https://issues.apache.org/jira/browse/MPMD-246 > Project: Maven PMD Plugin > Issue Type: Improvement > Components: PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel > Fix For: 3.9.0 > > > To help debugging processing errors (or any error in PMD), maven should be > able to output the processing errors with exception stacktraces. > Currently, only the number of the problematic files are displayed. > Furthermore, PMD usually adds the processing errors to the XML report. But > the XML report that is generated with the maven pmd plugin doesn't contain > the errors. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MNG-6323) Deadlock in multithreaded dependency resolution
[
https://issues.apache.org/jira/browse/MNG-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Caradoc-Davies updated MNG-6323:
Description:
Maven 3.5.2 multithreaded builds experience a deadlock not seen with Maven
3.5.0.
To reproduce the issue, clone GeoServer:
{noformat}
git clone https://github.com/geoserver/geoserver.git
cd geoserver
{noformat}
Build GeoServer community modules with:
{noformat}
mvn -f src/community/pom.xml -B -T4 -U -Prelease -PcommunityRelease -DskipTests
clean install
{noformat}
Builds that normally take 2-4 minutes instead experience long hangs. {{jstack}}
output (attached) suggests a deadlock (two different hangs attached). Some of
the locks are in {{TIME_WAIT}} and eventually the build completes after 30-45
minutes, but this is enough to cause builds on Travis to be killed for their
failure to output for ten minutes. (Travis upgraded to Maven 3.5.2 a week ago.)
I have only seen the failures with -U. The hang does not occur in
single-threaded builds.
See also discussion on the geoserver-devel mailing list:
http://osgeo-org.1560.x6.nabble.com/Travis-failures-started-with-new-trusty-images-td5346836.html
was:
Maven 3.5.2 multithreaded builds experience a deadlock not seen with Maven
3.5.0.
To reproduce the issue, clone GeoServer:
{noformat}
git clone https://github.com/geoserver/geoserver.git
cd geoserver
{noformat}
Build GeoServer community modules with:
{noformat}
mvn -f src/community/pom.xml -B -T4 -U -Prelease -PcommunityRelease -DskipTests
clean install
{noformat}
Builds that normally take 2-4 minutes instead experience long hangs. {{jstack}}
output (attached) suggests a deadlock (two different hangs attached). Some of
the locks are in {{TIME_WAIT}} and eventually the build completes after 30-45
minutes, but this is enough to cause builds on Travis to be killed for their
failure to output for ten minutes. (Travis upgraded to Maven 3.5.2 a week ago.)
I have only seen the failures with -U. The hang does not occur in
single-threaded builds.
See also discussion on the geoserver-devel mailing list:
http://osgeo-org.1560.x6.nabble.com/Travis-failures-started-with-new-trusty-images-td5346836.html
See also discussion
> Deadlock in multithreaded dependency resolution
> ---
>
> Key: MNG-6323
> URL: https://issues.apache.org/jira/browse/MNG-6323
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.2
>Reporter: Ben Caradoc-Davies
> Attachments: geoserver-community-maven-hang-jstack-2.txt,
> geoserver-community-maven-hang-jstack.txt
>
>
> Maven 3.5.2 multithreaded builds experience a deadlock not seen with Maven
> 3.5.0.
> To reproduce the issue, clone GeoServer:
> {noformat}
> git clone https://github.com/geoserver/geoserver.git
> cd geoserver
> {noformat}
> Build GeoServer community modules with:
> {noformat}
> mvn -f src/community/pom.xml -B -T4 -U -Prelease -PcommunityRelease
> -DskipTests clean install
> {noformat}
> Builds that normally take 2-4 minutes instead experience long hangs.
> {{jstack}} output (attached) suggests a deadlock (two different hangs
> attached). Some of the locks are in {{TIME_WAIT}} and eventually the build
> completes after 30-45 minutes, but this is enough to cause builds on Travis
> to be killed for their failure to output for ten minutes. (Travis upgraded to
> Maven 3.5.2 a week ago.)
> I have only seen the failures with -U. The hang does not occur in
> single-threaded builds.
> See also discussion on the geoserver-devel mailing list:
> http://osgeo-org.1560.x6.nabble.com/Travis-failures-started-with-new-trusty-images-td5346836.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (MNG-6323) Deadlock in multithreaded dependency resolution
Ben Caradoc-Davies created MNG-6323:
---
Summary: Deadlock in multithreaded dependency resolution
Key: MNG-6323
URL: https://issues.apache.org/jira/browse/MNG-6323
Project: Maven
Issue Type: Bug
Affects Versions: 3.5.2
Reporter: Ben Caradoc-Davies
Attachments: geoserver-community-maven-hang-jstack-2.txt,
geoserver-community-maven-hang-jstack.txt
Maven 3.5.2 multithreaded builds experience a deadlock not seen with Maven
3.5.0.
To reproduce the issue, clone GeoServer:
{noformat}
git clone https://github.com/geoserver/geoserver.git
cd geoserver
{noformat}
Build GeoServer community modules with:
{noformat}
mvn -f src/community/pom.xml -B -T4 -U -Prelease -PcommunityRelease -DskipTests
clean install
{noformat}
Builds that normally take 2-4 minutes instead experience long hangs. {{jstack}}
output (attached) suggests a deadlock (two different hangs attached). Some of
the locks are in {{TIME_WAIT}} and eventually the build completes after 30-45
minutes, but this is enough to cause builds on Travis to be killed for their
failure to output for ten minutes. (Travis upgraded to Maven 3.5.2 a week ago.)
I have only seen the failures with -U. The hang does not occur in
single-threaded builds.
See also discussion on the geoserver-devel mailing list:
http://osgeo-org.1560.x6.nabble.com/Travis-failures-started-with-new-trusty-images-td5346836.html
See also discussion
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (MPMD-244) Maven PMD plugin fails but no reason is given for the failure
[
https://issues.apache.org/jira/browse/MPMD-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel reassigned MPMD-244:
---
Assignee: Andreas Dangel
> Maven PMD plugin fails but no reason is given for the failure
> -
>
> Key: MPMD-244
> URL: https://issues.apache.org/jira/browse/MPMD-244
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.8
> Environment: Maven 3.5.0
> PMD 5.8.1
> OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode)
> Fedora 23
>Reporter: Goldstein Lyor
>Assignee: Andreas Dangel
>Priority: Blocker
> Fix For: 3.9.0
>
>
> After upgrading used PMD version from 5.6.1 to 5.8.1, Maven PMD plugin fails
> with no specific reason except {{Failed to process...}}. Furthermore, there
> is no PMD report or other file that indicates what is wrong.
> P.S. The file that it complains about passes without a problem for version
> 5.6.1
> {noformat}
> $ mvn -X -Dpmd.verbose=true clean install
> Maven home: /home/lyor/Software/apache-maven-3.5.0
> Java version: 1.8.0_91, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-2.b14.fc22.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.4.14-200.fc22.x86_64", arch: "amd64", family:
> "unix"
> .
> ..
> [INFO] --- maven-pmd-plugin:3.8:pmd (pmd) @ cb4-common-util ---
> [DEBUG] Dependency collection stats: {ConflictMarker.analyzeTime=1,
> ConflictMarker.markTime=0, ConflictMarker.nodeCount=280,
> ConflictIdSorter.graphTime=0, ConflictIdSorter.topsortTime=0,
> ConflictIdSorter.conflictIdCount=70, ConflictIdSorter.conflictIdCycleCount=0,
> ConflictResolver.totalTime=2, ConflictResolver.conflictItemCount=152,
> DefaultDependencyCollector.collectTime=38,
> DefaultDependencyCollector.transformTime=3}
> [DEBUG] org.apache.maven.plugins:maven-pmd-plugin:jar:3.8:
> [DEBUG]net.sourceforge.pmd:pmd-core:jar:5.8.1:runtime
> [DEBUG] com.beust:jcommander:jar:1.48:runtime
> [DEBUG] jaxen:jaxen:jar:1.1.6:runtime
> [DEBUG] net.java.dev.javacc:javacc:jar:5.0:runtime
> [DEBUG] net.sourceforge.saxon:saxon:jar:9.1.0.8:runtime
> [DEBUG] org.apache.commons:commons-lang3:jar:3.4:runtime
> [DEBUG] org.ow2.asm:asm:jar:5.0.4:runtime
> [DEBUG] com.google.code.gson:gson:jar:2.5:runtime
> [DEBUG] net.sourceforge.saxon:saxon:jar:dom:9.1.0.8:runtime
> [DEBUG]net.sourceforge.pmd:pmd-java:jar:5.8.1:runtime
> [DEBUG]net.sourceforge.pmd:pmd-javascript:jar:5.8.1:runtime
> [DEBUG] org.mozilla:rhino:jar:1.7.7:runtime
> [DEBUG]net.sourceforge.pmd:pmd-jsp:jar:5.8.1:runtime
> [DEBUG]org.apache.maven:maven-artifact:jar:2.2.1:compile
> [DEBUG]org.apache.maven:maven-model:jar:2.2.1:compile
> [DEBUG]org.apache.maven:maven-plugin-api:jar:2.2.1:compile
> [DEBUG]org.apache.maven:maven-project:jar:2.2.1:compile
> [DEBUG] org.apache.maven:maven-settings:jar:2.2.1:compile
> [DEBUG] org.apache.maven:maven-profile:jar:2.2.1:compile
> [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.2.1:compile
> [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.2.1:compile
> [DEBUG]
> backport-util-concurrent:backport-util-concurrent:jar:3.1:compile
> [DEBUG] org.apache.maven:maven-plugin-registry:jar:2.2.1:compile
> [DEBUG] org.codehaus.plexus:plexus-interpolation:jar:1.11:compile
> [DEBUG]
> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:compile
> [DEBUG] junit:junit:jar:3.8.1:compile
> [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:compile
> [DEBUG]org.apache.maven.doxia:doxia-sink-api:jar:1.4:compile
> [DEBUG] org.apache.maven.doxia:doxia-logging-api:jar:1.4:compile
> [DEBUG]org.apache.maven.doxia:doxia-decoration-model:jar:1.4:compile
> [DEBUG] org.codehaus.plexus:plexus-component-annotations:jar:1.6:compile
> [DEBUG]org.apache.maven.doxia:doxia-site-renderer:jar:1.4:compile
> [DEBUG] org.apache.maven.doxia:doxia-core:jar:1.4:compile
> [DEBUG] xerces:xercesImpl:jar:2.9.1:compile
> [DEBUG] commons-lang:commons-lang:jar:2.4:compile
> [DEBUG] org.apache.maven.doxia:doxia-module-xhtml:jar:1.4:compile
> [DEBUG] org.apache.maven.doxia:doxia-module-fml:jar:1.4:compile
> [DEBUG] org.codehaus.plexus:plexus-i18n:jar:1.0-beta-7:compile
> [DEBUG] org.codehaus.plexus:plexus-velocity:jar:1.1.7:compile
> [DEBUG] org.apache.velocity:velocity:jar:1.5:compile
> [DEBUG] oro:oro:jar:2.0.8:compile
> [DEBUG] org.apache.velocity:velocity-tools:jar:2.0:compile
> [DEBUG] commons-beanutils:commons-beanutils:jar:1.7.0:compile
> [DEBUG]
[jira] [Updated] (MPMD-244) Maven PMD plugin fails but no reason is given for the failure
[
https://issues.apache.org/jira/browse/MPMD-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel updated MPMD-244:
Fix Version/s: 3.9.0
> Maven PMD plugin fails but no reason is given for the failure
> -
>
> Key: MPMD-244
> URL: https://issues.apache.org/jira/browse/MPMD-244
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.8
> Environment: Maven 3.5.0
> PMD 5.8.1
> OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode)
> Fedora 23
>Reporter: Goldstein Lyor
>Priority: Blocker
> Fix For: 3.9.0
>
>
> After upgrading used PMD version from 5.6.1 to 5.8.1, Maven PMD plugin fails
> with no specific reason except {{Failed to process...}}. Furthermore, there
> is no PMD report or other file that indicates what is wrong.
> P.S. The file that it complains about passes without a problem for version
> 5.6.1
> {noformat}
> $ mvn -X -Dpmd.verbose=true clean install
> Maven home: /home/lyor/Software/apache-maven-3.5.0
> Java version: 1.8.0_91, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-2.b14.fc22.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.4.14-200.fc22.x86_64", arch: "amd64", family:
> "unix"
> .
> ..
> [INFO] --- maven-pmd-plugin:3.8:pmd (pmd) @ cb4-common-util ---
> [DEBUG] Dependency collection stats: {ConflictMarker.analyzeTime=1,
> ConflictMarker.markTime=0, ConflictMarker.nodeCount=280,
> ConflictIdSorter.graphTime=0, ConflictIdSorter.topsortTime=0,
> ConflictIdSorter.conflictIdCount=70, ConflictIdSorter.conflictIdCycleCount=0,
> ConflictResolver.totalTime=2, ConflictResolver.conflictItemCount=152,
> DefaultDependencyCollector.collectTime=38,
> DefaultDependencyCollector.transformTime=3}
> [DEBUG] org.apache.maven.plugins:maven-pmd-plugin:jar:3.8:
> [DEBUG]net.sourceforge.pmd:pmd-core:jar:5.8.1:runtime
> [DEBUG] com.beust:jcommander:jar:1.48:runtime
> [DEBUG] jaxen:jaxen:jar:1.1.6:runtime
> [DEBUG] net.java.dev.javacc:javacc:jar:5.0:runtime
> [DEBUG] net.sourceforge.saxon:saxon:jar:9.1.0.8:runtime
> [DEBUG] org.apache.commons:commons-lang3:jar:3.4:runtime
> [DEBUG] org.ow2.asm:asm:jar:5.0.4:runtime
> [DEBUG] com.google.code.gson:gson:jar:2.5:runtime
> [DEBUG] net.sourceforge.saxon:saxon:jar:dom:9.1.0.8:runtime
> [DEBUG]net.sourceforge.pmd:pmd-java:jar:5.8.1:runtime
> [DEBUG]net.sourceforge.pmd:pmd-javascript:jar:5.8.1:runtime
> [DEBUG] org.mozilla:rhino:jar:1.7.7:runtime
> [DEBUG]net.sourceforge.pmd:pmd-jsp:jar:5.8.1:runtime
> [DEBUG]org.apache.maven:maven-artifact:jar:2.2.1:compile
> [DEBUG]org.apache.maven:maven-model:jar:2.2.1:compile
> [DEBUG]org.apache.maven:maven-plugin-api:jar:2.2.1:compile
> [DEBUG]org.apache.maven:maven-project:jar:2.2.1:compile
> [DEBUG] org.apache.maven:maven-settings:jar:2.2.1:compile
> [DEBUG] org.apache.maven:maven-profile:jar:2.2.1:compile
> [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.2.1:compile
> [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.2.1:compile
> [DEBUG]
> backport-util-concurrent:backport-util-concurrent:jar:3.1:compile
> [DEBUG] org.apache.maven:maven-plugin-registry:jar:2.2.1:compile
> [DEBUG] org.codehaus.plexus:plexus-interpolation:jar:1.11:compile
> [DEBUG]
> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:compile
> [DEBUG] junit:junit:jar:3.8.1:compile
> [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:compile
> [DEBUG]org.apache.maven.doxia:doxia-sink-api:jar:1.4:compile
> [DEBUG] org.apache.maven.doxia:doxia-logging-api:jar:1.4:compile
> [DEBUG]org.apache.maven.doxia:doxia-decoration-model:jar:1.4:compile
> [DEBUG] org.codehaus.plexus:plexus-component-annotations:jar:1.6:compile
> [DEBUG]org.apache.maven.doxia:doxia-site-renderer:jar:1.4:compile
> [DEBUG] org.apache.maven.doxia:doxia-core:jar:1.4:compile
> [DEBUG] xerces:xercesImpl:jar:2.9.1:compile
> [DEBUG] commons-lang:commons-lang:jar:2.4:compile
> [DEBUG] org.apache.maven.doxia:doxia-module-xhtml:jar:1.4:compile
> [DEBUG] org.apache.maven.doxia:doxia-module-fml:jar:1.4:compile
> [DEBUG] org.codehaus.plexus:plexus-i18n:jar:1.0-beta-7:compile
> [DEBUG] org.codehaus.plexus:plexus-velocity:jar:1.1.7:compile
> [DEBUG] org.apache.velocity:velocity:jar:1.5:compile
> [DEBUG] oro:oro:jar:2.0.8:compile
> [DEBUG] org.apache.velocity:velocity-tools:jar:2.0:compile
> [DEBUG] commons-beanutils:commons-beanutils:jar:1.7.0:compile
> [DEBUG] commons-digester:commons-digester:jar:1.8:compile
> [DEBUG]
[jira] [Commented] (MPMD-244) Maven PMD plugin fails but no reason is given for the failure
[
https://issues.apache.org/jira/browse/MPMD-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16295369#comment-16295369
]
Andreas Dangel commented on MPMD-244:
-
With MPMD-246, we add the details of the processing errors to the report.
However, it would still be interesting to see the logs of PMD itself, when run
through m-pmd-p. This is indeed already possible.
1. Create a file {{logging.properties}} with the following content:
{noformat}
handlers=java.util.logging.ConsoleHandler
java.util.logging.ConsoleHandler.level=ALL
java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter
net.sourceforge.pmd.level = ALL
{noformat}
2. Run maven with additional options:
{{MAVEN_OPTS="-Djava.util.logging.config.file=logging.properties" mvn pmd:pmd}}
When this bug is fixed, the logs of PMD are integrated into the output of
maven. Thus, running maven with the debug flag (-X) enables the debug logging
of PMD, too.
> Maven PMD plugin fails but no reason is given for the failure
> -
>
> Key: MPMD-244
> URL: https://issues.apache.org/jira/browse/MPMD-244
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.8
> Environment: Maven 3.5.0
> PMD 5.8.1
> OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode)
> Fedora 23
>Reporter: Goldstein Lyor
>Priority: Blocker
>
> After upgrading used PMD version from 5.6.1 to 5.8.1, Maven PMD plugin fails
> with no specific reason except {{Failed to process...}}. Furthermore, there
> is no PMD report or other file that indicates what is wrong.
> P.S. The file that it complains about passes without a problem for version
> 5.6.1
> {noformat}
> $ mvn -X -Dpmd.verbose=true clean install
> Maven home: /home/lyor/Software/apache-maven-3.5.0
> Java version: 1.8.0_91, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-2.b14.fc22.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.4.14-200.fc22.x86_64", arch: "amd64", family:
> "unix"
> .
> ..
> [INFO] --- maven-pmd-plugin:3.8:pmd (pmd) @ cb4-common-util ---
> [DEBUG] Dependency collection stats: {ConflictMarker.analyzeTime=1,
> ConflictMarker.markTime=0, ConflictMarker.nodeCount=280,
> ConflictIdSorter.graphTime=0, ConflictIdSorter.topsortTime=0,
> ConflictIdSorter.conflictIdCount=70, ConflictIdSorter.conflictIdCycleCount=0,
> ConflictResolver.totalTime=2, ConflictResolver.conflictItemCount=152,
> DefaultDependencyCollector.collectTime=38,
> DefaultDependencyCollector.transformTime=3}
> [DEBUG] org.apache.maven.plugins:maven-pmd-plugin:jar:3.8:
> [DEBUG]net.sourceforge.pmd:pmd-core:jar:5.8.1:runtime
> [DEBUG] com.beust:jcommander:jar:1.48:runtime
> [DEBUG] jaxen:jaxen:jar:1.1.6:runtime
> [DEBUG] net.java.dev.javacc:javacc:jar:5.0:runtime
> [DEBUG] net.sourceforge.saxon:saxon:jar:9.1.0.8:runtime
> [DEBUG] org.apache.commons:commons-lang3:jar:3.4:runtime
> [DEBUG] org.ow2.asm:asm:jar:5.0.4:runtime
> [DEBUG] com.google.code.gson:gson:jar:2.5:runtime
> [DEBUG] net.sourceforge.saxon:saxon:jar:dom:9.1.0.8:runtime
> [DEBUG]net.sourceforge.pmd:pmd-java:jar:5.8.1:runtime
> [DEBUG]net.sourceforge.pmd:pmd-javascript:jar:5.8.1:runtime
> [DEBUG] org.mozilla:rhino:jar:1.7.7:runtime
> [DEBUG]net.sourceforge.pmd:pmd-jsp:jar:5.8.1:runtime
> [DEBUG]org.apache.maven:maven-artifact:jar:2.2.1:compile
> [DEBUG]org.apache.maven:maven-model:jar:2.2.1:compile
> [DEBUG]org.apache.maven:maven-plugin-api:jar:2.2.1:compile
> [DEBUG]org.apache.maven:maven-project:jar:2.2.1:compile
> [DEBUG] org.apache.maven:maven-settings:jar:2.2.1:compile
> [DEBUG] org.apache.maven:maven-profile:jar:2.2.1:compile
> [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.2.1:compile
> [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.2.1:compile
> [DEBUG]
> backport-util-concurrent:backport-util-concurrent:jar:3.1:compile
> [DEBUG] org.apache.maven:maven-plugin-registry:jar:2.2.1:compile
> [DEBUG] org.codehaus.plexus:plexus-interpolation:jar:1.11:compile
> [DEBUG]
> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:compile
> [DEBUG] junit:junit:jar:3.8.1:compile
> [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:compile
> [DEBUG]org.apache.maven.doxia:doxia-sink-api:jar:1.4:compile
> [DEBUG] org.apache.maven.doxia:doxia-logging-api:jar:1.4:compile
> [DEBUG]org.apache.maven.doxia:doxia-decoration-model:jar:1.4:compile
> [DEBUG] org.codehaus.plexus:plexus-component-annotations:jar:1.6:compile
> [DEBUG]org.apache.maven.doxia:doxia-site-renderer:jar:1.4:compile
> [DEBUG]
[jira] [Created] (MNG-6322) tag result in propertityPlaceHolder replace error
yongma created MNG-6322:
---
Summary: tag result in propertityPlaceHolder replace error
Key: MNG-6322
URL: https://issues.apache.org/jira/browse/MNG-6322
Project: Maven
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 3.3.9
Environment: spring 4.2.0.RELEASE,maven 3.3.9,mac os x 10.11,
jdk1.8,
Reporter: yongma
Attachments: ApplicationContext-mvc.xml, ApplicationContext.xml
4.0.0
FH
data-center-outchannel
war
0.0.2
FHM Maven Webapp
{color:red}http://maven.apache.org{color}
UTF-8
1.1
4.0.4.RELEASE
5.1.34
7.0.61
5.1.30
1.3.4-SNAPSHOT
true
src/main/resources/autogen/generatorConfig.xml
${project.build.directory}/generated-sources/mybatis-generator
2.5.3
2.2.2
0.5
3.4.6
2.0.0
dev
dev
product
product
org.springframework
spring-aop
${spring.version}
org.springframework
spring-aspects
${spring.version}
org.springframework
spring-beans
${spring.version}
org.springframework
spring-context
${spring.version}
org.springframework
spring-context-support
${spring.version}
org.springframework
spring-core
${spring.version}
org.springframework
spring-dao
2.0.8
org.springframework
spring-expression
${spring.version}
org.springframework
spring-jdbc
${spring.version}
org.springframework
spring-mock
2.0.8
org.springframework
spring-orm
${spring.version}
org.springframework
spring-test
${spring.version}
org.springframework
spring-tx
${spring.version}
org.springframework
spring-web
${spring.version}
org.springframework
spring-test
${spring.version}
org.springframework
spring-webmvc
${spring.version}
com.alibaba
dubbo
${dubbo.version}
org.springframework
spring
com.treefinance.commonservice
guid-service-facade
${uid-worker.version}
com.github.diamond
super-diamond-client
${super-diamond-client.version}
io.netty
netty-all
4.0.42.Final
com.google.guava
guava
20.0
[jira] [Created] (MNG-6321) tag result in propertityPlaceHolder replace error
yongma created MNG-6321:
---
Summary: tag result in propertityPlaceHolder replace error
Key: MNG-6321
URL: https://issues.apache.org/jira/browse/MNG-6321
Project: Maven
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 3.3.9
Environment: spring 4.2.0.RELEASE,maven 3.3.9,mac os x 10.11,
jdk1.8,
Reporter: yongma
Attachments: ApplicationContext-mvc.xml, ApplicationContext.xml
4.0.0
FH
data-center-outchannel
war
0.0.2
FHM Maven Webapp
{color:red}http://maven.apache.org{color}
UTF-8
1.1
4.0.4.RELEASE
5.1.34
7.0.61
5.1.30
1.3.4-SNAPSHOT
true
src/main/resources/autogen/generatorConfig.xml
${project.build.directory}/generated-sources/mybatis-generator
2.5.3
2.2.2
0.5
3.4.6
2.0.0
dev
dev
product
product
org.springframework
spring-aop
${spring.version}
org.springframework
spring-aspects
${spring.version}
org.springframework
spring-beans
${spring.version}
org.springframework
spring-context
${spring.version}
org.springframework
spring-context-support
${spring.version}
org.springframework
spring-core
${spring.version}
org.springframework
spring-dao
2.0.8
org.springframework
spring-expression
${spring.version}
org.springframework
spring-jdbc
${spring.version}
org.springframework
spring-mock
2.0.8
org.springframework
spring-orm
${spring.version}
org.springframework
spring-test
${spring.version}
org.springframework
spring-tx
${spring.version}
org.springframework
spring-web
${spring.version}
org.springframework
spring-test
${spring.version}
org.springframework
spring-webmvc
${spring.version}
com.alibaba
dubbo
${dubbo.version}
org.springframework
spring
com.treefinance.commonservice
guid-service-facade
${uid-worker.version}
com.github.diamond
super-diamond-client
${super-diamond-client.version}
io.netty
netty-all
4.0.42.Final
com.google.guava
guava
20.0
[jira] [Commented] (SUREFIRE-1453) Allow to specify non existant classes as "groups"
[
https://issues.apache.org/jira/browse/SUREFIRE-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16294817#comment-16294817
]
ASF GitHub Bot commented on SUREFIRE-1453:
--
Github user eolivelli commented on the issue:
https://github.com/apache/maven-surefire/pull/172
@Tibor17 I have added some IT.
I found a bug in JUnit48TestCategoriesIT, actually
testCategoriesABForkAlways did not call ".forkAlways()"
I have added an IT test for the case of no class matching the filter.
I have enhanced the testCategoriesAC in a way that it tests only using
Simple Class Names and not Fully Qualified Class Names.
In fact I saw that the original idea in was to let the use pass even
suffixes:
`if ( name.endsWith( enabled ) )`
But actually could not work because the 'pattern' had to be a resolvable
class name.
I did changed names in parameters in JUnit48TestCategoriesIT to make them
more "consistent"
> Allow to specify non existant classes as "groups"
> -
>
> Key: SUREFIRE-1453
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1453
> Project: Maven Surefire
> Issue Type: Improvement
> Components: classloading, Junit 4.x support, Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Enrico Olivelli
>Assignee: Tibor Digana
>Priority: Critical
> Fix For: 2.21.0.Jigsaw
>
>
> In a reactor project I would like to run only a subset of JUnit (4.12) tests
> tagged with @Category
> But the class which defines the category is not present in the dependency
> tree of every module.
> I get this error.
> I would like to simply skip these modules, maybe in conjunction with the
> failIfNoTest=false option
> {code:java}
> rg.apache.maven.surefire.util.SurefireReflectionException:
> java.lang.reflect.InvocationTargetException; nested exception is
> java.lang.reflect.InvocationTargetException: null
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Caused by: java.lang.RuntimeException: Unable to load category:
> magnews.testgroups.MinimumAcceptance
> at
> org.apache.maven.surefire.group.match.SingleGroupMatcher.loadGroupClasses(SingleGroupMatcher.java:134)
> at
> org.apache.maven.surefire.common.junit48.FilterFactory.createGroupFilter(FilterFactory.java:92)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreProvider.createJUnit48Filter(JUnitCoreProvider.java:183)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:115)
> ... 9 more
> Caused by: java.lang.ClassNotFoundException:
> magnews.testgroups.MinimumAcceptance
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.maven.surefire.group.match.SingleGroupMatcher.loadGroupClasses(SingleGroupMatcher.java:130)
> ... 12 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[GitHub] maven-surefire issue #172: [SUREFIRE-1453] Allow to specify non existant cla...
Github user eolivelli commented on the issue: https://github.com/apache/maven-surefire/pull/172 @Tibor17 I have added some IT. I found a bug in JUnit48TestCategoriesIT, actually testCategoriesABForkAlways did not call ".forkAlways()" I have added an IT test for the case of no class matching the filter. I have enhanced the testCategoriesAC in a way that it tests only using Simple Class Names and not Fully Qualified Class Names. In fact I saw that the original idea in was to let the use pass even suffixes: `if ( name.endsWith( enabled ) )` But actually could not work because the 'pattern' had to be a resolvable class name. I did changed names in parameters in JUnit48TestCategoriesIT to make them more "consistent" ---
