[jbosstools-issues] [JBoss JIRA] Commented: (JBDS-1312) Remove duplicate entries from modeshape-client.jar/META-INF
Dan Florian (JIRA)
jira-events at lists.jboss.org
Wed Dec 8 12:57:32 EST 2010
[ https://jira.jboss.org/browse/JBDS-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568686#comment-12568686 ]
Dan Florian commented on JBDS-1312:
-----------------------------------
Actually the issues I will be resolving are JBDS-1343 and JBIDE-6984. Not resolving this until we can confirm no dupe entries.
> Remove duplicate entries from modeshape-client.jar/META-INF
> -----------------------------------------------------------
>
> Key: JBDS-1312
> URL: https://jira.jboss.org/browse/JBDS-1312
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: Modeshape
> Affects Versions: 4.0.0.M2
> Reporter: Denis Golovin
> Assignee: Dan Florian
> Fix For: 4.0.0.CR1
>
> Attachments: PastedGraphic-1.tiff, PastedGraphic-2.tiff, Screenshot-modeshape-web-jcr-rest-client-2.1-SNAPSHOT-jar-with-dependencies.jar .png
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Duplicate entries should be removed to fix JBDS build exception:
> [pack200] java.util.zip.ZipException: duplicate entry: META-INF/LICENSE.txt
> [pack200] at java.util.zip.ZipOutputStream.putNextEntry(ZipOutputStream.java:192)
> [pack200] at java.util.jar.JarOutputStream.putNextEntry(JarOutputStream.java:109)
> [pack200] at org.eclipse.update.internal.jarprocessor.JarProcessor.recreateJar(JarProcessor.java:128)
> [pack200] at org.eclipse.update.internal.jarprocessor.JarProcessor.processJar(JarProcessor.java:317)
> [pack200] at org.eclipse.update.internal.jarprocessor.JarProcessor.extractEntries(JarProcessor.java:217)
> [pack200] at org.eclipse.update.internal.jarprocessor.JarProcessor.processJar(JarProcessor.java:304)
> [pack200] at org.eclipse.update.internal.jarprocessor.ZipProcessor.processZip(ZipProcessor.java:138)
> [pack200] at org.eclipse.update.internal.jarprocessor.JarProcessorExecutor.runJarProcessor(JarProcessorExecutor.java:31)
> [pack200] at org.eclipse.update.internal.provisional.SiteOptimizerApplication.runJarProcessor(SiteOptimizerApplication.java:189)
> [pack200] at org.eclipse.update.internal.provisional.SiteOptimizerApplication.run(SiteOptimizerApplication.java:509)
> [pack200] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [pack200] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [pack200] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [pack200] at java.lang.reflect.Method.invoke(Method.java:616)
> [pack200] at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
> [pack200] at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
> [pack200] at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> [pack200] at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> [pack200] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
> [pack200] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> [pack200] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [pack200] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [pack200] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [pack200] at java.lang.reflect.Method.invoke(Method.java:616)
> [pack200] at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
> [pack200] at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
> [pack200] at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
> [pack200] at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list