Eclipse Community Forums: Java Development Tools (JDT) » @Nullable field annotations when backporting to Eclipse 3.8

Help

Home

Home » Language IDEs » Java Development Tools (JDT) » @Nullable field annotations when backporting to Eclipse 3.8

Show: Today's Messages :: Show Polls :: Message Navigator

@Nullable field annotations when backporting to Eclipse 3.8 [message #1266294]

Fri, 07 March 2014 08:34

Felix Dorner

Messages: 295
Registered: March 2012

Senior Member

Hi,

I want to backport the Eclipse OCL development branch to Eclipse 3.8. A
small problem I face is that the jdt @Nullable annotations are not (yet)
allowed on fields there.

To fix that I added the kepler/luna version of
org.eclipse.jdt.annotation to the target platform... Is this a good
solution? Better ones? I don't want to comment out gazillions of
annotations.

Thanks,
Felix

Report message to a moderator

Re: @Nullable field annotations when backporting to Eclipse 3.8 [message #1266786 is a reply to message #1266294]

Sat, 08 March 2014 00:11

Stephan Herrmann

Messages: 1853
Registered: July 2009

Senior Member

What exactly is the goal of this backport? To be runtime-compatible with Eclipse 3.8?
For that matter null annotations don't make any difference, they are needed only at compile time.
So, if you add org.eclipse.jdt.annotation_1.1.0 to the target platform *and* if you use a kepler compiler then you should be safe. If you use the juno compiler against the newer annotations, nothing will break either, you will only get different nullness warnings / errors.

HTH,
Stephan

Report message to a moderator

Previous Topic:	(feature proposal) Arguments Panel
Next Topic:	workspace on network drive

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 18:13:33 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter