Uhm... I use the resource folder since the beginning of dabbling around with Tap5 and never had any issues. In fact it's the first thing I do when creating a new app via the archetype to create the packages under the resource directory and moving Index.tml there.
As I am talking about archetypes... The Tapestry quickstart vanished from the list I get with mvn archetype:generate lately, probably since the update to maven 2.0.9. Any reason for this? Regards, Otho 2008/12/9 Christian Edward Gruber <[EMAIL PROTECTED]> > No problem. Turns out it works for pages too. I've moved my .tml files > into /src/main/resources (since I don't mind the split) without difficulty. > > Christian. > > > On 9-Dec-08, at 06:52 , Maximilian Weißböck wrote: > > Thanks Christian! Exactly what I was looking for! >> >> Max >> >> >> -----Ursprüngliche Nachricht----- >>> Von: Christian Edward Gruber [mailto:[EMAIL PROTECTED] >>> Gesendet: Freitag, 5. Dezember 2008 17:06 >>> An: Tapestry users >>> Betreff: Re: AW: Advantages of various .tml storage locations? >>> >>> It's not a fix, it's a design. Code goes in /src/main/java. Resources >>> go in /src/main/resources. It's part of having a place for >>> everything, and everything in its place. >>> >>> You could hack it by a custom execution of the resources plugin >>> pointing to your "alternative resources location" (ie, src/main/java) >>> but this isn't something that needs a solution - it's how the tool >>> works. >>> >>> Actually, i think you could set the resources location to src/main/ >>> java anyway... one sec... >>> >>> Yep. >>> >>> Use the <build><resources>...</resources></build> section of the pom >>> to point at resources in /src/main/java. eg: >>> >>> <resources> >>> <resource> >>> <targetPath>/</targetPath> >>> <filtering>true</filtering> >>> <directory>${basedir}/src/main/java</directory> >>> <includes> <include>**/*.tml</include> </includes> >>> </resource> >>> </resources> >>> This should pick up .tml files in /src/main/java. Not maven best >>> practice, but if it works for you, have fun. I still expect it will >>> only work for components, not pages. Howard? True? >>> >>> Christian. >>> >>> On 5-Dec-08, at 06:05 , Maximilian Weißböck wrote: >>> >>> I would much prefer solution number 1. as it keeps things >>>> on the same place that belong together. >>>> >>>> Sadly maven build does not work with this solution. >>>> Is there any maven guru how knows how to "fix" this? >>>> >>>> Thanks, Max >>>> >>>> -----Ursprüngliche Nachricht----- >>>>> Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von >>>>> James >>>>> Hillyerd >>>>> Gesendet: Donnerstag, 4. Dezember 2008 23:06 >>>>> An: Tapestry users >>>>> Betreff: Advantages of various .tml storage locations? >>>>> >>>>> What are the pros/cons of keeping page .tml in: >>>>> >>>>> 1. src/main/java >>>>> >>>>> vs >>>>> >>>>> 2. src/main/resources >>>>> >>>>> vs >>>>> >>>>> 3. src/main/webapp >>>>> >>>>> ? >>>>> >>>>> >>>>> I see JumpStart uses #1, and the tutorial uses #3. Seems like it >>>>> would >>>>> easier to use #1 or #2 so at least the components and pages .tml >>>>> are in >>>>> the >>>>> same directory tree. >>>>> >>>>> Thanks. >>>>> >>>>> -james >>>>> >>>>> -- >>>>> James A. Hillyerd <[EMAIL PROTECTED]> >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
