The current plan is to upgrade to Eclipse 3.4 in Fedora 10. We can use this as a tracker bug for issues. OTTOMH I can think of a few things we'll need to do: - use p2 -- update pdebuild.sh to generate p2 metadata -- ensure our metadata is properly read by p2 if we're going to use the dropins approach for additional plugins -- ensure our arch-specific/arch-independent split still works - ensure we have all dependent packages updated and OSGi-ified a la Orbit (eclipse.org/orbit) - ensure secondary arches can still build and run
todo++: - OSGi-ify objectweb-asm and provide a monolithic JAR to match Orbit's JAR - ensure automated tests run against 3.4 and we have no failures Also see: https://fedoraproject.org/wiki/Features/Eclipse34 which will more than likely be kept up to date more than this bug (except for blocker bugs).
traiged
I realise this work is still ongoing, but it looks to me as if eclipse.spec should be creating/owning the "dropins" directory, perhaps as /usr/share/eclipse/dropins. I thought it might save some Bugzilla red-tape to mention it now, just in case.
(In reply to comment #3) > I realise this work is still ongoing, but it looks to me as if eclipse.spec > should be creating/owning the "dropins" directory, perhaps as > /usr/share/eclipse/dropins. I thought it might save some Bugzilla red-tape to > mention it now, just in case. Thanks, Sean. I had forgotten to add that. It's definitely needed :)
This is now in rawhide.