On Tue, Feb 17, 2009 at 6:58 PM, Andrew Overholt <overholt@xxxxxxxxxx> wrote:
So content.xml is just for first use startup optimization and not needed
-clean (and rm -rf ~/.eclipse) did not worked, testing tomorrow with a clean eclipse installation, for some reason I am having a 5k download speed using yum to reinstall eclipse
* Robert Marcano <robert@xxxxxxxxxxxxxxxxx> [2009-02-16 17:56]:
> but I do not know how to generate the content.xml (with only pluginsSure, you can use the p2 ant targets (make sure to run them with the
> and features directories, eclipse do not see them on the about
> window). Is there a way to generate it outside the pdebuild script?
Eclipse antRunner application and not just plain ant). I think there's
generate.p2.metadata among others. But as it currently stands this is
just used to speed up initial installation so don't bend over backwards
trying to do it. p2 will generate the same metadata upon first use and
plop it into the user's ~/.eclipse directory.
So content.xml is just for first use startup optimization and not needed
If they're not being seen, you may be a victim of:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=251167
Try running with -clean to see if they're picked up. If they're still
not picked up, try putting the same directory somewhere on disk and
doing an installation from a local site and see if it completes or gives
dependency missing errors.
-clean (and rm -rf ~/.eclipse) did not worked, testing tomorrow with a clean eclipse installation, for some reason I am having a 5k download speed using yum to reinstall eclipse
Andrew
--
Robert Marcano
-- fedora-devel-java-list mailing list fedora-devel-java-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-java-list
