| Summary: | need ibm 142 JDK installed on build.eclipse.org | ||
|---|---|---|---|
| Product: | Community | Reporter: | Paul Webster <pwebster> |
| Component: | Cross-Project | Assignee: | Cross-Project issues <cross-project.inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | thatnitind |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 322416 | ||
|
Description
Paul Webster
Just logging the history: it was an empty folder when I came across it, which I then removed and recreated as a symlink to an already-installed JRE. :/opt/public/common/j2sdk1.4.2_19 seems to be a full SDK. Can you use that? does it make sense to symlink from ibm-java2-142 to j2sdk1.4.2_19? AFAIK the Sun/Oracle JDK will work for us. But my scripts expect a JDK at ibm-java2-142 (AFAIK for PDE build it's mostly for the jars). PW I've reduced the severity (I have a workaround). But I can see that having this directory missing can cause existing builds (including any respins of older builds) to fail. PW I've added the symlink. |