Home » Eclipse Projects » Equinox » p2-self provisioning into emty folder or assembled product?
| p2-self provisioning into emty folder or assembled product? [message #120207] |
Mon, 27 October 2008 08:06  |
 Alexander NyÃ?en
Messages: 38
Registered: July 2009 |
Member |
|
|
Hallo p2-experts,
just a simple question: when doing a self-provisioning of a RCP with the p2
director application, do I have to run the director on a destination where I
unzipped my already assembled product (so the director only adds the p2
information), or should I use a completely empty directory for that, so that
the p2 director creates everything "from scratch", including the features
and plugins, as well as the launcher binaries? Having read the p2 director
documentation and having investigated several examples on the web, this is
not yet clear to me.
I ask because I used the first approach and thought I got it working, but
installing any subsequent features into my "p2ized" product fails, because
of unsatisfied dependencies to plug-ins, which should already be installed
in the product (so I suppose they are not installed correctly). However, if
I run the p2 director on an empty directory, it just creates the p2
directory and neither features or plugins sub-directories nor any binaries.
Regards
Alexander
|
|
|
| Re: p2-self provisioning into emty folder or assembled product? [message #120445 is a reply to message #120207] |
Fri, 31 October 2008 15:25  |
Andrew Niefer
Messages: 990
Registered: July 2009 |
Senior Member |
|
|
You should install into an empty directory, installing over the results
from pde.build won't save you anything as things will be overwritten.
So it is better to install into an empty directory as a way to ensure
that your metadata is all good.
When calling the director to do the install, make sure you specify all 3 of
-destination, -bundlepool and -vmargs -Declipse.p2.data.area
Generally, destination and bundlepool should be the same and
eclipse.p2.data.area should be destination/p2.
If you don't specify bundlepool it creates a pool for you somewhere else
on your disk (user directory?) would could be why you don't see anything.
-Andrew
Alexander Nyßen wrote:
> Hallo p2-experts,
>
> just a simple question: when doing a self-provisioning of a RCP with the p2
> director application, do I have to run the director on a destination where I
> unzipped my already assembled product (so the director only adds the p2
> information), or should I use a completely empty directory for that, so that
> the p2 director creates everything "from scratch", including the features
> and plugins, as well as the launcher binaries? Having read the p2 director
> documentation and having investigated several examples on the web, this is
> not yet clear to me.
>
> I ask because I used the first approach and thought I got it working, but
> installing any subsequent features into my "p2ized" product fails, because
> of unsatisfied dependencies to plug-ins, which should already be installed
> in the product (so I suppose they are not installed correctly). However, if
> I run the p2 director on an empty directory, it just creates the p2
> directory and neither features or plugins sub-directories nor any binaries.
>
> Regards
> Alexander
>
>
|
|
|
| Re: p2-self provisioning into emty folder or assembled product? [message #120500 is a reply to message #120445] |
Sat, 01 November 2008 09:49 |
Eclipse User |
|
|
|
Originally posted by: any.swc.rwth-aachen.de
Just to get it right. If I install into an empty directory, is the p2
director app also expected to create the plugins, features, and
configuration folders (as this is not the case when I use it) or just the p2
directory, which I am then expected to "merge" into my PDE exported product?
Regards
Alexander
"Andrew Niefer" <aniefer@ca.ibm.com> schrieb im Newsbeitrag
news:gef81a$51p$1@build.eclipse.org...
> You should install into an empty directory, installing over the results
> from pde.build won't save you anything as things will be overwritten.
>
> So it is better to install into an empty directory as a way to ensure that
> your metadata is all good.
>
> When calling the director to do the install, make sure you specify all 3
> of
> -destination, -bundlepool and -vmargs -Declipse.p2.data.area
> Generally, destination and bundlepool should be the same and
> eclipse.p2.data.area should be destination/p2.
>
> If you don't specify bundlepool it creates a pool for you somewhere else
> on your disk (user directory?) would could be why you don't see anything.
>
> -Andrew
>
> Alexander Nyßen wrote:
>> Hallo p2-experts,
>>
>> just a simple question: when doing a self-provisioning of a RCP with the
>> p2 director application, do I have to run the director on a destination
>> where I unzipped my already assembled product (so the director only adds
>> the p2 information), or should I use a completely empty directory for
>> that, so that the p2 director creates everything "from scratch",
>> including the features and plugins, as well as the launcher binaries?
>> Having read the p2 director documentation and having investigated several
>> examples on the web, this is not yet clear to me.
>>
>> I ask because I used the first approach and thought I got it working, but
>> installing any subsequent features into my "p2ized" product fails,
>> because of unsatisfied dependencies to plug-ins, which should already be
>> installed in the product (so I suppose they are not installed correctly).
>> However, if I run the p2 director on an empty directory, it just creates
>> the p2 directory and neither features or plugins sub-directories nor any
>> binaries.
>>
>> Regards
>> Alexander
|
|
|
| Re: p2-self provisioning into emty folder or assembled product? [message #120560 is a reply to message #120500] |
Mon, 03 November 2008 16:33 |
Andrew Niefer
Messages: 990
Registered: July 2009 |
Senior Member |
|
|
The director is expected to create everything.
Alexander Nyßen wrote:
> Just to get it right. If I install into an empty directory, is the p2
> director app also expected to create the plugins, features, and
> configuration folders (as this is not the case when I use it) or just
> the p2 directory, which I am then expected to "merge" into my PDE
> exported product?
>
> Regards
> Alexander
>
> "Andrew Niefer" <aniefer@ca.ibm.com> schrieb im Newsbeitrag
> news:gef81a$51p$1@build.eclipse.org...
>> You should install into an empty directory, installing over the
>> results from pde.build won't save you anything as things will be
>> overwritten.
>>
>> So it is better to install into an empty directory as a way to ensure
>> that your metadata is all good.
>>
>> When calling the director to do the install, make sure you specify all
>> 3 of
>> -destination, -bundlepool and -vmargs -Declipse.p2.data.area
>> Generally, destination and bundlepool should be the same and
>> eclipse.p2.data.area should be destination/p2.
>>
>> If you don't specify bundlepool it creates a pool for you somewhere
>> else on your disk (user directory?) would could be why you don't see
>> anything.
>>
>> -Andrew
>>
>> Alexander Nyßen wrote:
>>> Hallo p2-experts,
>>>
>>> just a simple question: when doing a self-provisioning of a RCP with
>>> the p2 director application, do I have to run the director on a
>>> destination where I unzipped my already assembled product (so the
>>> director only adds the p2 information), or should I use a completely
>>> empty directory for that, so that the p2 director creates everything
>>> "from scratch", including the features and plugins, as well as the
>>> launcher binaries? Having read the p2 director documentation and
>>> having investigated several examples on the web, this is not yet
>>> clear to me.
>>>
>>> I ask because I used the first approach and thought I got it working,
>>> but installing any subsequent features into my "p2ized" product
>>> fails, because of unsatisfied dependencies to plug-ins, which should
>>> already be installed in the product (so I suppose they are not
>>> installed correctly). However, if I run the p2 director on an empty
>>> directory, it just creates the p2 directory and neither features or
>>> plugins sub-directories nor any binaries.
>>>
>>> Regards
>>> Alexander
>
|
|
|
| Re: p2-self provisioning into emty folder or assembled product? [message #120609 is a reply to message #120560] |
Mon, 03 November 2008 22:11 |
| Eclipse User |
|
|
|
Originally posted by: any.swc.rwth-aachen.de
Thanks. That brings me forward.
Investigating the logs, I thnink that the reason why in my case the p2
director does not create more than just the p2 directory probably is the
following:
!SESSION 2008-11-03
22:37:54.777 -----------------------------------------------
eclipse.buildId=I20081030-1917
java.version=1.6.0
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=de_DE
Framework arguments: -application
org.eclipse.equinox.p2.director.app.application -installIU
sc.viper.ide.product -profile ViPERProfile -profileProperties
org.eclipse.update.install.features=true -p2.os linux -p2.ws gtk -p2.arch
x86 -metadataRepository
file:/home/viper/build_workspace/sc.viper.ide.releng/build/p 2_repository -artifactRepository
file:/home/viper/build_workspace/sc.viper.ide.releng/build/p 2_repository -destination
/home/viper/build_workspace/sc.viper.ide.releng/build/M.2008 11032110/p2_install/ViPER
-bundlepool
/home/viper/build_workspace/sc.viper.ide.releng/build/M.2008 11032110/p2_install/ViPER
-roaming
Command-line arguments: -os linux -ws gtk -arch x86 -application
org.eclipse.equinox.p2.director.app.application -debug -installIU
sc.viper.ide.product -profile ViPERProfile -profileProperties
org.eclipse.update.install.features=true -p2.os linux -p2.ws gtk -p2.arch
x86 -metadataRepository
file:/home/viper/build_workspace/sc.viper.ide.releng/build/p 2_repository -artifactRepository
file:/home/viper/build_workspace/sc.viper.ide.releng/build/p 2_repository -destination
/home/viper/build_workspace/sc.viper.ide.releng/build/M.2008 11032110/p2_install/ViPER
-bundlepool
/home/viper/build_workspace/sc.viper.ide.releng/build/M.2008 11032110/p2_install/ViPER
-roaming
!ENTRY org.eclipse.equinox.p2.director 4 0 2008-11-03 22:38:40.318
!MESSAGE Problems resolving provisioning plan.
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-11-03 22:38:40.318
!MESSAGE No solution found because the problem in /tmp/p2Encoding36800.opb
is unsatisfiable.
!ENTRY org.eclipse.equinox.p2.director 4 1 2008-11-03 22:39:17.182
!MESSAGE Cannot find a solution satisfying the following requirements
com.jcraft.jsch [0.1.28].
!ENTRY org.eclipse.osgi 4 0 2008-11-03 22:39:18.153
!MESSAGE Application error
!STACK 1
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.ant.core.AntRunner.run(AntRunner.java:513)
at org.eclipse.ant.core.AntRunner.start(AntRunner.java:600)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:386)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
However, the com.jcraft.jsch plug-in is bundled by my thirdparty feature
(which is included as the first feature within the RCP feature, specified by
my product) in all versions provided by Orbit and thus also in version
0.1.28. It is thus also contained in the p2 repository, which is generated
during build. Any idea how I could find out what causes this dependency
problem?
Regards
Alexander
"Andrew Niefer" <aniefer@ca.ibm.com> schrieb im Newsbeitrag
news:gen95b$e0n$2@build.eclipse.org...
> The director is expected to create everything.
>
> Alexander Nyßen wrote:
>> Just to get it right. If I install into an empty directory, is the p2
>> director app also expected to create the plugins, features, and
>> configuration folders (as this is not the case when I use it) or just the
>> p2 directory, which I am then expected to "merge" into my PDE exported
>> product?
>>
>> Regards
>> Alexander
>>
>> "Andrew Niefer" <aniefer@ca.ibm.com> schrieb im Newsbeitrag
>> news:gef81a$51p$1@build.eclipse.org...
>>> You should install into an empty directory, installing over the results
>>> from pde.build won't save you anything as things will be overwritten.
>>>
>>> So it is better to install into an empty directory as a way to ensure
>>> that your metadata is all good.
>>>
>>> When calling the director to do the install, make sure you specify all 3
>>> of
>>> -destination, -bundlepool and -vmargs -Declipse.p2.data.area
>>> Generally, destination and bundlepool should be the same and
>>> eclipse.p2.data.area should be destination/p2.
>>>
>>> If you don't specify bundlepool it creates a pool for you somewhere else
>>> on your disk (user directory?) would could be why you don't see
>>> anything.
>>>
>>> -Andrew
>>>
>>> Alexander Nyßen wrote:
>>>> Hallo p2-experts,
>>>>
>>>> just a simple question: when doing a self-provisioning of a RCP with
>>>> the p2 director application, do I have to run the director on a
>>>> destination where I unzipped my already assembled product (so the
>>>> director only adds the p2 information), or should I use a completely
>>>> empty directory for that, so that the p2 director creates everything
>>>> "from scratch", including the features and plugins, as well as the
>>>> launcher binaries? Having read the p2 director documentation and having
>>>> investigated several examples on the web, this is not yet clear to me.
>>>>
>>>> I ask because I used the first approach and thought I got it working,
>>>> but installing any subsequent features into my "p2ized" product fails,
>>>> because of unsatisfied dependencies to plug-ins, which should already
>>>> be installed in the product (so I suppose they are not installed
>>>> correctly). However, if I run the p2 director on an empty directory, it
>>>> just creates the p2 directory and neither features or plugins
>>>> sub-directories nor any binaries.
>>>>
>>>> Regards
>>>> Alexander
>>
|
|
|
| Re: p2-self provisioning into emty folder or assembled product? [message #120673 is a reply to message #120609] |
Tue, 04 November 2008 11:22 |
| Eclipse User |
|
|
|
Originally posted by: any.swc.rwth-aachen.de
It seems to be a bug to me, related to the orbit bundles. I filed it as
253668.
Regards
Alexander
"Alexander Nyßen" <any@swc.rwth-aachen.de> schrieb im Newsbeitrag
news:gensun$d0s$1@build.eclipse.org...
> Thanks. That brings me forward.
>
> Investigating the logs, I thnink that the reason why in my case the p2
> director does not create more than just the p2 directory probably is the
> following:
>
> !SESSION 2008-11-03
> 22:37:54.777 -----------------------------------------------
> eclipse.buildId=I20081030-1917
> java.version=1.6.0
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=de_DE
> Framework arguments: -application
> org.eclipse.equinox.p2.director.app.application -installIU
> sc.viper.ide.product -profile ViPERProfile -profileProperties
> org.eclipse.update.install.features=true -p2.os linux -p2.ws gtk -p2.arch
> x86 -metadataRepository
> file:/home/viper/build_workspace/sc.viper.ide.releng/build/p 2_repository -artifactRepository
> file:/home/viper/build_workspace/sc.viper.ide.releng/build/p 2_repository -destination
> /home/viper/build_workspace/sc.viper.ide.releng/build/M.2008 11032110/p2_install/ViPER
> -bundlepool
> /home/viper/build_workspace/sc.viper.ide.releng/build/M.2008 11032110/p2_install/ViPER
> -roaming
> Command-line arguments: -os linux -ws gtk -arch x86 -application
> org.eclipse.equinox.p2.director.app.application -debug -installIU
> sc.viper.ide.product -profile ViPERProfile -profileProperties
> org.eclipse.update.install.features=true -p2.os linux -p2.ws gtk -p2.arch
> x86 -metadataRepository
> file:/home/viper/build_workspace/sc.viper.ide.releng/build/p 2_repository -artifactRepository
> file:/home/viper/build_workspace/sc.viper.ide.releng/build/p 2_repository -destination
> /home/viper/build_workspace/sc.viper.ide.releng/build/M.2008 11032110/p2_install/ViPER
> -bundlepool
> /home/viper/build_workspace/sc.viper.ide.releng/build/M.2008 11032110/p2_install/ViPER
> -roaming
>
> !ENTRY org.eclipse.equinox.p2.director 4 0 2008-11-03 22:38:40.318
> !MESSAGE Problems resolving provisioning plan.
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-11-03 22:38:40.318
> !MESSAGE No solution found because the problem in /tmp/p2Encoding36800.opb
> is unsatisfiable.
>
> !ENTRY org.eclipse.equinox.p2.director 4 1 2008-11-03 22:39:17.182
> !MESSAGE Cannot find a solution satisfying the following requirements
> com.jcraft.jsch [0.1.28].
>
> !ENTRY org.eclipse.osgi 4 0 2008-11-03 22:39:18.153
> !MESSAGE Application error
> !STACK 1
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:513)
> at org.eclipse.ant.core.AntRunner.start(AntRunner.java:600)
> at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:386)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
>
> However, the com.jcraft.jsch plug-in is bundled by my thirdparty feature
> (which is included as the first feature within the RCP feature, specified
> by my product) in all versions provided by Orbit and thus also in version
> 0.1.28. It is thus also contained in the p2 repository, which is generated
> during build. Any idea how I could find out what causes this dependency
> problem?
>
> Regards
> Alexander
>
>
> "Andrew Niefer" <aniefer@ca.ibm.com> schrieb im Newsbeitrag
> news:gen95b$e0n$2@build.eclipse.org...
>> The director is expected to create everything.
>>
>> Alexander Nyßen wrote:
>>> Just to get it right. If I install into an empty directory, is the p2
>>> director app also expected to create the plugins, features, and
>>> configuration folders (as this is not the case when I use it) or just
>>> the p2 directory, which I am then expected to "merge" into my PDE
>>> exported product?
>>>
>>> Regards
>>> Alexander
>>>
>>> "Andrew Niefer" <aniefer@ca.ibm.com> schrieb im Newsbeitrag
>>> news:gef81a$51p$1@build.eclipse.org...
>>>> You should install into an empty directory, installing over the results
>>>> from pde.build won't save you anything as things will be overwritten.
>>>>
>>>> So it is better to install into an empty directory as a way to ensure
>>>> that your metadata is all good.
>>>>
>>>> When calling the director to do the install, make sure you specify all
>>>> 3 of
>>>> -destination, -bundlepool and -vmargs -Declipse.p2.data.area
>>>> Generally, destination and bundlepool should be the same and
>>>> eclipse.p2.data.area should be destination/p2.
>>>>
>>>> If you don't specify bundlepool it creates a pool for you somewhere
>>>> else on your disk (user directory?) would could be why you don't see
>>>> anything.
>>>>
>>>> -Andrew
>>>>
>>>> Alexander Nyßen wrote:
>>>>> Hallo p2-experts,
>>>>>
>>>>> just a simple question: when doing a self-provisioning of a RCP with
>>>>> the p2 director application, do I have to run the director on a
>>>>> destination where I unzipped my already assembled product (so the
>>>>> director only adds the p2 information), or should I use a completely
>>>>> empty directory for that, so that the p2 director creates everything
>>>>> "from scratch", including the features and plugins, as well as the
>>>>> launcher binaries? Having read the p2 director documentation and
>>>>> having investigated several examples on the web, this is not yet clear
>>>>> to me.
>>>>>
>>>>> I ask because I used the first approach and thought I got it working,
>>>>> but installing any subsequent features into my "p2ized" product
>>>>> fails, because of unsatisfied dependencies to plug-ins, which should
>>>>> already be installed in the product (so I suppose they are not
>>>>> installed correctly). However, if I run the p2 director on an empty
>>>>> directory, it just creates the p2 directory and neither features or
>>>>> plugins sub-directories nor any binaries.
>>>>>
>>>>> Regards
>>>>> Alexander
>>>
>
|
|
|
Goto Forum:
Current Time: Sat Apr 27 02:01:47 GMT 2024
Powered by FUDForum. Page generated in 0.03240 seconds |
] 
Search
Help
Register
Login
Home
