On Tue, 2003-07-08 at 01:25, Aslak Helles�y wrote: > Andrew Stevens wrote: > > >On Mon, 2003-07-07 at 11:49, Eric Jain wrote: > > > > > >>Fact is, I can no longer use XDoclet without having Javadoc dump tons of > >>warnings on me. Which I wouldn't care about much, except that there > >>often are important warnings which are now hard to find. > >> > >>Any suggestions what to do? > >> > >> > > > >Use the dotted form of the tags and specify the appropriate parameters > >to your javadoc command or ant task so that it doesn't complain about > >them. That's why we added support for the dotted form in the first > >place; the javadoc parameter uses colons as its separator. > > > > > > > The issue is something else Andrew. See other posts in the same thread.
Didn't see them till after I'd hit 'send', but by then it was too late. I had another thought as to why hyphens are now a problem - could it be related to the metadata JSR? More specifically, are hyphens valid characters in java identifiers? I never use them myself, but can't remember whether the Java Language Spec actually prohibits them (and don't have it to hand at the moment); if so, and the metadata JSR is planning to use @tags for attributes, and they're going to force metadata attribute @tags to be valid identifiers (same as class/package/variable names), then perhaps javadoc is enforcing it now so that people get used to it? Of course, that's a lot of 'if's, and could be absolutely nothing to do with it. Does anyone know what's going on with the metadata JSR? Is it in public review yet, or is it still only the expert group that know what's planned? Andrew. ------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
