Bugzilla – Full Text Bug Listing
| Summary: | org.json bundle does not specify JDT compiler compliance | ||
|---|---|---|---|
| Product: | [Tools] Orbit | Reporter: | Steffen Pingel <steffen.pingel> |
| Component: | bundles | Assignee: | Austin Riddle <austin.riddle> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Steffen Pingel
On a side not, the build.properties seems to be over inclusive and has several warnings. Hi Steffen, We just finished going through bug 327288 which may have to do with you are experiencing. How long ago did you check out? Are you on v1_0 or v1_0_0? Most of the bundles in orbit have binaries checked in because those binaries came from the product vendor/source directly. The reason the json bundle does not include binaries is because the json.org folks don't supply a binary form of their code. The stable release of orbit has binaries based on the source code that is checked in. (In reply to comment #0) > I have the v1_0 branch of the org.json bundle checked out in my workspace and > ran into a UnsupportedClassVersion error. Apparently the bundle does not > specify JDT compiler settings that correspond to the MANIFEST specifications. > Also, it only has source and no binaries which seems unusual for an Orbit > bundle. Closing due to inactivity and lack of reproducibility after bug 327288. Thanks. Looks like it's fixed now (I'm on the 1_0_0 branch). |