Sorry, don't know what happened there. When I typed "Ba", Outlook just sent my email! I'll bet that doesn't happen in Thunderbird! Anyway, what I was trying to type was:
Basically, it'd be an abstraction of the JDK5 annotations API. So, if you're not using JDK5 or you don't want to have to modify the source code, you could still provide metadata information for your classes. I can imagine having "providers" for JDK5 annotations, Jakarta Commons Attributes, some XML file format, maybe Groovy, etc. I don't know about using it like XDoclet, but you'd be able to use it the same way you would JDK5 annotations. -----Original Message----- From: James Carman [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 08, 2006 1:07 PM To: 'Jakarta Commons Developers List' Subject: RE: Commons Metadata? Ba -----Original Message----- From: Thomas Dudziak [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 08, 2006 1:05 PM To: Jakarta Commons Developers List Subject: Re: Commons Metadata? On 3/8/06, James Carman <[EMAIL PROTECTED]> wrote: > If I write it, I can have the Trails project use it probably (I'm a > committer). Do we just have to have clients who are interested in the > project or do we also need more than one developer to work on it? If it can be used like XDoclet, and also at runtime, then I would guess that there are potentially a lot of users. And if you need developers, I could help. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
