Re-hi all Here's another pair of questions for to clear my doubts.
1. In Tiles 2.0.1 there were two source distributions, one for tiles-core and one for tiles-api. In the trunk I configured the assembly module so that it creates only one distribution with all sources. Should we maintain the old "one-package-per-module" structure, or "one-package-catch-all"? (Like Shale does). 2. Should we include the test webapp in source and binary distributions? Struts 1 uses a different approach: it creates several distributions (library, all, etc.) to allow the user to choose what to download, but since Tiles is pretty "tiny" (compared to Struts, obviously) I think that only one binary that contains everything should be ok. Thoughts? Antonio
