X

Geertjan's Blog

  • August 28, 2010

NetBeans RCP Pic Of The Month

Geertjan Wielenga
Product Manager

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.

Join the discussion

Comments ( 6 )
  • johann sorel Sunday, August 29, 2010

    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.


  • Geertjan Sunday, August 29, 2010

    The above annotation creates the usual layer.xml at compile time.


  • johann sorel Sunday, August 29, 2010

    "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.


  • Edvin Syse Sunday, August 29, 2010

    Nice! In what release will this be available?


  • Aljoscha Rittner Monday, August 30, 2010

    Hi!

    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 )

    br, josh.


  • Jesse Glick Thursday, September 16, 2010

    #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).


Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.