[jira] [Commented] (MSHADE-454) Shade Plugin does not work with JDK 20
[
https://issues.apache.org/jira/browse/MSHADE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753292#comment-17753292
]
Torsten Curdt commented on MSHADE-454:
--
Interesting. I did know that makes a difference. Apparently it does. Thanks for
the help.
I just released 2.9.0. Should be available once the maven repo has synced.
> Shade Plugin does not work with JDK 20
> --
>
> Key: MSHADE-454
> URL: https://issues.apache.org/jira/browse/MSHADE-454
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Patrick Barry
>Priority: Major
>
> We are trying to use JDK 20 and this was the only plugin we had to
> work-around because it would not work. Are there plans to update this plugin
> to support JDK 20+? Is there a work-around until changes are made?
>
> Our current work-around is using assembly plugin, but we use shade plugin in
> many of the apps we are migrating and our preference is to continue to use
> Shade-plugin.
> Currently- if you try to use shade plugin with JDK 20, you get : Unsupported
> class file major version 64
>
> {noformat}
> Error creating shaded jar: Unsupported class file major version 64
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:104)
> at java.lang.reflect.Method.invoke (Method.java:578)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:283)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:226)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:407)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:348)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: Unsupported class file major version 64
> at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute
> (ShadeMojo.java:624)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBui
[jira] [Commented] (MSHADE-454) Shade Plugin does not work with JDK 20
[
https://issues.apache.org/jira/browse/MSHADE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753272#comment-17753272
]
Torsten Curdt commented on MSHADE-454:
--
Maybe the "package" and "deploy" in one is causing this?
> Shade Plugin does not work with JDK 20
> --
>
> Key: MSHADE-454
> URL: https://issues.apache.org/jira/browse/MSHADE-454
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Patrick Barry
>Priority: Major
>
> We are trying to use JDK 20 and this was the only plugin we had to
> work-around because it would not work. Are there plans to update this plugin
> to support JDK 20+? Is there a work-around until changes are made?
>
> Our current work-around is using assembly plugin, but we use shade plugin in
> many of the apps we are migrating and our preference is to continue to use
> Shade-plugin.
> Currently- if you try to use shade plugin with JDK 20, you get : Unsupported
> class file major version 64
>
> {noformat}
> Error creating shaded jar: Unsupported class file major version 64
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:104)
> at java.lang.reflect.Method.invoke (Method.java:578)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:283)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:226)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:407)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:348)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: Unsupported class file major version 64
> at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute
> (ShadeMojo.java:624)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.e
[jira] [Commented] (MSHADE-454) Shade Plugin does not work with JDK 20
[
https://issues.apache.org/jira/browse/MSHADE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753269#comment-17753269
]
Torsten Curdt commented on MSHADE-454:
--
Can you try a `mvn -B -Prelease --file pom.xml package deploy` because that's
what the CI server tries to do.
> Shade Plugin does not work with JDK 20
> --
>
> Key: MSHADE-454
> URL: https://issues.apache.org/jira/browse/MSHADE-454
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Patrick Barry
>Priority: Major
>
> We are trying to use JDK 20 and this was the only plugin we had to
> work-around because it would not work. Are there plans to update this plugin
> to support JDK 20+? Is there a work-around until changes are made?
>
> Our current work-around is using assembly plugin, but we use shade plugin in
> many of the apps we are migrating and our preference is to continue to use
> Shade-plugin.
> Currently- if you try to use shade plugin with JDK 20, you get : Unsupported
> class file major version 64
>
> {noformat}
> Error creating shaded jar: Unsupported class file major version 64
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:104)
> at java.lang.reflect.Method.invoke (Method.java:578)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:283)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:226)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:407)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:348)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: Unsupported class file major version 64
> at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute
> (ShadeMojo.java:624)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at
[jira] [Commented] (MSHADE-454) Shade Plugin does not work with JDK 20
[
https://issues.apache.org/jira/browse/MSHADE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17752908#comment-17752908
]
Torsten Curdt commented on MSHADE-454:
--
Seems like the maven-source-plugin introduced some changes in 3.3.0 that broke
the release pipeline. And it seems like I am not the only one struggling with
that change.
While I think understand the reasoning behind the introduced check, it seems
like false error in the jdependency case.
But I happy to have someone convince me otherwise.
I would love to fix the release build properly. Not quite sure how that
classifier thing is supposed work/help here.
But if it's urgent I guess I could downgrade the plugin for the release.
Let me know if you have some input [~patrickjamesbarry] [~michael-o]
> Shade Plugin does not work with JDK 20
> --
>
> Key: MSHADE-454
> URL: https://issues.apache.org/jira/browse/MSHADE-454
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Patrick Barry
>Priority: Major
>
> We are trying to use JDK 20 and this was the only plugin we had to
> work-around because it would not work. Are there plans to update this plugin
> to support JDK 20+? Is there a work-around until changes are made?
>
> Our current work-around is using assembly plugin, but we use shade plugin in
> many of the apps we are migrating and our preference is to continue to use
> Shade-plugin.
> Currently- if you try to use shade plugin with JDK 20, you get : Unsupported
> class file major version 64
>
> {noformat}
> Error creating shaded jar: Unsupported class file major version 64
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:104)
> at java.lang.reflect.Method.invoke (Method.java:578)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:283)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:226)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:407)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:348)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: Unsupported class file major version 64
> at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute
> (ShadeMojo.java:624)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutio
[jira] [Commented] (MSHADE-454) Shade Plugin does not work with JDK 20
[
https://issues.apache.org/jira/browse/MSHADE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17752694#comment-17752694
]
Torsten Curdt commented on MSHADE-454:
--
Meh. The CI pipeline failed to release.
{noformat}
Error: We have duplicated artifacts attached.
1165[INFO]
1166[INFO] BUILD FAILURE
1167[INFO]
1168[INFO] Total time: 21.139 s
1169[INFO] Finished at: 2023-08-10T08:24:40Z
1170[INFO]
1171Error: Failed to execute goal
org.apache.maven.plugins:maven-source-plugin:3.3.0:jar-no-fork (attach-sources)
on project jdependency: Presumably you have configured maven-source-plugn to
execute twice times in your build. You have to configure a classifier for at
least on of them. -> [Help 1]{noformat}
Not sure why the source plugin is complaining. If someone has some insights?
https://github.com/tcurdt/jdependency/actions/runs/5818725372/job/15775712616
> Shade Plugin does not work with JDK 20
> --
>
> Key: MSHADE-454
> URL: https://issues.apache.org/jira/browse/MSHADE-454
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Patrick Barry
>Priority: Major
>
> We are trying to use JDK 20 and this was the only plugin we had to
> work-around because it would not work. Are there plans to update this plugin
> to support JDK 20+? Is there a work-around until changes are made?
>
> Our current work-around is using assembly plugin, but we use shade plugin in
> many of the apps we are migrating and our preference is to continue to use
> Shade-plugin.
> Currently- if you try to use shade plugin with JDK 20, you get : Unsupported
> class file major version 64
>
> {noformat}
> Error creating shaded jar: Unsupported class file major version 64
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:104)
> at java.lang.reflect.Method.invoke (Method.java:578)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:283)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:226)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:407)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:348)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: Unsupported class file major version 64
> at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute
> (ShadeMojo.java:624)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExec
[jira] [Commented] (MSHADE-454) Shade Plugin does not work with JDK 20
[
https://issues.apache.org/jira/browse/MSHADE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17752687#comment-17752687
]
Torsten Curdt commented on MSHADE-454:
--
Sorry for being a little behind. I sure can.
> Shade Plugin does not work with JDK 20
> --
>
> Key: MSHADE-454
> URL: https://issues.apache.org/jira/browse/MSHADE-454
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Patrick Barry
>Priority: Major
>
> We are trying to use JDK 20 and this was the only plugin we had to
> work-around because it would not work. Are there plans to update this plugin
> to support JDK 20+? Is there a work-around until changes are made?
>
> Our current work-around is using assembly plugin, but we use shade plugin in
> many of the apps we are migrating and our preference is to continue to use
> Shade-plugin.
> Currently- if you try to use shade plugin with JDK 20, you get : Unsupported
> class file major version 64
>
> {noformat}
> Error creating shaded jar: Unsupported class file major version 64
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:104)
> at java.lang.reflect.Method.invoke (Method.java:578)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:283)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:226)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:407)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:348)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: Unsupported class file major version 64
> at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute
> (ShadeMojo.java:624)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (
[jira] [Created] (MSHADE-327) improved integration test coverage for relocation and minification
Torsten Curdt created MSHADE-327: Summary: improved integration test coverage for relocation and minification Key: MSHADE-327 URL: https://issues.apache.org/jira/browse/MSHADE-327 Project: Maven Shade Plugin Issue Type: Test Affects Versions: 3.2.1 Reporter: Torsten Curdt This shows that relocation and minification of the jar work together. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] Commented: (MEV-609) The following POMs do not even parse
[
http://jira.codehaus.org/browse/MEV-609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=242078#action_242078
]
Torsten Curdt commented on MEV-609:
---
It wasn't clear a patch was expected for this. It would probably be much easier
to fix in place if one has file level access. Even easier than verifying and
applying all those patches.
Kind of sad you just close this and leave the repo broken.
> The following POMs do not even parse
>
>
> Key: MEV-609
> URL: http://jira.codehaus.org/browse/MEV-609
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Invalid POM
>Reporter: Torsten Curdt
>Assignee: Juven Xu
>
> {code}
> repository/acegisecurity/acegi-security/0.7.0/acegi-security-0.7.0.pom failed
> Invalid byte 2 of 3-byte UTF-8 sequence.
> repository/activemq/activemq-itest-ejb/1.1-G1M3/activemq-itest-ejb-1.1-G1M3.pom
> failed locator.ent (No such file or directory)
> repository/activemq/activemq-itest-ejb/1.2/activemq-itest-ejb-1.2.pom failed
> locator.ent (No such file or directory)
> repository/ant/ant/1.6.5/ant-1.6.5.pom failed The prefix "xsi" for attribute
> "xsi:schemaLocation" associated with an element type "project" is not bound.
> repository/com/javaexchangeconnector/jec/1.52_01/jec-1.52_01.pom failed The
> element type "artifactId" must be terminated by the matching end-tag
> "".
> repository/com/novell/ldap/jldap/2006-09-28/jldap-2006-09-28.pom failed The
> reference to entity "cvsroot" must end with the ';' delimiter.
> repository/com/pragmaticautomation/pragautox10/1.0/pragautox10-1.0.pom failed
> Invalid byte 1 of 1-byte UTF-8 sequence.
> repository/easyconf/easyconf/0.9.0/easyconf-0.9.0.pom failed Invalid byte 2
> of 2-byte UTF-8 sequence.
> repository/generama/generama/1.2.3/generama-1.2.3.pom failed Invalid byte 1
> of 1-byte UTF-8 sequence.
> repository/jhunlang/jmorph/0.2/jmorph-0.2.pom failed Invalid byte 2 of 2-byte
> UTF-8 sequence.
> repository/net/sourceforge/jsdp/jsdp/1.0/jsdp-1.0.pom failed The prefix "xsi"
> for attribute "xsi:schemaLocation" associated with an element type "project"
> is not bound.
> repository/net/sourceforge/stripes/stripes/1.3.1/stripes-1.3.1.pom failed The
> string "--" is not permitted within comments.
> repository/org/apache/maven/continuum/continuum-parent/1.0/continuum-parent-1.0-javadoc.pom
> failed Content is not allowed in prolog.
> repository/org/apache/maven/maven/2.0/maven-2.0-javadoc.pom failed Content is
> not allowed in prolog.
> repository/org/apache/maven/maven-plugin-tools/2.0/maven-plugin-tools-2.0-javadoc.pom
> failed Content is not allowed in prolog.
> repository/org/apache/maven/maven-script/2.0/maven-script-2.0-javadoc.pom
> failed Content is not allowed in prolog.
> repository/org/apache/maven/reporting/maven-reporting/2.0/maven-reporting-2.0-javadoc.pom
> failed Content is not allowed in prolog.
> repository/org/apache/maven/scm/maven-scm/1.0-alpha-4/maven-scm-1.0-alpha-4-javadoc.pom
> failed Content is not allowed in prolog.
> repository/org/apache/maven/scm/maven-scm-managers/1.0-alpha-4/maven-scm-managers-1.0-alpha-4-javadoc.pom
> failed Content is not allowed in prolog.
> repository/org/apache/maven/scm/maven-scm-providers/1.0-alpha-4/maven-scm-providers-1.0-alpha-4-javadoc.pom
> failed Content is not allowed in prolog.
> repository/org/codehaus/gant/gant/1.0.0/gant-1.0.0.pom failed The entity
> "copy" was referenced, but not declared.
> repository/org/codehaus/gant/gant/1.0.1/gant-1.0.1.pom failed The entity
> "copy" was referenced, but not declared.
> repository/org/codehaus/gant/gant/1.0.2/gant-1.0.2.pom failed The entity
> "copy" was referenced, but not declared.
> repository/org/codehaus/gant/gant/1.1.0/gant-1.1.0.pom failed The entity
> "copy" was referenced, but not declared.
> repository/org/codehaus/gant/gant/1.1.1/gant-1.1.1.pom failed The entity
> "copy" was referenced, but not declared.
> repository/org/codehaus/gant/gant/1.1.2/gant-1.1.2.pom failed The entity
> "copy" was referenced, but not declared.
> repository/org/codehaus/gant/gant/1.2.0/gant-1.2.0.pom failed The entity
> "copy" was referenced, but not declared.
> repository/org/codehaus/gant/gant/1.3.0/gant-1.3.0.pom failed The entity
> "copy" was referenced, but not declared.
> repository/org/codehaus/jackson/jackson-lgpl/0.9.3/jackson-lgpl-0.9.3.pom
> failed The element type "description" must be terminated by the matching
> end-tag "".
> repository/org/codehaus/modello/modello/1.0-alpha-17/modello-1.0-alpha-17.pom
> failed Invalid byte 1 of 1-byte UTF-8 sequence.
> repository/org/codehaus/mojo/clirr-maven-plugin/2.1/clirr-maven-plugin-2.1.pom
> failed Invalid byte 2 of 4-byte UTF-8 sequence.
> repository/org/codehaus/mojo/clirr-maven-plugin/2.1.1/clirr-maven-plugin-2.1.1.pom
> failed Invalid byte 2 of 4-byte UTF-8
[jira] Commented: (MSHADE-84) added support for minijar'ing
[ http://jira.codehaus.org/browse/MSHADE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231227#action_231227 ] Torsten Curdt commented on MSHADE-84: - Well, spotted with the input streams ...they were first closed inside jdependency but I changed this as this is the more expected behavior (obviously ;) Style I just applied through eclipse which also fixed a couple of unrelated style issues. > added support for minijar'ing > - > > Key: MSHADE-84 > URL: http://jira.codehaus.org/browse/MSHADE-84 > Project: Maven 2.x Shade Plugin > Issue Type: Improvement >Affects Versions: 1.3.4 >Reporter: Torsten Curdt > Attachments: minijar.diff, minijar.diff > > > http://github.com/tcurdt/maven-plugins/commit/5ac23b358b15ed315c871a3b8cb3301a86802a8d > just set "minimizeJar" to "true" in the configuration to strip unused classes -- 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: (MSHADE-84) added support for minijar'ing
[ http://jira.codehaus.org/browse/MSHADE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Curdt updated MSHADE-84: Attachment: minijar.diff close inputstreams and style > added support for minijar'ing > - > > Key: MSHADE-84 > URL: http://jira.codehaus.org/browse/MSHADE-84 > Project: Maven 2.x Shade Plugin > Issue Type: Improvement >Affects Versions: 1.3.4 >Reporter: Torsten Curdt > Attachments: minijar.diff, minijar.diff > > > http://github.com/tcurdt/maven-plugins/commit/5ac23b358b15ed315c871a3b8cb3301a86802a8d > just set "minimizeJar" to "true" in the configuration to strip unused classes -- 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: (MSHADE-84) added support for minijar'ing
added support for minijar'ing - Key: MSHADE-84 URL: http://jira.codehaus.org/browse/MSHADE-84 Project: Maven 2.x Shade Plugin Issue Type: Improvement Affects Versions: 1.3.4 Reporter: Torsten Curdt Attachments: minijar.diff http://github.com/tcurdt/maven-plugins/commit/5ac23b358b15ed315c871a3b8cb3301a86802a8d just set "minimizeJar" to "true" in the configuration to strip unused classes -- 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-2638) Update to latest version of SNMP4J (1.10.1)
Update to latest version of SNMP4J (1.10.1) --- Key: MAVENUPLOAD-2638 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2638 Project: Maven Upload Requests Issue Type: Wish Reporter: Torsten Curdt Just updated to the latest version. Official build from http://www.snmp4j.org/ -- 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-2637) Update to latest version of SNMP4J-agent (1.3.1)
Update to latest version of SNMP4J-agent (1.3.1) Key: MAVENUPLOAD-2637 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2637 Project: Maven Upload Requests Issue Type: Wish Reporter: Torsten Curdt Just updated to the latest version. Official build from http://www.snmp4j.org/ -- 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-609) The following POMs do not even parse
The following POMs do not even parse
Key: MEV-609
URL: http://jira.codehaus.org/browse/MEV-609
Project: Maven Evangelism
Issue Type: Bug
Components: Invalid POM
Reporter: Torsten Curdt
{code}
repository/acegisecurity/acegi-security/0.7.0/acegi-security-0.7.0.pom failed
Invalid byte 2 of 3-byte UTF-8 sequence.
repository/activemq/activemq-itest-ejb/1.1-G1M3/activemq-itest-ejb-1.1-G1M3.pom
failed locator.ent (No such file or directory)
repository/activemq/activemq-itest-ejb/1.2/activemq-itest-ejb-1.2.pom failed
locator.ent (No such file or directory)
repository/ant/ant/1.6.5/ant-1.6.5.pom failed The prefix "xsi" for attribute
"xsi:schemaLocation" associated with an element type "project" is not bound.
repository/com/javaexchangeconnector/jec/1.52_01/jec-1.52_01.pom failed The
element type "artifactId" must be terminated by the matching end-tag
"".
repository/com/novell/ldap/jldap/2006-09-28/jldap-2006-09-28.pom failed The
reference to entity "cvsroot" must end with the ';' delimiter.
repository/com/pragmaticautomation/pragautox10/1.0/pragautox10-1.0.pom failed
Invalid byte 1 of 1-byte UTF-8 sequence.
repository/easyconf/easyconf/0.9.0/easyconf-0.9.0.pom failed Invalid byte 2 of
2-byte UTF-8 sequence.
repository/generama/generama/1.2.3/generama-1.2.3.pom failed Invalid byte 1 of
1-byte UTF-8 sequence.
repository/jhunlang/jmorph/0.2/jmorph-0.2.pom failed Invalid byte 2 of 2-byte
UTF-8 sequence.
repository/net/sourceforge/jsdp/jsdp/1.0/jsdp-1.0.pom failed The prefix "xsi"
for attribute "xsi:schemaLocation" associated with an element type "project" is
not bound.
repository/net/sourceforge/stripes/stripes/1.3.1/stripes-1.3.1.pom failed The
string "--" is not permitted within comments.
repository/org/apache/maven/continuum/continuum-parent/1.0/continuum-parent-1.0-javadoc.pom
failed Content is not allowed in prolog.
repository/org/apache/maven/maven/2.0/maven-2.0-javadoc.pom failed Content is
not allowed in prolog.
repository/org/apache/maven/maven-plugin-tools/2.0/maven-plugin-tools-2.0-javadoc.pom
failed Content is not allowed in prolog.
repository/org/apache/maven/maven-script/2.0/maven-script-2.0-javadoc.pom
failed Content is not allowed in prolog.
repository/org/apache/maven/reporting/maven-reporting/2.0/maven-reporting-2.0-javadoc.pom
failed Content is not allowed in prolog.
repository/org/apache/maven/scm/maven-scm/1.0-alpha-4/maven-scm-1.0-alpha-4-javadoc.pom
failed Content is not allowed in prolog.
repository/org/apache/maven/scm/maven-scm-managers/1.0-alpha-4/maven-scm-managers-1.0-alpha-4-javadoc.pom
failed Content is not allowed in prolog.
repository/org/apache/maven/scm/maven-scm-providers/1.0-alpha-4/maven-scm-providers-1.0-alpha-4-javadoc.pom
failed Content is not allowed in prolog.
repository/org/codehaus/gant/gant/1.0.0/gant-1.0.0.pom failed The entity "copy"
was referenced, but not declared.
repository/org/codehaus/gant/gant/1.0.1/gant-1.0.1.pom failed The entity "copy"
was referenced, but not declared.
repository/org/codehaus/gant/gant/1.0.2/gant-1.0.2.pom failed The entity "copy"
was referenced, but not declared.
repository/org/codehaus/gant/gant/1.1.0/gant-1.1.0.pom failed The entity "copy"
was referenced, but not declared.
repository/org/codehaus/gant/gant/1.1.1/gant-1.1.1.pom failed The entity "copy"
was referenced, but not declared.
repository/org/codehaus/gant/gant/1.1.2/gant-1.1.2.pom failed The entity "copy"
was referenced, but not declared.
repository/org/codehaus/gant/gant/1.2.0/gant-1.2.0.pom failed The entity "copy"
was referenced, but not declared.
repository/org/codehaus/gant/gant/1.3.0/gant-1.3.0.pom failed The entity "copy"
was referenced, but not declared.
repository/org/codehaus/jackson/jackson-lgpl/0.9.3/jackson-lgpl-0.9.3.pom
failed The element type "description" must be terminated by the matching
end-tag "".
repository/org/codehaus/modello/modello/1.0-alpha-17/modello-1.0-alpha-17.pom
failed Invalid byte 1 of 1-byte UTF-8 sequence.
repository/org/codehaus/mojo/clirr-maven-plugin/2.1/clirr-maven-plugin-2.1.pom
failed Invalid byte 2 of 4-byte UTF-8 sequence.
repository/org/codehaus/mojo/clirr-maven-plugin/2.1.1/clirr-maven-plugin-2.1.1.pom
failed Invalid byte 2 of 4-byte UTF-8 sequence.
repository/org/codehaus/mojo/osxappbundle-maven-plugin/1.0-alpha-1/osxappbundle-maven-plugin-1.0-alpha-1.pom
failed Invalid byte 1 of 1-byte UTF-8 sequence.
repository/org/codehaus/mojo/solaris-maven-plugin/1.0-alpha-1/solaris-maven-plugin-1.0-alpha-1.pom
failed Invalid byte 1 of 1-byte UTF-8 sequence.
repository/org/codehaus/mvel/1.2.22-java1.4/mvel-1.2.22-java1.4.pom failed The
element type "packaging" must be terminated by the matching end-tag
"".
repository/org/codehaus/plexus/plexus/1.0.4/plexus-1.0.4.pom failed The entity
"oslash" was referenced, but not declared.
repository/org/codehaus/plexus/plexus/1.0.5/plexus-1.0.5.pom failed T
[jira] Commented: (MAVENUPLOAD-2249) New bundles for ANTLR and StringTemplate artifacts
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152017#action_152017 ] Torsten Curdt commented on MAVENUPLOAD-2249: The stringtemplate pom has 3.3-SNAPSHOT as version. It should be 3.2. > New bundles for ANTLR and StringTemplate artifacts > -- > > Key: MAVENUPLOAD-2249 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2249 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Jim Idle > > http://www.antlr.org/download/maven/stringtemplate-3.0-bundle.jar > http://www.antlr.org/download/maven/stringtemplate-3.2-bundle.jar > http://www.antlr.org/download/maven/antlr-runtime-3.1-bundle.jar > http://www.antlr.org/download/maven/antlr-runtime-3.1.1-bundle.jar > http://www.antlr.org/download/maven/antlr-3.1-bundle.jar > http://www.antlr.org/download/maven/antlr-3.1.1-bundle.jar > I am one of the maintainers of the ANTLR parser generator and have produced > new artifacts for the repository. Please upload them - you can see that the > URLs are from the official ANTLR web site. This will be the last manual > upload as these dependencies will now allow us to shift to a maven build > process. We then intend to create a repository and register it for rsync. > Thanks, > Jim Idle -- 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-2247) please pull releases from the vafer.org repo via rsync_ssh
please pull releases from the vafer.org repo via rsync_ssh -- Key: MAVENUPLOAD-2247 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2247 Project: Maven Upload Requests Issue Type: Wish Reporter: Torsten Curdt "org.vafer","[EMAIL PROTECTED]:m2repo/releases","rsync_ssh","Torsten Curdt","[EMAIL PROTECTED]",, -- 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: (MRELEASE-381) url syntax not good enough for the git scm provider
url syntax not good enough for the git scm provider
---
Key: MRELEASE-381
URL: http://jira.codehaus.org/browse/MRELEASE-381
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: scm
Affects Versions: 2.0-beta-7
Reporter: Torsten Curdt
The problem is that git supports 2 different URL schemes. For the normal RFC
2396 standard and ssh style. So in theory all these styles should work:
normal anonymous absolute:
{code}git clone git://github.com/olamy/scm-git-test-one-module.git{code}
normal anonymous relative:
{code}git clone git://github.com:olamy/scm-git-test-one-module.git{code}
normal developer absolute:
{code}git clone ssh://[EMAIL PROTECTED]/olamy/scm-git-test-one-module.git{code}
normal developer relative:
{code}git clone ssh://[EMAIL PROTECTED]/~git/olamy/scm-git-test-one-module{code}
ssh developer absolute:
{code}git clone [EMAIL PROTECTED]/olamy/scm-git-test-one-module.git{code}
ssh developer relative:
{code}git clone [EMAIL PROTECTED]:olamy/scm-git-test-one-module{code}
In reality the ssh:// URL is not always supported. (For example github does
not). In fact they suggest to use
normal anonymous absolute:
{code}git://github.com/olamy/scm-git-test-one-module.git{code}
ssh developer relative:
[EMAIL PROTECTED]:olamy/scm-git-test-one-module.git{code}
For the initial checkout the developer will use the command line and set
"[EMAIL PROTECTED]:olamy/scm-git-test-one-module.git" as the remote address. So
subsequent commits and tags (from the plugin) can work just fine as the URL
does not need to be specified anymore. But when the release plugin checks out
the code it will fail if the proper developer url "ssh://[EMAIL
PROTECTED]/~git/olamy/scm-git-test-one-module" (normal developer relative) is
set. (As the maven pom seems to expect that format).
There are 3 ways to fix or work around this:
1) Use the normal anonymous URLs for both connections (developer and anonymous)
inside the pom. This will confused developers though as the generated site
tells the new developers to use the anonymous URL to checkout the code. They
will not be able to push if they do.
2) Have the scm/release plugin ignore the developer URL and use the anonymous
URL for the checkout. Again this will be confusing on the generated site as the
normal developer rel/abs URLs might not be supported.
3) Somehow store the URL in the format "[EMAIL
PROTECTED]:olamy/scm-git-test-one-module" in the pom. The problem is that the
POM expects the normal (RFC 2396) format AFAIU.
--
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-2180) please upload the new jdeb 0.7 release
please upload the new jdeb 0.7 release -- Key: MAVENUPLOAD-2180 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2180 Project: Maven Upload Requests Issue Type: Task Reporter: Torsten Curdt A new release -- 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-1893) please upload the new jdeb 0.6 release
please upload the new jdeb 0.6 release -- Key: MAVENUPLOAD-1893 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1893 Project: maven-upload-requests Issue Type: Bug Reporter: Torsten Curdt -- 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-1826) please upload the new jdeb 0.5 release
please upload the new jdeb 0.5 release -- Key: MAVENUPLOAD-1826 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1826 Project: maven-upload-requests Issue Type: Task Reporter: Torsten Curdt new release available -- 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-1729) please upload the new jdeb 0.4 release
please upload the new jdeb 0.4 release -- Key: MAVENUPLOAD-1729 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1729 Project: maven-upload-requests Issue Type: Task Reporter: Torsten Curdt -- 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-1717) please upload a new jdeb release
please upload a new jdeb release Key: MAVENUPLOAD-1717 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1717 Project: maven-upload-requests Issue Type: Task Reporter: Torsten Curdt adds maven support and more -- 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-1717) please upload a new jdeb release
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107409 ] Torsten Curdt commented on MAVENUPLOAD-1717: ups ...bundle URL is http://vafer.org/repository/releases/org/vafer/jdeb/0.3/jdeb-0.3-bundle.jar > please upload a new jdeb release > > > Key: MAVENUPLOAD-1717 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1717 > Project: maven-upload-requests > Issue Type: Task >Reporter: Torsten Curdt > > adds maven support and more -- 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-1678) please upload new jdeb version 0.2
please upload new jdeb version 0.2 -- Key: MAVENUPLOAD-1678 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1678 Project: maven-upload-requests Issue Type: Task Reporter: Torsten Curdt -- 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-1438) please upload new version of vafer.org dependency
please upload new version of vafer.org dependency - Key: MAVENUPLOAD-1438 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1438 Project: maven-upload-requests Issue Type: Task Reporter: Torsten Curdt sorry ...the old release was missing something :) please upload as other releases are depending on this. -- 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-1434) please upload new version of vafer.org dependency
please upload new version of vafer.org dependency - Key: MAVENUPLOAD-1434 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1434 Project: maven-upload-requests Issue Type: Task Reporter: Torsten Curdt required for the new release of minijar which is supposed to be used for the maven 2.0..6 release -- 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-1389) please upload release of vafer.org jdeb
please upload release of vafer.org jdeb --- Key: MAVENUPLOAD-1389 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1389 Project: maven-upload-requests Issue Type: Task Reporter: Torsten Curdt library for packaging java projects as debian package -- 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-1324) please upload new version of vafer.org dependency
please upload new version of vafer.org dependency - Key: MAVENUPLOAD-1324 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1324 Project: maven-upload-requests Issue Type: Task Reporter: Torsten Curdt please new release need it for the mojo minijar release -- 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: (CONTINUUM-815) directory configuration
[ http://jira.codehaus.org/browse/CONTINUUM-815?page=comments#action_72358 ] Torsten Curdt commented on CONTINUUM-815: - ups ...I meant "when installing continuum" ;-) > directory configuration > --- > > Key: CONTINUUM-815 > URL: http://jira.codehaus.org/browse/CONTINUUM-815 > Project: Continuum > Issue Type: Improvement > Components: Documentation >Affects Versions: 1.0.3 >Reporter: Torsten Curdt > > When I was installing maven it was not clear what the directories are for > that I had to specify. > - working directory > - build output directory > - local repository > The installation guide should explain values like these. Especially awkward > is that the builds happen in the working area - not in the build output area. > Just needs some documentation. -- 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: (CONTINUUM-816) runas in run script
runas in run script --- Key: CONTINUUM-816 URL: http://jira.codehaus.org/browse/CONTINUUM-816 Project: Continuum Issue Type: Bug Components: Core system Affects Versions: 1.0.3 Environment: linux Reporter: Torsten Curdt When I installed continuum I've changed the "runas" user in the run script but then started it via "run.sh console". Unfortunately the console mode is ignoring the "runas" user setting so when I was trying to run it with "run.sh start" afterwards I was getting exception because the continuum user could not access the files. After fixing the ownerships everything was ok again. I suggest that "run.sh console" should also use the "runas" user. -- 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: (CONTINUUM-815) directory configuration
directory configuration --- Key: CONTINUUM-815 URL: http://jira.codehaus.org/browse/CONTINUUM-815 Project: Continuum Issue Type: Improvement Components: Documentation Affects Versions: 1.0.3 Reporter: Torsten Curdt When I was installing maven it was not clear what the directories are for that I had to specify. - working directory - build output directory - local repository The installation guide should explain values like these. Especially awkward is that the builds happen in the working area - not in the build output area. Just needs some documentation. -- 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: (MPMD-28) Support for multi-projects poms
[ http://jira.codehaus.org/browse/MPMD-28?page=comments#action_68851 ] Torsten Curdt commented on MPMD-28: --- Sorry, I had to beg too long to get this applied. I am not going to do the work twice. Most of the code was copied from another maven plugin, so I am not sure what you refer to regarding the naming scheme. > Support for multi-projects poms > --- > > Key: MPMD-28 > URL: http://jira.codehaus.org/browse/MPMD-28 > Project: Maven 2.x Pmd Plugin > Type: Improvement > Reporter: Torsten Curdt > Assignee: Mike Perham > Attachments: multiproject.diff > > > Added support for multi-projects so if you set "aggregate" to "true" the > parent project will generate the report and the childs will not execute it > anymore -- 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-924) vafer.org dependency bundle
vafer.org dependency bundle --- Key: MAVENUPLOAD-924 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-924 Project: maven-upload-requests Type: Task Reporter: Torsten Curdt I need it for maven and mojo! Please 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-2280) Make inheritance of reports configurable
[ http://jira.codehaus.org/browse/MNG-2280?page=comments#action_64864 ] Torsten Curdt commented on MNG-2280: So what does the do? Well, I have already submitted fixes for the other plugins to fix the aggregation for multi-project poms ...and then I wanted to the same for the project info plugin. But for that plugin it is not aggregation. See what I mean? For jci I want be able to define the project info report on the parent pom but not have it executed for the childs. That's why I thought aggregation is not the right term. At least for the project info plugin the best thing would to be able to prohibit the inheritance to the child poms. That's what I really would want to have. More control of the inheritance. And I think this does make sense - but AFAIU it is not possible. So the work-around is that the plugin gets called but gets ignored so it acts as it was not in the child pom that's why I was talking about inheritance - of course that clashed with ..whatever that means exactly in the current implementation. Another approach would be to re-think the project info plugin so basically provide 3 modes of operation. 1 - separate reports per pom, 2 - aggregate the information of all poms into one, 3 - only execute the one of the parent pom (or not inheriting) But no matter what - I think an AbstractAggregatingMavenReport class would make sense. It's already a bit of code doublication getting all the source directories etc. in each plugin. > Make inheritance of reports configurable > > > Key: MNG-2280 > URL: http://jira.codehaus.org/browse/MNG-2280 > Project: Maven 2 > Type: Improvement > Reporter: Torsten Curdt > Attachments: multiproject.diff > > > This makes it possible to configure inheriance of reports. > > false > ... -- 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-2280) Make inheritance of reports configurable
Make inheritance of reports configurable Key: MNG-2280 URL: http://jira.codehaus.org/browse/MNG-2280 Project: Maven 2 Type: Improvement Reporter: Torsten Curdt Attachments: multiproject.diff This makes it possible to configure inheriance of reports. false ... -- 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: (MPMD-28) Support for multi-projects poms
Support for multi-projects poms --- Key: MPMD-28 URL: http://jira.codehaus.org/browse/MPMD-28 Project: Maven 2.x Pmd Plugin Type: Improvement Reporter: Torsten Curdt Attachments: multiproject.diff Added support for multi-projects so if you set "aggregate" to "true" the parent project will generate the report and the childs will not execute it anymore -- 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: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse
[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=all ] Torsten Curdt closed MNGECLIPSE-114: Resolution: Fixed Fix Version: 0.0.6 > cannot run junit testcases from within Eclipse > -- > > Key: MNGECLIPSE-114 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-114 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Environment: OSX, Eclipse 3.2RC1 > Reporter: Torsten Curdt > Assignee: Eugene Kuleshov > Fix For: 0.0.6 > Attachments: commons-jci.tgz, eclipse.png, run.png > > > Dependencies seem to get ignored when running junit testcases from within > Eclipse. I just get an exception: > java.lang.NoClassDefFoundError: junit/framework/TestListener > The junit jar is listed through the maven dependencies though. When I add it > by hand (add external jar) junit starts up but then I am missing my other > dependencies. -- 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: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse
[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=comments#action_64451 ] Torsten Curdt commented on MNGECLIPSE-114: -- The new plugin plus the "update sources" seems to have fixed it. Thanks heaps, mate! > cannot run junit testcases from within Eclipse > -- > > Key: MNGECLIPSE-114 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-114 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Environment: OSX, Eclipse 3.2RC1 > Reporter: Torsten Curdt > Assignee: Eugene Kuleshov > Fix For: 0.0.6 > Attachments: commons-jci.tgz, eclipse.png, run.png > > > Dependencies seem to get ignored when running junit testcases from within > Eclipse. I just get an exception: > java.lang.NoClassDefFoundError: junit/framework/TestListener > The junit jar is listed through the maven dependencies though. When I add it > by hand (add external jar) junit starts up but then I am missing my other > dependencies. -- 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: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse
[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=all ] Torsten Curdt updated MNGECLIPSE-114: - Attachment: commons-jci.tgz > cannot run junit testcases from within Eclipse > -- > > Key: MNGECLIPSE-114 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-114 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Environment: OSX, Eclipse 3.2RC1 > Reporter: Torsten Curdt > Assignee: Eugene Kuleshov > Attachments: commons-jci.tgz, eclipse.png, run.png > > > Dependencies seem to get ignored when running junit testcases from within > Eclipse. I just get an exception: > java.lang.NoClassDefFoundError: junit/framework/TestListener > The junit jar is listed through the maven dependencies though. When I add it > by hand (add external jar) junit starts up but then I am missing my other > dependencies. -- 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: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse
[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=comments#action_64417 ] Torsten Curdt commented on MNGECLIPSE-114: -- >From the command line test are running fine for me as well. Started with a fresh launch config and this is what gets called: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/java -classpath /Users/tcurdt/dev/jakarta/commons-jci/tests/target/classes:/Users/tcurdt/dev/jakarta/commons-jci/core/target/classes:/Users/tcurdt/.m2/repository/commons-collections/commons-collections/3.1/commons-collections-3.1.jar:/Users/tcurdt/.m2/repository/commons-io/commons-io/1.1/commons-io-1.1.jar:/Users/tcurdt/.m2/repository/commons-lang/commons-lang/2.1/commons-lang-2.1.jar:/Users/tcurdt/.m2/repository/commons-logging/commons-logging-api/1.0.4/commons-logging-api-1.0.4.jar:/Applications/eclipse-SDK-3.2RC1/plugins/org.eclipse.jdt.junit_3.2.0.v20060412-1600/junitsupport.jar:/Applications/eclipse-SDK-3.2RC1/plugins/org.eclipse.jdt.junit.runtime_3.2.0.v20060412-1600/junitruntime.jar org.eclipse.jdt.internal.junit.runner.RemoteTestRunner -version 3 -port 59767 -testNameFile /tmp/testNames33471.txt No junit jar! And other dependencies are missing, too! The test subproject also depends on all the compiler modules and they have dependencies to the compiler implementations. They are not in the path either. > cannot run junit testcases from within Eclipse > -- > > Key: MNGECLIPSE-114 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-114 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Environment: OSX, Eclipse 3.2RC1 > Reporter: Torsten Curdt > Assignee: Eugene Kuleshov > Attachments: eclipse.png, run.png > > > Dependencies seem to get ignored when running junit testcases from within > Eclipse. I just get an exception: > java.lang.NoClassDefFoundError: junit/framework/TestListener > The junit jar is listed through the maven dependencies though. When I add it > by hand (add external jar) junit starts up but then I am missing my other > dependencies. -- 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: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse
[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=all ] Torsten Curdt updated MNGECLIPSE-114: - Attachment: run.png > cannot run junit testcases from within Eclipse > -- > > Key: MNGECLIPSE-114 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-114 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Environment: OSX, Eclipse 3.2RC1 > Reporter: Torsten Curdt > Assignee: Eugene Kuleshov > Attachments: eclipse.png, run.png, tests.tgz, workspace.tgz > > > Dependencies seem to get ignored when running junit testcases from within > Eclipse. I just get an exception: > java.lang.NoClassDefFoundError: junit/framework/TestListener > The junit jar is listed through the maven dependencies though. When I add it > by hand (add external jar) junit starts up but then I am missing my other > dependencies. -- 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: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse
[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=all ] Torsten Curdt updated MNGECLIPSE-114: - Attachment: eclipse.png > cannot run junit testcases from within Eclipse > -- > > Key: MNGECLIPSE-114 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-114 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Environment: OSX, Eclipse 3.2RC1 > Reporter: Torsten Curdt > Assignee: Eugene Kuleshov > Attachments: eclipse.png, tests.tgz, workspace.tgz > > > Dependencies seem to get ignored when running junit testcases from within > Eclipse. I just get an exception: > java.lang.NoClassDefFoundError: junit/framework/TestListener > The junit jar is listed through the maven dependencies though. When I add it > by hand (add external jar) junit starts up but then I am missing my other > dependencies. -- 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: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse
[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=all ] Torsten Curdt updated MNGECLIPSE-114: - Attachment: tests.tgz workspace.tgz > cannot run junit testcases from within Eclipse > -- > > Key: MNGECLIPSE-114 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-114 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Environment: OSX, Eclipse 3.2RC1 > Reporter: Torsten Curdt > Assignee: Eugene Kuleshov > Attachments: tests.tgz, workspace.tgz > > > Dependencies seem to get ignored when running junit testcases from within > Eclipse. I just get an exception: > java.lang.NoClassDefFoundError: junit/framework/TestListener > The junit jar is listed through the maven dependencies though. When I add it > by hand (add external jar) junit starts up but then I am missing my other > dependencies. -- 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: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse
cannot run junit testcases from within Eclipse -- Key: MNGECLIPSE-114 URL: http://jira.codehaus.org/browse/MNGECLIPSE-114 Project: Maven 2.x Extension for Eclipse Type: Bug Environment: OSX, Eclipse 3.2RC1 Reporter: Torsten Curdt Assigned to: Eugene Kuleshov Dependencies seem to get ignored when running junit testcases from within Eclipse. I just get an exception: java.lang.NoClassDefFoundError: junit/framework/TestListener The junit jar is listed through the maven dependencies though. When I add it by hand (add external jar) junit starts up but then I am missing my other dependencies. -- 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-2253) Improve documentation on multi-projects
Improve documentation on multi-projects --- Key: MNG-2253 URL: http://jira.codehaus.org/browse/MNG-2253 Project: Maven 2 Type: Improvement Components: Documentation: General Versions: documentation Reporter: Torsten Curdt Simon gives a nice overview about how multi-projects work. Would be worth having all this information in the documentation somewhere http://www.mail-archive.com/users@maven.apache.org/msg41444.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: (MAVENUPLOAD-834) Please update to the latest stable version.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-834?page=comments#action_63595 ] Torsten Curdt commented on MAVENUPLOAD-834: --- Ok, changed. The updated bundle is at http://vafer.org/pub/org.eclipse.jdt.core-bundle.jar > Please update to the latest stable version. > --- > > Key: MAVENUPLOAD-834 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-834 > Project: maven-upload-requests > Type: Task > Reporter: Torsten Curdt > > > http://vafer.org/pub/jdtcore-bundle.jar > http://eclipse.org > Please update to the latest stable version (3.2M6) -- 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-834) Please update to the latest stable version.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-834?page=comments#action_63440 ] Torsten Curdt commented on MAVENUPLOAD-834: --- Actually it is called "org.eclipse.jdt.core_3.2.0.v_653.jar". Do you reckon we should use the full name? I found "core" just a bit too ambiguous. > Please update to the latest stable version. > --- > > Key: MAVENUPLOAD-834 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-834 > Project: maven-upload-requests > Type: Task > Reporter: Torsten Curdt > > > http://vafer.org/pub/jdtcore-bundle.jar > http://eclipse.org > Please update to the latest stable version (3.2M6) -- 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-834) Please update to the latest stable version.
Please update to the latest stable version. --- Key: MAVENUPLOAD-834 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-834 Project: maven-upload-requests Type: Task Reporter: Torsten Curdt http://vafer.org/pub/jdtcore-bundle.jar http://eclipse.org Please update to the latest stable version (3.2M6) -- 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: (MAVENUPLOAD-833) new jdtcore version 3.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-833?page=all ] Torsten Curdt closed MAVENUPLOAD-833: - Resolution: Incomplete could not modify after clone > new jdtcore version 3.2 > --- > > Key: MAVENUPLOAD-833 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-833 > Project: maven-upload-requests > Type: Task > Reporter: Torsten Curdt > Assignee: Carlos Sanchez > > > please update to this latest stable release -- 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-833) new jdtcore version 3.2
new jdtcore version 3.2 --- Key: MAVENUPLOAD-833 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-833 Project: maven-upload-requests Type: Task Reporter: Torsten Curdt Assigned to: Carlos Sanchez please update to this latest stable release -- 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
