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 Mon, 04 May 2009 02:39:44 GMT


Matthew Watson updated MECLIPSE-557:

    Attachment: patch3

This patch creates another plugin and model for each contained jar and adds them as a dependency
on the containing model.

This works around the jar signing issues by leaving the jars alone.

Each sub-jar is given the group id of the parent with the artifact id appended (with a ".")
and their own artifact id is the name of the jar.

For junit, this produces (along with appropriate poms:
org/junit/3.8.2/junit.jar (which is simply a zip of the eclipse plugin directory)
org/junit/junit/3.8.2/junit.jar (which is the contained jar itself)

for org.eclipse.emf.teneo.hibernate we get:
org/eclipse/emf/teneo/hibernate/1.0.1/hibernate-1.0.1.jar: the zipped plugin directory

The idea is that no-one should depend on the sub-jar poms directly, only transitively via
the containing pom.
This works for all my usage cases.

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