[jira] (MCHANGES-159) Publish the schema with the JAR file
[ https://jira.codehaus.org/browse/MCHANGES-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MCHANGES-159. Resolution: Not A Bug So based on the comments it is not a bug. Publish the schema with the JAR file Key: MCHANGES-159 URL: https://jira.codehaus.org/browse/MCHANGES-159 Project: Maven Changes Plugin Issue Type: Improvement Components: changes.xml Reporter: Trygve Laugstøl Use something like the build helper plugin to attach the generated .xsd to the build so that others can use the schema format. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCOMPILER-230) failOnError doesn't work when set inside an execution
[
https://jira.codehaus.org/browse/MCOMPILER-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352292#comment-352292
]
Karl-Heinz Marbaise commented on MCOMPILER-230:
---
Can you create a full working example project which shows the problem? Apart
from that it looks to me that you missing that maven-compiler-plugin execution
is done by the life-cycle which you don't influence, cause you added a
supplemental execution. Might this you problem?
failOnError doesn't work when set inside an execution
-
Key: MCOMPILER-230
URL: https://jira.codehaus.org/browse/MCOMPILER-230
Project: Maven Compiler Plugin
Issue Type: Bug
Affects Versions: 3.1
Environment: Linux Mint 17 Cinnamon
Reporter: Jonathan Ogilvie
I have the following plugin configuration in my pom:
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version${maven-compiler-plugin.version}/version
executions
execution
idannotation-processing/id
phasegenerate-sources/phase
goals
goalcompile/goal
/goals
configuration
proconly/proc
failOnErrorfalse/failOnError
/configuration
/execution
execution
idcompile-without-generated-source/id
phasecompile/phase
goals
goalcompile/goal
/goals
configuration
excludesexclude${project.build.dir}/generated-sources/**/exclude/excludes
procnone/proc
/configuration
/execution
/executions
configuration
source${java.version}/source
target${java.version}/target
proconly/proc
/configuration
/plugin
{code}
During the first execution, the build still fails on error. If I move
failOnError to the top-level pluginconfiguration node or define it on
the command line instead, the value sticks, but then I can't enable
failOnError for the second execution.
Of note: it seems like this works if I negate the whole thing and switch the
place I'm overriding. If I set it false at the top level configuration, and
true on an execution, I can get the desired behavior.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1071) LinkageError org.apache.maven.surefire.shade.org.apache.maven.shared.utils.io.IOUtil
[ https://jira.codehaus.org/browse/SUREFIRE-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352295#comment-352295 ] Julian Payne commented on SUREFIRE-1071: I will do that as soon as I get the new version - thanks for all your help. LinkageError org.apache.maven.surefire.shade.org.apache.maven.shared.utils.io.IOUtil Key: SUREFIRE-1071 URL: https://jira.codehaus.org/browse/SUREFIRE-1071 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Affects Versions: 2.16 Environment: Maven 3.1.1 and Maven 3.2.1 Reporter: Julian Payne Priority: Blocker Every so often when I am running the unit tests on a standard Maven project I get a linkage error: [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ asf-maven- plugin --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ asf-maven-plugi n --- [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ as f-maven-plugin --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory d:\rtc-workspace-asf-10\asf-build-sys tem\maven-plugins\asf-maven-plugin\src\test-resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ asf-mav en-plugin --- [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] --- maven-surefire-plugin:2.16:test (default-test) @ asf-maven-plugin --- [INFO] Surefire report directory: d:\rtc-workspace-asf-10\asf-build-system\maven -plugins\asf-maven-plugin\target\surefire-reports --- T E S T S --- Exception in thread Thread-7 java.lang.LinkageError: org.apache.maven.surefire .shade.org.apache.maven.shared.utils.io.IOUtil at java.lang.ClassLoader.defineClassImpl(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:306) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:14 3) at java.net.URLClassLoader.defineClass(URLClassLoader.java:700) at java.net.URLClassLoader.access$400(URLClassLoader.java:81) at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1148) at java.security.AccessController.doPrivileged(AccessController.java:366 ) at java.net.URLClassLoader.findClass(URLClassLoader.java:583) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(Cl assRealm.java:389) at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass( SelfFirstStrategy.java:42) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadCl ass(ClassRealm.java:259) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm .java:235) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm .java:227) at org.apache.maven.surefire.shade.org.apache.maven.shared.utils.cli.Str eamPumper.run(StreamPumper.java:95) Terminate batch job (Y/N)? y This error is not reproducible but I am getting it from time to time when running maven on the command line as well as in my Jenkins jobs that are running Maven jobs. When this LinkageError occurs the maven run blocks. This is what I have in the effective pom for the run above that blocked: plugin artifactIdmaven-surefire-plugin/artifactId version2.16/version inheritedtrue/inherited configuration argLine-Xms768m -Xmx768m/argLine trimStackTracetrue/trimStackTrace childDelegationfalse/childDelegation classpathDependencyExcludes classpathDependencyExcludeorg.dom4j:dom4j/classpathDependencyExclude /classpathDependencyExcludes /configuration /plugin Thanks, Julian Payne -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1096) Fork test for TestNG with smlsuite
Michal Bocek created SUREFIRE-1096: -- Summary: Fork test for TestNG with smlsuite Key: SUREFIRE-1096 URL: https://jira.codehaus.org/browse/SUREFIRE-1096 Project: Maven Surefire Issue Type: Bug Components: TestNG support Affects Versions: 2.17, 2.16, 2.15, 2.14 Reporter: Michal Bocek When i setup surefire for forking tests via: forkCount3/forkCount reuseForkstrue/reuseForks parallelfalse/parallel}} And i'm using TestNG provider with xml suite definition: suiteXmlFiles suiteXmlFilesuite.xml/suiteXmlFile /suiteXmlFiles I'm getting exception: Caused by: java.lang.ClassCastException: java.io.File cannot be cast to java.lang.Class at org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkOnceMultiple(ForkStarter.java:201) at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:160) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:806) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:701) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:629) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1096) Fork test for TestNG with xmlsuite
[ https://jira.codehaus.org/browse/SUREFIRE-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Bocek updated SUREFIRE-1096: --- Summary: Fork test for TestNG with xmlsuite (was: Fork test for TestNG with smlsuite) Fork test for TestNG with xmlsuite -- Key: SUREFIRE-1096 URL: https://jira.codehaus.org/browse/SUREFIRE-1096 Project: Maven Surefire Issue Type: Bug Components: TestNG support Affects Versions: 2.14, 2.15, 2.16, 2.17 Reporter: Michal Bocek When i setup surefire for forking tests via: forkCount3/forkCount reuseForkstrue/reuseForks parallelfalse/parallel}} And i'm using TestNG provider with xml suite definition: suiteXmlFiles suiteXmlFilesuite.xml/suiteXmlFile /suiteXmlFiles I'm getting exception: Caused by: java.lang.ClassCastException: java.io.File cannot be cast to java.lang.Class at org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkOnceMultiple(ForkStarter.java:201) at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:160) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:806) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:701) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:629) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1096) ClassCastException: Fork test for TestNG with xmlsuite
[ https://jira.codehaus.org/browse/SUREFIRE-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Bocek updated SUREFIRE-1096: --- Description: When i setup surefire for forking tests via: forkCount3/forkCount reuseForkstrue/reuseForks parallelfalse/parallel And i'm using TestNG provider with xml suite definition: suiteXmlFiles suiteXmlFilesuite.xml/suiteXmlFile /suiteXmlFiles I'm getting exception: Caused by: java.lang.ClassCastException: java.io.File cannot be cast to java.lang.Class at org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkOnceMultiple(ForkStarter.java:201) at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:160) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:806) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:701) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:629) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) was: When i setup surefire for forking tests via: forkCount3/forkCount reuseForkstrue/reuseForks parallelfalse/parallel}} And i'm using TestNG provider with xml suite definition: suiteXmlFiles suiteXmlFilesuite.xml/suiteXmlFile /suiteXmlFiles I'm getting exception: Caused by: java.lang.ClassCastException: java.io.File cannot be cast to java.lang.Class at org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkOnceMultiple(ForkStarter.java:201) at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:160) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:806) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:701) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:629) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) ClassCastException: Fork test for TestNG with xmlsuite -- Key: SUREFIRE-1096 URL: https://jira.codehaus.org/browse/SUREFIRE-1096 Project: Maven Surefire Issue Type: Bug Components: TestNG support Affects Versions: 2.14, 2.15, 2.16, 2.17 Reporter: Michal Bocek When i setup surefire for forking tests via: forkCount3/forkCount reuseForkstrue/reuseForks parallelfalse/parallel And i'm using TestNG provider with xml suite definition: suiteXmlFiles suiteXmlFilesuite.xml/suiteXmlFile /suiteXmlFiles I'm getting exception: Caused by: java.lang.ClassCastException: java.io.File cannot be cast to java.lang.Class at org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkOnceMultiple(ForkStarter.java:201) at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:160) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:806) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:701) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:629) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1096) ClassCastException: Fork test for TestNG with xmlsuite
[ https://jira.codehaus.org/browse/SUREFIRE-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Bocek updated SUREFIRE-1096: --- Summary: ClassCastException: Fork test for TestNG with xmlsuite (was: Fork test for TestNG with xmlsuite) ClassCastException: Fork test for TestNG with xmlsuite -- Key: SUREFIRE-1096 URL: https://jira.codehaus.org/browse/SUREFIRE-1096 Project: Maven Surefire Issue Type: Bug Components: TestNG support Affects Versions: 2.14, 2.15, 2.16, 2.17 Reporter: Michal Bocek When i setup surefire for forking tests via: forkCount3/forkCount reuseForkstrue/reuseForks parallelfalse/parallel}} And i'm using TestNG provider with xml suite definition: suiteXmlFiles suiteXmlFilesuite.xml/suiteXmlFile /suiteXmlFiles I'm getting exception: Caused by: java.lang.ClassCastException: java.io.File cannot be cast to java.lang.Class at org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkOnceMultiple(ForkStarter.java:201) at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:160) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:806) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:701) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:629) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1096) ClassCastException: Fork test for TestNG with xmlsuite
[ https://jira.codehaus.org/browse/SUREFIRE-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352296#comment-352296 ] Michal Bocek commented on SUREFIRE-1096: After quick investigation it looks like when surefire trying to get the suite collection in ForkStarter class it expected collection of classes but TestNgProvider will generate in TestNGXmlTestSuite collection of suite files. ClassCastException: Fork test for TestNG with xmlsuite -- Key: SUREFIRE-1096 URL: https://jira.codehaus.org/browse/SUREFIRE-1096 Project: Maven Surefire Issue Type: Bug Components: TestNG support Affects Versions: 2.14, 2.15, 2.16, 2.17 Reporter: Michal Bocek When i setup surefire for forking tests via: forkCount3/forkCount reuseForkstrue/reuseForks parallelfalse/parallel And i'm using TestNG provider with xml suite definition: suiteXmlFiles suiteXmlFilesuite.xml/suiteXmlFile /suiteXmlFiles I'm getting exception: Caused by: java.lang.ClassCastException: java.io.File cannot be cast to java.lang.Class at org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkOnceMultiple(ForkStarter.java:201) at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:160) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:806) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:701) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:629) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1096) ClassCastException: Fork test for TestNG with xmlsuite
[ https://jira.codehaus.org/browse/SUREFIRE-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352297#comment-352297 ] Michal Bocek commented on SUREFIRE-1096: Can be connected with SUREFIRE-463 ClassCastException: Fork test for TestNG with xmlsuite -- Key: SUREFIRE-1096 URL: https://jira.codehaus.org/browse/SUREFIRE-1096 Project: Maven Surefire Issue Type: Bug Components: TestNG support Affects Versions: 2.14, 2.15, 2.16, 2.17 Reporter: Michal Bocek When i setup surefire for forking tests via: forkCount3/forkCount reuseForkstrue/reuseForks parallelfalse/parallel And i'm using TestNG provider with xml suite definition: suiteXmlFiles suiteXmlFilesuite.xml/suiteXmlFile /suiteXmlFiles I'm getting exception: Caused by: java.lang.ClassCastException: java.io.File cannot be cast to java.lang.Class at org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkOnceMultiple(ForkStarter.java:201) at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:160) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:806) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:701) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:629) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCOMPILER-231) Make compiler output paths relative to the project or module root
[ https://jira.codehaus.org/browse/MCOMPILER-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352300#comment-352300 ] Karl-Heinz Marbaise commented on MCOMPILER-231: --- Can you give an concrete example what you see in contradiction to what you like to see? Make compiler output paths relative to the project or module root - Key: MCOMPILER-231 URL: https://jira.codehaus.org/browse/MCOMPILER-231 Project: Maven Compiler Plugin Issue Type: Improvement Reporter: David M. Lloyd Priority: Minor Using the latest 3.2-SNAPSHOT as of the time of this report, all compiler messages which start with a file name are printing the absolute file name. There should be a filter step which checks a message to see if it starts with the project or module path, and if so, makes the path relative, to reduce screen real-estate consumption. It seems to me that the compiler plugin had this capability at some point in the past (though maybe I've just dreamed it)? I suppose it's even possible that if it did regress, that it was one of my patches that did it (though I don't recall seeing this kind of code anywhere). -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-420) Implements RFC 6585 (return code 429: too many requests)
Olivier Lamy created WAGON-420: -- Summary: Implements RFC 6585 (return code 429: too many requests) Key: WAGON-420 URL: https://jira.codehaus.org/browse/WAGON-420 Project: Maven Wagon Issue Type: New Feature Components: wagon-http Reporter: Olivier Lamy -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-420) Implements RFC 6585 (return code 429: too many requests)
[ https://jira.codehaus.org/browse/WAGON-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated WAGON-420: --- Fix Version/s: 2.7 Implements RFC 6585 (return code 429: too many requests) Key: WAGON-420 URL: https://jira.codehaus.org/browse/WAGON-420 Project: Maven Wagon Issue Type: New Feature Components: wagon-http Reporter: Olivier Lamy Assignee: Olivier Lamy Fix For: 2.7 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-420) Implements RFC 6585 (return code 429: too many requests)
[ https://jira.codehaus.org/browse/WAGON-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy reassigned WAGON-420: -- Assignee: Olivier Lamy Implements RFC 6585 (return code 429: too many requests) Key: WAGON-420 URL: https://jira.codehaus.org/browse/WAGON-420 Project: Maven Wagon Issue Type: New Feature Components: wagon-http Reporter: Olivier Lamy Assignee: Olivier Lamy Fix For: 2.7 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCOMPILER-231) Make compiler output paths relative to the project or module root
[
https://jira.codehaus.org/browse/MCOMPILER-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352304#comment-352304
]
David M. Lloyd commented on MCOMPILER-231:
--
Sure, for example:
{noformat}
[ERROR]
/home/david/src/java/jboss-mgmt/tool/src/main/java/org/wildfly/core/management/processor/model/value/MapAttributeValueTypeDescription.java:[31,12]
org.wildfly.core.management.processor.model.value.MapAttributeValueTypeDescription.Builder
is not abstract and does not override abstract method getName() in
org.wildfly.core.management.processor.model.value.AttributeValueTypeDescription.Builder
{noformat}
Could automatically be rewritten as:
{noformat}
[ERROR]
tool/src/main/java/org/wildfly/core/management/processor/model/value/MapAttributeValueTypeDescription.java:[31,12]
org.wildfly.core.management.processor.model.value.MapAttributeValueTypeDescription.Builder
is not abstract and does not override abstract method getName() in
org.wildfly.core.management.processor.model.value.AttributeValueTypeDescription.Builder
{noformat}
or even:
{noformat}
[ERROR]
src/main/java/org/wildfly/core/management/processor/model/value/MapAttributeValueTypeDescription.java:[31,12]
org.wildfly.core.management.processor.model.value.MapAttributeValueTypeDescription.Builder
is not abstract and does not override abstract method getName() in
org.wildfly.core.management.processor.model.value.AttributeValueTypeDescription.Builder
{noformat}
Make compiler output paths relative to the project or module root
-
Key: MCOMPILER-231
URL: https://jira.codehaus.org/browse/MCOMPILER-231
Project: Maven Compiler Plugin
Issue Type: Improvement
Reporter: David M. Lloyd
Priority: Minor
Using the latest 3.2-SNAPSHOT as of the time of this report, all compiler
messages which start with a file name are printing the absolute file name.
There should be a filter step which checks a message to see if it starts with
the project or module path, and if so, makes the path relative, to reduce
screen real-estate consumption.
It seems to me that the compiler plugin had this capability at some point in
the past (though maybe I've just dreamed it)? I suppose it's even possible
that if it did regress, that it was one of my patches that did it (though I
don't recall seeing this kind of code anywhere).
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MANT-77) Upgrade ant dep to 1.8.1
[ https://jira.codehaus.org/browse/MANT-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MANT-77: Fix Version/s: 2.4 Upgrade ant dep to 1.8.1 Key: MANT-77 URL: https://jira.codehaus.org/browse/MANT-77 Project: Maven Ant Plugin Issue Type: Task Affects Versions: 2.4 Reporter: Karl-Heinz Marbaise Priority: Minor Fix For: 2.4 Upgrade ant dependency to 1.8.1 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MANT-77) Upgrade ant dep to 1.8.1
Karl-Heinz Marbaise created MANT-77: --- Summary: Upgrade ant dep to 1.8.1 Key: MANT-77 URL: https://jira.codehaus.org/browse/MANT-77 Project: Maven Ant Plugin Issue Type: Task Affects Versions: 2.4 Reporter: Karl-Heinz Marbaise Priority: Minor Upgrade ant dependency to 1.8.1 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MANT-77) Upgrade ant dep to 1.8.1
[ https://jira.codehaus.org/browse/MANT-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MANT-77. --- Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1622545|http://svn.apache.org/r1622545]. Upgrade ant dep to 1.8.1 Key: MANT-77 URL: https://jira.codehaus.org/browse/MANT-77 Project: Maven Ant Plugin Issue Type: Task Affects Versions: 2.4 Reporter: Karl-Heinz Marbaise Assignee: Karl-Heinz Marbaise Priority: Minor Fix For: 2.4 Upgrade ant dependency to 1.8.1 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MANTRUN-173) maven-antrun-plugin not forward compatible with maven 3.
[
https://jira.codehaus.org/browse/MANTRUN-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MANTRUN-173.
---
Resolution: Cannot Reproduce
Assignee: Karl-Heinz Marbaise
Unfortunately i can't reproduce the issue. So i close it. If you have any
objections don't hesitate to reopen it.
maven-antrun-plugin not forward compatible with maven 3.
Key: MANTRUN-173
URL: https://jira.codehaus.org/browse/MANTRUN-173
Project: Maven Antrun Plugin
Issue Type: Bug
Affects Versions: 1.7
Environment: Windows 7, Maven 3, Java 1.6
Reporter: Peter Sherwood
Assignee: Karl-Heinz Marbaise
Priority: Critical
Fix For: 1.8
Attachments: MANTRUN173b-o.a.m.p.mmap.patch,
MANTRUN173-o.a.m.p.mmap.patch, mavenerror.txt
In some environments we do not have a Nexus style repository and so to make
an out of the box build cycle we use antrun to install a jar into a local
repository. This works absolutely fine with no exceptions in Maven 2.2.1 in
the same environment mentioned above. Moving directly to Maven 3 the build
does not work and records the following exception:
{noformat}
Caused by: java.lang.NoSuchMethodError:
org/apache/maven/settings/RuntimeInfo.init(Lorg/apache/maven/settings/Settings;)V
at
org.apache.maven.artifact.ant.AbstractArtifactTask.readSettings(AbstractArtifactTask.java:382)
at
org.apache.maven.artifact.ant.AbstractArtifactTask.loadSettings(AbstractArtifactTask.java:311)
at
org.apache.maven.artifact.ant.AbstractArtifactTask.initSettings(AbstractArtifactTask.java:278)
at
org.apache.maven.artifact.ant.AbstractArtifactTask.getSettings(AbstractArtifactTask.java:223)
at
org.apache.maven.artifact.ant.AbstractArtifactTask.getDefaultLocalRepository(AbstractArtifactTask.java:212)
at
org.apache.maven.artifact.ant.AbstractArtifactTask.getLocalRepository(AbstractArtifactTask.java:700)
at
org.apache.maven.artifact.ant.AbstractArtifactTask.createLocalArtifactRepository(AbstractArtifactTask.java:110)
at org.apache.maven.artifact.ant.Pom.getMavenProject(Pom.java:272)
at org.apache.maven.artifact.ant.Pom.setVersion(Pom.java:570)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at
org.apache.tools.ant.IntrospectionHelper$AttributeSetter.setObject(IntrospectionHelper.java:1498)
at
org.apache.tools.ant.IntrospectionHelper.setAttribute(IntrospectionHelper.java:405)
... 38 more
{noformat}
My POM is as follows and has been cut down to show the problem only.
{code:xml}
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;
xmlns:artifact=antlib:org.apache.maven.artifact.ant
modelVersion4.0.0/modelVersion
groupIdMavenAntTest/groupId
artifactIdMavenAntTest/artifactId
version1.0/version
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
version1.7/version
executions
execution
phaseinitialize/phase
configuration
target
xmlns:artifact=antlib:org.apache.maven.artifact.ant
path id=maven-ant-tasks.classpath
path=${settings.localRepository}${file.separator}org${file.separator}apache${file.separator}maven${file.separator}maven-ant-tasks${file.separator}2.1.3${file.separator}maven-ant-tasks-2.1.3.jar
/
typedef
resource=org/apache/maven/artifact/ant/antlib.xml
uri=antlib:org.apache.maven.artifact.ant
classpathref=maven-ant-tasks.classpath /
taskdef
resource=net/sf/antcontrib/antcontrib.properties
classpathref=maven.plugin.classpath /
artifact:pom id=saxonInstall
groupId=net.sf.saxon artifactId=saxon
version=9.3.0.5 name=Saxon
XSLT Parser
/artifact:pom
if
available
[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project
[
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352321#comment-352321
]
Karl-Heinz Marbaise commented on MDEP-451:
--
The fix for the problem is easy:
{code}
Index:
src/main/java/org/apache/maven/plugin/dependency/fromConfiguration/CopyMojo.java
===
---
src/main/java/org/apache/maven/plugin/dependency/fromConfiguration/CopyMojo.java
(revision 1622302)
+++
src/main/java/org/apache/maven/plugin/dependency/fromConfiguration/CopyMojo.java
(working copy)
@@ -37,7 +37,7 @@
* @version $Id$
* @since 1.0
*/
-@Mojo( name = copy, defaultPhase = LifecyclePhase.PROCESS_SOURCES,
requiresProject = false, threadSafe = true )
+@Mojo( name = copy, defaultPhase = LifecyclePhase.PROCESS_SOURCES,
requiresProject = true, threadSafe = true )
public class CopyMojo
extends AbstractFromConfigurationMojo
{code}
The problem is that dependency:copy goal is intended to work outside the life
cycle and outside off the project context. So i don't see a chance to change
the current behaviour. But what i could imagine is to create a separate goal
like copy-with-project.
Regression: mvn dependency:copy doesn't run under maven 3.x multi-module
project
Key: MDEP-451
URL: https://jira.codehaus.org/browse/MDEP-451
Project: Maven Dependency Plugin
Issue Type: Bug
Components: copy
Affects Versions: 2.8
Environment: All
Reporter: Lenny Primak
Priority: Critical
Attachments: deptest.tar
I have a muldi-module project,
running mvn dependency:copy on root project just runs
on root project without recursing into the modules.
This works under maven 3.0.3 but doesn't run at all in the
current 3.2.2 version of maven
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project
[
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352321#comment-352321
]
Karl-Heinz Marbaise edited comment on MDEP-451 at 9/4/14 5:10 PM:
--
The fix for the problem is easy:
{code}
Index:
src/main/java/org/apache/maven/plugin/dependency/fromConfiguration/CopyMojo.java
===
---
src/main/java/org/apache/maven/plugin/dependency/fromConfiguration/CopyMojo.java
(revision 1622302)
+++
src/main/java/org/apache/maven/plugin/dependency/fromConfiguration/CopyMojo.java
(working copy)
@@ -37,7 +37,7 @@
* @version $Id$
* @since 1.0
*/
-@Mojo( name = copy, defaultPhase = LifecyclePhase.PROCESS_SOURCES,
requiresProject = false, threadSafe = true )
+@Mojo( name = copy, defaultPhase = LifecyclePhase.PROCESS_SOURCES,
requiresProject = true, threadSafe = true )
public class CopyMojo
extends AbstractFromConfigurationMojo
{code}
The problem is that dependency:copy goal is intended to work outside the life
cycle and outside off the project context. So i don't see a chance to change
the current behaviour. But what i could imagine is to create a separate goal
like copy-with-project.
Furthermore i have checked to run dependency:copy on the root of the project
and i don't have any difference between Maven 2.2.1, 3.0.3, 3.0.5, 3.1.1,
3.2.1, 3.2.2 and 3.2.3...in all versions the same behaviour. Have you allways
specified the same version of maven-dependency-plugin ?
was (Author: khmarbaise):
The fix for the problem is easy:
{code}
Index:
src/main/java/org/apache/maven/plugin/dependency/fromConfiguration/CopyMojo.java
===
---
src/main/java/org/apache/maven/plugin/dependency/fromConfiguration/CopyMojo.java
(revision 1622302)
+++
src/main/java/org/apache/maven/plugin/dependency/fromConfiguration/CopyMojo.java
(working copy)
@@ -37,7 +37,7 @@
* @version $Id$
* @since 1.0
*/
-@Mojo( name = copy, defaultPhase = LifecyclePhase.PROCESS_SOURCES,
requiresProject = false, threadSafe = true )
+@Mojo( name = copy, defaultPhase = LifecyclePhase.PROCESS_SOURCES,
requiresProject = true, threadSafe = true )
public class CopyMojo
extends AbstractFromConfigurationMojo
{code}
The problem is that dependency:copy goal is intended to work outside the life
cycle and outside off the project context. So i don't see a chance to change
the current behaviour. But what i could imagine is to create a separate goal
like copy-with-project.
Regression: mvn dependency:copy doesn't run under maven 3.x multi-module
project
Key: MDEP-451
URL: https://jira.codehaus.org/browse/MDEP-451
Project: Maven Dependency Plugin
Issue Type: Bug
Components: copy
Affects Versions: 2.8
Environment: All
Reporter: Lenny Primak
Priority: Critical
Attachments: deptest.tar
I have a muldi-module project,
running mvn dependency:copy on root project just runs
on root project without recursing into the modules.
This works under maven 3.0.3 but doesn't run at all in the
current 3.2.2 version of maven
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (WAGON-420) Implements RFC 6585 (return code 429: too many requests)
[ https://jira.codehaus.org/browse/WAGON-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed WAGON-420. -- Resolution: Fixed pr https://github.com/apache/maven-wagon/pull/15 merged Implements RFC 6585 (return code 429: too many requests) Key: WAGON-420 URL: https://jira.codehaus.org/browse/WAGON-420 Project: Maven Wagon Issue Type: New Feature Components: wagon-http Reporter: Olivier Lamy Assignee: Olivier Lamy Fix For: 2.7 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-407) wagon-maven-plugin ITs fail with missing class: org.apache.commons.io.IOUtils
[ https://jira.codehaus.org/browse/WAGON-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352325#comment-352325 ] Dan Tran commented on WAGON-407: Oliver, any chance this would get into 2.7 release? wagon-maven-plugin ITs fail with missing class: org.apache.commons.io.IOUtils - Key: WAGON-407 URL: https://jira.codehaus.org/browse/WAGON-407 Project: Maven Wagon Issue Type: Bug Components: wagon-http Reporter: Stuart McCulloch See http://www.mail-archive.com/users@maven.apache.org/msg132210.html thread -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MINDEXER-91) Add a Spring based example
[ https://jira.codehaus.org/browse/MINDEXER-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352326#comment-352326 ] Olivier Lamy commented on MINDEXER-91: -- merged. Thanks! Add a Spring based example -- Key: MINDEXER-91 URL: https://jira.codehaus.org/browse/MINDEXER-91 Project: Maven Indexer Issue Type: Test Reporter: Martin Todorov Assignee: Martin Todorov Fix For: 6.0 As discussed with Tamas, this will require extracting the currently existing example module into a separate one and adding a new one under maven-indexer-examples, producing the following modules: - indexer-examples-basic - indexer-examples-spring -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352327#comment-352327 ] Lenny Primak commented on MDEP-451: --- Yes, the maven dependency plugin version remained constant. The reason that I noticed the breakage is because my build started failing when upgrading maven, so the behavior definitely changed. I would gladly use a new goal if the change to existing one breaks things. Thanks Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Priority: Critical Attachments: deptest.tar I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
