Hi, I would like to go the further possible for the check on if a class must be regenerated or not and avoid the "touch". (This 50% for myself, 50% for marc/david vision on "deployment for the dummies" that they talked about on jboss dev) So I propose this: - Add a parameter -Dxdoclet.force=true to not look at timestamp at all and force a regeneration : This would be used by xdoclet developers or "when you don't know" (finally timespamp check is very weak IMHO) - Timestamp checking on the class to regenerate but also its hierarchy of super classes and interfaces up to java.lang.Object - Timestamp checking on merge files (.j or .xml) - regeneration of DD files only if one of previous checks returned true (as Ara proposed) - Eventually but it is not a top prioroity : @xdoclet-generated / @xdoclet-version usage when upgrading xdoclet to a newer version (xdoclet.force should be enough) or when developing xdoclet (xdoclet.force is also more easy)
Do you agree on this this? Vincent. _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
