Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] Strategy for ensuring 1.5 API compatibility on OS X?

Hi all,

I've been running into the problem of using Java 1.6 API; namely String.isEmpty and I imagine it's driving my Windows compatriots nuts. It's a pain in the neck because OSX doesn't provide a 1.5 JDK to build against. There are a number of byzantine work-arounds (e.g. see: which seem to me to be more trouble then they are worth. I'm inclined to punt this issue to the build server as it should be protecting against this sort of thing anyway. But I'm wondering if there is anyway to handle this with the API tools or what other Mac committer's practices are.



Back to the top