> > I think we should put samples and test > > in each module's folders: > > Optional > > Jboss > > Src > > Script > > Tests > > Samples <- > > > > This way if a guy comes up with JDO templates for Kodo vendor he can > > simply provide the whole stuff including samples in a single ready to > > commit zip file. > > > > Agree? > > Tests, sure, but I'm not convinced about the samples - it makes it harder > to demonstrate how we can have one set of source files producing a jar > that's deployable on a variety of app servers. Plus, either they've got > to come up with more samples or (more likely) they'll re-use the ones we > have with their tags instead, in which case is it really that much work to > merge them into a common set? > > Also, I though the samples were moving up to the same level as core & > optional, since they contain examples of both lots of tags?
Keep the giant samples in root. These samples are more focused on that module. Jboss samples in jboss module demonstrate all jboss tags and options. Samples in root demonstrate a complete multi-faceted project, including some jboss/multi-vendor stuff. Ara. _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
