Ralf and I talked a bit. Summary, you need to use the p2 publisher to
get all the new infrastructure (including things like the p2.inf
support).
*** Note to all, if you are contributing to Galileo you should be
using Galileo tooling to make your contribution.
Jeff
Ralf Sternberg wrote:
Hi Thomas,
thanks for your analysis. Do you have a hint how those requirements can
be added to the metadata? I tried different combinations of command line
arguments, but with none of them "A.PDE" ended up in the content.xml. My
current method of creating metadata is the following:
java -Xmx512m -cp $ECLIPSE_LAUNCHER org.eclipse.core.launcher.Main \
-application
org.eclipse.equinox.p2.metadata.generator.EclipseGenerator \
-updateSite "$inputDir" \
-metadataRepository "file://$inputDir" \
-metadataRepositoryName "RAP Update Site" \
-artifactRepository "file://$inputDir" \
-artifactRepositoryName "RAP Artifacts" \
-reusePack200Files \
-noDefaultIUs
Java is 1.5.0_19, $ECLIPSE_LAUNCHER points to
org.eclipse.equinox.launcher_1.0.200.v20090513.jar from an Eclipse
3.5RC1 installation.
Thanks, Ralf
Thomas Hallgren wrote:
Hi Ralf,
A search for "A.PDE" in the content.xml of
http://download.eclipse.org/rt/rap/1.2/runtime-update/content.jar gives no hits.
So for some reason, the requirement is not added properly to your feature.
Regards,
Thomas Hallgren
Ralf Sternberg wrote:
Hi,
including a p2.inf file in the feature as suggested does not prevent the
IDE to install this feature. I created this RAP runtime repository for
testing:
http://download.eclipse.org/rt/rap/1.2/runtime-update/
The RAP runtime *can* be installed into 3.5RC2 without any warning, and
after restarting the IDE is, of course, inoperable.
Any ideas?
Ralf
Thomas Hallgren wrote:
Hi Ralf,
I think that should do it. Give it a try.
Regards,
Thomas Hallgren
Ralf Sternberg wrote:
Hi,
We'd like to provide an SDK feature for RAP as suggested in bug 275753.
If I understand Thomas Hallgren's comment on bug 276000 correctly, we
can now go ahead and include a feature with a requirement to
"A.PDE.Target.provisioning":
https://bugs.eclipse.org/bugs/show_bug.cgi?id=276000#c19
To do so, is it sufficient to include a file named "p2.inf" in the
feature with content like this:
---
requires.1.namespace=A.PDE.Target.provisioning
requires.1.name=<Anything>
requires.1.range=[0.0.0,0.0.0]
---
or are there any more steps needed?
Thanks,
Ralf
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
------------------------------------------------------------------------
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
|