I did 'hg pull' on my hg clone of the NetBeans sources, then built via ant, ran it, and used the New Action wizard, with the above result.
Too much annotations kills annotations.I hope there is still a way to generate usual layer.xml from the wizard. ortherwise it will become horrible to maintain such code.
I think it's not a good idea.
The above annotation creates the usual layer.xml at compile time.
"at compile time" that's the problem.
In fact this is a knowned story, same thing happened with services META-INF <=> annotation, now it's Layer.xml <=> annotation .
That's just a personnal opinion but I prefer registering everything in a single file rather then search for @SomeAnnotationNameIDontKnow .
If at least the wizard could offer us the choice with a checkbox "generate with annotation".
annotations should be considered a bonus for thoses who wish them, not a default behavior. that's what I think.
Nice! In what release will this be available?
I would prefer a generated comment like:
<!-- generated action by org.module.demo.SomeAction (SomeAction:11)-->
I like the annotations and I like the old declarative way in the layer.xml. But currently it is impossible to create my own annontations in maven based platform projects (see http://netbeans.org/bugzilla/show_bug.cgi?id=184952 )
#184952 only pertains to running processors from inside the IDE's editor, mainly useful for getting live error messages. You can still write the annotations and have them processed by the Maven build (AFAIK).
Monday, October 22
9:00 - 9:45: Moscone West - Room 2014
Delivering Mobile Apps to the Field with Oracle JET (DEV6242)
Over the last
few days, I introduced and held an Oracle JET workshop in Oslo,
earlier in the same week in Amsterdam, the week before that...
Together with my colleague JB Brock I've spent the past week in
South Africa. Last year, with Andrejus Baranovskis from Oracle