On Thursday 23 October 2003 14:02, [EMAIL PROTECTED] wrote: > ok, ok, > > I can do the following: > > 1. while editing, you can get an context sensitiv help. eg. type @, and > you will get all available tags.
cool > 2. when save and compile a sourcefile (eg. ctrl. s) the tags are checked recool > 3. after the checking has succeeded, generate the .xinfo etc. files. It > should be possible to switch this feature off. super cool > 4. when the .xinfo files etc. differ from meta tags, there should be a > merge option. uber cool > 5. and of course, there should be an consistency check. > > I don't like to take marven to do all those tasks, because I'm not > familar with and maven seems to be a bit "havy wighted". If you don't > mind, I'll take xdoclet. as you want. > by the way - because I'm very new to this forum: I don't know, whether > we can discuss eclipse related things here. If not, give me a hint! I'll be happy to discuss with you on eclipse stuff, but probably not here... or maybe we should prepend email subject with [ECLIPSE] to allow filtering? One last thing that could be really nice would be, "block.xml" <compenent> element consistency check. This is really 'Merlin related' but could be usefull (but I agree this is not really to setup block association with project). For exemple : <component name="IMServer" class="net.java.dev.openim.IMServerImpl" activatio n="startup"/> should be coherent with @[EMAIL PROTECTED] declarations. Cheers --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
