We had a model in our source code with annotations on it to declare a persistency options, something like:
/** List of all bets */
@OneToMany(fetch = FetchType.LAZY, cascade = { CascadeType.ALL }, mappedBy = "event")
private final List
Since I have another nice feature of Eclipse enabled all the time, it's Save Actions, every time I save file some actions are performed, such as Organize Imports, Formatting, Sort members.
So at the end I haven't really noticed that I've destroyed part of the mapping declaration, since Sort Members is somehow not working very well with annotations (I guess it sort annotations separately from the element they attached to :) ).
So, be aware about evil features.
Update:
Our mapping testcases found the problem and CruiseControl reported about it 1 minute after the commit. :) +1 to Unit testing and Continuous Integration
1 comment:
The other evil eclipse feature .... "Show Selected Element Only"
Post a Comment