[jbosstools-issues] [JBoss JIRA] (JBIDE-12336) org.jboss.ide.eclipse.archives.core bundles some old/obselete jars

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-12336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706689#comment-12706689 ] 

Rob Stryker commented on JBIDE-12336:
-------------------------------------

glad to see you guys have a workaround for now. This allows us to put this in for next version I guess... and gives us lots of time to regression test it
                
> org.jboss.ide.eclipse.archives.core bundles some old/obselete jars
> ------------------------------------------------------------------
>
>                 Key: JBIDE-12336
>                 URL: https://issues.jboss.org/browse/JBIDE-12336
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: Archives
>         Environment: Fedora
>            Reporter: Gerard Ryan
>            Assignee: Rob Stryker
>         Attachments: JBIDE-12336.patch
>
>
> As detailed on the jbosstools-dev mailing list[1], I'm packaging JBoss Tools for Fedora, and the bundled jars in the lib/ directory of the org.jboss.ide.eclipse.archives.core plugin are causing me some trouble.
> The root of the issue is that Fedora packages disallow bundled dependencies; and when new packages are being created, only the latest version of the software must be packaged. This was not too much of a problem for the truezip dependency, even though some things did need to be changed for it, as detailed in the truezip migration from v6 to v7 guide[2].
> It didn't work so well for the jbossxb dependency, however. jbossxb hasn't seen any activity in quite a while, and it depends on the seemingly obselete (this may not be the best description) jboss-reflect. jboss-reflect, in its current state, cannot be included in Fedora for reasons listed in the review for the package that I proposed for it[3].
> I'm trying to find the optimal solution to this problem. What I would really like to know from the JBoss Tools perspective is: How crucial to this plugin is jbossxb? Is there anything else that would work as a dropin replacement, or any other workaround possible? Since development of jbossxb seems dormant, not having to package it for Fedora would be the best solution for me. I realise that it may be necessary though, but I thought I would bring it up here, before I go looking for the jbossxb developers, in case my best case scenario is a possibility!
> Thanks in advance for any insight/help you can provide! :)
> [1] http://lists.jboss.org/pipermail/jbosstools-dev/2012-July/005548.html
> [2] http://truezip.java.net/migration.html
> [3] https://bugzilla.redhat.com/show_bug.cgi?id=836404

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira