Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] CVS access to Orbit

On Mon, Jan 14, 2013 at 3:47 PM, Doug Schaefer <dschaefer@xxxxxxx> wrote:
+1. Was trying to set things up for my contractor who's not a committer
and ran into this problem as well. And I'm not sure how to install some of
these things from the p2 repo since they don't have features.

No comment on the CVS issue, but the orbit repos have at least one category that lists individual bundles.  That info could probably be captured in a target platform definition file that can be exported/imported, and they can be shared.  I think they're actually a better fit for setting up dev environments that depend on Orbit bundles than CVS (which I've always found a pain).

That's probably easier than providing the command line to update target platforms (but that's what I use):

 eclipse/eclipse \
-application org.eclipse.equinox.p2.director \
-noSplash \
-repository \
http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/repository \
-installIUs \
org.apache.commons.jxpath/1.3.0.v200911051830,\
org.apache.batik.xml/1.6.0.v201011041432



--
Paul Webster
Hi floor.  Make me a sammich! - GIR

Back to the top