http://tacos.sourceforge.net/tacos4.1/tacos-core/quick-start/resolvers.html
implements that for T4.1
but the maven instructions mentioned there are what you're after... it
boils down to redefining the
resources location like this:
<build>
...
<resources>
<resource>
<directory>src/main/java</directory>
<excludes>
<exclude>**/*.java</exclude>
</excludes>
</resource>
...
</resources>
...
</build>
On Fri, Dec 5, 2008 at 1:05 PM, Maximilian Weißböck
<[EMAIL PROTECTED]> 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]
>
>
--
Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr
Tapestry / Tacos developer
Open Source / JEE Consulting
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
