[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [p2-dev] p2 director build accessing ganymede jar files
|
In its binary form in the delta pack,
the org.eclipse.equinox.executable feature does not specify a "bin.includes"
property. This means that for a headless build, it is just a build-time
feature and will not contribute a feature jar to the results. The
purpose of this feature is to contribute the executable root files and
to bring in the org.eclipse.equinox.launcher jar and the launcher fragments.
p2 integration with PDE/Build generates
metadata on the results of the build, not on the inputs. Therefore
the executable feature won't be included in the resulting metadata. If
you want the executable in your results, you will need to get the source
version of it from CVS instead.
-Andrew
Francis Upton <francisu@xxxxxxxx>
Sent by: p2-dev-bounces@xxxxxxxxxxx
09/25/2008 04:17 PM
Please respond to
P2 developer discussions <p2-dev@xxxxxxxxxxx> |
|
To
| P2 developer discussions <p2-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| Re: [p2-dev] p2 director build accessing
ganymede jar files |
|
Thanks Pascal, that took care of that problem.
Now I have this problem, and this build used to work before. I do
have in my com.oaklandsw.transform.feature.deps.rt feature an included
feature of org.eclipse.equinox.executable. However the org.eclipse.equinox.executable
feature is not ending up in my AR/CR. I'm using the normal generated
p2.generator stuff from the PDE build. How is an "included feature"
supposed to wind up the AR/CR?
Thanks again,
Francis
!SESSION 2008-09-25 13:02:03.960 -----------------------------------------------
eclipse.buildId=I20080617-2000
java.version=1.5.0_10
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Framework arguments: -application org.eclipse.equinox.p2.director.app.application
-flavor tooling -installIU com.oaklandsw.transform.product7 -p2.os linux
-p2.ws gtk -p2.arch x86 -roaming -profile OSDTProfile -profileProperties
org.eclipse.update.install.features=true -metadataRepository file:/d/build/transform/build/repo
-artifactRepository file:/d/build/transform/build/repo
-destination /d/build/transform/build/kits/transform7-kits/linux.gtk.x86
-bundlepool /d/build/transform/build/kits/transform7-kits/linux.gtk.x86
Command-line arguments: -os linux -ws gtk -arch x86 -application
org.eclipse.equinox.p2.director.app.application -consolelog -flavor tooling
-installIU com.oaklandsw.transform.product7 -p2.os linux -p2.ws gtk -p2.arch
x86 -roaming -profile OSDTProfile -profileProperties org.eclipse.update.install.features=true
-metadataRepository file:/d/build/transform/build/repo
-artifactRepository file:/d/build/transform/build/repo
-destination /d/build/transform/build/kits/transform7-kits/linux.gtk.x86
-bundlepool /d/build/transform/build/kits/transform7-kits/linux.gtk.x86
!ENTRY org.eclipse.equinox.p2.director 2 0 2008-09-25 13:02:10.992
!MESSAGE Problems resolving provisioning plan.
!SUBENTRY 1 org.eclipse.equinox.p2.director 2 0 2008-09-25 13:02:10.993
!MESSAGE Unable to satisfy dependency from com.oaklandsw.transform.feature.deps.rt.feature.group
2.7.3 to requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.equinox.executable.feature.group/[3.3.100.v20080606-7H-ELQEDdVv0SVkW65GwAA,3.3.100.v20080606-7H-ELQEDdVv0SVkW65GwAA].
!ENTRY org.eclipse.equinox.p2.director 4 0 2008-09-25 13:02:11.156
!MESSAGE Problems resolving provisioning plan.
!SUBENTRY 1 org.eclipse.equinox.p2.director 2 0 2008-09-25 13:02:11.156
!MESSAGE Unable to satisfy dependency from com.oaklandsw.transform.feature.deps.rt.feature.group
2.7.3 to requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.equinox.executable.feature.group/[3.3.100.v20080606-7H-ELQEDdVv0SVkW65GwAA,3.3.100.v20080606-7H-ELQEDdVv0SVkW65GwAA].
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-09-25 13:02:11.157
!MESSAGE No solution found because the problem in /tmp/p2Encoding53674.opb
is unsatisfiable.
!ENTRY org.eclipse.equinox.p2.director 4 1 2008-09-25 13:02:11.670
!MESSAGE Cannot complete the install because some dependencies are not
satisfiable
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-09-25 13:02:11.670
!MESSAGE Unsatisfied dependency: [com.oaklandsw.transform.feature.deps.rt.feature.group
2.7.3] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.equinox.executable.feature.group/[3.3.100.v20080606-7H-ELQEDdVv0SVkW65GwAA,3.3.100.v20080606-7H-ELQEDdVv0SVkW65GwAA]
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-09-25 13:02:11.671
!MESSAGE Unsatisfied dependency: [com.oaklandsw.transform.feature.product7.feature.group
2.7.3] requiredCapability: org.eclipse.equinox.p2.iu/com.oaklandsw.transform.feature.deps.gui.feature.group/[2.7.3,2.7.3]
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-09-25 13:02:11.671
!MESSAGE Unsatisfied dependency: [com.oaklandsw.transform.feature.deps.gui.feature.group
2.7.3] requiredCapability: org.eclipse.equinox.p2.iu/com.oaklandsw.transform.feature.deps.rt.feature.group/[2.7.3,2.7.3]
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-09-25 13:02:11.671
!MESSAGE Unsatisfied dependency: [com.oaklandsw.transform.product7 2.7.3]
requiredCapability: org.eclipse.equinox.p2.iu/com.oaklandsw.transform.feature.product7.feature.group/[2.7.3,2.7.3]
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2008-09-25 13:02:11.673
!MESSAGE Unsatisfied dependency: [com.oaklandsw.transform.feature.deps.rt.feature.group
2.7.3] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.equinox.executable.feature.group/[3.3.100.v20080606-7H-ELQEDdVv0SVkW65GwAA,3.3.100.v20080606-7H-ELQEDdVv0SVkW65GwAA]
Pascal Rapicault wrote:
This problem is the topic of bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=241430
The current workaround is to remove/rename the two p2 files in the .settings
folder of the install where you are running the director from.
Let us know if this helps.
Francis
Upton ---25/09/2008 03:00:14 PM---I have been happily running p2 director
to do an installation as part of my build process for some
I have been happily running p2 director to do an installation as part of
my build process for some time now, and it normally completes in a few
seconds. It does not actually produce the correct result, but that's
the subject of another story.
My problem is that yesterday, my build just hung and then timed out when
running p2 director. It did this consistently, and I did not change
anything. After some debugging with kill -3 and wireshark, I saw
that
it was trying to download files from downloads.eclipse.org. And of
course yesterday was 3.4.1 so that explained the huge delay.
As my youngest daughter (who is 2) says when confronted with certain
foods: "I don't like that".
Is there anyway to prevent it from checking remote sites when doing my
build? My repository (archive and content) is entirely local and
the
installation of Eclipse I'm pointed to in my build is also local.
Thanks,
Francis
--
You have brains in your head.
You have feet in your shoes.
- Dr Seuss, Oh the Places You'll Go
Francis Upton IV
francis@xxxxxxxxxxxxxxxx
Tel 510 835 3123
Fax 510 779 5226
Cell 510 432 1589
Skype francisupton
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
--
You have brains in your head.
You have feet in your shoes.
- Dr Seuss, Oh the Places You'll Go
Francis Upton IV
francis@xxxxxxxxxxxxxxxx
Tel 510 835 3123
Fax 510 779 5226
Cell 510 432 1589
Skype francisupton
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev