I agree that we need to specify what we are compatible with – I just noticed that, at the moment, there is nothing on the website or wiki about this.
I would strongly push for 3.x compatibility (3.7 is ok with me). At our site, although (most) of the developers use 4.2.2 as their development IDE, our target platform is 3.7. This is probably fairly common – the jump from 3.x to 4.x is a big one, and many large applications are still based on 3.x. If nebula requires 4.x, then we can’t use it. The other compatibility issue is Java level. We are ok is Java 7 is required, though most Eclipse projects seem to only need Java 6 (or even Java 5). Does the Eclipse Foundation have any rules or guidelines on this? Thanks Matthew From: [email protected] [mailto:[email protected]] On Behalf Of Wim Jongman Sent: 15 June 2013 19:54 To: Nebula Dev Cc: Nebula Dev Subject: Re: [nebula-dev] Incubator build is failing because or RAP repo problem I'm fine with making that an official rule. I think we even need to stay compatible with 3.x for a while. I'm happy building against indigo. In practice it will not make much difference since the SWT and JFace api is pretty solid. Met vriendelijke groet, Wim On 15 jun. 2013, at 17:13, Tom Schindl <[email protected]<mailto:[email protected]>> wrote: Shouldn't it point to the latest stuff we are compatible with? We used to be release-1 IIRC although this was never written down. Tom
_______________________________________________ nebula-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/nebula-dev
