[
https://jira.codehaus.org/browse/MECLIPSE-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297652#comment-297652
]
Barrie Treloar commented on MECLIPSE-682:
-----------------------------------------
I suspect this will be marked WONT_FIX.
eclipse:to-maven and eclipse:install-plugins are hacks to get Maven and Eclipse
PDE development working together.
And it never really panned out well.
I recommend migrating to Tycho for Maven Eclipse PDE development.
> Directory-shaped bundles are not unpacked
> -----------------------------------------
>
> Key: MECLIPSE-682
> URL: https://jira.codehaus.org/browse/MECLIPSE-682
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Affects Versions: 2.8
> Environment: Maven 3.0.2.
> Reporter: Giedrius Noreikis
>
> Steps to reproduce:
> 1. Install a directory-shaped bundle (e.g.
> {{org.eclipse.equinox.launcher.win32.win32.x86_1.1.2.R36x_v20101222}}) to a
> remote repository:
> {{mvn eclipse:to-maven -DeclipseDir=eclipse
> -DdeployTo=central::default::<url>}}
> 2. Delete the bundle from the local {{eclipse/plugins}} directory.
> 3. Now get back the plugin from the Maven repository:
> {{mvn eclipse:install-plugins -DeclipseDir=eclipse}}
> Normally, one should end up with a directory (because {{Eclipse-BundleShape:
> dir}} was specifed in the bundle's manifest, and thus the generated pom has a
> {{<eclipse.unpack>true</eclipse.unpack>}} property), but a .jar file is
> created instead.
> This seems to be a compatibility with Maven 3 issue - I can't reproduce it on
> Maven 2.2.1.
--
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
