> > BTW a question for the core XDoclet guys: > > Are you planning a migration path/program/tool etc. for migrating projects > based on the XDoclet 1.2 standard stuff/templates to XDoclet2? >
We haven't planned it yet, but we will. XDoclet 2 will be incompatible with XDoclet 1.x in the following places: 1) On the @tag level, since we plan to change (simplify) tags considerably. Less tags. 2) On the Ant level, since the invocation mechanism will be slightly different. It shouldn't be too hard to write a migration tool to solve (1). XDoclet 2 will have the notion of deprecated tags, and we might still support older tags. If we choose not to support older tags, we could write a translator that translates all the @tags in the source code. This shouldn't be too hard, using xjavadoc's conde mutation functionality. However, if we outsource plugins, then migration from, say, old @jboss tags to new ones will be out of our control. However, we might implement a generic migration tool that can be configured/extended to migrate a particular set of @tags. We'll probably still keep the old (custom written) template engine available in XDoclet 2. This means all the legacy code (whether from XDoclet 1.2 or your own) will still work. On the Ant level I don't think it would be worthwhile to write a migration tool, but rather a migration *doc*. There won't be that much to migrate from the Ant scripts. Aslak ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
