[jira] Updated: (MECLIPSE-557) eclipse:to-maven produces unusable jars (jars containing jars)

["Matthew Watson (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MECLIPSE-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthew Watson updated MECLIPSE-557:
------------------------------------

    Attachment: patch

Here is a patch to ExplodedPlugin.java I wrote to fix the problem.

Note, I'm not sure, but the problem may also occur in non-directory plugins, but I haven't hit one yet.

> eclipse:to-maven produces unusable jars (jars containing jars)
> --------------------------------------------------------------
>
>                 Key: MECLIPSE-557
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-557
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>          Components: Core : .project, OSGi, Manifest
>    Affects Versions: 2.6
>         Environment: Linux, Suse 10.x, maven 2.0.x. jdk 1.6.0_10, eclipse-jee-ganymede-SR2-linux-gtk (3.4.2)
>            Reporter: Matthew Watson
>         Attachments: patch
>
>
> The eclipse install contains plugins that are actually directories, which contain the plugin.xml etc and a jar file (for example: org.hibernate.eclipse_3.2.3.GA, org.junit4_4.3.1) or more than one jar file (e.g. org.eclipse.emf.teneo.hibernate_1.0.1.v200809211527)
> eclipse:to-maven simply jars up the directory when it puts it in the repository, which means all the classes in the jar(s) inside are unreachable.
> I am not sure what a suitable behaviour is - I have expanded the jars in org.eclipse.emf.teneo.hibernate_1.0.1.v200809211527 and re-jarred it and it then works fine in maven, so this may be a (optional) solution.

-- 
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