| Summary: | [publisher] Provide a mechanism to publish an existing JRE | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Andrew Niefer <aniefer> |
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | caniszczyk, curtis.windatt.public, darin.eclipse, Ed.Merks, pascal, simon_kaegi |
| Version: | 3.4 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| See Also: |
https://git.eclipse.org/r/117968 https://git.eclipse.org/c/equinox/rt.equinox.p2.git/commit/?id=e92e31abc7ed83117b9cd25b4026531b4ae47064 |
||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 218623 | ||
|
Description
Andrew Niefer
Note that the .product file entry looks something like: <vm> <windows>org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/IBM_1.5.0-20070201</windows> </vm> This by itself is not sufficient information to bundle the jre, we would require an actual path on disk. True, but if you have access to JavRuntime, something like JavaRuntime.getVMInstall(...) should give you access to the path. Until progress are made on the p2 front for handling JREs, I would not go crazy on this and simply generate the "a.jre" IU. If the .product file contains a EE (not just a named JRE), this should work nicely. Thinking about it... I'm not sure why we even offer people to select a named JRE in various places in PDE. We should be forcing (I mean suggesting better habits) people to choose an EE. New Gerrit change created: https://git.eclipse.org/r/117968 Gerrit change https://git.eclipse.org/r/117968 was merged to [master]. Commit: http://git.eclipse.org/c/equinox/rt.equinox.p2.git/commit/?id=e92e31abc7ed83117b9cd25b4026531b4ae47064 I don't believe there is anything actionable remaining here. With the possibility to redistribute JREs, there is other work being done in this area. |