| P2 Director product-based install fails unable to satisfy dependencies [message #121356] |
Thu, 20 November 2008 15:40  |
 Chris Williams
Messages: 29
Registered: July 2009 |
Junior Member |
|
|
I'm trying to get a p2-enabled 3.4+ compatible version of our product
building. I started from scratch with a new product build, and I can get
it to build the zips for the platforms we're targeting and it seems to
generate the p2 metadata fine. But when I try to run the p2 director to
generate a complete p2-enabled product it fails:
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-11-20 10:25:26.335
!MESSAGE Unsatisfied dependency: [com.aptana.ide.rcp.product 1.2.0.019866]
requiredCapability:
toolingcom.aptana.ide.rcp.product/com.aptana.ide.rcp.product .ini/[1.2.0.019866,1.2.0.019866]
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-11-20 10:25:26.335
!MESSAGE Unsatisfied dependency: [com.aptana.ide.rcp.product 1.2.0.019866]
requiredCapability:
toolingcom.aptana.ide.rcp.product/com.aptana.ide.rcp.product .config/[1.2.0.019866,1.2.0.019866]
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-11-20 10:25:26.336
!MESSAGE Unsatisfied dependency: [com.aptana.ide.rcp.product 1.2.0.019866]
requiredCapability:
toolingcom.aptana.ide.rcp.product/com.aptana.ide.rcp.product .launcher/[1.2.0.019866,1.2.0.019866]
If I look at the content.xml file, I assume these are the crucial lines:
<required namespace='toolingcom.aptana.ide.rcp.product'
name='com.aptana.ide.rcp.product.launcher'
range='[1.2.0.019866,1.2.0.019866]' multiple='true'/>
<required namespace='toolingcom.aptana.ide.rcp.product'
name='com.aptana.ide.rcp.product.ini' range='[1.2.0.019866,1.2.0.019866]'/>
<required namespace='toolingcom.aptana.ide.rcp.product'
name='com.aptana.ide.rcp.product.config'
range='[1.2.0.019866,1.2.0.019866]'/>
But to my naive eye, it looks like that same file does contain the
dependency it's asking for:
<unit id='com.aptana.ide.rcp.product.launcher.carbon.macosx.x86'
version='1.2.0.019866'>
<provides size='2'>
<provided namespace='org.eclipse.equinox.p2.iu'
name='com.aptana.ide.rcp.product.launcher.carbon.macosx.x86'
version='1.2.0.019866'/>
<provided namespace='toolingcom.aptana.ide.rcp.product'
name='com.aptana.ide.rcp.product.launcher' version='1.2.0.019866'/>
</provides>
Am I missing something here? why can't it satisfy those dependencies? Has
anyone else seen anything like this?
-Chris
|
|
|
| Re: P2 Director product-based install fails unable to satisfy dependencies [message #121457 is a reply to message #121356] |
Mon, 24 November 2008 16:10  |
Andrew Niefer
Messages: 990
Registered: July 2009 |
Senior Member |
|
|
Which architecture are you specifying in your call to the director?
Even though the Mac has universal binaries, you still need to specify an
architecture (either x86 or ppc) using -p2.arch.
Even though Eclipse's universal binaries will run on both x86 and ppc,
the install itself needs to specify one or the other. The launcher will
set the runtime architecture based on the machine it is running on, but
the p2 profile is static and it must be specified at install time.
You may want to consider generating metadata for both x86 and ppc. For
example the Eclipse SDK zip for carbon are created for ppc (though it
runs on both) and will require ppc IUs to be installed on top of it.
-Andrew
Chris Williams wrote:
> I'm trying to get a p2-enabled 3.4+ compatible version of our product
> building. I started from scratch with a new product build, and I can get
> it to build the zips for the platforms we're targeting and it seems to
> generate the p2 metadata fine. But when I try to run the p2 director to
> generate a complete p2-enabled product it fails:
>
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-11-20 10:25:26.335
> !MESSAGE Unsatisfied dependency: [com.aptana.ide.rcp.product
> 1.2.0.019866] requiredCapability:
> toolingcom.aptana.ide.rcp.product/com.aptana.ide.rcp.product .ini/[1.2.0.019866,1.2.0.019866]
>
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-11-20 10:25:26.335
> !MESSAGE Unsatisfied dependency: [com.aptana.ide.rcp.product
> 1.2.0.019866] requiredCapability:
> toolingcom.aptana.ide.rcp.product/com.aptana.ide.rcp.product .config/[1.2.0.019866,1.2.0.019866]
>
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-11-20 10:25:26.336
> !MESSAGE Unsatisfied dependency: [com.aptana.ide.rcp.product
> 1.2.0.019866] requiredCapability:
> toolingcom.aptana.ide.rcp.product/com.aptana.ide.rcp.product .launcher/[1.2.0.019866,1.2.0.019866]
>
>
> If I look at the content.xml file, I assume these are the crucial lines:
>
> <required namespace='toolingcom.aptana.ide.rcp.product'
> name='com.aptana.ide.rcp.product.launcher'
> range='[1.2.0.019866,1.2.0.019866]' multiple='true'/>
> <required namespace='toolingcom.aptana.ide.rcp.product'
> name='com.aptana.ide.rcp.product.ini' range='[1.2.0.019866,1.2.0.019866]'/>
> <required namespace='toolingcom.aptana.ide.rcp.product'
> name='com.aptana.ide.rcp.product.config'
> range='[1.2.0.019866,1.2.0.019866]'/>
>
> But to my naive eye, it looks like that same file does contain the
> dependency it's asking for:
>
> <unit id='com.aptana.ide.rcp.product.launcher.carbon.macosx.x86'
> version='1.2.0.019866'>
> <provides size='2'>
> <provided namespace='org.eclipse.equinox.p2.iu'
> name='com.aptana.ide.rcp.product.launcher.carbon.macosx.x86'
> version='1.2.0.019866'/>
> <provided namespace='toolingcom.aptana.ide.rcp.product'
> name='com.aptana.ide.rcp.product.launcher' version='1.2.0.019866'/>
> </provides>
>
>
> Am I missing something here? why can't it satisfy those dependencies?
> Has anyone else seen anything like this?
>
> -Chris
>
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.30089 seconds
] 
Search
Help
Register
Login
Home
