[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [p2-dev] Problem using p2 to install plugin
|
I guess my first email was a bit too long winded, because
at the bottom I mentioned that the error message on install doesn't change
substantially (only the timestamp changes) after having used the export
wizard to publish the feature, which generated the artifacts.xml
and content.xml files. I also tried using:
java -jar C:/Program\
Files/eclipse_installs/eclipse-SDK-3.5-win32/eclipse/plugins/org.eclipse.equinox.launcher_1.0.200.v20090520.jar
-application org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher
-metadataRepository file:/C:/eclipse_metadata/repository -artifactRepository
file:/C:/eclipse_metadata/repository -source C:/eclipse_extension/
-publishArtifacts
eclipse_metadata is an empty directory before running this
command, and eclipse_extension is where I've put a copy of my already
built features & plugins directories. It also contains a
.eclipseextension file, which I've tried removing, just in case that was causing
problems.
I haven't tried creating an Ant task, because it would
be more difficult to integrate into our build system than the above
command, but unless one of you can tell me why that might behave differently, I
wouldn't expect any different results.
If anyone thinks seeing either of my generated XML
files would help find the problem, I can send them along if
necessary.
Thanks!
Kristina
You can also create an update site project. When you build it you will find
the artifact.xml and content.xml have been created in the same location as the
site.xml. Just do a file export on this update project to some location. The
<feature>.feature.group is the name of the IU and it will be in the
content.xml. Paul's suggestion of using ant is probably better but the IDE will
build a site that will install. It is my preference for quick and dirty. It is
best to delete the features, plugins, content.xml, and artifact.xml files on
this update project before rebuilding it.
---07/23/2009 02:57:07 PM---Hi Kristina,
From: |
<Warren_Paul@xxxxxxx> |
To: |
<p2-dev@xxxxxxxxxxx> |
Date: |
07/23/2009 02:57 PM |
Subject: |
RE: [p2-dev] Problem using p2 to install
plugin |
Hi Kristina,I am not a p2 export or
committer but I have been playing with p2 for quite a while.I think you are on the right
lines. <feature>.feature.group is p2 metadata. You don't get this building
your feature in eclipse IDE. As you have discovered you need to export your
feature with p2 metadata or, preferably I would think - at least for releng
anyways, use antrunner and pde build's build.xml to build the feature adding the
following to your build.properties file:-generate.p2.metadata=true
p2.metadata.repo =
file:/path/to/your/destination
p2.artifact.repo =
file:/path/to/your/destination
p2.flavor =
tooling
p2.publish.artifacts=trueThis should build you feature and publish a p2 repo to
file:/path/to/your/destinationYou should then be able to install the feature through
'Install New Software' by adding file:/path/to/your/destination as a new
location.HTH_Paul
From:
p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Kristina Taylor
Sent: 23 July 2009 20:08
To:
p2-dev@xxxxxxxxxxx
Subject: [p2-dev] Problem using p2 to install plugin
I know that the "-dev" mailing lists are
not meant for user problems, but there doesn't seem to be a p2-specific user
newsgroup. Please feel free to tell me where to go, if I'm in the wrong place.
:) I have a feature that was originally developed
for Eclipse 3.2 and has been working with minor bug fixes ever since. We want to
support Eclipse 3.5, and the only ways I can manage to get it enabled are
somewhat hacky. The following install procedures
both work smoothly: 1) Add
-Dorg.eclipse.equinox.p2.reconciler.dropins.directory=<install directory>
2) Enable the "Classic Update" capability in
preferences, and add an extension location that points to the same <install
directory> as above. Neither of these are very
good options for us to tell our customers to use. Besides, we'd like to keep up
with the times and make our feature/plugins "p2 enabled". Using the new "Install New Software" in Eclipse 3.5, adding the
location above as a site, and choosing to install our feature, I get the
following error message: "Cannot complete the install because one or more
required items could not be found. Missing
requirement: 1248373809037 0.0.0.1248373809037 requires '<feature
id>.feature.group [4.10.0]' but it could not be found" (where <feature
id> is the symbolic name of my feature, and 4.10.0 is the version # for
everything involved). Now, there's nothing named
"<feature id>.feature.group" in any of my Manifest.mf or feature.xml
files, but from 2 days of web searches and trying various things, this id
appears to be part of the metadata that p2 generates when there are no
pre-generated content.xml or artifacts.xml files in the install location. The
thing is, I get basically the same message after using the export wizard on my
feature, generating the content.xml and artifacts.xml files, when trying to
install from the exported location. The number at the beginning of that error
message appears to be the timestamp from the time I attempted the install, since
it changes each time I try. However, that number is never the same as the value
in p2.timestamp in the generated content.xml file. I tried using the
FeaturesAndBundlesPublisher from the command line, and unsuprisingly, that
didn't seem to really make any difference in the content of the .xml
files.All of my plugins and plugin fragments are at
the same revision as my feature (4.10.0). My feature "includes" 3 plugins, one
of which depends on the other (the 3rd is a help page), and 2 plugin fragments
for localization. I've tried removing the plugin fragments, in case those were
the nameless thing causing the failed dependency, but that made no difference.
How can I figure out what it is that is causing the failed dependency? The error
shows up in the log 4 times, which seems like once for the feature, and once for
each of the plugins, but that's just speculation on my part. If there's no easy
answer, I'm willing to step through the installer code to try to figure this
out, but I don't know where to start. Which project should I be checking out of
CVS? I couldn't find anything labelled org.eclipse.equinox.p2, but I might be
going blind. Thanks,Kristina Taylor_______________________________________________
p2-dev
mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
*** eSafe scanned this email for malicious content ***
*** IMPORTANT: Do not open attachments from unrecognized senders ***
