[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[tm-dev] FW: [cross-project-issues-dev] Strategy for ensuring 1.5 API compatibility on OS X?
- From: "Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
- Date: Thu, 29 Sep 2011 18:46:33 +0000
- Accept-language: en-US
- Delivered-to: email@example.com
- Thread-index: AQHMfkm/3cGO8EXV6EuJLw7g0qG6YZVkDvoAgAD7zID//6i0sA==
- Thread-topic: [cross-project-issues-dev] Strategy for ensuring 1.5 API compatibility on OS X?
FYI - instructions for how to ensure you don't call Java 1.6 API's in a project that's supposed to be 1.5 or 1.4 only ... without having to install the old JRE's.
Martin Oberhuber, SMTS / Product Architect - Development Tools, Wind River
direct +43.662.457915.85 fax +43.662.457915.6
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Miles Parker
Sent: Thursday, September 29, 2011 6:58 PM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Strategy for ensuring 1.5 API compatibility on OS X?
Thanks Pascal, that's perfect. Now I get an error when I try to do something that's only supported in 1.6. For other people wanting to set this up you have to:
1. Setup the API analysis builder and natures for your projects as well as project specific settings naturally -- which seems to be evolving into a best practice anyway.
2. Under Pascal's link, I have "Invalid references to System Libraries".
3. The first time you turn this on you'll need to configure the system libraries.
a) Update site: The Eclipse Project Updates - http://download.eclipse.org/eclipse/updates/3.7
b) Add PDE/API Tools Environment Descriptions
On Sep 28, 2011, at 6:57 PM, Pascal Rapicault wrote:
> Assuming that you are doing this in the context of PDE projects, the PDE API tools provide such a feature.
> See under Preferences > Plugin dev > API Errors / Warning > API Use >
> General > invalid references to execution env
> Otherwise Maven has some plugins of its own like animal sniffer
> On 2011-09-28, at 9:47 PM, Miles Parker wrote:
>> 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: http://stackoverflow.com/questions/3762854/detecting-non-1-5-java-code-while-developing-on-a-mac-under-1-6) 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.
>> cross-project-issues-dev mailing list
> cross-project-issues-dev mailing list
cross-project-issues-dev mailing list