[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [virgo-dev] Virgo P2 repository
- From: Pete Carapetyan <pete@xxxxxxxxxxx>
- Date: Thu, 29 Jul 2010 10:46:42 -0500
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=Ih6fxbBLY+WC1X53OgPsli37shDp/GEKe/aauTeZeeK+ApQ2yrqhLKXQtr5/+4Dn2O HEeRX/oBZ86khbuRxKKb0C1QEfi+cd5rZEwIo69wWu14oRkAZwOr2QnsvyMMydKZl7oK UzXrGgSSDJ/FXn4ST7povX6JtSuITwp5xUWfM=
This is a heads up that if you use it as an application platform, it has to be installed at or near root on windows or you'll get errors due to long path names. I filed it as a bug but it got immediately marked as wont-fix.
This iced Virgo as a desktop platform for me, because I can't control where users install it.
I will be very interested in following this thread, because my desires still remain to use Virgo.
On Thu, Jul 29, 2010 at 7:57 AM, Iliev, Hristo <hristo.iliev@xxxxxxx>
We want to use Virgo (kernel) as application platform. Since we are using Nexus repository manager we want to have P2 repository with Virgo inside and consume Virgo binaries from it.
Besides the usual benefits from such approach ("own repositories to ensure stability within your organization") having a P2 repository means that Virgo can be:
* installed with the standard Eclipse P2 installer
* installed based on the OS/platform (only the relevant scripts/bundles/native parts)
* put in one repository - Kernel & Web can be a features inside, so one can install Web on top of Kernel
* updated/installed from external agent (based on P2 API or Eclipse P2 Installer tool)
* provided to Eclipse developers as embedded application platform (or via dependency for eclipse plugins)
We want this P2 repository to be a part of the Virgo build. The result can be provided on http://build.eclipse.org as a start. The benefits from this approach (compared to having a proprietary P2 repo) are that the repo will be:
* modifiable, controlled and supported by the Virgo community
* as close to the source as possible - this will allow the P2 repo to reflect the latest changes in Virgo
The steps for creating a P2 repository will be:
* upload equinox P2 bundles in s3 repository
* modify the build to invoke P2 publishing (ant java task)
Seems like P2 repo is a goal that can be achieved relatively easy but I'd like to hear also your opinion on this. Is someone already trying to do this or tried it in the past?
virgo-dev mailing list