Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » Java Development Tools (JDT) » @Nullable field annotations when backporting to Eclipse 3.8
@Nullable field annotations when backporting to Eclipse 3.8 [message #1266294] Fri, 07 March 2014 08:34 Go to next message
Felix Dorner is currently offline Felix DornerFriend
Messages: 284
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
Re: @Nullable field annotations when backporting to Eclipse 3.8 [message #1266786 is a reply to message #1266294] Sat, 08 March 2014 00:11 Go to previous message
Stephan Herrmann is currently offline Stephan HerrmannFriend
Messages: 1048
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


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


Current Time: Fri Dec 19 00:04:06 GMT 2014

Powered by FUDForum. Page generated in 0.02408 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software