Howard,
After reading all the responses to my question and trying a few things
I'm confused.
I'm not a new user and have been using tapestry since T3, however I've
never been 100% satisfied by how I've managed to setup T5 projects in
the past and keep coming back to this step for new projects in the hope
that it has somehow improved.
I think documentation of project setup is one of the most important
aspects of a framework, and one which seems to be routinely neglected in
tapestry. This is possibly why people's setups become "tortured"?
* The most up-to-date 'getting started' instruction i can find is
the 'tutorial 1' which is pretty outdated, especially if you
intend to use T5.2.
* 'Tutorial 1' also mentions that Jetty 5 should be used (instead of
6), however that was supposedly in 2006, jetty 5.1 is now
'deprecated' according to the jetty site, while jetty 7 is available.
* Alternatively there is the Screencast, created in 2006 and written
for T5.0.
* Using the 5.2.2 quickstart archetype results in maven errors
(group id: org.apache.tapestry, artifact id: quickstart, version:
5.2.2, repository: http://repo1.maven.org/maven2).
* Adding the T5.2 dependency (any sub-version) fails - "The
repository system is offline and the requested artifact is not
locally available.
* The download for the 5.2.0 binary doesn't work
(http://www.apache.org/dyn/closer.cgi/tapestry/tapestry-bin-5.2.0.zip)
* Downloading the binarys for 5.1.0.5 includes many jars, but no
instructions regarding project setup or which dependencies are
needed for which types of applications.
So for a T5.2 project, using the most compatible and up-to-date versions
of eclipse and jetty, where should new users start?
regards, p.
On 5/11/2010 10:27 AM, Howard Lewis Ship wrote:
I'm always amazed at how tortured people's setups are.
It's really simple:
Create a project (using Maven, or otherwise).
Use the RunJettyRun Eclipse plugin.
Make sure you are NOT compiling to src/main/webapp/WEB-INF/classes (compile
to target/classes or something)
Make sure your libraries are NOT in src/main/webapp/WEB-INF/lib (they won't
be if you are using Maven/Gradle/etc.)
(The above two resolve potential class resolution problems where classes are
loaded by the wrong class loader).
Start RunJettyRun targetted at src/main/webapp
You're done!
