Community
Participate
Working Groups
This is related to bug 107783. I need to restrict access to System Libraries using the pattern: **/*[@since="1.5"] **/*#*[@since="1.5"] (where # is a new segment separator (borrowed from javadoc syntax) between a class one of its members (e.g. a method)) I can currently take advantage of 1.5 language features while targeting a lesser, 1.4-level JRE at runtime. However, to leverage things like generics in Collections, I need to compile against 1.5 System Libraries. This work great (Thanks Olivier!), but currently requires extreme care. To guarantee the goal of running on a 1.4 JRE *and* class library, I need to avoid accessing stuff like: - Class: java.lang.StringBuilder - Method: java.lang.Integer#valueOf(int) To phrase the problem in a completely different way, I would like to be able to compile against one set of Libraries, and then I need to verify that I can also *LINK* against a different set of libraries (which I don't need to be able to compile against). That is, I am binary, but *not* source, -compatible with the second set of libraries.
> That is, I am binary, but *not* source, -compatible with the > second set of libraries. Let me restate: I *believe* that I am binary-compatible with some other set of libraries, and I would like JDT to enforce this during build.
Randy, Api Tools can help you with this. Check the next integration build.
*** Bug 336237 has been marked as a duplicate of this bug. ***
