| Is an Eclipse tarball a p2 enabled repository? [message #109611] |
Tue, 13 May 2008 14:03  |
Eclipse User |
|
|
|
Originally posted by: irbull.cs.uvic.ca
I just discovered the cool Eclipse Provisioning Agent, and this seems
like a good way to play with some of the new features available in p2.
From what I have read (mostly on the p2 wiki pages), the SDK tarballs
can be used just like an update site. So I was wondering, can I:
1. Download Eclipse SDK 3.4 M7
2. Download the equinox provisioning agent
3. Add my Eclipse SDK . Zip as a metadata repository (an artifact
repository) in the provisioning agent
4. Create a profile
5. Install Eclipse in that profile
I realize this is redundant (as I already have Eclipse), but this could
be useful when deploying a new version of Eclipse to a bunch of machines
on a network.
I have tried this, however, there doesn't seem to be any SDK feature.
The closest I saw was "org.eclipse.sdk.feature.group", which had
unsatisfied dependencies.
|
|
|
| Re: Is an Eclipse tarball a p2 enabled repository? [message #109650 is a reply to message #109611] |
Tue, 13 May 2008 22:36  |
| Eclipse User |
|
|
|
What you read seems erroneous. Could you please point me at the page where
you read this to I can correct this?
Basically p2 will be able to point at zips containing p2 metadata and
install from them. Think for example of the GEF.zip containing a content.xml
and artifacts.xml.
As for being able to point at an existing installed SDK, it is something
that we always have / had in mind but did not get around to implement in
1.0. However, the p2 design gives the ability to develop this functionality
as an extension of p2 instead of being something that has to be done
specially. Basically, you simply have to look at the profile repository as a
metadata source (IMetadataRepository) and that's it
PaScaL
"Ian Bull" <irbull@cs.uvic.ca> wrote in message
news:g0cl57$7ue$1@build.eclipse.org...
>I just discovered the cool Eclipse Provisioning Agent, and this seems like
>a good way to play with some of the new features available in p2. From what
>I have read (mostly on the p2 wiki pages), the SDK tarballs can be used
>just like an update site. So I was wondering, can I:
>
> 1. Download Eclipse SDK 3.4 M7
> 2. Download the equinox provisioning agent
> 3. Add my Eclipse SDK . Zip as a metadata repository (an artifact
> repository) in the provisioning agent
> 4. Create a profile
> 5. Install Eclipse in that profile
>
> I realize this is redundant (as I already have Eclipse), but this could be
> useful when deploying a new version of Eclipse to a bunch of machines on a
> network.
>
> I have tried this, however, there doesn't seem to be any SDK feature. The
> closest I saw was "org.eclipse.sdk.feature.group", which had unsatisfied
> dependencies.
>
>
>
|
|
|
| Re: Is an Eclipse tarball a p2 enabled repository? [message #109679 is a reply to message #109650] |
Tue, 13 May 2008 23:45 |
| Eclipse User |
|
|
|
Originally posted by: irbull.cs.uvic.ca
Thanks for the response Pascal.
I think it was just my misunderstanding of the Admin UI [1], which looks
like it will install a full Eclipse SDK from an update site, and the
fact that repositories can be "local". I think I just assumed that I
could use the Eclipse-SDK.zip in the same way as GEF.zip (and use the
Zip to install the entire stack). No worries, I was just trying to get
a better understanding of what could be done with p2.
[1] http://wiki.eclipse.org/Equinox_p2_Getting_Started_Admin_UI
With the current implementation of p2, can I create an RCP application
(with launcher, osgi, p2, etc...), create an update site for this, and
use the Admin UI to install this? Similar to what the platform has done
with http://download.eclipse.org/eclipse/testUpdates?
Cheers,
Ian
Pascal Rapicault wrote:
> What you read seems erroneous. Could you please point me at the page where
> you read this to I can correct this?
> Basically p2 will be able to point at zips containing p2 metadata and
> install from them. Think for example of the GEF.zip containing a content.xml
> and artifacts.xml.
>
> As for being able to point at an existing installed SDK, it is something
> that we always have / had in mind but did not get around to implement in
> 1.0. However, the p2 design gives the ability to develop this functionality
> as an extension of p2 instead of being something that has to be done
> specially. Basically, you simply have to look at the profile repository as a
> metadata source (IMetadataRepository) and that's it
>
> PaScaL
>
> "Ian Bull" <irbull@cs.uvic.ca> wrote in message
> news:g0cl57$7ue$1@build.eclipse.org...
>> I just discovered the cool Eclipse Provisioning Agent, and this seems like
>> a good way to play with some of the new features available in p2. From what
>> I have read (mostly on the p2 wiki pages), the SDK tarballs can be used
>> just like an update site. So I was wondering, can I:
>>
>> 1. Download Eclipse SDK 3.4 M7
>> 2. Download the equinox provisioning agent
>> 3. Add my Eclipse SDK . Zip as a metadata repository (an artifact
>> repository) in the provisioning agent
>> 4. Create a profile
>> 5. Install Eclipse in that profile
>>
>> I realize this is redundant (as I already have Eclipse), but this could be
>> useful when deploying a new version of Eclipse to a bunch of machines on a
>> network.
>>
>> I have tried this, however, there doesn't seem to be any SDK feature. The
>> closest I saw was "org.eclipse.sdk.feature.group", which had unsatisfied
>> dependencies.
>>
>>
>>
>
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.47938 seconds
Home