Home » Eclipse Projects » Equinox » Config IU - Unsatisfied dependency.
| Config IU - Unsatisfied dependency. [message #121149] |
Thu, 13 November 2008 13:19  |
Eclipse User |
|
|
|
Originally posted by: any.swc.rwth-aachen.de
Hallo,
as I have to build multiple configurations of my product (win32, linux,
macosx), which I want to p2-ize, I decided to not generate the p2 metadata
via the PDE build options, but by calling the p2 generator (and p2 director)
explicitly from my customTargets.xml (this will allow to generate p2
metadata and do provisioning for each platform independently).
My goal is to take the already assembled product (for each platform),
generate metadata for it (using p2 generator) and provisioning the p2-ized
product with the director. So far so good. I created the following shell
script to test p2 metadata generation and provisioning on my already
assembled product (I noticed that calling the generator with a productFile
and config operation will not create the features and plugins within the
repository, so I assume I need to calls on the generator):
/home/viper/build_workspace/sc.viper.ide.releng/builder/ecli pse -vm
/home/viper/java/jre1.6.0/bin/java -application
org.eclipse.equinox.p2.metadata.generator.EclipseGenerator -nosplash -debug
-consoleLog --launcher.suppressErrors -source
/home/viper/build_workspace/sc.viper.ide.releng/build/M.2008 11131225/p2_generate/ViPER
-metadataRepository file:/home/viper/p2rep -artifactRepository
file:/home/viper/p2rep -publishArtifacts -p2.os
linux -append -noDefaultIUs -root sc.viper.ide.feature.group -rootVersion
1.0.0.v200811131225 -flavor tooling
/home/viper/build_workspace/sc.viper.ide.releng/builder/ecli pse -vm
/home/viper/java/jre1.6.0/bin/java -application
org.eclipse.equinox.p2.metadata.generator.EclipseGenerator -nosplash -debug
-consoleLog --launcher.suppressErrors -config
/home/viper/build_workspace/sc.viper.ide.releng/build/M.2008 11131225/p2_generate/ViPER
-metadataRepository file:/home/viper/p2rep -artifactRepository
file:/home/viper/p2rep -publishArtifacts -p2.os linux -launcherConfig
linux_gtk_x86 -exe
/home/viper/build_workspace/sc.viper.ide.releng/build/M.2008 11131225/p2_generate/ViPER/viper
-productFile
/home/viper/build_workspace/sc.viper.ide.releng/build/plugin s/sc.viper.ide/sc.viper.ide.product
-append -flavor tooling
/home/viper/build_workspace/sc.viper.ide.releng/builder/ecli pse -vm
/home/viper/java/jre1.6.0/bin/java -application
org.eclipse.equinox.p2.director.app.application -nosplash -debug -consoleLog
--launcher.suppressErrors -installIU sc.viper.ide.product -version
1.0.0.v200811131225 -profile ViPERProfile -profileProperties
org.eclipse.update.install.features=true -p2.os linux -p2.ws gtk -p2.arch
x86 -metadataRepository file:/home/viper/p2rep -artifactRepository
file:/home/viper/p2rep -destination /home/viper/p2ins -bundlepool
/home/viper/p2ins -roaming
The created repository looks ok so far (features and plugins as well a
binary folder, which contains a platform specific launcher). However,
calling the director yields the following problem:
!ENTRY org.eclipse.equinox.p2.director 4 0 2008-11-13 14:04:44.800
!MESSAGE Problems resolving provisioning plan.
!SUBENTRY 1 org.eclipse.equinox.p2.director 2 0 2008-11-13 14:04:44.801
!MESSAGE Unable to satisfy dependency from sc.viper.ide.product
1.0.0.v200811131225 to requiredCapability:
toolingsc.viper.ide.product/sc.viper.ide.product.config/[1.0 .0.v200811131225,1.0.0.v200811131225].
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-11-13 14:04:44.802
!MESSAGE No solution found because the problem in /tmp/p2Encoding53620.opb
is unsatisfiable.
Installation failed.
!ENTRY org.eclipse.equinox.p2.director 4 1 2008-11-13 14:04:47.320
!MESSAGE Cannot complete the install because some dependencies are not
satisfiable
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-11-13 14:04:47.321
!MESSAGE Unsatisfied dependency: [sc.viper.ide.product 1.0.0.v200811131225]
requiredCapability:
toolingsc.viper.ide.product/sc.viper.ide.product.config/[1.0 .0.v200811131225,1.0.0.v200811131225]
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-11-13 14:04:47.321
!MESSAGE Unsatisfied dependency: [sc.viper.ide.product 1.0.0.v200811131225]
requiredCapability:
toolingsc.viper.ide.product/sc.viper.ide.product.config/[1.0 .0.v200811131225,1.0.0.v200811131225]
Any ideas?
Regards
Alexander
|
|
|
| Re: Config IU - Unsatisfied dependency. [message #121247 is a reply to message #121149] |
Mon, 17 November 2008 08:18  |
 Alexander NyÃ?en
Messages: 38
Registered: July 2009 |
Member |
|
|
Ok, I now debugged into
org.eclipse.equinox.internal.provisional.p2.metadata.generat or.Generator and
investigated that (in my second call to the generator appliccation, i.e.
when passing launcherConfig, productFile, etc) the config IU for the product
is not created, because the GeneratorResult parameter passed into
generateProductConfigCUs method of the Generator class does not contain any
configData. This in turn seems to be caused, because storeConfigData is
never called (which seems to be the only method manipulating the
GeneratorResult's configData). This method however would only get called
within generateConfigIUs, if the passed in configData, i.e. that obtained
from the manipulator, does not provide any bundles but a launcherConfig. And
this seems to be never the case in my situation.
May it be possible, that it only possible to have the config IU generated
when calling the Generator in its incremental mode (as done by PDE build,
i.e. the p2.generator ant task), and not when calling it via the Generator
Application (as done within my scripts), as it does not seem to be possible
to fulfill the conditions to have it created within generateProductConfigCUs
within a single call of the application?
Regards
Alexander
"Alexander Nyßen" <any@swc.rwth-aachen.de> schrieb im Newsbeitrag
news:gfh9hi$2l1$1@build.eclipse.org...
> Hallo,
>
> as I have to build multiple configurations of my product (win32, linux,
> macosx), which I want to p2-ize, I decided to not generate the p2 metadata
> via the PDE build options, but by calling the p2 generator (and p2
> director) explicitly from my customTargets.xml (this will allow to
> generate p2 metadata and do provisioning for each platform independently).
>
> My goal is to take the already assembled product (for each platform),
> generate metadata for it (using p2 generator) and provisioning the p2-ized
> product with the director. So far so good. I created the following shell
> script to test p2 metadata generation and provisioning on my already
> assembled product (I noticed that calling the generator with a productFile
> and config operation will not create the features and plugins within the
> repository, so I assume I need to calls on the generator):
>
> /home/viper/build_workspace/sc.viper.ide.releng/builder/ecli pse -vm
> /home/viper/java/jre1.6.0/bin/java -application
> org.eclipse.equinox.p2.metadata.generator.EclipseGenerator -nosplash -debug
> -consoleLog --launcher.suppressErrors -source
> /home/viper/build_workspace/sc.viper.ide.releng/build/M.2008 11131225/p2_generate/ViPER
> -metadataRepository file:/home/viper/p2rep -artifactRepository
> file:/home/viper/p2rep -publishArtifacts -p2.os
> linux -append -noDefaultIUs -root sc.viper.ide.feature.group -rootVersion
> 1.0.0.v200811131225 -flavor tooling
>
> /home/viper/build_workspace/sc.viper.ide.releng/builder/ecli pse -vm
> /home/viper/java/jre1.6.0/bin/java -application
> org.eclipse.equinox.p2.metadata.generator.EclipseGenerator -nosplash -debug
> -consoleLog --launcher.suppressErrors -config
> /home/viper/build_workspace/sc.viper.ide.releng/build/M.2008 11131225/p2_generate/ViPER
> -metadataRepository file:/home/viper/p2rep -artifactRepository
> file:/home/viper/p2rep -publishArtifacts -p2.os linux -launcherConfig
> linux_gtk_x86 -exe
> /home/viper/build_workspace/sc.viper.ide.releng/build/M.2008 11131225/p2_generate/ViPER/viper
> -productFile
> /home/viper/build_workspace/sc.viper.ide.releng/build/plugin s/sc.viper.ide/sc.viper.ide.product
> -append -flavor tooling
>
> /home/viper/build_workspace/sc.viper.ide.releng/builder/ecli pse -vm
> /home/viper/java/jre1.6.0/bin/java -application
> org.eclipse.equinox.p2.director.app.application -nosplash -debug -consoleLog
> --launcher.suppressErrors -installIU sc.viper.ide.product -version
> 1.0.0.v200811131225 -profile ViPERProfile -profileProperties
> org.eclipse.update.install.features=true -p2.os linux -p2.ws gtk -p2.arch
> x86 -metadataRepository file:/home/viper/p2rep -artifactRepository
> file:/home/viper/p2rep -destination /home/viper/p2ins -bundlepool
> /home/viper/p2ins -roaming
>
> The created repository looks ok so far (features and plugins as well a
> binary folder, which contains a platform specific launcher). However,
> calling the director yields the following problem:
>
> !ENTRY org.eclipse.equinox.p2.director 4 0 2008-11-13 14:04:44.800
> !MESSAGE Problems resolving provisioning plan.
> !SUBENTRY 1 org.eclipse.equinox.p2.director 2 0 2008-11-13 14:04:44.801
> !MESSAGE Unable to satisfy dependency from sc.viper.ide.product
> 1.0.0.v200811131225 to requiredCapability:
> toolingsc.viper.ide.product/sc.viper.ide.product.config/[1.0 .0.v200811131225,1.0.0.v200811131225].
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-11-13 14:04:44.802
> !MESSAGE No solution found because the problem in /tmp/p2Encoding53620.opb
> is unsatisfiable.
> Installation failed.
>
> !ENTRY org.eclipse.equinox.p2.director 4 1 2008-11-13 14:04:47.320
> !MESSAGE Cannot complete the install because some dependencies are not
> satisfiable
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-11-13 14:04:47.321
> !MESSAGE Unsatisfied dependency: [sc.viper.ide.product
> 1.0.0.v200811131225] requiredCapability:
> toolingsc.viper.ide.product/sc.viper.ide.product.config/[1.0 .0.v200811131225,1.0.0.v200811131225]
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-11-13 14:04:47.321
> !MESSAGE Unsatisfied dependency: [sc.viper.ide.product
> 1.0.0.v200811131225] requiredCapability:
> toolingsc.viper.ide.product/sc.viper.ide.product.config/[1.0 .0.v200811131225,1.0.0.v200811131225]
>
> Any ideas?
>
> Regards
> Alexander
|
|
|
| Re: Config IU - Unsatisfied dependency. [message #124619 is a reply to message #121247] |
Fri, 16 January 2009 09:07 |
| Eclipse User |
|
|
|
Originally posted by: r.zozmann.exxcellent.de
Hi Alexander,
i have the same problem. Does you have found any solutions for that?
Regards
Ralf
Alexander Nyßen wrote:
> Ok, I now debugged into
> org.eclipse.equinox.internal.provisional.p2.metadata.generat or.Generator
> and investigated that (in my second call to the generator appliccation,
> i.e. when passing launcherConfig, productFile, etc) the config IU for
> the product is not created, because the GeneratorResult parameter passed
> into generateProductConfigCUs method of the Generator class does not
> contain any configData. This in turn seems to be caused, because
> storeConfigData is never called (which seems to be the only method
> manipulating the GeneratorResult's configData). This method however
> would only get called within generateConfigIUs, if the passed in
> configData, i.e. that obtained from the manipulator, does not provide
> any bundles but a launcherConfig. And this seems to be never the case in
> my situation.
>
> May it be possible, that it only possible to have the config IU
> generated when calling the Generator in its incremental mode (as done by
> PDE build, i.e. the p2.generator ant task), and not when calling it via
> the Generator Application (as done within my scripts), as it does not
> seem to be possible to fulfill the conditions to have it created within
> generateProductConfigCUs within a single call of the application?
>
> Regards
> Alexander
>
>
> "Alexander Nyßen" <any@swc.rwth-aachen.de> schrieb im Newsbeitrag
> news:gfh9hi$2l1$1@build.eclipse.org...
>> Hallo,
>>
>> as I have to build multiple configurations of my product (win32,
>> linux, macosx), which I want to p2-ize, I decided to not generate the
>> p2 metadata via the PDE build options, but by calling the p2 generator
>> (and p2 director) explicitly from my customTargets.xml (this will
>> allow to generate p2 metadata and do provisioning for each platform
>> independently).
>>
>> My goal is to take the already assembled product (for each platform),
>> generate metadata for it (using p2 generator) and provisioning the
>> p2-ized product with the director. So far so good. I created the
>> following shell script to test p2 metadata generation and provisioning
>> on my already assembled product (I noticed that calling the generator
>> with a productFile and config operation will not create the features
>> and plugins within the repository, so I assume I need to calls on the
>> generator):
>>
>> /home/viper/build_workspace/sc.viper.ide.releng/builder/ecli pse -vm
>> /home/viper/java/jre1.6.0/bin/java -application
>> org.eclipse.equinox.p2.metadata.generator.EclipseGenerator -nosplash
>> -debug -consoleLog --launcher.suppressErrors -source
>> /home/viper/build_workspace/sc.viper.ide.releng/build/M.2008 11131225/p2_generate/ViPER
>> -metadataRepository file:/home/viper/p2rep -artifactRepository
>> file:/home/viper/p2rep -publishArtifacts -p2.os linux -append
>> -noDefaultIUs -root sc.viper.ide.feature.group -rootVersion
>> 1.0.0.v200811131225 -flavor tooling
>>
>> /home/viper/build_workspace/sc.viper.ide.releng/builder/ecli pse -vm
>> /home/viper/java/jre1.6.0/bin/java -application
>> org.eclipse.equinox.p2.metadata.generator.EclipseGenerator -nosplash
>> -debug -consoleLog --launcher.suppressErrors -config
>> /home/viper/build_workspace/sc.viper.ide.releng/build/M.2008 11131225/p2_generate/ViPER
>> -metadataRepository file:/home/viper/p2rep -artifactRepository
>> file:/home/viper/p2rep -publishArtifacts -p2.os linux -launcherConfig
>> linux_gtk_x86 -exe
>> /home/viper/build_workspace/sc.viper.ide.releng/build/M.2008 11131225/p2_generate/ViPER/viper
>> -productFile
>> /home/viper/build_workspace/sc.viper.ide.releng/build/plugin s/sc.viper.ide/sc.viper.ide.product
>> -append -flavor tooling
>>
>> /home/viper/build_workspace/sc.viper.ide.releng/builder/ecli pse -vm
>> /home/viper/java/jre1.6.0/bin/java -application
>> org.eclipse.equinox.p2.director.app.application -nosplash -debug
>> -consoleLog --launcher.suppressErrors -installIU sc.viper.ide.product
>> -version 1.0.0.v200811131225 -profile ViPERProfile -profileProperties
>> org.eclipse.update.install.features=true -p2.os linux -p2.ws gtk
>> -p2.arch x86 -metadataRepository file:/home/viper/p2rep
>> -artifactRepository file:/home/viper/p2rep -destination
>> /home/viper/p2ins -bundlepool /home/viper/p2ins -roaming
>>
>> The created repository looks ok so far (features and plugins as well a
>> binary folder, which contains a platform specific launcher). However,
>> calling the director yields the following problem:
>>
>> !ENTRY org.eclipse.equinox.p2.director 4 0 2008-11-13 14:04:44.800
>> !MESSAGE Problems resolving provisioning plan.
>> !SUBENTRY 1 org.eclipse.equinox.p2.director 2 0 2008-11-13 14:04:44.801
>> !MESSAGE Unable to satisfy dependency from sc.viper.ide.product
>> 1.0.0.v200811131225 to requiredCapability:
>> toolingsc.viper.ide.product/sc.viper.ide.product.config/[1.0 .0.v200811131225,1.0.0.v200811131225].
>>
>> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-11-13 14:04:44.802
>> !MESSAGE No solution found because the problem in
>> /tmp/p2Encoding53620.opb is unsatisfiable.
>> Installation failed.
>>
>> !ENTRY org.eclipse.equinox.p2.director 4 1 2008-11-13 14:04:47.320
>> !MESSAGE Cannot complete the install because some dependencies are not
>> satisfiable
>> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-11-13 14:04:47.321
>> !MESSAGE Unsatisfied dependency: [sc.viper.ide.product
>> 1.0.0.v200811131225] requiredCapability:
>> toolingsc.viper.ide.product/sc.viper.ide.product.config/[1.0 .0.v200811131225,1.0.0.v200811131225]
>>
>> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-11-13 14:04:47.321
>> !MESSAGE Unsatisfied dependency: [sc.viper.ide.product
>> 1.0.0.v200811131225] requiredCapability:
>> toolingsc.viper.ide.product/sc.viper.ide.product.config/[1.0 .0.v200811131225,1.0.0.v200811131225]
>>
>>
>> Any ideas?
>>
>> Regards
>> Alexander
>
|
|
|
Goto Forum:
Current Time: Fri Apr 19 13:41:25 GMT 2024
Powered by FUDForum. Page generated in 0.02394 seconds |
] 
Search
Help
Register
Login
Home
