George, I don't use Maven for Tapestry projects, but I think the answer is
here:
http://www.ninthavenue.com.au/how-to-change-mavens-default-resource-folder .


On 13 February 2014 14:23, George Christman <gchrist...@cardaddy.com> wrote:

> Geoff, I just tried putting a TML into java along side it's java
> counterpart, however it appears as if Tap doesn't know about it. How do you
> tell Tap about it? Also, I'm using Jetty if that matters.
>
>
> On Wed, Feb 12, 2014 at 7:02 PM, Geoff Callender <
> geoff.callender.jumpst...@gmail.com> wrote:
>
> > The only reason I can think of to separate a page or component's source
> > definition files is because something is forcing you to. Why fragment
> > something if you don't have to? I'm not just talking about a page or
> > component's JAVA and TML, I'm including its PROPERTIES and JS. It may
> even
> > have a CSS or LESS that belongs solely to it.
> >
> > IMHO, Maven screwed up our thinking by splitting src/main/ into java/ and
> > resources/ . It makes people hell-bent on separating non-JAVA from JAVA.
> A
> > better split might have been into definition/ and resources/ , where
> > resources/ is for shared stuff.
> >
> >
> > On 13 February 2014 08:56, Chris Poulsen <mailingl...@nesluop.dk> wrote:
> >
> > > Hi,
> > >
> > > The documentation also has a say on that one:
> > >
> > >
> > >
> >
> http://tapestry.apache.org/component-templates.html#ComponentTemplates-TemplateLocation
> > >
> > > --
> > > Chris
> > >
> > >
> > > On Wed, Feb 12, 2014 at 5:28 PM, Thiago H de Paula Figueiredo <
> > > thiag...@gmail.com> wrote:
> > >
> > > > On Wed, 12 Feb 2014 13:38:00 -0200, George Christman <
> > > > gchrist...@cardaddy.com> wrote:
> > > >
> > > >  Hi Guys, I'm using 5.4 and my colleague brought to my attention in
> > > Igor's
> > > >> Tapestry5 book he noticed an example where the tml templates were
> > being
> > > >> packaged together with the java classes. Anyhow I took it a step
> > further
> > > >> and looked into Geoff's jumpstart package structure and noticed he
> was
> > > >> doing the same thing. The question is where is the best place to put
> > the
> > > >> templates and/or is there a major downside to placing the templates
> in
> > > >> the java package?
> > > >>
> > > >
> > > > Your question is all about where to put sources. It's up to you.
> > > > For Tapestry itself, all it matters is that the templates go into the
> > > > webapp root or classpath; in both cases, in the right folder. I think
> > the
> > > > recommended way is classpath.
> > > >
> > > > My choice? src/main/resources, which later goes to the classpath, no
> > > > doubts about it.
> > > >
> > > > --
> > > > Thiago H. de Paula Figueiredo
> > > > Tapestry, Java and Hibernate consultant and developer
> > > > http://machina.com.br
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > > > For additional commands, e-mail: users-h...@tapestry.apache.org
> > > >
> > > >
> > >
> >
>
>
>
> --
> George Christman
> www.CarDaddy.com
> P.O. Box 735
> Johnstown, New York
>

Reply via email to