Community
Participate
Working Groups
In Bug 325531, comment 5 Stefan correctly indicates that @Basic should not be added when unnecessary. The fix for Bug 325531 only addressed the import problem and not the unnecessary @Basic.
Created attachment 195221 [details] patch
The bug is not a big deal, but also is the fix. This one stayed open for a long time and now it has a fix. The bug does not need workaround because it's about creating a new basic attribute without the redundant @Basic annotation. The fix is trivial - just a string parameter changed from "@Basic" to "". I've reviewed it and I think it's ok. I've tested it manually. The risk is low.
I don't think I can make a case for this as an important bug fix for RC1 since it is more of an issue of preference, although I would suspect most would prefer to not insert the basic annotation into the code. I will leave this targeted to 3.1 for now. If someone would like to argue for inclusion into RC1, please do so here so it can be documented for PMC review.
(In reply to comment #3) Just one note: > ... although I would suspect most would > prefer to not insert the basic annotation into the code That's exactly what the fix is about. With it, when a new attribute is created the @Basic annotation is NOT being inserted into the code ...
The 3.2 target now represents the Juno release.
Retargeting this bug to the Kepler realease (3.3).
The Basic annotation is removed with the following git commit: http://git.eclipse.org/c/dali/webtools.dali.git/commit/?id=387e840daab9cab568e723283ceda994db8c9b58 The change still needs to be released.
Changes are released...