[jira] [Commented] (MCOMPILER-431) Support java 15
[ https://issues.apache.org/jira/browse/MCOMPILER-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17198221#comment-17198221 ] David J. M. Karlsen commented on MCOMPILER-431: --- Oh noes - rookie mistake! I had forgot to change the buildpipeline JDK selection. Sorry about the noise. It works perfectly fine with JDK 15! > Support java 15 > > > Key: MCOMPILER-431 > URL: https://issues.apache.org/jira/browse/MCOMPILER-431 > Project: Maven Compiler Plugin > Issue Type: Improvement >Affects Versions: 3.8.1 >Reporter: David J. M. Karlsen >Priority: Major > > Fails with > error: release version 15 not supported > for maven.compiler.source/target = 15 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MCOMPILER-431) Support java 15
David J. M. Karlsen created MCOMPILER-431: - Summary: Support java 15 Key: MCOMPILER-431 URL: https://issues.apache.org/jira/browse/MCOMPILER-431 Project: Maven Compiler Plugin Issue Type: Improvement Affects Versions: 3.8.1 Reporter: David J. M. Karlsen Fails with error: release version 15 not supported for maven.compiler.source/target = 15 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MDEP-613) Analyze failed: Unsupported class file major version 55 (Java 11)
[
https://issues.apache.org/jira/browse/MDEP-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17007824#comment-17007824
]
David J. M. Karlsen commented on MDEP-613:
--
It's been a while - could 3.1.2 be released?
> Analyze failed: Unsupported class file major version 55 (Java 11)
> -
>
> Key: MDEP-613
> URL: https://issues.apache.org/jira/browse/MDEP-613
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 3.1.0
>Reporter: Mincong Huang
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Labels: up-for-grabs
> Fix For: 3.1.2
>
> Attachments: log.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Class file of major version 55 (Java 11) is not yet supported by Maven
> Dependency Plugin. So when running command {{mvn dependency:analysis}} on
> classes created by Java 11, il failed. See {{log.txt}} for the full log trace.
> This is caused by ASM, which does not support major version 55 (Java 11) yet.
> However, their HEAD contains already the solution, so using the SNAPSHOT
> version will work. This support will be included in the next release 6.2.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MCOMPILER-339) Skip --release flag if compilerVersion is lower than 1.9
[
https://issues.apache.org/jira/browse/MCOMPILER-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David J. M. Karlsen updated MCOMPILER-339:
--
Description:
usecase: I have a build which is jdk10 by default, declared via the parent-pom.
However, one submodule must be compiled and run with java8. I had hoped to get
this working, by setting:
{noformat}
8
1.8
1.8
1.8
{noformat}
but it will fail with
{noformat}
Caused by: java.lang.IllegalArgumentException: invalid flag:
--release*11:53:45* at com.sun.tools.javac.api.JavacTool.processOptions
(JavacTool.java:206)*11:53:45* at com.sun.tools.javac.api.JavacTool.getTask
(JavacTool.java:156)*11:53:45* at com.sun.tools.javac.api.JavacTool.getTask
(JavacTool.java:107)*11:53:45* at com.sun.tools.javac.api.JavacTool.getTask
(JavacTool.java:64)*11:53:45* at
org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess
(JavaxToolsCompiler.java:125)*11:53:45* at
org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile
(JavacCompiler.java:174)*11:53:45* at
org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute
(AbstractCompilerMojo.java:1075)*11:53:45* at
org.apache.maven.plugin.compiler.TestCompilerMojo.execute
(TestCompilerMojo.java:176)*11:53:45* at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:134)*11:53:45* at
org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:208)*11:53:45* at
org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:154)*11:53:45* at
org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:146)*11:53:45* at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)*11:53:45* at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:200)*11:53:45* at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:196)*11:53:45* at
java.util.concurrent.FutureTask.run (FutureTask.java:266)*11:53:45* at
java.util.concurrent.Executors$RunnableAdapter.call
(Executors.java:511)*11:53:45* at java.util.concurrent.FutureTask.run
(FutureTask.java:266)*11:53:45* at
java.util.concurrent.ThreadPoolExecutor.runWorker
(ThreadPoolExecutor.java:1149)*11:53:45* at
java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:624)*11:53:45* at java.lang.Thread.run
(Thread.java:748)
{noformat}
If the release flag could only be enabled for compiler versions supporting it
it would be easier to juggle the build.
was:
usecase: I have a build which is jdk10 by default, declared via the parent-pom.
However, one submodule must be compiled and run with java8. I had hoped to get
this working, by setting:
{noformat}
8
1.8
1.8
1.8
{noformat}
but it will fail with
{noformat}
Caused by: java.lang.IllegalArgumentException: invalid flag:
--release*11:53:45* at com.sun.tools.javac.api.JavacTool.processOptions
(JavacTool.java:206)*11:53:45* at com.sun.tools.javac.api.JavacTool.getTask
(JavacTool.java:156)*11:53:45* at com.sun.tools.javac.api.JavacTool.getTask
(JavacTool.java:107)*11:53:45* at com.sun.tools.javac.api.JavacTool.getTask
(JavacTool.java:64)*11:53:45* at
org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess
(JavaxToolsCompiler.java:125)*11:53:45* at
org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile
(JavacCompiler.java:174)*11:53:45* at
org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute
(AbstractCompilerMojo.java:1075)*11:53:45* at
org.apache.maven.plugin.compiler.TestCompilerMojo.execute
(TestCompilerMojo.java:176)*11:53:45* at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:134)*11:53:45* at
org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:208)*11:53:45* at
org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:154)*11:53:45* at
org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:146)*11:53:45* at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)*11:53:45* at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:200)*11:53:45* at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:196)*11:53:45* at
java.util.concurrent.FutureTask.run (FutureTask.java:266)*11:53:45* at
java.util.concurrent.Executors$RunnableAdapter.call
(Executors.java:511)*11:53:45* at java.util.concurrent.FutureTask.run
[jira] [Updated] (MCOMPILER-339) Skip --release flag if compilerVersion is lower than 1.9
[
https://issues.apache.org/jira/browse/MCOMPILER-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David J. M. Karlsen updated MCOMPILER-339:
--
Description:
usecase: I have a build which is jdk10 by default, declared via the parent-pom.
However, one submodule must be compiled and run with java8. I had hoped to get
this working, by setting:
{noformat}
8
1.8
1.8
1.8
{noformat}
but it will fail with
{noformat}
Caused by: java.lang.IllegalArgumentException: invalid flag:
--release*11:53:45* at com.sun.tools.javac.api.JavacTool.processOptions
(JavacTool.java:206)*11:53:45* at com.sun.tools.javac.api.JavacTool.getTask
(JavacTool.java:156)*11:53:45* at com.sun.tools.javac.api.JavacTool.getTask
(JavacTool.java:107)*11:53:45* at com.sun.tools.javac.api.JavacTool.getTask
(JavacTool.java:64)*11:53:45* at
org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess
(JavaxToolsCompiler.java:125)*11:53:45* at
org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile
(JavacCompiler.java:174)*11:53:45* at
org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute
(AbstractCompilerMojo.java:1075)*11:53:45* at
org.apache.maven.plugin.compiler.TestCompilerMojo.execute
(TestCompilerMojo.java:176)*11:53:45* at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:134)*11:53:45* at
org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:208)*11:53:45* at
org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:154)*11:53:45* at
org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:146)*11:53:45* at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)*11:53:45* at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:200)*11:53:45* at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:196)*11:53:45* at
java.util.concurrent.FutureTask.run (FutureTask.java:266)*11:53:45* at
java.util.concurrent.Executors$RunnableAdapter.call
(Executors.java:511)*11:53:45* at java.util.concurrent.FutureTask.run
(FutureTask.java:266)*11:53:45* at
java.util.concurrent.ThreadPoolExecutor.runWorker
(ThreadPoolExecutor.java:1149)*11:53:45* at
java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:624)*11:53:45* at java.lang.Thread.run
(Thread.java:748)
{noformat}
> Skip --release flag if compilerVersion is lower than 1.9
>
>
> Key: MCOMPILER-339
> URL: https://issues.apache.org/jira/browse/MCOMPILER-339
> Project: Maven Compiler Plugin
> Issue Type: Improvement
>Affects Versions: 3.7.0
>Reporter: David J. M. Karlsen
>Priority: Major
>
> usecase: I have a build which is jdk10 by default, declared via the
> parent-pom.
> However, one submodule must be compiled and run with java8. I had hoped to
> get this working, by setting:
> {noformat}
>
> 8
> 1.8
> 1.8
> 1.8
>
> {noformat}
>
> but it will fail with
> {noformat}
> Caused by: java.lang.IllegalArgumentException: invalid flag:
> --release*11:53:45* at com.sun.tools.javac.api.JavacTool.processOptions
> (JavacTool.java:206)*11:53:45* at
> com.sun.tools.javac.api.JavacTool.getTask (JavacTool.java:156)*11:53:45*
> at com.sun.tools.javac.api.JavacTool.getTask (JavacTool.java:107)*11:53:45*
> at com.sun.tools.javac.api.JavacTool.getTask (JavacTool.java:64)*11:53:45*
>at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess
> (JavaxToolsCompiler.java:125)*11:53:45* at
> org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile
> (JavacCompiler.java:174)*11:53:45* at
> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute
> (AbstractCompilerMojo.java:1075)*11:53:45* at
> org.apache.maven.plugin.compiler.TestCompilerMojo.execute
> (TestCompilerMojo.java:176)*11:53:45* at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:134)*11:53:45* at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)*11:53:45* at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)*11:53:45* at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)*11:53:45* at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)*11:53:45* at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:200)*11:53:45*
[jira] [Created] (MCOMPILER-339) Skip --release flag if compilerVersion is lower than 1.9
David J. M. Karlsen created MCOMPILER-339: - Summary: Skip --release flag if compilerVersion is lower than 1.9 Key: MCOMPILER-339 URL: https://issues.apache.org/jira/browse/MCOMPILER-339 Project: Maven Compiler Plugin Issue Type: Improvement Affects Versions: 3.7.0 Reporter: David J. M. Karlsen -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1330) JUnit 5 surefire-provider code donation
[ https://issues.apache.org/jira/browse/SUREFIRE-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318803#comment-16318803 ] David J. M. Karlsen commented on SUREFIRE-1330: --- Is there any progress on this? It's s bit of an obstacle - and I don't want to downgrade to surefire 2.19 which brings other problems. > JUnit 5 surefire-provider code donation > --- > > Key: SUREFIRE-1330 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1330 > Project: Maven Surefire > Issue Type: New Feature >Reporter: Benedikt Ritter >Assignee: Tibor Digana > Labels: junit5 > Fix For: 3.0-RC1 > > Attachments: junit-platform-surefire-provider.zip > > > The JUnit team wishes to contribute their surefire provider implementation > for JUnit 5 to the Maven team. > The code is currently located at GitHub: > https://github.com/junit-team/junit5/tree/master/junit-platform-surefire-provider > They have recently relicensed the code under terms of Apache License 2.0: > https://github.com/junit-team/junit5/issues/541 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1403) [Jigsaw] [Java 9] add "--add-modules java.se.ee" to forked CLI argument
[
https://issues.apache.org/jira/browse/SUREFIRE-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16303335#comment-16303335
]
David J. M. Karlsen commented on SUREFIRE-1403:
---
I don't think surefire should force any modules onto the user - the user should
control the environment. See https://github.com/JavaMoney/jsr354-ri/issues/178
which will fail with surefire 2.20.1 but pass with 2.20
> [Jigsaw] [Java 9] add "--add-modules java.se.ee" to forked CLI argument
> ---
>
> Key: SUREFIRE-1403
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1403
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Reporter: Tibor Digana
>Assignee: Tibor Digana
> Fix For: 2.20.1
>
> Attachments: surefire-1403.zip
>
>
> Calling *findClass( cls, "java.se.ee")* in *IsolatedClassLoader* does not
> help and does not do anything because the module is ignored in Java 9.
> In-plugin provider does not have any problem to load classes from entire JDK.
> Forked JVM would work only after added
> {{--add-modules java.se.ee}}
> The fix would be to add "--add-modules java.se.ee" if {{--add-modules}} is
> not specified by user at Java 9+.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MNG-6240) Duplicate components in plugin extension realm when plugin depends on maven-aether-resolver
[
https://issues.apache.org/jira/browse/MNG-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049599#comment-16049599
]
David J. M. Karlsen commented on MNG-6240:
--
That's grand - when do you think 3.5.1 can be cut - would love getting over to
3.5.x but MNG-6240 is a showstopper for the time being.
> Duplicate components in plugin extension realm when plugin depends on
> maven-aether-resolver
> ---
>
> Key: MNG-6240
> URL: https://issues.apache.org/jira/browse/MNG-6240
> Project: Maven
> Issue Type: Bug
> Components: Class Loading
>Affects Versions: 3.5.0
>Reporter: Guillaume Boué
>Assignee: Guillaume Boué
> Fix For: 3.5.1
>
>
> When a plugin extension has a dependency on {{maven-aether-resolver}}, the
> components of this artifact are added into the plugin realm even though Maven
> Core already provides them. This is a regression introduced by the rename of
> this module to {{maven-resolver-provider}} in 3.5.0.
> This rename has kept all the classes of {{maven-aether-resolver}} for
> compatibility, therefore the old artifact name also needs to be exported by
> Maven Core in {{extension.xml}}.
> A visible side-effect of this is MDEPLOY-221, where the two
> {{MetadataGeneratorFactory}} components of {{maven-aether-provider}} (which
> are {{SnapshotMetadataGeneratorFactory}} and
> {{VersionsMetadataGeneratorFactory}}) are present twice as Guice bindings,
> and wrong metadata information is deployed as a consequence. This is due to
> the Flex Mojos plugin extension which depends on {{maven-aether-resolver}}
> used in the build.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MDEPLOY-221) deploy generates wrong timestamps in maven-metadata.xml
[
https://issues.apache.org/jira/browse/MDEPLOY-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007246#comment-16007246
]
David J. M. Karlsen commented on MDEPLOY-221:
-
Same here
- Nexus Repository Manager 2.14.3-02
- mvn 3.5.0
- "--builder singlethreaded clean deploy -DskipTests=true -DfailIfNoTests=false
-DdeployAtEnd"
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#deployAtEnd
for that last parameter
> deploy generates wrong timestamps in maven-metadata.xml
> ---
>
> Key: MDEPLOY-221
> URL: https://issues.apache.org/jira/browse/MDEPLOY-221
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy
>Affects Versions: 2.8.2
>Reporter: Roland Illig
>
> When deploying an artifact to a Nexus server, the file {{maven-metadata.xml}}
> can end up with inconsistent timestamps.
> {noformat}
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 24 kB/s)
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 171 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76.jar
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76.jar
> (18 kB at 591 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76.pom
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76.pom
> (2.2 kB at 71 kB/s)
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> (1.2 kB at 92 kB/s)
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> (1.2 kB at 92 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 59 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 43 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> (1.2 kB at 33 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> (1.2 kB at 40 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76-sources.jar
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76-sources.jar
> (12 kB at 386 kB/s)
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> (1.2 kB at 92 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 59 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 65 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Uploaded:
[jira] [Created] (MASSEMBLY-839) publish xsd descriptor schema
David J. M. Karlsen created MASSEMBLY-839: - Summary: publish xsd descriptor schema Key: MASSEMBLY-839 URL: https://issues.apache.org/jira/browse/MASSEMBLY-839 Project: Maven Assembly Plugin Issue Type: Task Affects Versions: 3.0.0 Reporter: David J. M. Karlsen http://maven.apache.org/plugins/maven-assembly-plugin/ has a link to http://maven.apache.org/xsd/assembly-2.0.0.xsd - this does not exist -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MSITE-770) Concurrent modification exception when running maven site report
David J. M. Karlsen created MSITE-770:
-
Summary: Concurrent modification exception when running maven site
report
Key: MSITE-770
URL: https://issues.apache.org/jira/browse/MSITE-770
Project: Maven Site Plugin
Issue Type: Bug
Reporter: David J. M. Karlsen
{noformat}
10:28:35 [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.5:site (default-site) on project
jfr-srv: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.5:site failed.
ConcurrentModificationException -> [Help 1]
10:28:35 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.apache.maven.plugins:maven-site-plugin:3.5:site (default-site)
on project jfr-srv: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.5:site failed.
10:28:35at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
10:28:35at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
10:28:35at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
10:28:35at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
10:28:35at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
10:28:35at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:181)
10:28:35at java.util.concurrent.FutureTask.run(FutureTask.java:266)
10:28:35at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
10:28:35at java.util.concurrent.FutureTask.run(FutureTask.java:266)
10:28:35at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
10:28:35at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
10:28:35at java.lang.Thread.run(Thread.java:745)
10:28:35 Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
default-site of goal org.apache.maven.plugins:maven-site-plugin:3.5:site failed.
10:28:35at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
10:28:35at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
10:28:35... 11 more
10:28:35 Caused by: java.util.ConcurrentModificationException
10:28:35at
java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901)
10:28:35at java.util.ArrayList$Itr.next(ArrayList.java:851)
10:28:35at
org.apache.maven.report.projectinfo.PluginManagementReport$PluginManagementRenderer.renderSectionPluginManagement(PluginManagementReport.java:204)
10:28:35at
org.apache.maven.report.projectinfo.PluginManagementReport$PluginManagementRenderer.renderBody(PluginManagementReport.java:189)
10:28:35at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:83)
10:28:35at
org.apache.maven.report.projectinfo.PluginManagementReport.executeReport(PluginManagementReport.java:83)
10:28:35at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255)
10:28:35at
org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:227)
10:28:35at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:330)
10:28:35at
org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:181)
10:28:35at
org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:135)
10:28:35at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
10:28:35... 12 more
10:28:35 [ERROR]
10:28:35 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
10:28:35 [ERROR]
10:28:35 [ERROR] For more information about the errors and possible solutions,
please read the following articles:
10:28:35 [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
{noformat}
My pom:
{noformat}
parent-reports
org.apache.maven.plugins
maven-pmd-plugin
3.6
${project.build.java.target}
[jira] (MASSEMBLY-659) Nullpointer in assembly:single when enforcer plugin v1.3 used
David J. M. Karlsen created MASSEMBLY-659:
-
Summary: Nullpointer in assembly:single when enforcer plugin v1.3
used
Key: MASSEMBLY-659
URL: https://jira.codehaus.org/browse/MASSEMBLY-659
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.4
Reporter: David J. M. Karlsen
Attachments: online-distribution.xml
I get this exception when the enforcer-plugin (!) is pluginManaged to version
1.3.
It works with enforcer v1.2
{noformat}
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default) on project
cp-client-dist: Execution default of goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single failed.
NullPointerException - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default) on project
cp-client-dist: Execution default of goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default
of goal org.apache.maven.plugins:maven-assembly-plugin:2.4:single failed.
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: java.lang.NullPointerException
at
org.apache.maven.plugin.assembly.archive.archiver.AssemblyProxyArchiver$DefaultFileInfo.isFile(AssemblyProxyArchiver.java:871)
at
org.apache.maven.plugin.assembly.filter.ComponentsXmlArchiverFileFilter.isSelected(ComponentsXmlArchiverFileFilter.java:193)
at
org.apache.maven.plugin.assembly.archive.archiver.AssemblyProxyArchiver.acceptFile(AssemblyProxyArchiver.java:825)
at
org.apache.maven.plugin.assembly.archive.archiver.AssemblyProxyArchiver.addFile(AssemblyProxyArchiver.java:476)
at
org.apache.maven.plugin.assembly.archive.task.AddArtifactTask.execute(AddArtifactTask.java:212)
at
org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.addNormalArtifact(AddDependencySetsTask.java:351)
at
org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.addDependencySet(AddDependencySetsTask.java:186)
at
org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.execute(AddDependencySetsTask.java:124)
at
org.apache.maven.plugin.assembly.archive.phase.DependencySetAssemblyPhase.execute(DependencySetAssemblyPhase.java:76)
at
org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:183)
at
org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:436)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 20 more
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following
[jira] (MDEP-287) Make maven-dependency-plugin @threadSafe
[ https://jira.codehaus.org/browse/MDEP-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=304543#comment-304543 ] David J. M. Karlsen commented on MDEP-287: -- Any chance of this getting fixed? I could provide a patch - but this is really a one-liner, given that the plugin really is thread-safe. Make maven-dependency-plugin @threadSafe Key: MDEP-287 URL: https://jira.codehaus.org/browse/MDEP-287 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Affects Versions: 2.1 Reporter: Andreas Sewe Assignee: Brian Fox The plugin is not yet marked as @threadSafe. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-623) Add a configuration mode to be able to use git svn (at least for release plugin)
[ https://jira.codehaus.org/browse/SCM-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=296425#comment-296425 ] David J. M. Karlsen commented on SCM-623: - +1 for gitsvn artifact Add a configuration mode to be able to use git svn (at least for release plugin) Key: SCM-623 URL: https://jira.codehaus.org/browse/SCM-623 Project: Maven SCM Issue Type: New Feature Components: maven-scm-provider-git Affects Versions: 1.5 Reporter: Olivier Lamy Assignee: Olivier Lamy Fix For: 1.7 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-816) regression: java.lang.Exception: No tests found matching from org.junit.runner.Request$1@1808199
[
https://jira.codehaus.org/browse/SUREFIRE-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=288932#comment-288932
]
David J. M. Karlsen commented on SUREFIRE-816:
--
Duplicate of SUREFIRE-789 - I could make it work with 2.12-SNAPSHOT.
When will 2.12 be released?
regression: java.lang.Exception: No tests found matching from
org.junit.runner.Request$1@1808199
-
Key: SUREFIRE-816
URL: https://jira.codehaus.org/browse/SUREFIRE-816
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 2.11
Environment: maven 3.0.3
Reporter: David J. M. Karlsen
Assignee: Kristian Rosenvold
In 2.11 I get:
{noformat}
java.lang.Exception: No tests found matching from
org.junit.runner.Request$1@1808199 at
org.junit.internal.requests.FilterRequest.getRunner(FilterRequest.java:37)
at org.junit.runner.JUnitCore.run(JUnitCore.java:136) at
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:61)
at
org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:140)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597) at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
{noformat}
this passed fine with 2.10.
The test-class uses parameters - and in this execution no parameters are
returned, and hence no tests should be executed either.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-816) regression: java.lang.Exception: No tests found matching from org.junit.runner.Request$1@1808199
David J. M. Karlsen created SUREFIRE-816:
Summary: regression: java.lang.Exception: No tests found matching
from org.junit.runner.Request$1@1808199
Key: SUREFIRE-816
URL: https://jira.codehaus.org/browse/SUREFIRE-816
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 2.11
Environment: maven 3.0.3
Reporter: David J. M. Karlsen
In 2.11 I get:
{noformat}
java.lang.Exception: No tests found matching from
org.junit.runner.Request$1@1808199 at
org.junit.internal.requests.FilterRequest.getRunner(FilterRequest.java:37) at
org.junit.runner.JUnitCore.run(JUnitCore.java:136) at
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:61)
at
org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:140)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597) at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
{noformat}
this passed fine with 2.10.
The test-class uses parameters - and in this execution no parameters are
returned, and hence no tests should be executed either.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MDEP-329) Mark plugin as @threadsafe
Mark plugin as @threadsafe
--
Key: MDEP-329
URL: https://jira.codehaus.org/browse/MDEP-329
Project: Maven 2.x Dependency Plugin
Issue Type: Improvement
Affects Versions: 2.3
Environment: maven 3
Reporter: David J. M. Karlsen
Assignee: Brian Fox
Can the plugin be marked @threadsafe for maven3 parallel builds?
Then we can avoid this warning:
{noformat}
18:17:53 [WARNING]
*
18:17:53 [WARNING] * Your build is requesting parallel execution, but project
*
18:17:53 [WARNING] * contains the following plugin(s) that are not marked as
*
18:17:53 [WARNING] * @threadSafe to support parallel building.
*
18:17:53 [WARNING] * While this /may/ work fine, please look for plugin
updates*
18:17:53 [WARNING] * and/or request plugins be made thread-safe.
*
18:17:53 [WARNING] * If reporting an issue, report it against the plugin in
*
18:17:53 [WARNING] * question, not against maven-core
*
18:17:53 [WARNING]
*
18:17:53 [WARNING] The following plugins are not marked @threadSafe in
pays-core-entra-service:
18:17:53 [WARNING] org.apache.maven.plugins:maven-dependency-plugin:2.1
18:17:53 [WARNING]
*
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-4621) Handle offline mode for Licence generation gracefully.
Handle offline mode for Licence generation gracefully.
--
Key: MNG-4621
URL: http://jira.codehaus.org/browse/MNG-4621
Project: Maven 2 3
Issue Type: Bug
Components: Plugin API
Affects Versions: 2.2.1
Reporter: David J. M. Karlsen
Instead of
[INFO] [site:site {execution: default-site}]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.report.projectinfo.LicenseReport.getLicenseURL(LicenseReport.java:156)
at
org.apache.maven.report.projectinfo.LicenseReport.canGenerateReport(LicenseReport.java:114)
at
org.apache.maven.plugins.site.AbstractSiteRenderingMojo.filterReports(AbstractSiteRenderingMojo.java:177)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:81)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:55
6)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav
a:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO]
[INFO] Total time: 7 seconds
[INFO] Finished at: Tue Apr 06 17:18:00 CEST 2010
[INFO] Final Memory: 34M/81M
[INFO]
-o (offline mode) should be handled gracefully (for instance return false from
canGenerateReport).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-4540) False positives on ${version} usage
False positives on ${version} usage
---
Key: MNG-4540
URL: http://jira.codehaus.org/browse/MNG-4540
Project: Maven 2 3
Issue Type: Bug
Components: Design, Patterns Best Practices
Affects Versions: 3.0-alpha-5
Reporter: David J. M. Karlsen
I get this warning with mvn 3 alpha5:
[WARNING] The expression ${version} is deprecated. Please use
${project.version} instead. @
com.davidkarlsen.zipcodeservice:zipcodeservice-selenium-tests:1.0-SNAPSHOT,
/u/david/projects/davidkarlsen.com/zipcodeservice/zipcodeservice-selenium-tests/pom.xml
but this is not the case, the pom's contain cxf.version, not version:
:~/projects/davidkarlsen.com/zipcodeservice$ find . -name pom.xml -exec fgrep
-il '${version}' '{}' \;
:~/projects/davidkarlsen.com/zipcodeservice$ find . -name pom.xml -exec fgrep
-il '${cxf.version}' '{}' \;
./zipcodeservice-core/pom.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4540) False positives on ${version} usage
[
http://jira.codehaus.org/browse/MNG-4540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=207754#action_207754
]
David J. M. Karlsen commented on MNG-4540:
--
You're right - it got pulled in through another parent pom which hadn't been
deployed (updated) yet.
Sorry for the noise.
False positives on ${version} usage
---
Key: MNG-4540
URL: http://jira.codehaus.org/browse/MNG-4540
Project: Maven 2 3
Issue Type: Bug
Components: Design, Patterns Best Practices
Affects Versions: 3.0-alpha-5
Reporter: David J. M. Karlsen
Assignee: Benjamin Bentmann
Attachments: pom.xml
I get this warning with mvn 3 alpha5:
[WARNING] The expression ${version} is deprecated. Please use
${project.version} instead. @
com.davidkarlsen.zipcodeservice:zipcodeservice-selenium-tests:1.0-SNAPSHOT,
/u/david/projects/davidkarlsen.com/zipcodeservice/zipcodeservice-selenium-tests/pom.xml
but this is not the case, the pom's contain cxf.version, not version:
:~/projects/davidkarlsen.com/zipcodeservice$ find . -name pom.xml -exec fgrep
-il '${version}' '{}' \;
:~/projects/davidkarlsen.com/zipcodeservice$ find . -name pom.xml -exec fgrep
-il '${cxf.version}' '{}' \;
./zipcodeservice-core/pom.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SUREFIRE-587) Doesn't run tests if they don't end with Test
Doesn't run tests if they don't end with Test - Key: SUREFIRE-587 URL: http://jira.codehaus.org/browse/SUREFIRE-587 Project: Maven Surefire Issue Type: Bug Components: JUnit 3.x support, Junit 4.x support Affects Versions: 2.4.3 Environment: N/A Reporter: David J. M. Karlsen Priority: Critical We have a mix of test - some purely junit4 (e.g. not extending anything and annotating with @Test) - and some which extends TestCase. I've discovered that the ones extending TestCase won't run if the classname doesn't end with Test - so that the class CommonsAttributesParserTests won't get included (notice the ending s). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MCHANGES-182) Plugin seems to be tied to Sun JDK
Plugin seems to be tied to Sun JDK -- Key: MCHANGES-182 URL: http://jira.codehaus.org/browse/MCHANGES-182 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: announcement Affects Versions: 2.1 Reporter: David J. M. Karlsen [ERROR] BUILD ERROR [INFO] [INFO] Error getting reports from the plugin 'org.apache.maven.plugins:maven-changes-plugin:2.1': Unable to load the mojo 'org.apache.maven.plugins:maven-changes-plugin:2.1:announcement-mail' in the plugin 'org.apache.maven.plugins:maven-changes-plugin'. A required class is missing: com.sun.net.ssl.internal.ssl.Provider [INFO] [INFO] For more information, run Maven with the -e switch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2578) Sync with datanucleus M2 repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=191651#action_191651 ] David J. M. Karlsen commented on MAVENUPLOAD-2578: -- This seems to be broken: Central has 1.0.1: http://repo2.maven.org/maven2/org/datanucleus/datanucleus-cache/ The latest in the source repo is 1.1.1: http://www.datanucleus.org/downloads/maven2/org/datanucleus/datanucleus-cache/ Sync with datanucleus M2 repo - Key: MAVENUPLOAD-2578 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2578 Project: Maven Upload Requests Issue Type: Wish Reporter: Data Nucleus Assignee: Carlos Sanchez org.datanucleus,j...@www.datanucleus.org:/home/jpox/htdocs/downloads/maven2,rsync_ssh,Andy Jefferson,i...@datanucleus.org,, The domain is obviously mine, registered under my name. I put the Maven public key into the user jpox $home/.ssh/authorized_keys Left as an exercise to see if that works -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2608) CLONE -Sync with datanucleus M2 repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=191652#action_191652 ] David J. M. Karlsen commented on MAVENUPLOAD-2608: -- Reopened since the syncing doesn't seem to work. CLONE -Sync with datanucleus M2 repo Key: MAVENUPLOAD-2608 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2608 Project: Maven Upload Requests Issue Type: Wish Reporter: David J. M. Karlsen Assignee: Carlos Sanchez org.datanucleus,j...@www.datanucleus.org:/home/jpox/htdocs/downloads/maven2,rsync_ssh,Andy Jefferson,i...@datanucleus.org,, The domain is obviously mine, registered under my name. I put the Maven public key into the user jpox $home/.ssh/authorized_keys Left as an exercise to see if that works -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2608) CLONE -Sync with datanucleus M2 repo
CLONE -Sync with datanucleus M2 repo Key: MAVENUPLOAD-2608 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2608 Project: Maven Upload Requests Issue Type: Wish Reporter: David J. M. Karlsen Assignee: Carlos Sanchez org.datanucleus,j...@www.datanucleus.org:/home/jpox/htdocs/downloads/maven2,rsync_ssh,Andy Jefferson,i...@datanucleus.org,, The domain is obviously mine, registered under my name. I put the Maven public key into the user jpox $home/.ssh/authorized_keys Left as an exercise to see if that works -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPIR-135) NPE if license URL is not defined
[ http://jira.codehaus.org/browse/MPIR-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172060#action_172060 ] David J. M. Karlsen commented on MPIR-135: -- This happens in offline mode as well (-o). [INFO] [site:site] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.report.projectinfo.LicenseReport.getLicenseURL(Licen seReport.java:156) at org.apache.maven.report.projectinfo.LicenseReport.canGenerateReport(L icenseReport.java:114) at org.apache.maven.plugins.site.AbstractSiteRenderingMojo.filterReports (AbstractSiteRenderingMojo.java:177) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:81) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:678) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:540) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:519) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 1 minute 27 seconds [INFO] Finished at: Sun Apr 05 18:50:26 CEST 2009 [INFO] Final Memory: 43M/93M [INFO] NPE if license URL is not defined - Key: MPIR-135 URL: http://jira.codehaus.org/browse/MPIR-135 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Components: license Affects Versions: 2.1 Environment: maven 2.0.9 java 1.5 Reporter: Andreas Höhmann Assignee: Vincent Siveton Fix For: 2.1.1 [INFO] [site:site] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.report.projectinfo.LicenseReport.getLicenseURL(LicenseReport.java:156) at org.apache.maven.report.projectinfo.LicenseReport.canGenerateReport(LicenseReport.java:114) at org.apache.maven.plugins.site.AbstractSiteRenderingMojo.filterReports(AbstractSiteRenderingMojo.java:177) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:81) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:49 9) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav a:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at
[jira] Commented: (MENFORCER-48) Support for a specific vendor of a JDK
[ http://jira.codehaus.org/browse/MENFORCER-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162847#action_162847 ] David J. M. Karlsen commented on MENFORCER-48: -- Good point - java.vendor should reveal this. Maybe add to the docs? Support for a specific vendor of a JDK -- Key: MENFORCER-48 URL: http://jira.codehaus.org/browse/MENFORCER-48 Project: Maven 2.x Enforcer Plugin Issue Type: Improvement Components: Standard Rules Affects Versions: 1.0-alpha-3 Environment: maven 2.0.9 Reporter: David J. M. Karlsen Assignee: Brian Fox Support for specifying a vendor string (or regexp?) to match. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2314) Upload hibernate tools 3.2.3.GA
Upload hibernate tools 3.2.3.GA --- Key: MAVENUPLOAD-2314 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2314 Project: Maven Upload Requests Issue Type: Wish Reporter: David J. M. Karlsen Please upload hibernate tools. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-264) prepare mojo calls package, not install
[ http://jira.codehaus.org/browse/MRELEASE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158512#action_158512 ] David J. M. Karlsen commented on MRELEASE-264: -- Here is a thread which show's how this is a problem when using the dependency plugin w/ a dependency from the reactor build: http://www.nabble.com/release%3Aprepare-amusement-with-the-dependency-plugin-td21063104.html prepare mojo calls package, not install - Key: MRELEASE-264 URL: http://jira.codehaus.org/browse/MRELEASE-264 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.0-beta-4 Reporter: Stefan Behnel The prepare mojo calls mvn package for the build after adapting the POM versions. This results in build failures if the project has interdependencies between modules (a rather common case). The problem is that the new version has not been deployed so far, so the required module artifacts are not yet available from the repository. The mojo should call mvn install to make artifacts available to the running build process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-1468) best practices: version management in multi project builds
[ http://jira.codehaus.org/browse/MNG-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158562#action_158562 ] David J. M. Karlsen commented on MNG-1468: -- The page http://docs.codehaus.org/display/MAVEN/Maven+Best+Practices has been deleted best practices: version management in multi project builds -- Key: MNG-1468 URL: http://jira.codehaus.org/browse/MNG-1468 Project: Maven 2 Issue Type: Bug Components: Design, Patterns Best Practices Reporter: Jason van Zyl Priority: Trivial Fix For: Documentation Deficit How to manage versions from a single place in a multi project build. The reference in the wiki can be found here: http://docs.codehaus.org/display/MAVEN/Maven+Best+Practices -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2302) Add javadocs to commons-cli 1.1
Add javadocs to commons-cli 1.1 --- Key: MAVENUPLOAD-2302 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2302 Project: Maven Upload Requests Issue Type: Wish Reporter: David J. M. Karlsen Attachments: commons-cli-1.1.javadoc.zip The http://repo1.maven.org/maven2/commons-cli/commons-cli/1.1/commons-cli-1.1-javadoc.javadoc.jar is an invalid filename for javadocs. Now we can't remove what's already there according to rules - but it should be possible to add the attached archive which is correct and support javadocs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MAVENUPLOAD-2250) Upload bundle for opensymhony.org's quartz scheduler
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David J. M. Karlsen updated MAVENUPLOAD-2250: - Attachment: quartz161bundle.zip Updated attachment Upload bundle for opensymhony.org's quartz scheduler Key: MAVENUPLOAD-2250 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2250 Project: Maven Upload Requests Issue Type: Wish Reporter: David J. M. Karlsen Attachments: org.opensymphony.quartz.161.zip, quartz161bundle.zip Bundle attached as file upload -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2297) Upload bundle for saxon 9.1.0.2 b
Upload bundle for saxon 9.1.0.2 b - Key: MAVENUPLOAD-2297 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2297 Project: Maven Upload Requests Issue Type: Wish Reporter: David J. M. Karlsen Upload bundle for free / opensource version of Saxon. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2250) Upload bundle for opensymhony.org's quartz scheduler
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=156240#action_156240 ] David J. M. Karlsen commented on MAVENUPLOAD-2250: -- Do you suggest I change it back to the same groups as today - or create relocation? Upload bundle for opensymhony.org's quartz scheduler Key: MAVENUPLOAD-2250 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2250 Project: Maven Upload Requests Issue Type: Wish Reporter: David J. M. Karlsen Attachments: org.opensymphony.quartz.161.zip Bundle attached as file upload -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-261) release:prepare shouls support flat directory multimodule projects
[ http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=156340#action_156340 ] David J. M. Karlsen commented on MRELEASE-261: -- Any news on this. Not being able to release a flat structure is a real PITA - and having nearly empty pom.xml's around just to satisfy maven is really bad publicity... release:prepare shouls support flat directory multimodule projects -- Key: MRELEASE-261 URL: http://jira.codehaus.org/browse/MRELEASE-261 Project: Maven 2.x Release Plugin Issue Type: Improvement Environment: linux / maven2 / svn Reporter: [EMAIL PROTECTED] Attachments: PrepareReleaseMojo.patch What I mean by flat file structure firstly. parent/pom.xml module1/pom.xml module2/pom.xml . . . module15/pom.xml the parent references the modules like so modules module../module1/module module../module2/module . . . module../module15/module /modules When i release:prepare only the parent project is tagged the modules projects versions are incremented etc but the modules are not tagged in svn. I use this structure as i use eclipse as my IDE. I would love to see a fix for the issue marked as closed here http://jira.codehaus.org/browse/MRELEASE-138. I am currenrly tagging by hand each submodule of the projects but it would be so nice to have the release plugin do this for me. forgive my english. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-350) CVS URL without username or password exception
[
http://jira.codehaus.org/browse/SCM-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=152456#action_152456
]
David J. M. Karlsen commented on SCM-350:
-
Preferably the credentials should be read from settings.xml's server element if
not defined in the url.
CVS URL without username or password exception
--
Key: SCM-350
URL: http://jira.codehaus.org/browse/SCM-350
Project: Maven SCM
Issue Type: Bug
Affects Versions: 1.0
Reporter: Danilo Eiji Seki
I wanted to use a CVS URL without username or password no matter what in the
SCM configuration.
I was able to do that successfuly for a project without reports using the
following:
{code:xml|title=pom.xml}
...
scm
connection
scm:cvs:pserver:cvs.domain.com.br:/opt/CVS/root:myproject
/connection
developerConnection
scm:cvs:pserver:cvs.domain.com.br:/opt/CVS/root:myproject
/developerConnection
/scm
...
{code}
and
{code:xml|title=settings.xml}
...
activeProfiles
activeProfilecvs-username/activeProfile
/activeProfiles
profiles
profile
idcvs-username/id
properties
usernamemyusername/username
/properties
/profile
/profiles
...
{code}
and using CVS login that generates a {{.cvspass}} for the user. This way, the
{{pom.xml}} file is totally free of usernames and passwords. But when
generating the site of a project with reports, I got the following error:
{noformat}
[INFO] Generate Checkstyle report.
[INFO] There are 17 checkstyle errors.
[INFO] Generate JavaDocs report.
[INFO] Generate Test JavaDocs report.
[INFO] Generate Source Xref report.
[INFO] Generate Test Source Xref report.
[INFO] Generate CPD Report report.
[INFO] Generate PMD Report report.
[INFO] Generate Continuous Integration report.
[INFO] Generate Dependencies report.
[INFO] Generate Issue Tracking report.
[INFO] Generate Project License report.
[INFO] Generate About report.
[INFO] Generate Project Summary report.
[INFO] Generate Source Repository report.
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Username isn't defined.
[INFO]
[INFO] Trace
java.lang.IllegalArgumentException: Username isn't defined.
at
org.apache.maven.scm.provider.cvslib.repository.CvsScmProviderRepository.getCvsRootForCvsPass(CvsScmProviderRepository.java:105)
at
org.apache.maven.scm.provider.cvslib.repository.CvsScmProviderRepository.getCvsRoot(CvsScmProviderRepository.java:73)
at
org.apache.maven.report.projectinfo.ScmReport$ScmRenderer.developerAccessCVS(ScmReport.java:479)
at
org.apache.maven.report.projectinfo.ScmReport$ScmRenderer.renderDeveloperAccessSection(ScmReport.java:323)
at
org.apache.maven.report.projectinfo.ScmReport$ScmRenderer.renderBody(ScmReport.java:186)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65)
at
org.apache.maven.report.projectinfo.ScmReport.executeReport(ScmReport.java:87)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:67)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:239)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:115)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:124)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at
[jira] Commented: (MAVENUPLOAD-2250) Upload bundle for opensymhony.org's quartz scheduler
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=152131#action_152131 ] David J. M. Karlsen commented on MAVENUPLOAD-2250: -- Not this (the attached one) archive at least: skunk:/tmp/x$ unzip ../org.opensymphony.quartz.161.zip Archive: ../org.opensymphony.quartz.161.zip creating: org/ creating: org/opensymphony/ creating: org/opensymphony/quartz/ creating: org/opensymphony/quartz/quartz-jboss/ creating: org/opensymphony/quartz/quartz-jboss/1.6.1/ inflating: org/opensymphony/quartz/quartz-jboss/1.6.1/quartz-jboss-1.6.1.pom.sha1 inflating: org/opensymphony/quartz/quartz-jboss/1.6.1/quartz-jboss-1.6.1.jar.sha1 inflating: org/opensymphony/quartz/quartz-jboss/1.6.1/quartz-jboss-1.6.1.jar.md5 inflating: org/opensymphony/quartz/quartz-jboss/1.6.1/quartz-jboss-1.6.1.pom.md5 inflating: org/opensymphony/quartz/quartz-jboss/1.6.1/quartz-jboss-1.6.1.pom inflating: org/opensymphony/quartz/quartz-jboss/1.6.1/quartz-jboss-1.6.1.jar creating: org/opensymphony/quartz/quartz-oracle/ creating: org/opensymphony/quartz/quartz-oracle/1.6.1/ inflating: org/opensymphony/quartz/quartz-oracle/1.6.1/quartz-oracle-1.6.1.pom.sha1 inflating: org/opensymphony/quartz/quartz-oracle/1.6.1/quartz-oracle-1.6.1.jar.sha1 inflating: org/opensymphony/quartz/quartz-oracle/1.6.1/quartz-oracle-1.6.1.jar.md5 inflating: org/opensymphony/quartz/quartz-oracle/1.6.1/quartz-oracle-1.6.1.pom.md5 inflating: org/opensymphony/quartz/quartz-oracle/1.6.1/quartz-oracle-1.6.1.pom inflating: org/opensymphony/quartz/quartz-oracle/1.6.1/quartz-oracle-1.6.1.jar creating: org/opensymphony/quartz/quartz-weblogic/ creating: org/opensymphony/quartz/quartz-weblogic/1.6.1/ inflating: org/opensymphony/quartz/quartz-weblogic/1.6.1/quartz-weblogic-1.6.1.pom.sha1 inflating: org/opensymphony/quartz/quartz-weblogic/1.6.1/quartz-weblogic-1.6.1.jar.sha1 inflating: org/opensymphony/quartz/quartz-weblogic/1.6.1/quartz-weblogic-1.6.1.jar.md5 inflating: org/opensymphony/quartz/quartz-weblogic/1.6.1/quartz-weblogic-1.6.1.pom.md5 inflating: org/opensymphony/quartz/quartz-weblogic/1.6.1/quartz-weblogic-1.6.1.pom inflating: org/opensymphony/quartz/quartz-weblogic/1.6.1/quartz-weblogic-1.6.1.jar creating: org/opensymphony/quartz/quartz-all/ creating: org/opensymphony/quartz/quartz-all/1.6.1/ inflating: org/opensymphony/quartz/quartz-all/1.6.1/quartz-all-1.6.1.pom.sha1 inflating: org/opensymphony/quartz/quartz-all/1.6.1/quartz-all-1.6.1.jar.sha1 inflating: org/opensymphony/quartz/quartz-all/1.6.1/quartz-all-1.6.1.jar.md5 inflating: org/opensymphony/quartz/quartz-all/1.6.1/quartz-all-1.6.1.pom.md5 inflating: org/opensymphony/quartz/quartz-all/1.6.1/quartz-all-1.6.1.pom inflating: org/opensymphony/quartz/quartz-all/1.6.1/quartz-all-1.6.1.jar creating: org/opensymphony/quartz/quartz/ creating: org/opensymphony/quartz/quartz/1.6.1/ inflating: org/opensymphony/quartz/quartz/1.6.1/quartz-1.6.1-javadoc.jar.sha1 inflating: org/opensymphony/quartz/quartz/1.6.1/quartz-1.6.1-javadoc.jar.md5 inflating: org/opensymphony/quartz/quartz/1.6.1/quartz-1.6.1-javadoc.jar inflating: org/opensymphony/quartz/quartz/1.6.1/quartz-1.6.1.pom.sha1 inflating: org/opensymphony/quartz/quartz/1.6.1/quartz-1.6.1.jar.sha1 inflating: org/opensymphony/quartz/quartz/1.6.1/quartz-1.6.1.jar.md5 inflating: org/opensymphony/quartz/quartz/1.6.1/quartz-1.6.1.pom.md5 inflating: org/opensymphony/quartz/quartz/1.6.1/quartz-1.6.1.jar inflating: org/opensymphony/quartz/quartz/1.6.1/quartz-1.6.1.pom skunk:/tmp/x$ unzip ../org.opensymphony.quartz.161.zip skunk:/tmp/x$ find . -name skunk:/tmp/x$ Upload bundle for opensymhony.org's quartz scheduler Key: MAVENUPLOAD-2250 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2250 Project: Maven Upload Requests Issue Type: Wish Reporter: David J. M. Karlsen Attachments: org.opensymphony.quartz.161.zip Bundle attached as file upload -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2251) Aspectj 16.2. upload bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=152132#action_152132 ] David J. M. Karlsen commented on MAVENUPLOAD-2251: -- This bundle had bad md5 filenames - this is fixed now (same location) Aspectj 16.2. upload bundle --- Key: MAVENUPLOAD-2251 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2251 Project: Maven Upload Requests Issue Type: Wish Reporter: David J. M. Karlsen Upload bundle for aspectj 1.6.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2252) Upload bundle for opensymhony.org's quartz scheduler v1.6.2
Upload bundle for opensymhony.org's quartz scheduler v1.6.2 --- Key: MAVENUPLOAD-2252 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2252 Project: Maven Upload Requests Issue Type: Wish Reporter: David J. M. Karlsen Bundle with sources, javadoc, poms and jars for v1.6.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2251) Aspectj 16.2. upload bundle
Aspectj 16.2. upload bundle --- Key: MAVENUPLOAD-2251 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2251 Project: Maven Upload Requests Issue Type: Wish Reporter: David J. M. Karlsen Upload bundle for aspectj 1.6.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MAVENUPLOAD-2203) Upload bundle org.umlgraph.doclet 5.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David J. M. Karlsen reopened MAVENUPLOAD-2203: -- Reopening with updated bundle Upload bundle org.umlgraph.doclet 5.1 - Key: MAVENUPLOAD-2203 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2203 Project: Maven Upload Requests Issue Type: Task Reporter: David J. M. Karlsen Assignee: Carlos Sanchez Attachments: org.umlgraph.doclet-5.1.zip, org.umlgraph.doclet-5.1.zip Upload bundle for umlgraph 5.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MAVENUPLOAD-2203) Upload bundle org.umlgraph.doclet 5.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David J. M. Karlsen updated MAVENUPLOAD-2203: - Attachment: org.umlgraph.doclet-5.1.zip Updated with license information and updated md5/sha1 sums Upload bundle org.umlgraph.doclet 5.1 - Key: MAVENUPLOAD-2203 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2203 Project: Maven Upload Requests Issue Type: Task Reporter: David J. M. Karlsen Assignee: Carlos Sanchez Attachments: org.umlgraph.doclet-5.1.zip, org.umlgraph.doclet-5.1.zip, org.umlgraph.doclet-5.1.zip Upload bundle for umlgraph 5.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2250) Upload bundle for opensymhony.org's quartz scheduler
Upload bundle for opensymhony.org's quartz scheduler Key: MAVENUPLOAD-2250 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2250 Project: Maven Upload Requests Issue Type: Wish Reporter: David J. M. Karlsen Attachments: org.opensymphony.quartz.161.zip Bundle attached as file upload -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3704) NPE in DefaultLIfecycleExecutor when run from within Hudson builds
[
http://jira.codehaus.org/browse/MNG-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=151608#action_151608
]
David J. M. Karlsen commented on MNG-3704:
--
This is still the case, even with 2.1.0-M1:
http://davidkarlsen.com/hudson/job/WAS6%20plugin/74/console
NPE in DefaultLIfecycleExecutor when run from within Hudson builds
--
Key: MNG-3704
URL: http://jira.codehaus.org/browse/MNG-3704
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 2.0.10
Reporter: John Casey
Assignee: John Casey
Priority: Blocker
Fix For: 2.1.0-M1
{noformat}
[INFO] [clean:clean]
[HUDSON] Archiving /home/j2ee-hudson/.hudson/jobs/CXF/workspace/trunk/pom.xml
to
/home/j2ee-hudson/.hudson/jobs/CXF/modules/org.apache.cxf$cxf/builds/2008-08-11_16-49-47/archive/org.apache.cxf/cxf/2.1.2-SNAPSHOT/pom.xml
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.restoreDynamicState(DefaultLifecycleExecutor.java:779)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:636)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:533)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:512)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:364)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:325)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:176)
at
org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:42)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:302)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at hudson.maven.agent.Main.launch(Main.java:133)
at hudson.maven.MavenBuilder.call(MavenBuilder.java:135)
at
hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:536)
at
hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:482)
at hudson.remoting.UserRequest.perform(UserRequest.java:69)
at hudson.remoting.UserRequest.perform(UserRequest.java:23)
at hudson.remoting.Request$2.run(Request.java:206)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
{noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3525) Settings.xml allowing mirror definitions inside profiles
[ http://jira.codehaus.org/browse/MNG-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149827#action_149827 ] David J. M. Karlsen commented on MNG-3525: -- This would most definately be useful for ppl going in and out of different environments. Can it be resceduled for 2.1.x? Settings.xml allowing mirror definitions inside profiles Key: MNG-3525 URL: http://jira.codehaus.org/browse/MNG-3525 Project: Maven 2 Issue Type: Improvement Components: Profiles Affects Versions: 2.0.9 Environment: N/A Reporter: Paul Grove Fix For: 3.0-alpha-2 I currently use Maven in 2 places 1. At work 2. Not at work At work we have a repository manager thus we have mirror properties in the settings.xml for the whole teams global settings. We also have a defined a number of repositories in our work profile so we can mirror these to different repo's managed by Archiva. Now when I work from home I have to comment out the mirror definitions and activate a home profile which does not define any repos so Maven just goes out to the WWW as normal. So the pain is having to comment out and un-comment the mirror settings every time I go from work to home and visa-versa. Can we not have the option to add mirrors inside profiles? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MAVENUPLOAD-2203) Upload bundle org.umlgraph.doclet 5.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David J. M. Karlsen updated MAVENUPLOAD-2203: - Attachment: org.umlgraph.doclet-5.1.zip Uh - big bummer - thanks for pointing it out! Please use the second attachment Upload bundle org.umlgraph.doclet 5.1 - Key: MAVENUPLOAD-2203 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2203 Project: Maven Upload Requests Issue Type: Task Reporter: David J. M. Karlsen Attachments: org.umlgraph.doclet-5.1.zip, org.umlgraph.doclet-5.1.zip Upload bundle for umlgraph 5.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEV-602) Upload bundle org.umlgraph.doclet 5.1
Upload bundle org.umlgraph.doclet 5.1 - Key: MEV-602 URL: http://jira.codehaus.org/browse/MEV-602 Project: Maven Evangelism Issue Type: Task Reporter: David J. M. Karlsen Upload bundle for umlgraph 5.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MEV-602) Upload bundle org.umlgraph.doclet 5.1
[ http://jira.codehaus.org/browse/MEV-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David J. M. Karlsen updated MEV-602: Attachment: org.umlgraph.doclet-5.1.zip Ready upload bundle Upload bundle org.umlgraph.doclet 5.1 - Key: MEV-602 URL: http://jira.codehaus.org/browse/MEV-602 Project: Maven Evangelism Issue Type: Task Reporter: David J. M. Karlsen Attachments: org.umlgraph.doclet-5.1.zip Upload bundle for umlgraph 5.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDOCCK-14) Plugin does not respect generated documentation
[
http://jira.codehaus.org/browse/MDOCCK-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=147679#action_147679
]
David J. M. Karlsen commented on MDOCCK-14:
---
Oh - I went through the issues but didn't notice that one - could 1.0-beta-3 be
released soon - it's been over a year since last rel.
Plugin does not respect generated documentation
---
Key: MDOCCK-14
URL: http://jira.codehaus.org/browse/MDOCCK-14
Project: Maven 2.x Documentation Checker Plugin
Issue Type: Bug
Affects Versions: 1.0-beta-2
Environment: N/A
Reporter: David J. M. Karlsen
Assignee: Benjamin Bentmann
The plugin does not respect generated content (from velocity templates), for
example the project at:
http://svn.codehaus.org/mojo/trunk/mojo/was6-maven-plugin/
generates completely valid documentation - but the plugin fails with:
[INFO] [docck:check {execution: verify}]
[INFO] Checking project: WAS6 Maven Plugin
[INFO] Using 2 extractors.
[INFO] Applying extractor for language: java
[INFO] Extractor for language: java found 12 mojo descriptors.
[INFO] Applying extractor for language: bsh
[INFO] Extractor for language: bsh found 0 mojo descriptors.
[ERROR] The following documentation problems were found:
o WAS6 Maven Plugin (3 errors, 0 warnings)
[ERROR] There is no 'usage' file in your site directory (in apt|html|xml
format).
[ERROR] There are no example files in your site directory (in apt|html|xml
format). They should either be called 'example*.(apt|html|xml)' or they
should be located in the 'examples' directory.
[ERROR] There is no 'faq' file in your site directory (in apt|fml|html|xml
format).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-356) Be able to provide username/password as CLI parameters (and not only from settings.xml)
Be able to provide username/password as CLI parameters (and not only from settings.xml) --- Key: MSITE-356 URL: http://jira.codehaus.org/browse/MSITE-356 Project: Maven 2.x Site Plugin Issue Type: Improvement Components: site:deploy Affects Versions: 2.0-beta-7 Environment: N/A Reporter: David J. M. Karlsen It would be very handy if it was possible to provide username and credentials as CLI params (-Dusername -Dpassword) when doing site:stage-deploy -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MDOCCK-14) Plugin does not respect generated documentation
Plugin does not respect generated documentation
---
Key: MDOCCK-14
URL: http://jira.codehaus.org/browse/MDOCCK-14
Project: Maven 2.x Documentation Checker Plugin
Issue Type: Bug
Affects Versions: 1.0-beta-2
Environment: N/A
Reporter: David J. M. Karlsen
The plugin does not respect generated content (from velocity templates), for
example the project at:
http://svn.codehaus.org/mojo/trunk/mojo/was6-maven-plugin/
generates completely valid documentation - but the plugin fails with:
[INFO] [docck:check {execution: verify}]
[INFO] Checking project: WAS6 Maven Plugin
[INFO] Using 2 extractors.
[INFO] Applying extractor for language: java
[INFO] Extractor for language: java found 12 mojo descriptors.
[INFO] Applying extractor for language: bsh
[INFO] Extractor for language: bsh found 0 mojo descriptors.
[ERROR] The following documentation problems were found:
o WAS6 Maven Plugin (3 errors, 0 warnings)
[ERROR] There is no 'usage' file in your site directory (in apt|html|xml
format).
[ERROR] There are no example files in your site directory (in apt|html|xml
format). They should either be called 'example*.(apt|html|xml)' or they should
be located in the 'examples' directory.
[ERROR] There is no 'faq' file in your site directory (in apt|fml|html|xml
format).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-200) Please add support for the AJDT plugin
[ http://jira.codehaus.org/browse/MECLIPSE-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=147455#action_147455 ] David J. M. Karlsen commented on MECLIPSE-200: -- Is the site staged anywhere (to be able to see documentation of new parameters) Please add support for the AJDT plugin -- Key: MECLIPSE-200 URL: http://jira.codehaus.org/browse/MECLIPSE-200 Project: Maven 2.x Eclipse Plugin Issue Type: New Feature Components: AJDT support Affects Versions: 2.2 Reporter: Eric Berry Assignee: Arnaud Heritier Fix For: 2.6 Attachments: ajdt.patch, maven-eclipse-plugin.zip, maven-eclipse-plugin.zip Please add support for the AJDT plugin. I have modified the eclipse plugin for our site with the needed changes. I have attached the modifications that I made for someone to look at and incorporate into the plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3553) cannot resolve dependency with scope import
[
http://jira.codehaus.org/browse/MNG-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=147117#action_147117
]
David J. M. Karlsen commented on MNG-3553:
--
I have a slightly different problem.
Our super pom (artifact A) declares:
dependencies
dependency
groupIdmy.groupid/groupId
artifactIdwebsphere-testenvironment/artifactId
version1.3-SNAPSHOT/version
typepom/type
scopeimport/scope
/dependency
/dependencies
that is - in the dependencies section - not dep.management.
I then have an artifact B which have A as parent. The dependencies are not
resolve, although to my surprise, if I run mvn help:effective-pom on artifact
B, the dep is actually listed:
dependencies
dependency
groupIdmy.groupid/groupId
artifactIdwebsphere-testenvironment/artifactId
version1.3-SNAPSHOT/version
typepom/type
scopeimport/scope
/dependency
/dependencies
All the dependencies in my.groupid:websphere-testenvironment:1.3-SNAPSHOT are
declared as provided.
So there seems to be some inheritance problem.
cannot resolve dependency with scope import
---
Key: MNG-3553
URL: http://jira.codehaus.org/browse/MNG-3553
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.9
Reporter: Thomas Diesler
Fix For: 2.0.11
This pom when added as a dependency of another project does not see
repository http://snapshots.jboss.org/maven2
!-- DependencyManagement --
dependencyManagement
dependencies
dependency
groupIdorg.jboss.jbossas/groupId
artifactIdjboss-as-component-matrix/artifactId
version${jboss.version}/version
typepom/type
scopeimport/scope
/dependency
/dependencies
/dependencyManagement
with effective settings
[EMAIL PROTECTED] trunk]$ mvn help:effective-settings
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] JBoss Web Services - Stack CXF
[INFO] JBoss Web Services - Stack CXF Management
[INFO] JBoss Web Services - Stack CXF Runtime Server
[INFO] JBoss Web Services - Stack CXF Runtime Client
[INFO] Searching repository for plugin with prefix: 'help'.
[INFO]
[INFO] Building JBoss Web Services - Stack CXF
[INFO]task-segment: [help:effective-settings] (aggregator-style)
[INFO]
[INFO] [help:effective-settings]
[INFO]
Effective settings:
?xml version=1.0?settings
localRepository/home/tdiesler/.m2/repository/localRepository
profiles
profile
activation
property
name!jboss.repository.off/name
/property
/activation
repositories
repository
snapshots /
idsnapshots.jboss.org/id
urlhttp://snapshots.jboss.org/maven2/url
/repository
repository
snapshots
enabledfalse/enabled
/snapshots
idrepository.jboss.org/id
urlhttp://repository.jboss.org/maven2/url
/repository
/repositories
idjboss.repository/id
/profile
/profiles
activeProfiles
activeProfileuser-profile/activeProfile
/activeProfiles
pluginGroups
pluginGrouporg.jboss.maven.plugins/pluginGroup
/pluginGroups
/settings
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MECLIPSE-388) Correct classpath ordering in .classpath
[
http://jira.codehaus.org/browse/MECLIPSE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David J. M. Karlsen updated MECLIPSE-388:
-
Attachment: MECLIPSE-388.patch
Updated patch, order is now:
test sources
main sources
test resources
main resources
I'll have a go at the integration-tests tomorrow and add them as well
Correct classpath ordering in .classpath
Key: MECLIPSE-388
URL: http://jira.codehaus.org/browse/MECLIPSE-388
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: Core : Dependencies resolution and build path
Affects Versions: 2.4
Reporter: Siarhei Dudzin
Priority: Critical
Attachments: MECLIPSE-388.patch, MECLIPSE-388.patch
Currently plugin sorts artifacts on its own (alphabetic order???) because the
order of dependencies that comes from maven is not reliable (random?). This
breaks tests that use JBoss Embedded which works under maven surefire plugin
because it still puts dependencies that came first at the beginning of the
classpath). Apparently not all classpath elements are put in random order. At
least I get the first ones listed in dependencies also first in the classpath
(can be seen as ${surefire.test.class.path} and in
target/surefire-reports/TEST-TestSuite.xml).
While there is not much we can do for maven eclipse plugin a solution is on
the way: MNG-1412. When maven 2.0.9 is released maven eclipse plugin can
revert back to the default classpath order.
Can we somehow schedule this?
Another question: is there anyway to put certain dependencies in the first
place except for renaming them so that alphabetic order does the job?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MECLIPSE-388) Correct classpath ordering in .classpath
[
http://jira.codehaus.org/browse/MECLIPSE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David J. M. Karlsen updated MECLIPSE-388:
-
Attachment: MECLIPSE-388-it-test.patch
The attached patch fixes all of the integration tests related to this issue but
two:
testProject03(org.apache.maven.plugin.eclipse.it.EclipsePluginIT)
testMyEclipseProject03(org.apache.maven.plugin.eclipse.it.MyEclipsePluginIT)
These need some further investigation - probably EclipseSourceDir's equals
method should take outputDir into consideration.
This test fail (unrelated to the patch):
testProject6(org.apache.maven.plugin.eclipse.it.RadPluginIT)
Correct classpath ordering in .classpath
Key: MECLIPSE-388
URL: http://jira.codehaus.org/browse/MECLIPSE-388
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: Core : Dependencies resolution and build path
Affects Versions: 2.4
Reporter: Siarhei Dudzin
Priority: Critical
Attachments: MECLIPSE-388-it-test.patch, MECLIPSE-388.patch,
MECLIPSE-388.patch
Currently plugin sorts artifacts on its own (alphabetic order???) because the
order of dependencies that comes from maven is not reliable (random?). This
breaks tests that use JBoss Embedded which works under maven surefire plugin
because it still puts dependencies that came first at the beginning of the
classpath). Apparently not all classpath elements are put in random order. At
least I get the first ones listed in dependencies also first in the classpath
(can be seen as ${surefire.test.class.path} and in
target/surefire-reports/TEST-TestSuite.xml).
While there is not much we can do for maven eclipse plugin a solution is on
the way: MNG-1412. When maven 2.0.9 is released maven eclipse plugin can
revert back to the default classpath order.
Can we somehow schedule this?
Another question: is there anyway to put certain dependencies in the first
place except for renaming them so that alphabetic order does the job?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-388) Correct classpath ordering in .classpath
[
http://jira.codehaus.org/browse/MECLIPSE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=145763#action_145763
]
David J. M. Karlsen commented on MECLIPSE-388:
--
Requiring 2.0.9 doesn't seem like a big issue for me (especially not when you
compare that to having a random/invalid classpath).
Also, it's important to preserve the order of test-resources, f.ex:
testResources
testResource
directorysrc/test/resources/directory
/testResource
testResource
directorysrc/main/config/directory
/testResource
/testResources
src/test/resources should be before src/main/config - this is not the case p.t.
Correct classpath ordering in .classpath
Key: MECLIPSE-388
URL: http://jira.codehaus.org/browse/MECLIPSE-388
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: Core : Dependencies resolution and build path
Affects Versions: 2.4
Reporter: Siarhei Dudzin
Priority: Critical
Currently plugin sorts artifacts on its own (alphabetic order???) because the
order of dependencies that comes from maven is not reliable (random?). This
breaks tests that use JBoss Embedded which works under maven surefire plugin
because it still puts dependencies that came first at the beginning of the
classpath). Apparently not all classpath elements are put in random order. At
least I get the first ones listed in dependencies also first in the classpath
(can be seen as ${surefire.test.class.path} and in
target/surefire-reports/TEST-TestSuite.xml).
While there is not much we can do for maven eclipse plugin a solution is on
the way: MNG-1412. When maven 2.0.9 is released maven eclipse plugin can
revert back to the default classpath order.
Can we somehow schedule this?
Another question: is there anyway to put certain dependencies in the first
place except for renaming them so that alphabetic order does the job?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MECLIPSE-388) Correct classpath ordering in .classpath
[
http://jira.codehaus.org/browse/MECLIPSE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David J. M. Karlsen updated MECLIPSE-388:
-
Attachment: MECLIPSE-388.patch
Here's a patch which use a LinkedHashSet and adds test resources before the
normal resources
Correct classpath ordering in .classpath
Key: MECLIPSE-388
URL: http://jira.codehaus.org/browse/MECLIPSE-388
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: Core : Dependencies resolution and build path
Affects Versions: 2.4
Reporter: Siarhei Dudzin
Priority: Critical
Attachments: MECLIPSE-388.patch
Currently plugin sorts artifacts on its own (alphabetic order???) because the
order of dependencies that comes from maven is not reliable (random?). This
breaks tests that use JBoss Embedded which works under maven surefire plugin
because it still puts dependencies that came first at the beginning of the
classpath). Apparently not all classpath elements are put in random order. At
least I get the first ones listed in dependencies also first in the classpath
(can be seen as ${surefire.test.class.path} and in
target/surefire-reports/TEST-TestSuite.xml).
While there is not much we can do for maven eclipse plugin a solution is on
the way: MNG-1412. When maven 2.0.9 is released maven eclipse plugin can
revert back to the default classpath order.
Can we somehow schedule this?
Another question: is there anyway to put certain dependencies in the first
place except for renaming them so that alphabetic order does the job?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MECLIPSE-479) More contaigner entries
More contaigner entries - Key: MECLIPSE-479 URL: http://jira.codehaus.org/browse/MECLIPSE-479 Project: Maven 2.x Eclipse Plugin Issue Type: Sub-task Affects Versions: 2.5.1 Environment: N/A Reporter: David J. M. Karlsen Priority: Trivial Attachments: MECLIPSE-479.patch There are more entries containing contaigner as shown: :~/projects/asf/maven/trunks/plugins/maven-eclipse-plugin$ find . -type f |xargs fgrep -li contaigner|grep -v svn ./src/main/java/org/apache/maven/plugin/eclipse/writers/rad/RadEjbClasspathWriter.java ./src/main/java/org/apache/maven/plugin/eclipse/reader/ReadWorkspaceLocations.java -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MECLIPSE-479) More contaigner entries
[ http://jira.codehaus.org/browse/MECLIPSE-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David J. M. Karlsen updated MECLIPSE-479: - Attachment: MECLIPSE-479.patch More contaigner entries - Key: MECLIPSE-479 URL: http://jira.codehaus.org/browse/MECLIPSE-479 Project: Maven 2.x Eclipse Plugin Issue Type: Sub-task Affects Versions: 2.5.1 Environment: N/A Reporter: David J. M. Karlsen Priority: Trivial Attachments: MECLIPSE-479.patch There are more entries containing contaigner as shown: :~/projects/asf/maven/trunks/plugins/maven-eclipse-plugin$ find . -type f |xargs fgrep -li contaigner|grep -v svn ./src/main/java/org/apache/maven/plugin/eclipse/writers/rad/RadEjbClasspathWriter.java ./src/main/java/org/apache/maven/plugin/eclipse/reader/ReadWorkspaceLocations.java -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (WAGON-237) deploy broke in 2.0.10-RC8
deploy broke in 2.0.10-RC8 -- Key: WAGON-237 URL: http://jira.codehaus.org/browse/WAGON-237 Project: Maven Wagon Issue Type: Bug Components: wagon-ssh Affects Versions: 1.0-beta-4 Environment: Maven version: 2.0.10-RC8 Java version: 1.5.0_13 Default locale: en_US, platform encoding: ISO8859-1 OS name: sunos version: 5.10 arch: sparc family: unix Reporter: David J. M. Karlsen Starting from 2.0.10-RC8 deploy (with ssh and password) started to fail - I'm getting: [DEBUG] Connecting to repository: 'repo.sandsli.dnb.no' with url: 'scp://repo.sandsli.dnb.no/dnb/data/proximity/inhouse.snapshot/storage'. Keyboard interactive required, supplied password is ignored event though the pw is in settings.xml: With help from Brett this was added: build extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-ssh/artifactId version1.0-beta-2/version /extension /extensions which resolved the case. Fragment from settings.xml: servers server usernameMyUser/username passwordMySecret/password filePermissions777/filePermissions directoryPermissions777/directoryPermissions idrepo.sandsli.dnb.no/id /server Fragment from pom.xml: distributionManagement repository idrepo.sandsli.dnb.no/id nameDnBNOR Felles Repository/name urlscp://repo.sandsli.dnb.no/dnb/data/proximity/inhouse/storage/url /repository snapshotRepository idrepo.sandsli.dnb.no/id nameDnBNOR Felles Snapshot Repository/name urlscp://repo.sandsli.dnb.no/dnb/data/proximity/inhouse.snapshot/storage/url /snapshotRepository site idrepo.sandsli.dnb.no/id urlscp://repo.sandsli.dnb.no/dnb/prosess/prosjektdok/no.dnbnor.websphere-1.3-SNAPSHOT/websphere-testenvironment/url /site /distributionManagement -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MENFORCER-48) Support for a specific vendor of a JDK
Support for a specific vendor of a JDK -- Key: MENFORCER-48 URL: http://jira.codehaus.org/browse/MENFORCER-48 Project: Maven 2.x Enforcer Plugin Issue Type: Improvement Components: Standard Rules Affects Versions: 1.0-alpha-3 Environment: maven 2.0.9 Reporter: David J. M. Karlsen Assignee: Brian Fox Support for specifying a vendor string (or regexp?) to match. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2135) org.aspectj:aspectjweaver:1.6.1
org.aspectj:aspectjweaver:1.6.1 --- Key: MAVENUPLOAD-2135 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2135 Project: Maven Upload Requests Issue Type: Improvement Reporter: David J. M. Karlsen -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2136) org.aspectj:aspectjlib:1.6.1
org.aspectj:aspectjlib:1.6.1 Key: MAVENUPLOAD-2136 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2136 Project: Maven Upload Requests Issue Type: Improvement Reporter: David J. M. Karlsen -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2137) org.aspectj:aspectjrt:1.6.1
org.aspectj:aspectjrt:1.6.1 --- Key: MAVENUPLOAD-2137 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2137 Project: Maven Upload Requests Issue Type: Improvement Reporter: David J. M. Karlsen -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2138) org.aspectj:aspectjtools:1.6.1
org.aspectj:aspectjtools:1.6.1 -- Key: MAVENUPLOAD-2138 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2138 Project: Maven Upload Requests Issue Type: Improvement Reporter: David J. M. Karlsen -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3632) Clearer javadocs for MojoExecutionException and MojoFailureException
[ http://jira.codehaus.org/browse/MNG-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=139800#action_139800 ] David J. M. Karlsen commented on MNG-3632: -- It's explained on the site: http://www.propellors.net/maven/site/guides/development/guide-plugin-documentation.html Clearer javadocs for MojoExecutionException and MojoFailureException Key: MNG-3632 URL: http://jira.codehaus.org/browse/MNG-3632 Project: Maven 2 Issue Type: Improvement Components: Plugin API Affects Versions: 2.0.9 Environment: N/A Reporter: David J. M. Karlsen State the difference between MojoExecutionException and MojoFailureException should be clearer in the javadocs (and maybe aslo on the site). Maybe add a @see between the two as well. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3632) Clearer javadocs for MojoExecutionException and MojoFailureException
Clearer javadocs for MojoExecutionException and MojoFailureException Key: MNG-3632 URL: http://jira.codehaus.org/browse/MNG-3632 Project: Maven 2 Issue Type: Improvement Components: Plugin API Affects Versions: 2.0.9 Environment: N/A Reporter: David J. M. Karlsen State the difference between MojoExecutionException and MojoFailureException should be clearer in the javadocs (and maybe aslo on the site). Maybe add a @see between the two as well. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MEV-582) Provide AspectJ 1.6 jars/poms/javadocs/sources
[ http://jira.codehaus.org/browse/MEV-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David J. M. Karlsen closed MEV-582. --- Fixed Provide AspectJ 1.6 jars/poms/javadocs/sources -- Key: MEV-582 URL: http://jira.codehaus.org/browse/MEV-582 Project: Maven Evangelism Issue Type: Wish Reporter: David J. M. Karlsen Attachments: aspectjrt.tar, aspectjtools.tar, aspectjweaver.tar Provide AspectJ 1.6 jars/poms/javadocs/sources -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (MEV-582) Provide AspectJ 1.6 jars/poms/javadocs/sources
[ http://jira.codehaus.org/browse/MEV-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David J. M. Karlsen resolved MEV-582. - Resolution: Fixed Seems like stuff is in place now: http://repo1.maven.org/maven2/org/aspectj/aspectjweaver/1.6.0/ Provide AspectJ 1.6 jars/poms/javadocs/sources -- Key: MEV-582 URL: http://jira.codehaus.org/browse/MEV-582 Project: Maven Evangelism Issue Type: Wish Reporter: David J. M. Karlsen Attachments: aspectjrt.tar, aspectjtools.tar, aspectjweaver.tar Provide AspectJ 1.6 jars/poms/javadocs/sources -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MEV-582) Provide AspectJ 1.6 jars/poms/javadocs/sources
[ http://jira.codehaus.org/browse/MEV-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David J. M. Karlsen reopened MEV-582: - Reopening as the javadocs weren't published. Provide AspectJ 1.6 jars/poms/javadocs/sources -- Key: MEV-582 URL: http://jira.codehaus.org/browse/MEV-582 Project: Maven Evangelism Issue Type: Wish Reporter: David J. M. Karlsen Attachments: aspectjrt.tar, aspectjtools.tar, aspectjweaver.tar Provide AspectJ 1.6 jars/poms/javadocs/sources -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEV-582) Provide AspectJ 1.6 jars/poms/javadocs/sources
Provide AspectJ 1.6 jars/poms/javadocs/sources -- Key: MEV-582 URL: http://jira.codehaus.org/browse/MEV-582 Project: Maven Evangelism Issue Type: Wish Reporter: David J. M. Karlsen Provide AspectJ 1.6 jars/poms/javadocs/sources -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MEV-582) Provide AspectJ 1.6 jars/poms/javadocs/sources
[ http://jira.codehaus.org/browse/MEV-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David J. M. Karlsen updated MEV-582: Attachment: aspectjrt.tar Attached is a bundle - please check that it's OK. Provide AspectJ 1.6 jars/poms/javadocs/sources -- Key: MEV-582 URL: http://jira.codehaus.org/browse/MEV-582 Project: Maven Evangelism Issue Type: Wish Reporter: David J. M. Karlsen Attachments: aspectjrt.tar Provide AspectJ 1.6 jars/poms/javadocs/sources -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MEV-582) Provide AspectJ 1.6 jars/poms/javadocs/sources
[ http://jira.codehaus.org/browse/MEV-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David J. M. Karlsen updated MEV-582: Attachment: aspectjtools.tar Bundle for tools - please check contents for potential errors. Provide AspectJ 1.6 jars/poms/javadocs/sources -- Key: MEV-582 URL: http://jira.codehaus.org/browse/MEV-582 Project: Maven Evangelism Issue Type: Wish Reporter: David J. M. Karlsen Attachments: aspectjrt.tar, aspectjtools.tar, aspectjweaver.tar Provide AspectJ 1.6 jars/poms/javadocs/sources -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MEV-582) Provide AspectJ 1.6 jars/poms/javadocs/sources
[ http://jira.codehaus.org/browse/MEV-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David J. M. Karlsen updated MEV-582: Attachment: aspectjweaver.tar Bundle for weaver - please check contents for potential errors. Provide AspectJ 1.6 jars/poms/javadocs/sources -- Key: MEV-582 URL: http://jira.codehaus.org/browse/MEV-582 Project: Maven Evangelism Issue Type: Wish Reporter: David J. M. Karlsen Attachments: aspectjrt.tar, aspectjtools.tar, aspectjweaver.tar Provide AspectJ 1.6 jars/poms/javadocs/sources -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-105) java.lang.NoSuchMethodError on changes:jira-report
[ http://jira.codehaus.org/browse/MCHANGES-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=130524#action_130524 ] David J. M. Karlsen commented on MCHANGES-105: -- I think so, yes. Could you push out a new snapshot so that I can test? java.lang.NoSuchMethodError on changes:jira-report -- Key: MCHANGES-105 URL: http://jira.codehaus.org/browse/MCHANGES-105 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: jira-report Affects Versions: 2.0-beta-3 Environment: maven 2.0.8 - please see output of mvn changes:jira-report -U -cpu -X -e /tmp/errors attached (error.log). Reproducable by using http://svn.codehaus.org/mojo/trunk/sandbox/was6-maven-plugin/ - and adding +issueManagement +systemjira/system + urlhttp://jira.codehaus.org/secure/IssueNavigator.jspa?reset=trueamp;mode=hideamp;pid=11062amp;sorter/order=DESCamp;sorter/field=priorityamp;resolution=-1amp;component=13178/url + /issueManagement + to the pom. Reporter: David J. M. Karlsen Attachments: error.log WAGON_VERSION: 1.0-beta-2 [INFO] [INFO] Building WAS6 Maven Plugin [INFO]task-segment: [changes:jira-report] [INFO] [INFO] [changes:jira-report] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org.apache.maven.doxia.siterenderer.Renderer.createSink(Ljava/io/File;Ljava/lang/String;)Lorg/apache/maven/doxia/siterenderer/sink/SiteRendererSink; [INFO] [INFO] Trace java.lang.NoSuchMethodError: org.apache.maven.doxia.siterenderer.Renderer.createSink(Ljava/io/File;Ljava/lang/String;)Lorg/apache/maven/doxia/siterenderer/sink/SiteRendererSink; at org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:63) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 13 seconds [INFO] Finished at: Mon Mar 17 13:07:16 CET 2008 [INFO] Final Memory: 8M/14M [INFO] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-105) java.lang.NoSuchMethodError on changes:jira-report
[ http://jira.codehaus.org/browse/MCHANGES-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=130573#action_130573 ] David J. M. Karlsen commented on MCHANGES-105: -- Green! [EMAIL PROTECTED]:~/projects/codehaus/mojo/mojo/was6-maven-plugin$ mvn clean org.apache.maven.plugins:maven-changes-plugin:2.0-20080411.201412-2:jira-report -f test_maven_changes_updated_pom.xml [INFO] Scanning for projects... WAGON_VERSION: 1.0-beta-2 [INFO] [INFO] Building WAS6 Maven Plugin [INFO]task-segment: [clean, org.apache.maven.plugins:maven-changes-plugin:2.0-20080411.201412-2:jira-report] [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugin-plugin/2.4.1/maven-plugin-plugin-2.4.1.pom 8K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugin-plugin/2.4.1/maven-plugin-plugin-2.4.1.jar 30K downloaded [INFO] [clean:clean] [INFO] Deleting directory /u/david/projects/codehaus/mojo/mojo/was6-maven-plugin/target [WARNING] Attempting to build MavenProject instance for Artifact (org.apache.maven.plugins:maven-changes-plugin:2.0-20080411.201412-2) of type: maven-plugin; constructing POM artifact instead. [INFO] [changes:jira-report] [INFO] Downloading from JIRA at: http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rsspid=11730statusIds=6resolutionIds=1sorter/field=createdsorter/order=DESCsorter/field=prioritysorter/order=DESCtempMax=100reset=truedecorator=none [ERROR] VM #displayTree: error : too few arguments to macro. Wanted 2 got 0 [ERROR] VM #menuItem: error : too few arguments to macro. Wanted 1 got 0 [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 23 seconds [INFO] Finished at: Sat Apr 12 02:29:51 CEST 2008 [INFO] Final Memory: 11M/20M [INFO] [EMAIL PROTECTED]:~/projects/codehaus/mojo/mojo/was6-maven-plugin$ ls target/ jira-results.xml site [EMAIL PROTECTED]:~/projects/codehaus/mojo/mojo/was6-maven-plugin$ ls target/site/ css images jira-report.html [EMAIL PROTECTED]:~/projects/codehaus/mojo/mojo/was6-maven-plugin$ java.lang.NoSuchMethodError on changes:jira-report -- Key: MCHANGES-105 URL: http://jira.codehaus.org/browse/MCHANGES-105 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: jira-report Affects Versions: 2.0-beta-3 Environment: maven 2.0.8 - please see output of mvn changes:jira-report -U -cpu -X -e /tmp/errors attached (error.log). Reproducable by using http://svn.codehaus.org/mojo/trunk/sandbox/was6-maven-plugin/ - and adding +issueManagement +systemjira/system + urlhttp://jira.codehaus.org/secure/IssueNavigator.jspa?reset=trueamp;mode=hideamp;pid=11062amp;sorter/order=DESCamp;sorter/field=priorityamp;resolution=-1amp;component=13178/url + /issueManagement + to the pom. Reporter: David J. M. Karlsen Attachments: error.log WAGON_VERSION: 1.0-beta-2 [INFO] [INFO] Building WAS6 Maven Plugin [INFO]task-segment: [changes:jira-report] [INFO] [INFO] [changes:jira-report] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org.apache.maven.doxia.siterenderer.Renderer.createSink(Ljava/io/File;Ljava/lang/String;)Lorg/apache/maven/doxia/siterenderer/sink/SiteRendererSink; [INFO] [INFO] Trace java.lang.NoSuchMethodError: org.apache.maven.doxia.siterenderer.Renderer.createSink(Ljava/io/File;Ljava/lang/String;)Lorg/apache/maven/doxia/siterenderer/sink/SiteRendererSink; at org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:63) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at
[jira] Created: (SUREFIRE-481) java.lang.NoSuchMethodError when forking on a 1.3 JDK
java.lang.NoSuchMethodError when forking on a 1.3 JDK - Key: SUREFIRE-481 URL: http://jira.codehaus.org/browse/SUREFIRE-481 Project: Maven Surefire Issue Type: Bug Components: Junit 4.x support Affects Versions: 2.4.2, 2.4.1, 2.4 Environment: Maven version: 2.0.7, 2.0.8, 2.0.9-RC8 or Java version: 1.5.0_12 Reporter: David J. M. Karlsen [INFO] [surefire:test] [DEBUG] dummy:dummy:jar:1.0 (selected for null) [DEBUG] org.apache.maven.surefire:surefire-booter:jar:2.4.2:runtime (selected for runtime) [DEBUG] org.apache.maven.surefire:surefire-api:jar:2.4.2:runtime (selected for runtime) [DEBUG] Adding to surefire booter test classpath: /heim/ab62939/.m2/repository/org/apache/maven/surefire/surefire-booter/2.4.2/surefire-booter-2.4.2.jar [DEBUG] Adding to surefire booter test classpath: /heim/ab62939/.m2/repository/org/apache/maven/surefire/surefire-api/2.4.2/surefire-api-2.4.2.jar [DEBUG] dummy:dummy:jar:1.0 (selected for null) [DEBUG] Retrieving parent-POM: org.apache.maven.surefire:surefire-providers::2.4.2 for project: null:surefire-junit:jar:null from the repository. [DEBUG] Adding managed dependencies for unknown:surefire-junit [DEBUG] org.apache.maven.surefire:surefire-api:jar:2.4.2 [DEBUG] org.apache.maven.surefire:surefire-booter:jar:2.4.2 [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.4.9 [DEBUG] org.apache.maven.surefire:surefire-junit:jar:2.4.2:test (selected for test) [DEBUG] junit:junit:jar:3.8.1:test (selected for test) [DEBUG] org.apache.maven.surefire:surefire-api:jar:2.4.2:test (selected for test) [DEBUG] Adding to surefire test classpath: /heim/ab62939/.m2/repository/org/apache/maven/surefire/surefire-junit/2.4.2/surefire-junit-2.4.2.jar [DEBUG] Adding to surefire test classpath: /heim/ab62939/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar [DEBUG] Adding to surefire test classpath: /heim/ab62939/.m2/repository/org/apache/maven/surefire/surefire-api/2.4.2/surefire-api-2.4.2.jar [DEBUG] Test Classpath : [snip...] [INFO] Surefire report directory: /tmp/dnbnorapi-trunk/dnbnorapi-server/target/surefire-reports Forking command line: /bin/sh -c cd /tmp/dnbnorapi-trunk/dnbnorapi-server /dnb/prosess/WebSphere5/AppServer/java/jre/bin/java -Xmx128M -jar /var/tmp/surefirebooter29275.jar /var/tmp/surefire29273tmp /var/tmp/surefire29274tmp java.lang.NoSuchMethodError at org.apache.maven.surefire.util.UrlUtils.getURL(UrlUtils.java:39) at org.apache.maven.surefire.booter.SurefireBooter.createClassLoader(SurefireBooter.java:730) at org.apache.maven.surefire.booter.SurefireBooter.createClassLoader(SurefireBooter.java:715) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:277) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:993) [ERROR] There are test failures. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (WAGON-105) NPE at org.apache.maven.wagon.repository.Repository.hashCode(Repository.java:241)
NPE at org.apache.maven.wagon.repository.Repository.hashCode(Repository.java:241) -- Key: WAGON-105 URL: http://jira.codehaus.org/browse/WAGON-105 Project: wagon Issue Type: Bug Environment: maven 2.0.9 RC6, Reporter: David J. M. Karlsen Priority: Blocker [INFO] [INFO] Building portal-core [INFO]task-segment: [clean, install] [INFO] [INFO] [clean:clean] [INFO] Deleting directory /tmp/portal-trunks/portal-core/target Downloading: http://repo.sandsli.dnb.no/px/repository/public/opensymphony/quartz/1.6.0/quartz-1.6.0.pom [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.wagon.repository.Repository.hashCode(Repository.java:241) at java.util.HashMap.put(HashMap.java:418) at java.util.HashSet.add(HashSet.java:194) at java.util.AbstractCollection.addAll(AbstractCollection.java:318) at java.util.HashSet.init(HashSet.java:100) at org.apache.maven.artifact.resolver.AbstractArtifactResolutionException.constructMessageBase(AbstractArtifactResolutionException.java:188) at org.apache.maven.artifact.resolver.AbstractArtifactResolutionException.init(AbstractArtifactResolutionException.java:67) at org.apache.maven.artifact.resolver.ArtifactNotFoundException.init(ArtifactNotFoundException.java:55) at org.apache.maven.artifact.resolver.ArtifactNotFoundException.init(ArtifactNotFoundException.java:48) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:212) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:74) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:545) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:249) at org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:105) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:380) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:300) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1415) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:405) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 1 minute 42 seconds [INFO] Finished at: Wed Apr 02 08:45:24 CEST 2008 [INFO] Final Memory: 24M/376M
[jira] Commented: (MNG-3495) NPE at org.apache.maven.wagon.repository.Repository.hashCode(Repository.java:241)
[ http://jira.codehaus.org/browse/MNG-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=129534#action_129534 ] David J. M. Karlsen commented on MNG-3495: -- Sure - how does it work? http://maven.apache.org/ref/2.0.8/maven-settings/settings.html#class_mirror isn't very informative. Probably all mirror's which have the same url have the same id? NPE at org.apache.maven.wagon.repository.Repository.hashCode(Repository.java:241) -- Key: MNG-3495 URL: http://jira.codehaus.org/browse/MNG-3495 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.9 Environment: maven 2.0.9 RC6, Reporter: David J. M. Karlsen Assignee: Brett Porter Priority: Blocker Fix For: 2.0.9 [INFO] [INFO] Building portal-core [INFO]task-segment: [clean, install] [INFO] [INFO] [clean:clean] [INFO] Deleting directory /tmp/portal-trunks/portal-core/target Downloading: http://repo.sandsli.dnb.no/px/repository/public/opensymphony/quartz/1.6.0/quartz-1.6.0.pom [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.wagon.repository.Repository.hashCode(Repository.java:241) at java.util.HashMap.put(HashMap.java:418) at java.util.HashSet.add(HashSet.java:194) at java.util.AbstractCollection.addAll(AbstractCollection.java:318) at java.util.HashSet.init(HashSet.java:100) at org.apache.maven.artifact.resolver.AbstractArtifactResolutionException.constructMessageBase(AbstractArtifactResolutionException.java:188) at org.apache.maven.artifact.resolver.AbstractArtifactResolutionException.init(AbstractArtifactResolutionException.java:67) at org.apache.maven.artifact.resolver.ArtifactNotFoundException.init(ArtifactNotFoundException.java:55) at org.apache.maven.artifact.resolver.ArtifactNotFoundException.init(ArtifactNotFoundException.java:48) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:212) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:74) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:545) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:249) at org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:105) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:380) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:300) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1415) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:405) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at
[jira] Created: (MDEP-160) analyze-report fails
analyze-report fails Key: MDEP-160 URL: http://jira.codehaus.org/browse/MDEP-160 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: analyze Affects Versions: 2.0 Environment: maven 2.0.8 java version 1.6.0_05 Java(TM) SE Runtime Environment (build 1.6.0_05-b13) Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode, sharing) Reporter: David J. M. Karlsen Assignee: Brian Fox mvn org.apache.maven.plugins:maven-dependency-plugin:2.0:analyze-report fails with: [INFO] [dependency:analyze-report] [INFO] /u/david/projects/codehaus/mojo/mojo/was6-maven-plugin/target [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org.apache.maven.doxia.siterenderer.Renderer.createSink(Ljava/io/File;Ljava/lang/String;)Lorg/apache/maven/doxia/siterenderer/sink/SiteRendererSink; [INFO] [INFO] Trace java.lang.NoSuchMethodError: org.apache.maven.doxia.siterenderer.Renderer.createSink(Ljava/io/File;Ljava/lang/String;)Lorg/apache/maven/doxia/siterenderer/sink/SiteRendererSink; at org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:63) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 44 seconds [INFO] Finished at: Tue Apr 01 22:14:23 CEST 2008 [INFO] Final Memory: 14M/25M [INFO] This can be tested on for example: svn co https://svn.codehaus.org/mojo/trunk/mojo/was6-maven-plugin test cd test mvn org.apache.maven.plugins:maven-dependency-plugin:2.0:analyze-report -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-105) java.lang.NoSuchMethodError on changes:jira-report
[ http://jira.codehaus.org/browse/MCHANGES-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=129370#action_129370 ] David J. M. Karlsen commented on MCHANGES-105: -- http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-changes-plugin/2.0-beta-4-SNAPSHOT/ works! [Although pom in https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-changes-plugin is still marked version2.0-SNAPSHOT/version] java.lang.NoSuchMethodError on changes:jira-report -- Key: MCHANGES-105 URL: http://jira.codehaus.org/browse/MCHANGES-105 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: jira-report Affects Versions: 2.0-beta-3 Environment: maven 2.0.8 - please see output of mvn changes:jira-report -U -cpu -X -e /tmp/errors attached (error.log). Reproducable by using http://svn.codehaus.org/mojo/trunk/sandbox/was6-maven-plugin/ - and adding +issueManagement +systemjira/system + urlhttp://jira.codehaus.org/secure/IssueNavigator.jspa?reset=trueamp;mode=hideamp;pid=11062amp;sorter/order=DESCamp;sorter/field=priorityamp;resolution=-1amp;component=13178/url + /issueManagement + to the pom. Reporter: David J. M. Karlsen Attachments: error.log WAGON_VERSION: 1.0-beta-2 [INFO] [INFO] Building WAS6 Maven Plugin [INFO]task-segment: [changes:jira-report] [INFO] [INFO] [changes:jira-report] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org.apache.maven.doxia.siterenderer.Renderer.createSink(Ljava/io/File;Ljava/lang/String;)Lorg/apache/maven/doxia/siterenderer/sink/SiteRendererSink; [INFO] [INFO] Trace java.lang.NoSuchMethodError: org.apache.maven.doxia.siterenderer.Renderer.createSink(Ljava/io/File;Ljava/lang/String;)Lorg/apache/maven/doxia/siterenderer/sink/SiteRendererSink; at org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:63) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 13 seconds [INFO] Finished at: Mon Mar 17 13:07:16 CET 2008 [INFO] Final Memory: 8M/14M [INFO] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-105) java.lang.NoSuchMethodError on changes:jira-report
[ http://jira.codehaus.org/browse/MCHANGES-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=129372#action_129372 ] David J. M. Karlsen commented on MCHANGES-105: -- I used: https://svn.codehaus.org/mojo/trunk/mojo/was6-maven-plugin as reproducable testcase java.lang.NoSuchMethodError on changes:jira-report -- Key: MCHANGES-105 URL: http://jira.codehaus.org/browse/MCHANGES-105 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: jira-report Affects Versions: 2.0-beta-3 Environment: maven 2.0.8 - please see output of mvn changes:jira-report -U -cpu -X -e /tmp/errors attached (error.log). Reproducable by using http://svn.codehaus.org/mojo/trunk/sandbox/was6-maven-plugin/ - and adding +issueManagement +systemjira/system + urlhttp://jira.codehaus.org/secure/IssueNavigator.jspa?reset=trueamp;mode=hideamp;pid=11062amp;sorter/order=DESCamp;sorter/field=priorityamp;resolution=-1amp;component=13178/url + /issueManagement + to the pom. Reporter: David J. M. Karlsen Attachments: error.log WAGON_VERSION: 1.0-beta-2 [INFO] [INFO] Building WAS6 Maven Plugin [INFO]task-segment: [changes:jira-report] [INFO] [INFO] [changes:jira-report] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org.apache.maven.doxia.siterenderer.Renderer.createSink(Ljava/io/File;Ljava/lang/String;)Lorg/apache/maven/doxia/siterenderer/sink/SiteRendererSink; [INFO] [INFO] Trace java.lang.NoSuchMethodError: org.apache.maven.doxia.siterenderer.Renderer.createSink(Ljava/io/File;Ljava/lang/String;)Lorg/apache/maven/doxia/siterenderer/sink/SiteRendererSink; at org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:63) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 13 seconds [INFO] Finished at: Mon Mar 17 13:07:16 CET 2008 [INFO] Final Memory: 8M/14M [INFO] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-105) java.lang.NoSuchMethodError on changes:jira-report
[ http://jira.codehaus.org/browse/MCHANGES-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=129375#action_129375 ] David J. M. Karlsen commented on MCHANGES-105: -- Ups - MCHANGES-100 wasn't supposed to be linked - sorry. java.lang.NoSuchMethodError on changes:jira-report -- Key: MCHANGES-105 URL: http://jira.codehaus.org/browse/MCHANGES-105 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: jira-report Affects Versions: 2.0-beta-3 Environment: maven 2.0.8 - please see output of mvn changes:jira-report -U -cpu -X -e /tmp/errors attached (error.log). Reproducable by using http://svn.codehaus.org/mojo/trunk/sandbox/was6-maven-plugin/ - and adding +issueManagement +systemjira/system + urlhttp://jira.codehaus.org/secure/IssueNavigator.jspa?reset=trueamp;mode=hideamp;pid=11062amp;sorter/order=DESCamp;sorter/field=priorityamp;resolution=-1amp;component=13178/url + /issueManagement + to the pom. Reporter: David J. M. Karlsen Attachments: error.log WAGON_VERSION: 1.0-beta-2 [INFO] [INFO] Building WAS6 Maven Plugin [INFO]task-segment: [changes:jira-report] [INFO] [INFO] [changes:jira-report] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org.apache.maven.doxia.siterenderer.Renderer.createSink(Ljava/io/File;Ljava/lang/String;)Lorg/apache/maven/doxia/siterenderer/sink/SiteRendererSink; [INFO] [INFO] Trace java.lang.NoSuchMethodError: org.apache.maven.doxia.siterenderer.Renderer.createSink(Ljava/io/File;Ljava/lang/String;)Lorg/apache/maven/doxia/siterenderer/sink/SiteRendererSink; at org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:63) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 13 seconds [INFO] Finished at: Mon Mar 17 13:07:16 CET 2008 [INFO] Final Memory: 8M/14M [INFO] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2431) Make it possible to specify that version should be the LATEST STABLE available
[ http://jira.codehaus.org/browse/MNG-2431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120832 ] David J. M. Karlsen commented on MNG-2431: -- Dependency ranges shold be sufficient for this. Make it possible to specify that version should be the LATEST STABLE available -- Key: MNG-2431 URL: http://jira.codehaus.org/browse/MNG-2431 Project: Maven 2 Issue Type: Improvement Components: Dependencies Affects Versions: 2.0.4 Reporter: Jimisola Laursen Fix For: Reviewed Pending Version Assignment Hi! I've been looking for a way to specify that the latest STABLE version of a library (dependency) should be used automatically. However, I can't seem to find any information on this. Is this not possible? The Dependency Version Ranges doesn't solve the problem for me since it sets with the lowest version satisfying the range. This guy had the same question about a year ago, but it doesn't look promising: http://www.nabble.com/newbie-ques%3A-downloading-latest-stable-jars-t74577.html#a202750 I asked the same question is this thread: http://www.nabble.com/How-to-get-the-latest-STABLE-version-of-a-library-dependency-automatical-tf1851718.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-344) connecting existing workspace artifact-projects
[ http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119515 ] David J. M. Karlsen commented on MECLIPSE-344: -- This issue is related to: http://jira.codehaus.org/browse/MECLIPSE-341 connecting existing workspace artifact-projects --- Key: MECLIPSE-344 URL: http://jira.codehaus.org/browse/MECLIPSE-344 Project: Maven 2.x Eclipse Plugin Issue Type: New Feature Components: Dependencies resolution and build path Reporter: Richard van Nieuwenhoven Assignee: Arnaud Heritier Attachments: MECLIPSE-344+rad7.patch, MECLIPSE-344+rad7.tgz, MECLIPSE-344.patch, MECLIPSE-344.tgz, workspace-new-files.tgz, workspace.patch, workspace_with_limit.patch This patch enables you to specify your workspace, and all dependent artefacts that are available in your eclipse-workspace will be attached as project references even if they are not in the reactor. the property can be set with -DworkspaceToConnect=. I did not have the time to create Test cases but, i maybe someone can help with that! The patch is based on the MECLIPSE-333 branch. as usual the new files are in the extra tgz. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3316) Barfs at attribues named .*encoding
[
http://jira.codehaus.org/browse/MNG-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David J. M. Karlsen updated MNG-3316:
-
Attachment: pom.xml
Please see attached file for example.
Barfs at attribues named .*encoding
---
Key: MNG-3316
URL: http://jira.codehaus.org/browse/MNG-3316
Project: Maven 2
Issue Type: Bug
Components: POM::Encoding
Affects Versions: 2.0.8
Reporter: David J. M. Karlsen
Priority: Blocker
Attachments: examplepom.xml, pom.xml
With 2.0.8 a regression snuck in:
Please see attached pom for details.
In several of my project I use xdoclet-maven-plugin. In
xdoclet-maven-plugin's configuration element there is an element, with an
attribute xmlencoding=${variable} (installed into my repository - NOT
talking about building them).
If maven tries to read these pom's (from my repo) it barfs with an error
message:
Project ID: some.group.id:myproject-war
Reason: Failed to build model from file
'c:\data\.m2\repository\some\group\id\myproject-war\1.3-SNAPSHOT\myproject-war-1.3-SNAPSHOT.pom'.
Error: '${ENCODING.DEFAULT}' for project some.group.id:myproject-war .
This did NOT happen before 2.0.8 - so it must be a regression.
What really puzzles me is why maven tries to parse these tags in the first
place (as they are configurations for elements which should be of no value
for this maven execution) - but I guess it was introduced when fixing
MNG-2932, MNG-2025 and/or MNG-2254 without knowing any details.
As 2.0.8 fails the entire build (which works on 2.0.7) I'm rating this as
Blocker.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3316) Barfs at attribues named .*encoding
[
http://jira.codehaus.org/browse/MNG-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119231
]
David J. M. Karlsen commented on MNG-3316:
--
Se attachment number two (pom.xml) which is a cleanup of the one originally
posted (examplepom.xml).
Parent pom has a correct and valid xml-header, I only refer to the
encoding.default variable in configuration elements for plugins.
With 2.0.8
mvn clean should be sufficient to trigger:
zoidberg:/tmp# mvn clean
[INFO] Scanning for projects...
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Error building POM (may not be this project's POM).
Project ID: unknown
Reason: Failed to build model from file '/tmp/pom.xml'.
Error: '${ENCODING.DEFAULT}' for project unknown
[INFO]
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Failed to build model from
file '/tmp/pom.xml'.
Error: '${ENCODING.DEFAULT}' for project unknown
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:376)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:289)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Failed to build
model from file '/tmp/pom.xml'.
Error: '${ENCODING.DEFAULT}' for project unknown
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1386)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:474)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:197)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:548)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:458)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:362)
... 11 more
Caused by: java.io.UnsupportedEncodingException: ${ENCODING.DEFAULT}
at sun.nio.cs.StreamDecoder.forInputStreamReader(StreamDecoder.java:52)
at java.io.InputStreamReader.init(InputStreamReader.java:83)
at
hidden.org.codehaus.plexus.util.xml.XmlReader.prepareReader(XmlReader.java:479)
at
hidden.org.codehaus.plexus.util.xml.XmlReader.doRawStream(XmlReader.java:462)
at
hidden.org.codehaus.plexus.util.xml.XmlReader.init(XmlReader.java:179)
at
hidden.org.codehaus.plexus.util.xml.XmlReader.init(XmlReader.java:142)
at
hidden.org.codehaus.plexus.util.xml.XmlReader.init(XmlReader.java:123)
at
hidden.org.codehaus.plexus.util.xml.XmlStreamReader.init(XmlStreamReader.java:67)
at
hidden.org.codehaus.plexus.util.ReaderFactory.newXmlReader(ReaderFactory.java:113)
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1376)
... 16 more
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Wed Jan 09 01:52:31 CET 2008
[INFO] Final Memory: 1M/4M
[INFO]
Barfs at attribues named .*encoding
---
Key: MNG-3316
URL: http://jira.codehaus.org/browse/MNG-3316
Project: Maven 2
Issue Type: Bug
Components: POM::Encoding
Affects Versions: 2.0.8
Reporter: David J. M. Karlsen
Priority: Blocker
Attachments: examplepom.xml, pom.xml
With 2.0.8 a regression snuck in:
Please see attached pom for details.
In several of my project I use xdoclet-maven-plugin. In
xdoclet-maven-plugin's configuration element there is an element, with an
attribute xmlencoding=${variable} (installed into my repository - NOT
talking about building them).
If maven tries to read these pom's (from my repo) it barfs with an error
message:
Project ID: some.group.id:myproject-war
Reason: Failed to build model from file
[jira] Commented: (SUREFIRE-55) Incorrect splitting of command line arguments in ForkConfiguration
[ http://jira.codehaus.org/browse/SUREFIRE-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118688 ] David J. M. Karlsen commented on SUREFIRE-55: - Try http://svn.davidkarlsen.com/avesvn/aspects/trunk/ run mvn -Pltw clean test or mvn -Pctw clean test *NIX both succeed on a windows machine - and bot will fail on a *NIX box. Incorrect splitting of command line arguments in ForkConfiguration -- Key: SUREFIRE-55 URL: http://jira.codehaus.org/browse/SUREFIRE-55 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.3, 2.x Environment: any Reporter: Walco van Loon Fix For: 2.4 Attachments: argline.patch ForkConfiguration.createCommandLine splits argLine on spaces, where it should use org.codehaus.plexus.util.cli.Commandline.setLine to create an argLine which splits quoted arguments containing spaces correctly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-55) Incorrect splitting of command line arguments in ForkConfiguration
[ http://jira.codehaus.org/browse/SUREFIRE-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118764 ] David J. M. Karlsen commented on SUREFIRE-55: - User error on my part - ignore my last comment. Incorrect splitting of command line arguments in ForkConfiguration -- Key: SUREFIRE-55 URL: http://jira.codehaus.org/browse/SUREFIRE-55 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.3, 2.x Environment: any Reporter: Walco van Loon Fix For: 2.4 Attachments: argline.patch ForkConfiguration.createCommandLine splits argLine on spaces, where it should use org.codehaus.plexus.util.cli.Commandline.setLine to create an argLine which splits quoted arguments containing spaces correctly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3163) Profile activation based on hostname or IP
[ http://jira.codehaus.org/browse/MNG-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116610 ] David J. M. Karlsen commented on MNG-3163: -- A more general approach would be to allow profiles to be triggered by shell. properties (not systemproperties). On windows a profile can be triggered by env.COMPUTERNAME and on *nix env.HOSTNAME ootb. Profile activation based on hostname or IP -- Key: MNG-3163 URL: http://jira.codehaus.org/browse/MNG-3163 Project: Maven 2 Issue Type: Improvement Components: Profiles Reporter: David J. M. Karlsen Priority: Minor Fix For: 2.x It would be very nice to be able to activate profiles based on hostname[s] or IP-address[es]. Yes, this could be exported from the system as a systemproperty quite easily on *NIX with -Dhostname=`hostname` but is a little more tricky on other platforms - so why not include it in maven itself? It would be even better if it can be expressed with regex'es or the likes. WDYT? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3316) Barfs at attribues named .*encoding
Barfs at attribues named .*encoding
---
Key: MNG-3316
URL: http://jira.codehaus.org/browse/MNG-3316
Project: Maven 2
Issue Type: Bug
Components: POM::Encoding
Affects Versions: 2.0.8
Reporter: David J. M. Karlsen
Priority: Blocker
Attachments: examplepom.xml
With 2.0.8 a regression snuck in:
Please see attached pom for details.
In several of my project I use xdoclet-maven-plugin. In xdoclet-maven-plugin's
configuration element there is an element, with an attribute
xmlencoding=${variable} (installed into my repository - NOT talking about
building them).
If maven tries to read these pom's (from my repo) it barfs with an error
message:
Project ID: some.group.id:myproject-war
Reason: Failed to build model from file
'c:\data\.m2\repository\some\group\id\myproject-war\1.3-SNAPSHOT\myproject-war-1.3-SNAPSHOT.pom'.
Error: '${ENCODING.DEFAULT}' for project some.group.id:myproject-war .
This did NOT happen before 2.0.8 - so it must be a regression.
What really puzzles me is why maven tries to parse these tags in the first
place (as they are configurations for elements which should be of no value for
this maven execution) - but I guess it was introduced when fixing MNG-2932,
MNG-2025 and/or MNG-2254 without knowing any details.
As 2.0.8 fails the entire build (which works on 2.0.7) I'm rating this as
Blocker.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3316) Barfs at attribues named .*encoding
[
http://jira.codehaus.org/browse/MNG-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116497
]
David J. M. Karlsen commented on MNG-3316:
--
It should also be noted that if I remote the element containing the xmlencoding
attribute the build will succeed.
Barfs at attribues named .*encoding
---
Key: MNG-3316
URL: http://jira.codehaus.org/browse/MNG-3316
Project: Maven 2
Issue Type: Bug
Components: POM::Encoding
Affects Versions: 2.0.8
Reporter: David J. M. Karlsen
Priority: Blocker
Attachments: examplepom.xml
With 2.0.8 a regression snuck in:
Please see attached pom for details.
In several of my project I use xdoclet-maven-plugin. In
xdoclet-maven-plugin's configuration element there is an element, with an
attribute xmlencoding=${variable} (installed into my repository - NOT
talking about building them).
If maven tries to read these pom's (from my repo) it barfs with an error
message:
Project ID: some.group.id:myproject-war
Reason: Failed to build model from file
'c:\data\.m2\repository\some\group\id\myproject-war\1.3-SNAPSHOT\myproject-war-1.3-SNAPSHOT.pom'.
Error: '${ENCODING.DEFAULT}' for project some.group.id:myproject-war .
This did NOT happen before 2.0.8 - so it must be a regression.
What really puzzles me is why maven tries to parse these tags in the first
place (as they are configurations for elements which should be of no value
for this maven execution) - but I guess it was introduced when fixing
MNG-2932, MNG-2025 and/or MNG-2254 without knowing any details.
As 2.0.8 fails the entire build (which works on 2.0.7) I'm rating this as
Blocker.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-132) Class not found when run/debug JUnit tests
[ http://jira.codehaus.org/browse/MECLIPSE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115970 ] David J. M. Karlsen commented on MECLIPSE-132: -- I do not thing this is a bug. It's a issue with eclipse not noticing that mvn has rebuilt it all (and the old state/references in eclipse are not valid). Pressing refresh on all the involved project solves the problem (e.g. eclipse rebuilds them). (Running eclipse europa on jdk 1.6) Class not found when run/debug JUnit tests Key: MECLIPSE-132 URL: http://jira.codehaus.org/browse/MECLIPSE-132 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: Dependencies resolution and build path Environment: gentoo linux 2006, kernel 2.6, sun-jdk-1.5.0.06, maven 2.0.4, eclipse sdk 3.2, myeclipse 5 m2 Reporter: Diego Ballve Attachments: maven-sample.zip This is for the behavior described in http://www.nabble.com/Keep-getting-%22Class-not-found%22-when-running-debugging-JUnit-tests-tf1851758.html#a5442440 You get Class not found when running/debuging JUnit tests. For me it happened when I was importing another project and its dependencies (both m2 projects). Clean compile works fine, problem is with run. The workaround to get it working is: In the project containing your tests, edit Java Build Path | Order and Export: Make sure M2 Dependencies appears BEFORE JRE System Library. Thanks, Diego -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MECLIPSE-341) Support RAD7
Support RAD7 Key: MECLIPSE-341 URL: http://jira.codehaus.org/browse/MECLIPSE-341 Project: Maven 2.x Eclipse Plugin Issue Type: New Feature Components: RAD support Affects Versions: 2.4 Environment: RAD7 Reporter: David J. M. Karlsen The current rad goal only supports RAD6. If I run this goal and try to import the projects into RAD, the capabilities are not recognized, thus it's not possible to debug on server and so on. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WAGON-80) Attempt to use proxySettings even when nonProxyHosts is defined
[ http://jira.codehaus.org/browse/WAGON-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112556 ] David J. M. Karlsen commented on WAGON-80: -- Any progress on this? It holds up corporate environments - as these usually are behind firewalls and proxies. We're not able to deploy the site or artifacts when proxy is off - and we can't download anything without it - so it's kind of a dead-end situation. Attempt to use proxySettings even when nonProxyHosts is defined --- Key: WAGON-80 URL: http://jira.codehaus.org/browse/WAGON-80 Project: wagon Issue Type: Bug Components: wagon-file, wagon-ftp, wagon-http, wagon-provider-api, wagon-provider-test, wagon-scm, wagon-ssh, wagon-ssh-external, wagon-webdav Environment: Maven 2.0.5 or maven 2.0.6, this report is based on 2.0.6 Reporter: David J. M. Karlsen Attachments: WAGON-80-wagon-provider-api.patch site-deploy hangs because of proxy-settings: [INFO] Generate Project Team report. [DEBUG] Generating /tmp/mobilebank/mobilebank-ear/target/site/project-info.html [DEBUG] Generating /tmp/mobilebank/mobilebank-ear/target/site/project-reports.html [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-site-plugin:2.0-beta-5:deploy' -- [DEBUG] (f) inputDirectory = /tmp/mobilebank/mobilebank-ear/target/site [DEBUG] (f) project = [EMAIL PROTECTED] [DEBUG] (f) settings = [EMAIL PROTECTED] [DEBUG] -- end configuration -- [INFO] [site:deploy] If I remove the proxies/proxy element[s] from my settings.xml it works. Scp is used for deployment. mvn -X site-deply|grep -i wagon gives: [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime (selected for runtime) [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime (selected for runtime) [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime (selected for runtime) [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-6 [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-6 [DEBUG] org.apache.maven.wagon:wagon-ssh-external:jar:1.0-alpha-6 [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-6 [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-6 [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime (selected for runtime) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (ARCHETYPE-101) maven-archetype-simple 1.0 is broken
[ http://jira.codehaus.org/browse/ARCHETYPE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David J. M. Karlsen closed ARCHETYPE-101. - Resolution: Cannot Reproduce Fix Version/s: 1.0-alpha-7 Hmm, closing as it seems OK after nuking local repo and trying again. maven-archetype-simple 1.0 is broken Key: ARCHETYPE-101 URL: http://jira.codehaus.org/browse/ARCHETYPE-101 Project: Maven Archetype Issue Type: Bug Components: Archetypes Affects Versions: 1.0 Environment: Windows XP, Java(TM) SE Runtime Environment (build 1.6.0_02-b05), maven 2.0.7 Reporter: David J. M. Karlsen Priority: Critical Fix For: 1.0-alpha-7 Archetype is broken. Running mvn archetype:create -DgroupId=com.davidkarlsen.jmsproxy -DartifactId=jmsproxy -DarchetypeArtifactId=maven-archetype-simple -U -cpu results in [INFO] Using following parameters for creating Archetype: maven-archetype-simple:RELEASE [INFO] [INFO] Parameter: groupId, Value: com.davidkarlsen.jmsproxy [INFO] Parameter: packageName, Value: com.davidkarlsen.jmsproxy [INFO] Parameter: package, Value: com.davidkarlsen.jmsproxy [INFO] Parameter: artifactId, Value: jmsproxy [INFO] Parameter: basedir, Value: C:\data [INFO] Parameter: version, Value: 1.0-SNAPSHOT [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error creating from archetype Embedded error: The META-INF/maven/archetype.xml descriptor cannot be found. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Sat Sep 15 13:53:06 CEST 2007 [INFO] Final Memory: 4M/8M [INFO] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (ARCHETYPE-101) maven-archetype-simple 1.0 is broken
[ http://jira.codehaus.org/browse/ARCHETYPE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107521 ] David J. M. Karlsen commented on ARCHETYPE-101: --- Hmm, strange - tried nuking org\apache\maven\archetype and org\apache\maven\archetypes (which I also tried yesterday). And now it works both with maven-archetype-plugin 1.0-alpha-7 and 1.0-alpha-4 !? maven-archetype-simple 1.0 is broken Key: ARCHETYPE-101 URL: http://jira.codehaus.org/browse/ARCHETYPE-101 Project: Maven Archetype Issue Type: Bug Components: Archetypes Affects Versions: 1.0 Environment: Windows XP, Java(TM) SE Runtime Environment (build 1.6.0_02-b05), maven 2.0.7 Reporter: David J. M. Karlsen Priority: Critical Fix For: 1.0-alpha-7 Archetype is broken. Running mvn archetype:create -DgroupId=com.davidkarlsen.jmsproxy -DartifactId=jmsproxy -DarchetypeArtifactId=maven-archetype-simple -U -cpu results in [INFO] Using following parameters for creating Archetype: maven-archetype-simple:RELEASE [INFO] [INFO] Parameter: groupId, Value: com.davidkarlsen.jmsproxy [INFO] Parameter: packageName, Value: com.davidkarlsen.jmsproxy [INFO] Parameter: package, Value: com.davidkarlsen.jmsproxy [INFO] Parameter: artifactId, Value: jmsproxy [INFO] Parameter: basedir, Value: C:\data [INFO] Parameter: version, Value: 1.0-SNAPSHOT [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error creating from archetype Embedded error: The META-INF/maven/archetype.xml descriptor cannot be found. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Sat Sep 15 13:53:06 CEST 2007 [INFO] Final Memory: 4M/8M [INFO] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (ARCHETYPE-101) maven-archetype-simple 1.0 is broken
maven-archetype-simple 1.0 is broken Key: ARCHETYPE-101 URL: http://jira.codehaus.org/browse/ARCHETYPE-101 Project: Maven Archetype Issue Type: Bug Components: Archetypes Affects Versions: 1.0 Environment: Windows XP, Java(TM) SE Runtime Environment (build 1.6.0_02-b05), maven 2.0.7 Reporter: David J. M. Karlsen Priority: Critical Archetype is broken. Running mvn archetype:create -DgroupId=com.davidkarlsen.jmsproxy -DartifactId=jmsproxy -DarchetypeArtifactId=maven-archetype-simple -U -cpu results in [INFO] Using following parameters for creating Archetype: maven-archetype-simple:RELEASE [INFO] [INFO] Parameter: groupId, Value: com.davidkarlsen.jmsproxy [INFO] Parameter: packageName, Value: com.davidkarlsen.jmsproxy [INFO] Parameter: package, Value: com.davidkarlsen.jmsproxy [INFO] Parameter: artifactId, Value: jmsproxy [INFO] Parameter: basedir, Value: C:\data [INFO] Parameter: version, Value: 1.0-SNAPSHOT [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error creating from archetype Embedded error: The META-INF/maven/archetype.xml descriptor cannot be found. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Sat Sep 15 13:53:06 CEST 2007 [INFO] Final Memory: 4M/8M [INFO] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3163) Profile activation based on hostname or IP
Profile activation based on hostname or IP -- Key: MNG-3163 URL: http://jira.codehaus.org/browse/MNG-3163 Project: Maven 2 Issue Type: Improvement Components: Profiles Reporter: David J. M. Karlsen Priority: Minor It would be very nice to be able to activate profiles based on hostname[s] or IP-address[es]. Yes, this could be exported from the system as a systemproperty quite easily on *NIX with -Dhostname=`hostname` but is a little more tricky on other platforms - so why not include it in maven itself? It would be even better if it can be expressed with regex'es or the likes. WDYT? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
