[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [equinox-dev] [prov] p2 provisioned eclipse missing companion library
|
When I read your note I went testing with a local copy of the data that was
supposed to be on the test update site and it seems to work (see steps
below).
What I usually find not easy to get right is the metadata generation. The
way the generator is setup into the launch config is to generate a top
level IU refering to all the IUs that are generated by this invocation of
the generator. As you can imagine this is an aweful hack that will soon be
discarded. So my recommendation is to generate metadata piece meal and be
sure that the folder only contains the bits and pieces you really wnat
(e.g. if you want to generate MD for EMF, create a folder containing only
EMF).
As for creating an IU allowing the installation of multiple configurations
(like we do today with the SDK), that requires some magic that you can find
in our build files (see eclipse project org.eclipse.releng.eclipsebuild,
folder /equinox/equinox.prov/run.xml). In short we overlay the launcher
feature over the SDK and massage it at gen time. The real path forward on
that space is to derive most / all of the information from a .product file
thus allowing the creation of the metadata in one call and then do the
creation of the artifacts on another one. This is still be to defined but
Andrew N is actively working on it.
HTH,
PaScaL
Steps I tried:
- install 3.4 I build from next week using the admin ui
- start
- install releng tools
- install
- install agent.feature.featureGroup
- install user.ui.feature.featureGroup
- starts (then I can't see the user ui but that's an implementation detail
:-))
From: Timothy Webb <tim@xxxxxxxxxx>
To: Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
Date: 01/31/2008 10:27 PM
Subject: Re: [equinox-dev] [prov] p2 provisioned eclipse missing companion library
Pascal,
I'm close now but after a number of hours in the debugger, I'm finding
that the resolver isn't correctly finding the IU fragments for some of
the bundles. Are others attempting to do installation of things other
than the SDK or other pre-configured line-ups?
All my meta data now looks correct but it still am having issues
having the install of IUs work.
Tim
On Jan 31, 2008, at 3:14 PM, Pascal Rapicault wrote:
> John and I have been doing that since M3 (some hickups of course
> occured)
> and that worked and I confirm that yesterday's build works as well.
> However we are deploying a 3.4 eclipse and not a 3.3.
> Normally when p2 installs the SDK, a -startup and -launcher.library
> arguments are being set to point ot the jar.
>
> You say: In our eclipse.ini file we drop down next to the exe,
> Do you actually drop the ini file? If so this is the pb. The ini
> files are
> no longer file that you lay down. Instead they result from the
> installation
> of some IUs (for example, see the
> toolingorg.eclipse.equinox.launcher IU)
>
> HTH,
>
> PaScaL
>
>
> |------------>
> | From: |
> |------------>
>>
--------------------------------------------------------------------------------------------------------------------------------------------------|
> |Timothy Webb
> <
> tim
> @trwebb
> .com
> >
>
|
>>
--------------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | To: |
> |------------>
>>
--------------------------------------------------------------------------------------------------------------------------------------------------|
> |Equinox development mailing list <equinox-
> dev
> @eclipse
> .org
> >
>
|
>>
--------------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | Date: |
> |------------>
>>
--------------------------------------------------------------------------------------------------------------------------------------------------|
> |01/31/2008 03:47
> PM
>
|
>>
--------------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | Subject: |
> |------------>
>>
--------------------------------------------------------------------------------------------------------------------------------------------------|
> |[equinox-dev] [prov] p2 provisioned eclipse missing companion
> library
>
|
>>
--------------------------------------------------------------------------------------------------------------------------------------------------|
>
>
>
>
>
> Are others having success using p2 to provision an Eclipse where the
> cache directory is not collocated with the eclipse exe?
>
> I'm running into an issue where despite having what appears to be the
> right set of software downloaded in the cache, configured in the
> platform.xml / config.ini, etc., each time I try to run the
> eclipse.exe, I receive "The eclipse executable launcher was unable to
> locate its companion launcher jar." In looking through the C code for
> the launcher, it looks like Eclipse is designed to search for the
> companion library in the plugins area, located near the exe, or by
> specifying --launcher.library on the command line. In our eclipse.ini
> file we drop down next to the exe, I don't see a --launcher.library
> argument configured. Is this something that should be setup by
> default in the normal touchpoints? Or, is there a branch of the
> Eclipse.exe that is designed to work better with p2-style deployments?
>
> Thanks,
> Tim
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
>
>
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
