On Fri, 06 Sep 2013 10:28:04 -0300, Barry Books <trs...@gmail.com> wrote:
Thanks, I guess I was not clear what I meant by works. RunJettyRun knows
about Maven
It says so, but I cannot really see what it does (besides configuring
src/main/webapp as the webapp context root automatically).
so I can just right click on my project select "Run Jetty" and it 'just
works'. No messing with classpaths, creating a run configuration
etc.
With Maven you still need to create a run configuration. The classpath
configuration part (webapp classpath tab), as far as I know, it's just
taken from the project configuration in Eclipse as is.
If you can do that with Eclipse/Gradle I'd like to know how because
when I try it Tapestry does not start and if I go to the website I get
this:
Directory: /sandbox/META-INF/
<http://localhost:8080/sandbox/META-INF/>102
bytes Sep 5, 2013 7:13:00 AMWEB-INF/
<http://localhost:8080/sandbox/WEB-INF/>136
bytes Sep 5, 2013 7:13:19 AM
That's because you probably didn't set the webapp context root folder
and/or didn't configure the classpath.
It did occur to me that the test case runner is now its own module so I
tried this:
*import* org.apache.tapestry5.test.Jetty7Runner;
*public* *class* Jetty {
*public* *static* *void* main(String[] args) *throws* Exception{
Jetty7Runner runner = *new*
Jetty7Runner("src/main/webapp","/",8080,8443);
}
}
and that works if I add src/main/resources to the classpath and check
exported entries only.
src/main/resources should be part of the classpath in a way or another
(directly or through adding the folder to which classes are compiled.
This may even be better because I don't need a
plugin but still does not fit my definition of 'just works'. I would rate
it promising.
Running an embedded Jetty instance, for me, is the best option after
RunJettyRun.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
