[jira] (MPECLIPSE-138) Generated .classpath files are not compatible with m2e
Radim Kolar created MPECLIPSE-138: - Summary: Generated .classpath files are not compatible with m2e Key: MPECLIPSE-138 URL: https://jira.codehaus.org/browse/MPECLIPSE-138 Project: Maven 1.x Eclipse Plugin Issue Type: Bug Reporter: Radim Kolar Priority: Critical If you run Eclipse maven plugin m2e included in Eclipse Juno on project files generated by maven eclipse plugin, m2e will complain about Unsupported IClasspathEntry kind=4. More information here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=394042 -- 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] (MSHADE-127) NPE if shade plugin runs in artifact with packaging pom
Radim Kolar created MSHADE-127: -- Summary: NPE if shade plugin runs in artifact with packaging pom Key: MSHADE-127 URL: https://jira.codehaus.org/browse/MSHADE-127 Project: Maven 2.x Shade Plugin Issue Type: Bug Affects Versions: 1.7.1 Reporter: Radim Kolar Priority: Blocker Attachments: pom.xml If you run shade plugin in artifact with packagingpom/packaging it fails during replace step: [INFO] Replacing original artifact with shaded artifact. [INFO] Replacing null with C:\apache-nutch\nutch\runtime\deploy\runtime-1.5-SNAPSHOT-shaded.pom [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 12.422s [INFO] Finished at: Mon Aug 06 15:44:11 CEST 2012 [INFO] Final Memory: 4M/62M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:1.7.1:shade (make-shaded-jar) on project runtime: Error creating shaded jar: null: NullPointerException - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:1.7.1:shade (make-shaded-jar) on project runtime: Error creating shaded jar: null at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) 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:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) 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.MojoExecutionException: Error creating shaded jar: null at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:556) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: java.lang.NullPointerException at org.apache.maven.plugins.shade.mojo.ShadeMojo.replaceFile(ShadeMojo.java:570) at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:536) ... 21 more -- 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] (MSHADE-129) outputDirectory do not works together with outputFile
Radim Kolar created MSHADE-129: -- Summary: outputDirectory do not works together with outputFile Key: MSHADE-129 URL: https://jira.codehaus.org/browse/MSHADE-129 Project: Maven 2.x Shade Plugin Issue Type: Improvement Affects Versions: 1.7.1 Reporter: Radim Kolar I would really like to have outputDirectory work with outputFile. Currently it works only with finalName. If this is intended behaviour, then please DOCUMENT IT. -- 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] (MASSEMBLY-616) do not included artifacts with scope system as dependencies
Radim Kolar created MASSEMBLY-616:
-
Summary: do not included artifacts with scope system as
dependencies
Key: MASSEMBLY-616
URL: https://jira.codehaus.org/browse/MASSEMBLY-616
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.3
Environment: FreeBSD 8, 64bit, openjdk6/7
Reporter: Radim Kolar
If you are building assembly with dependencies included:
useTransitiveDependenciestrue/useTransitiveDependencies
and one of dependencies has scope like that:
dependencies
dependency
groupIdjdk.tools/groupId
artifactIdjdk.tools/artifactId
version1.6/version
scopesystem/scope
systemPath${java.home}/../lib/tools.jar/systemPath
/dependency
/dependencies
then assembly plugin tries to fetch that artifact from repository. Artifact of
course is not there.
--
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] (MASSEMBLY-604) Please document formatdir/format
Radim Kolar created MASSEMBLY-604: - Summary: Please document formatdir/format Key: MASSEMBLY-604 URL: https://jira.codehaus.org/browse/MASSEMBLY-604 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.3 Environment: FreeBSD 64 bit Reporter: Radim Kolar Please document that you can also pack files into directory, not only archive. I mean - formatdir/format I had to dig in source code to discover that. -- 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] (MASSEMBLY-604) Please document formatdir/format
[ https://jira.codehaus.org/browse/MASSEMBLY-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=295727#comment-295727 ] Radim Kolar commented on MASSEMBLY-604: --- I am talking about this: http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html Element TypeDescription formats/format* Please document formatdir/format Key: MASSEMBLY-604 URL: https://jira.codehaus.org/browse/MASSEMBLY-604 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.3 Environment: FreeBSD 64 bit Reporter: Radim Kolar Please document that you can also pack files into directory, not only archive. I mean - formatdir/format I had to dig in source code to discover that. -- 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
