maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew Watson (JIRA)" <>
Subject [jira] Updated: (MECLIPSE-557) eclipse:to-maven produces unusable jars (jars containing jars)
Date Fri, 01 May 2009 06:29:45 GMT


Matthew Watson updated MECLIPSE-557:

    Attachment: patch2

This patch is slightly more correct

> eclipse:to-maven produces unusable jars (jars containing jars)
> --------------------------------------------------------------
>                 Key: MECLIPSE-557
>                 URL:
>             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
>            Reporter: Matthew Watson
>         Attachments: patch, patch2
> 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:
For more information on JIRA, see:


View raw message