A wise old hermit known only as Ara Abrahamian <[EMAIL PROTECTED]> once said:
> <ejbdoclet ejbClassNameSuffix="Bean,Ejb,EJB,Entity"/> > > <To Andrew> > Andrew, are you interested in implementing it? I have some CVS access > problems atm. Done, as you've probably noticed. > Also when will we release 1.1.2? I think we can fix it for > next week. > </To Andrew> What is/isn't on the list for 1.1.2, then? 1. Consolidate i18n messages. 2. Translations for at least one other language. (saves effort if 1's done first, though) 3. Bluestone support. 4. Switch to using xjavadoc. plus as many of the SF tracker items as we can manage, in particular the following FRs? 5. #516874 ejb:relationship -> ejb:relation 6. #514224 DAO changes. 7. #516425 field/constructor level @todo's 8. #512180 make @ejb:select a method-level tag 9. #492015 fine-grained dataobjects I might also try and tinker with the build.xml to do something about #503810 "build problems in dist zip". 1 & 2 would be nice for 1.1.2 (since it's in there, we may as well get it fully working). I should have 3 ready; 6, maybe or maybe not, depending on when you had in mind to do the release. 4 should probably wait till at least 1.2, though since the 1.4.0 JDK's been released now, we ought to migrate to xjavadoc ASAP (or include some other workaround for the javadoc API changes). 8 could wait, but doesn't sound like it would be a big change. Oh yes, and as usual 10. Clear up those javadoc warnings that are being generated during the build. 11. Make sure the docs are complete and up to date (e.g. I don't see @ejb:relationship in ejbdoclet.html) Can anyone think of anything else? Andrew. _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
