Can't you set up multiple resource folders, some filtered, some not?
On 7/2/07, Steven Coco <[EMAIL PROTECTED]> wrote:
Hi. Has there been discussion about the fact that Maven can filter resources, located in src/main/resources, and if templates are placed there, then Maven may munge expansions intended for Tapestry, or maybe also vice-versa? The tutorial says templates should be placed here. I have been using WEB-INF, mainly because application reloading during development is instant this way, but when they are in the resources directory, it doesn't pick up changes. And other than that there seems to be no difference. But I can easily see a problem with resource filtering. In light of this comment, what then is the fate for component templates? I think they currently are required to appear in src/main/resources, so there may be real problems. You can configure excludes in Maven's resource plugin; but that may not be a guaranteed solution: you may have properties bundles for components that do need to be filtered by Maven, and the task of configuring those excludes is not straightforward, and things may get too onerous to be practical. The potential for clashes should be a pretty big concern I'd think; since resource filtering is common, and once a project scales up with many pages and components, the odds of a Tapestry expansion matching a Maven one will be high. Any comments on this? Ciao! Steev Coco. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
