You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Paul Stanton <pa...@mapshed.com.au> on 2010/11/05 00:22:02 UTC
best stack ...
Hi all,
I'm starting a new project, which will be in beta (non-prod) for some
time and I'd like to start with the current cutting edge setup with the
hope that it will be the standard or release phase down the track.
I'd like to set up my development environment for rapid development.
The project may need to be deployed to tomcat for hosting, but
development could be done on Resin if necessary. I've never used Resin
but if the development time advantages are sufficient I would consider
this approach.
I've always used Eclipse.
Haven't used Tapestry 5.2 yet but would like to start..
Don't really like Maven but have found it's a necessary evil if you want
to develop with Tapestry 5.
The quickstart tutorial seems a little outdated
(http://tapestry.apache.org/tapestry5/tutorial1/env.html) - is there an
updated version or a tutorial anywhere?
also, there's been some discussion regarding tomcat not working well
with the custom classloader in tapestry .. does anyone have a setup
tutorial/guide on how to get these two working together?
thanks, paul.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: best stack ...
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
On Thu, 04 Nov 2010 21:27:22 -0200, Howard Lewis Ship <hl...@gmail.com>
wrote:
> I prefer Jetty to run my application.
> I'm always amazed at how tortured people's setups are.
Mee too.
> It's really simple:
> Create a project (using Maven, or otherwise).
> Use the RunJettyRun Eclipse plugin.
You can even use Jetty without a plugin: add Jetty to your classpath and
create a main mathod that starts an embedded instance of it. Then run or
debug it as you were running or testing a hello world. :) I've posted my
code (just some lines) in this mailing list before but I'm extremely lazy
to search it this moment. :P
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: best stack ...
Posted by Paul Stanton <pa...@mapshed.com.au>.
AH!!
just figured out that m2eclipse was configured to be offline... i use
multiple workspaces (for different project groups) and this workspace
has never used the plugin before ... :(
however, i now have the surefire problem fixed, and i assume perhaps the
T5.2 maven issues listed earlier ...
p.
On 6/11/2010 12:39 PM, Paul Stanton wrote:
> Hi Andreas,
>
> Rest assured, I am connected ... but my concern is more regards to why
> there is no 'tried and true' setup path for new users wanting to use
> the latest and or recommended stack.
>
> Many developers aren't familiar with maven and therefore need their
> hands held through this step.
>
> Others, like myself are partially familiar, but would appreciate
> confirmation that they aren't 'doing it wrong', the simplest way to
> provide this is through a clear and concise setup doc, which stays up
> to date with the project.
>
> by the way, i've given up on getting 5.2 working for now, instead
> starting a 5.1 project following howards screencast as closely as it's
> 'out-of-dateness' allows.
>
> I've installed "run-jetty-run" and created a hello world app which
> runs fine via eclipse.
>
> however when i try to run a maven install, i get the following error:
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.4.3:test
> (default-test) on project MyProject: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.4.3:test failed:
> Plugin org.apache.maven.plugins:maven-surefire-plugin:2.4.3 or one of
> its dependencies could not be resolved: Unable to get dependency
> information for
> org.apache.maven.plugins:maven-surefire-plugin:maven-plugin:2.4.3:
> Failed to process POM for
> org.apache.maven.plugins:maven-surefire-plugin:maven-plugin:2.4.3:
> Non-resolvable parent POM org.apache.maven.surefire:surefire:2.4.3 for
> org.apache.maven.plugins:maven-surefire-plugin:2.4.3: Failed to
> resolve POM for org.apache.maven.surefire:surefire:2.4.3 due to The
> repository system is offline and the requested artifact is not locally
> available at
> C:\dir\.m2\repository\org\apache\maven\surefire\surefire\2.4.3\surefire-2.4.3.pom
> org.apache.maven.surefire:surefire:pom:2.4.3
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2, releases=true, snapshots=false)
>
> I possibly need to add a repository?
>
> regards, p.
>
> On 6/11/2010 11:36 AM, Andreas Andreou wrote:
>> Not sure why you get "The
>> repository system is offline and the requested artifact is not
>> locally available"
>>
>> That usually shows up when a build is offline - you'd need to be online
>> for maven to download the deps... or perhaps that's a maven/eclipse
>> issue, gg it.
>>
>> As for the archetype catalog, i just reuploaded an update for it that
>> should
>> give the option to create 5.2.3-SNAPSHOT projects. It may take a
>> couple of
>> hours before the web server sync and this becomes available.
>>
>> On Sat, Nov 6, 2010 at 02:08, Paul Stanton<pa...@mapshed.com.au> wrote:
>>> 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!
>>>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: best stack ...
Posted by Paul Stanton <pa...@mapshed.com.au>.
Hi Andreas,
Rest assured, I am connected ... but my concern is more regards to why
there is no 'tried and true' setup path for new users wanting to use the
latest and or recommended stack.
Many developers aren't familiar with maven and therefore need their
hands held through this step.
Others, like myself are partially familiar, but would appreciate
confirmation that they aren't 'doing it wrong', the simplest way to
provide this is through a clear and concise setup doc, which stays up to
date with the project.
by the way, i've given up on getting 5.2 working for now, instead
starting a 5.1 project following howards screencast as closely as it's
'out-of-dateness' allows.
I've installed "run-jetty-run" and created a hello world app which runs
fine via eclipse.
however when i try to run a maven install, i get the following error:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.4.3:test (default-test)
on project MyProject: Execution default-test of goal
org.apache.maven.plugins:maven-surefire-plugin:2.4.3:test failed: Plugin
org.apache.maven.plugins:maven-surefire-plugin:2.4.3 or one of its
dependencies could not be resolved: Unable to get dependency information
for org.apache.maven.plugins:maven-surefire-plugin:maven-plugin:2.4.3:
Failed to process POM for
org.apache.maven.plugins:maven-surefire-plugin:maven-plugin:2.4.3:
Non-resolvable parent POM org.apache.maven.surefire:surefire:2.4.3 for
org.apache.maven.plugins:maven-surefire-plugin:2.4.3: Failed to resolve
POM for org.apache.maven.surefire:surefire:2.4.3 due to The repository
system is offline and the requested artifact is not locally available at
C:\dir\.m2\repository\org\apache\maven\surefire\surefire\2.4.3\surefire-2.4.3.pom
org.apache.maven.surefire:surefire:pom:2.4.3
from the specified remote repositories:
central (http://repo1.maven.org/maven2, releases=true, snapshots=false)
I possibly need to add a repository?
regards, p.
On 6/11/2010 11:36 AM, Andreas Andreou wrote:
> Not sure why you get "The
> repository system is offline and the requested artifact is not
> locally available"
>
> That usually shows up when a build is offline - you'd need to be online
> for maven to download the deps... or perhaps that's a maven/eclipse
> issue, gg it.
>
> As for the archetype catalog, i just reuploaded an update for it that should
> give the option to create 5.2.3-SNAPSHOT projects. It may take a couple of
> hours before the web server sync and this becomes available.
>
> On Sat, Nov 6, 2010 at 02:08, Paul Stanton<pa...@mapshed.com.au> wrote:
>> 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!
>>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: best stack ...
Posted by Andreas Andreou <an...@di.uoa.gr>.
Not sure why you get "The
repository system is offline and the requested artifact is not
locally available"
That usually shows up when a build is offline - you'd need to be online
for maven to download the deps... or perhaps that's a maven/eclipse
issue, gg it.
As for the archetype catalog, i just reuploaded an update for it that should
give the option to create 5.2.3-SNAPSHOT projects. It may take a couple of
hours before the web server sync and this becomes available.
On Sat, Nov 6, 2010 at 02:08, Paul Stanton <pa...@mapshed.com.au> wrote:
> 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!
>>
>
--
Andreas Andreou - andyhot@apache.org - http://blog.andyhot.gr
Tapestry PMC / Tacos developer
Open Source / JEE Consulting
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: best stack ...
Posted by Paul Stanton <pa...@mapshed.com.au>.
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!
>
Re: best stack ...
Posted by Andreas Andreou <an...@di.uoa.gr>.
Depends on the type of project you're making and policies you enforce.
If you always depend on releases or if your snapshot deps are from
projects that don't often change their deps, then yes, it's very easy to
manage libs manually (basically a one-time setup process)
On Fri, Nov 5, 2010 at 14:28, Adam Zimowski <zi...@gmail.com> wrote:
>> it takes a brave soul to manage 30 to 40 megs of libraries manually
>
> We do, and we're not that brave either :) It really isn't all that
> bad as Maven fans want you to think.
>
> Adam
>
> On Fri, Nov 5, 2010 at 7:25 AM, Peter Stavrinides
> <P....@albourne.com> wrote:
>> You are not forced to develop with Maven, but it takes a brave soul to manage 30 to 40 megs of libraries manually :) lol.
>>
>> Peter
>>
>> ----- Original Message -----
>> From: "Adam Zimowski" <zi...@gmail.com>
>> To: "Tapestry users" <us...@tapestry.apache.org>
>> Sent: Friday, 5 November, 2010 04:35:38 GMT +02:00 Athens, Beirut, Bucharest, Istanbul
>> Subject: Re: best stack ...
>>
>>> Don't really like Maven but have found it's a necessary evil if you want to develop with Tapestry 5.
>>
>> Well, while Maven is helpfull it's not exactly true :-) We have a
>> large Tapestry app (ported struts 1 gozilla), and zero Maven.
>> Remember, Maven is just a tool to automate things. You can setup your
>> project infrastructure and builds without it.
>>
>> Here is our stack:
>>
>> -- Web/App Layer --
>> Eclipse
>> Jetty (local dev as well as production) - we don't use RunJettyRun,
>> rather we use a standard Eclipse run task executing Main from Jetty's
>> start.jar.
>> Tapestry 5.2 - the beauty of Tap IOC is that we are now Spring free,
>> after all these years with Struts-Spring torture.
>> AspectJ for AOP
>> (minor libs)
>>
>> -- Business Layer ---
>> OpenEJB
>> Hibernate
>> Ant - EJB deploys, Hibernate schema builds etc.
>> (minor libs)
>>
>> What we have found that Tapestry-Hibernate integration is completely
>> unnecessary for us since our Hibernate layer is abstracted out behind
>> the EJBs. So is Tapestry-Spring - also not necessary.
>>
>> Anotherwords, all we have is a pure Tapestry (with few component libs)
>> to run our huge Ecommerce app.
>>
>> Adam
>>
>>
>>
>>
>> On Thu, Nov 4, 2010 at 7:41 PM, Anas Mughal <an...@yahoo.com> wrote:
>>> Use Maven archetype to create the project for you:
>>>
>>>
>>>
>>>
>>> http://tapestry.apache.org/tapestry5.1/quickstart/
>>>
>>>
>>>
>>>
>>> It will take care of everything.Then, import it into Eclipse as Maven project.
>>>
>>> --
>>> Anas Mughal
>>> http://anas-mughal.com
>>>
>>>
>>>
>>> --- On Thu, 11/4/10, Howard Lewis Ship <hl...@gmail.com> wrote:
>>>
>>> From: Howard Lewis Ship <hl...@gmail.com>
>>> Subject: Re: best stack ...
>>> To: "Tapestry users" <us...@tapestry.apache.org>
>>> Date: Thursday, November 4, 2010, 7:27 PM
>>>
>>> I prefer Jetty to run my application.
>>>
>>> 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!
>>>
>>>
>>> On Thu, Nov 4, 2010 at 4:22 PM, Paul Stanton <pa...@mapshed.com.au> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I'm starting a new project, which will be in beta (non-prod) for some time
>>>> and I'd like to start with the current cutting edge setup with the hope that
>>>> it will be the standard or release phase down the track.
>>>>
>>>> I'd like to set up my development environment for rapid development.
>>>>
>>>> The project may need to be deployed to tomcat for hosting, but development
>>>> could be done on Resin if necessary. I've never used Resin but if the
>>>> development time advantages are sufficient I would consider this approach.
>>>>
>>>> I've always used Eclipse.
>>>> Haven't used Tapestry 5.2 yet but would like to start..
>>>> Don't really like Maven but have found it's a necessary evil if you want to
>>>> develop with Tapestry 5.
>>>>
>>>> The quickstart tutorial seems a little outdated (
>>>> http://tapestry.apache.org/tapestry5/tutorial1/env.html) - is there an
>>>> updated version or a tutorial anywhere?
>>>>
>>>> also, there's been some discussion regarding tomcat not working well with
>>>> the custom classloader in tapestry .. does anyone have a setup
>>>> tutorial/guide on how to get these two working together?
>>>>
>>>> thanks, paul.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Howard M. Lewis Ship
>>>
>>> Creator of Apache Tapestry
>>>
>>> The source for Tapestry training, mentoring and support. Contact me to learn
>>> how I can get you up and productive in Tapestry fast!
>>>
>>> (971) 678-5210
>>> http://howardlewisship.com
>>>
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Andreas Andreou - andyhot@apache.org - http://blog.andyhot.gr
Tapestry PMC / Tacos developer
Open Source / JEE Consulting
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: best stack ...
Posted by Michael Gentry <mg...@masslight.net>.
I've opted to use Maven to run Jetty (mvn jetty:run). Combined with
the m2eclipse plugin, this gives me a lot of flexibility.
In Eclipse, I can Run or Debug. I can also run from the command-line.
In the pom.xml I can specify which version of Jetty I want to use.
This is important if you want to use JNDI, because the RunJettyRun
plugin doesn't (the last time I looked) support Jetty Plus, which
provides JNDI. This has ended up being the simplest for me.
RunJettyRun was great until I needed JNDI.
mrg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: best stack ...
Posted by Howard Lewis Ship <hl...@gmail.com>.
I bet you make sure your JARs have version numbers in the name, though!
Take a peek at Gradle when you get a chance; it's really
best-of-both-worlds.
On Fri, Nov 5, 2010 at 5:28 AM, Adam Zimowski <zi...@gmail.com> wrote:
> > it takes a brave soul to manage 30 to 40 megs of libraries manually
>
> We do, and we're not that brave either :) It really isn't all that
> bad as Maven fans want you to think.
>
> Adam
>
> On Fri, Nov 5, 2010 at 7:25 AM, Peter Stavrinides
> <P....@albourne.com> wrote:
> > You are not forced to develop with Maven, but it takes a brave soul to
> manage 30 to 40 megs of libraries manually :) lol.
> >
> > Peter
> >
> > ----- Original Message -----
> > From: "Adam Zimowski" <zi...@gmail.com>
> > To: "Tapestry users" <us...@tapestry.apache.org>
> > Sent: Friday, 5 November, 2010 04:35:38 GMT +02:00 Athens, Beirut,
> Bucharest, Istanbul
> > Subject: Re: best stack ...
> >
> >> Don't really like Maven but have found it's a necessary evil if you want
> to develop with Tapestry 5.
> >
> > Well, while Maven is helpfull it's not exactly true :-) We have a
> > large Tapestry app (ported struts 1 gozilla), and zero Maven.
> > Remember, Maven is just a tool to automate things. You can setup your
> > project infrastructure and builds without it.
> >
> > Here is our stack:
> >
> > -- Web/App Layer --
> > Eclipse
> > Jetty (local dev as well as production) - we don't use RunJettyRun,
> > rather we use a standard Eclipse run task executing Main from Jetty's
> > start.jar.
> > Tapestry 5.2 - the beauty of Tap IOC is that we are now Spring free,
> > after all these years with Struts-Spring torture.
> > AspectJ for AOP
> > (minor libs)
> >
> > -- Business Layer ---
> > OpenEJB
> > Hibernate
> > Ant - EJB deploys, Hibernate schema builds etc.
> > (minor libs)
> >
> > What we have found that Tapestry-Hibernate integration is completely
> > unnecessary for us since our Hibernate layer is abstracted out behind
> > the EJBs. So is Tapestry-Spring - also not necessary.
> >
> > Anotherwords, all we have is a pure Tapestry (with few component libs)
> > to run our huge Ecommerce app.
> >
> > Adam
> >
> >
> >
> >
> > On Thu, Nov 4, 2010 at 7:41 PM, Anas Mughal <an...@yahoo.com>
> wrote:
> >> Use Maven archetype to create the project for you:
> >>
> >>
> >>
> >>
> >> http://tapestry.apache.org/tapestry5.1/quickstart/
> >>
> >>
> >>
> >>
> >> It will take care of everything.Then, import it into Eclipse as Maven
> project.
> >>
> >> --
> >> Anas Mughal
> >> http://anas-mughal.com
> >>
> >>
> >>
> >> --- On Thu, 11/4/10, Howard Lewis Ship <hl...@gmail.com> wrote:
> >>
> >> From: Howard Lewis Ship <hl...@gmail.com>
> >> Subject: Re: best stack ...
> >> To: "Tapestry users" <us...@tapestry.apache.org>
> >> Date: Thursday, November 4, 2010, 7:27 PM
> >>
> >> I prefer Jetty to run my application.
> >>
> >> 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!
> >>
> >>
> >> On Thu, Nov 4, 2010 at 4:22 PM, Paul Stanton <pa...@mapshed.com.au>
> wrote:
> >>
> >>> Hi all,
> >>>
> >>> I'm starting a new project, which will be in beta (non-prod) for some
> time
> >>> and I'd like to start with the current cutting edge setup with the hope
> that
> >>> it will be the standard or release phase down the track.
> >>>
> >>> I'd like to set up my development environment for rapid development.
> >>>
> >>> The project may need to be deployed to tomcat for hosting, but
> development
> >>> could be done on Resin if necessary. I've never used Resin but if the
> >>> development time advantages are sufficient I would consider this
> approach.
> >>>
> >>> I've always used Eclipse.
> >>> Haven't used Tapestry 5.2 yet but would like to start..
> >>> Don't really like Maven but have found it's a necessary evil if you
> want to
> >>> develop with Tapestry 5.
> >>>
> >>> The quickstart tutorial seems a little outdated (
> >>> http://tapestry.apache.org/tapestry5/tutorial1/env.html) - is there an
> >>> updated version or a tutorial anywhere?
> >>>
> >>> also, there's been some discussion regarding tomcat not working well
> with
> >>> the custom classloader in tapestry .. does anyone have a setup
> >>> tutorial/guide on how to get these two working together?
> >>>
> >>> thanks, paul.
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>
> >>>
> >>
> >>
> >> --
> >> Howard M. Lewis Ship
> >>
> >> Creator of Apache Tapestry
> >>
> >> The source for Tapestry training, mentoring and support. Contact me to
> learn
> >> how I can get you up and productive in Tapestry fast!
> >>
> >> (971) 678-5210
> >> http://howardlewisship.com
> >>
> >>
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to learn
how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
Re: best stack ...
Posted by Adam Zimowski <zi...@gmail.com>.
> it takes a brave soul to manage 30 to 40 megs of libraries manually
We do, and we're not that brave either :) It really isn't all that
bad as Maven fans want you to think.
Adam
On Fri, Nov 5, 2010 at 7:25 AM, Peter Stavrinides
<P....@albourne.com> wrote:
> You are not forced to develop with Maven, but it takes a brave soul to manage 30 to 40 megs of libraries manually :) lol.
>
> Peter
>
> ----- Original Message -----
> From: "Adam Zimowski" <zi...@gmail.com>
> To: "Tapestry users" <us...@tapestry.apache.org>
> Sent: Friday, 5 November, 2010 04:35:38 GMT +02:00 Athens, Beirut, Bucharest, Istanbul
> Subject: Re: best stack ...
>
>> Don't really like Maven but have found it's a necessary evil if you want to develop with Tapestry 5.
>
> Well, while Maven is helpfull it's not exactly true :-) We have a
> large Tapestry app (ported struts 1 gozilla), and zero Maven.
> Remember, Maven is just a tool to automate things. You can setup your
> project infrastructure and builds without it.
>
> Here is our stack:
>
> -- Web/App Layer --
> Eclipse
> Jetty (local dev as well as production) - we don't use RunJettyRun,
> rather we use a standard Eclipse run task executing Main from Jetty's
> start.jar.
> Tapestry 5.2 - the beauty of Tap IOC is that we are now Spring free,
> after all these years with Struts-Spring torture.
> AspectJ for AOP
> (minor libs)
>
> -- Business Layer ---
> OpenEJB
> Hibernate
> Ant - EJB deploys, Hibernate schema builds etc.
> (minor libs)
>
> What we have found that Tapestry-Hibernate integration is completely
> unnecessary for us since our Hibernate layer is abstracted out behind
> the EJBs. So is Tapestry-Spring - also not necessary.
>
> Anotherwords, all we have is a pure Tapestry (with few component libs)
> to run our huge Ecommerce app.
>
> Adam
>
>
>
>
> On Thu, Nov 4, 2010 at 7:41 PM, Anas Mughal <an...@yahoo.com> wrote:
>> Use Maven archetype to create the project for you:
>>
>>
>>
>>
>> http://tapestry.apache.org/tapestry5.1/quickstart/
>>
>>
>>
>>
>> It will take care of everything.Then, import it into Eclipse as Maven project.
>>
>> --
>> Anas Mughal
>> http://anas-mughal.com
>>
>>
>>
>> --- On Thu, 11/4/10, Howard Lewis Ship <hl...@gmail.com> wrote:
>>
>> From: Howard Lewis Ship <hl...@gmail.com>
>> Subject: Re: best stack ...
>> To: "Tapestry users" <us...@tapestry.apache.org>
>> Date: Thursday, November 4, 2010, 7:27 PM
>>
>> I prefer Jetty to run my application.
>>
>> 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!
>>
>>
>> On Thu, Nov 4, 2010 at 4:22 PM, Paul Stanton <pa...@mapshed.com.au> wrote:
>>
>>> Hi all,
>>>
>>> I'm starting a new project, which will be in beta (non-prod) for some time
>>> and I'd like to start with the current cutting edge setup with the hope that
>>> it will be the standard or release phase down the track.
>>>
>>> I'd like to set up my development environment for rapid development.
>>>
>>> The project may need to be deployed to tomcat for hosting, but development
>>> could be done on Resin if necessary. I've never used Resin but if the
>>> development time advantages are sufficient I would consider this approach.
>>>
>>> I've always used Eclipse.
>>> Haven't used Tapestry 5.2 yet but would like to start..
>>> Don't really like Maven but have found it's a necessary evil if you want to
>>> develop with Tapestry 5.
>>>
>>> The quickstart tutorial seems a little outdated (
>>> http://tapestry.apache.org/tapestry5/tutorial1/env.html) - is there an
>>> updated version or a tutorial anywhere?
>>>
>>> also, there's been some discussion regarding tomcat not working well with
>>> the custom classloader in tapestry .. does anyone have a setup
>>> tutorial/guide on how to get these two working together?
>>>
>>> thanks, paul.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>>
>>
>>
>> --
>> Howard M. Lewis Ship
>>
>> Creator of Apache Tapestry
>>
>> The source for Tapestry training, mentoring and support. Contact me to learn
>> how I can get you up and productive in Tapestry fast!
>>
>> (971) 678-5210
>> http://howardlewisship.com
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: best stack ...
Posted by Peter Stavrinides <P....@albourne.com>.
You are not forced to develop with Maven, but it takes a brave soul to manage 30 to 40 megs of libraries manually :) lol.
Peter
----- Original Message -----
From: "Adam Zimowski" <zi...@gmail.com>
To: "Tapestry users" <us...@tapestry.apache.org>
Sent: Friday, 5 November, 2010 04:35:38 GMT +02:00 Athens, Beirut, Bucharest, Istanbul
Subject: Re: best stack ...
> Don't really like Maven but have found it's a necessary evil if you want to develop with Tapestry 5.
Well, while Maven is helpfull it's not exactly true :-) We have a
large Tapestry app (ported struts 1 gozilla), and zero Maven.
Remember, Maven is just a tool to automate things. You can setup your
project infrastructure and builds without it.
Here is our stack:
-- Web/App Layer --
Eclipse
Jetty (local dev as well as production) - we don't use RunJettyRun,
rather we use a standard Eclipse run task executing Main from Jetty's
start.jar.
Tapestry 5.2 - the beauty of Tap IOC is that we are now Spring free,
after all these years with Struts-Spring torture.
AspectJ for AOP
(minor libs)
-- Business Layer ---
OpenEJB
Hibernate
Ant - EJB deploys, Hibernate schema builds etc.
(minor libs)
What we have found that Tapestry-Hibernate integration is completely
unnecessary for us since our Hibernate layer is abstracted out behind
the EJBs. So is Tapestry-Spring - also not necessary.
Anotherwords, all we have is a pure Tapestry (with few component libs)
to run our huge Ecommerce app.
Adam
On Thu, Nov 4, 2010 at 7:41 PM, Anas Mughal <an...@yahoo.com> wrote:
> Use Maven archetype to create the project for you:
>
>
>
>
> http://tapestry.apache.org/tapestry5.1/quickstart/
>
>
>
>
> It will take care of everything.Then, import it into Eclipse as Maven project.
>
> --
> Anas Mughal
> http://anas-mughal.com
>
>
>
> --- On Thu, 11/4/10, Howard Lewis Ship <hl...@gmail.com> wrote:
>
> From: Howard Lewis Ship <hl...@gmail.com>
> Subject: Re: best stack ...
> To: "Tapestry users" <us...@tapestry.apache.org>
> Date: Thursday, November 4, 2010, 7:27 PM
>
> I prefer Jetty to run my application.
>
> 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!
>
>
> On Thu, Nov 4, 2010 at 4:22 PM, Paul Stanton <pa...@mapshed.com.au> wrote:
>
>> Hi all,
>>
>> I'm starting a new project, which will be in beta (non-prod) for some time
>> and I'd like to start with the current cutting edge setup with the hope that
>> it will be the standard or release phase down the track.
>>
>> I'd like to set up my development environment for rapid development.
>>
>> The project may need to be deployed to tomcat for hosting, but development
>> could be done on Resin if necessary. I've never used Resin but if the
>> development time advantages are sufficient I would consider this approach.
>>
>> I've always used Eclipse.
>> Haven't used Tapestry 5.2 yet but would like to start..
>> Don't really like Maven but have found it's a necessary evil if you want to
>> develop with Tapestry 5.
>>
>> The quickstart tutorial seems a little outdated (
>> http://tapestry.apache.org/tapestry5/tutorial1/env.html) - is there an
>> updated version or a tutorial anywhere?
>>
>> also, there's been some discussion regarding tomcat not working well with
>> the custom classloader in tapestry .. does anyone have a setup
>> tutorial/guide on how to get these two working together?
>>
>> thanks, paul.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to learn
> how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: best stack ...
Posted by Adam Zimowski <zi...@gmail.com>.
> Don't really like Maven but have found it's a necessary evil if you want to develop with Tapestry 5.
Well, while Maven is helpfull it's not exactly true :-) We have a
large Tapestry app (ported struts 1 gozilla), and zero Maven.
Remember, Maven is just a tool to automate things. You can setup your
project infrastructure and builds without it.
Here is our stack:
-- Web/App Layer --
Eclipse
Jetty (local dev as well as production) - we don't use RunJettyRun,
rather we use a standard Eclipse run task executing Main from Jetty's
start.jar.
Tapestry 5.2 - the beauty of Tap IOC is that we are now Spring free,
after all these years with Struts-Spring torture.
AspectJ for AOP
(minor libs)
-- Business Layer ---
OpenEJB
Hibernate
Ant - EJB deploys, Hibernate schema builds etc.
(minor libs)
What we have found that Tapestry-Hibernate integration is completely
unnecessary for us since our Hibernate layer is abstracted out behind
the EJBs. So is Tapestry-Spring - also not necessary.
Anotherwords, all we have is a pure Tapestry (with few component libs)
to run our huge Ecommerce app.
Adam
On Thu, Nov 4, 2010 at 7:41 PM, Anas Mughal <an...@yahoo.com> wrote:
> Use Maven archetype to create the project for you:
>
>
>
>
> http://tapestry.apache.org/tapestry5.1/quickstart/
>
>
>
>
> It will take care of everything.Then, import it into Eclipse as Maven project.
>
> --
> Anas Mughal
> http://anas-mughal.com
>
>
>
> --- On Thu, 11/4/10, Howard Lewis Ship <hl...@gmail.com> wrote:
>
> From: Howard Lewis Ship <hl...@gmail.com>
> Subject: Re: best stack ...
> To: "Tapestry users" <us...@tapestry.apache.org>
> Date: Thursday, November 4, 2010, 7:27 PM
>
> I prefer Jetty to run my application.
>
> 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!
>
>
> On Thu, Nov 4, 2010 at 4:22 PM, Paul Stanton <pa...@mapshed.com.au> wrote:
>
>> Hi all,
>>
>> I'm starting a new project, which will be in beta (non-prod) for some time
>> and I'd like to start with the current cutting edge setup with the hope that
>> it will be the standard or release phase down the track.
>>
>> I'd like to set up my development environment for rapid development.
>>
>> The project may need to be deployed to tomcat for hosting, but development
>> could be done on Resin if necessary. I've never used Resin but if the
>> development time advantages are sufficient I would consider this approach.
>>
>> I've always used Eclipse.
>> Haven't used Tapestry 5.2 yet but would like to start..
>> Don't really like Maven but have found it's a necessary evil if you want to
>> develop with Tapestry 5.
>>
>> The quickstart tutorial seems a little outdated (
>> http://tapestry.apache.org/tapestry5/tutorial1/env.html) - is there an
>> updated version or a tutorial anywhere?
>>
>> also, there's been some discussion regarding tomcat not working well with
>> the custom classloader in tapestry .. does anyone have a setup
>> tutorial/guide on how to get these two working together?
>>
>> thanks, paul.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to learn
> how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: best stack ...
Posted by Anas Mughal <an...@yahoo.com>.
Use Maven archetype to create the project for you:
http://tapestry.apache.org/tapestry5.1/quickstart/
It will take care of everything.Then, import it into Eclipse as Maven project.
--
Anas Mughal
http://anas-mughal.com
--- On Thu, 11/4/10, Howard Lewis Ship <hl...@gmail.com> wrote:
From: Howard Lewis Ship <hl...@gmail.com>
Subject: Re: best stack ...
To: "Tapestry users" <us...@tapestry.apache.org>
Date: Thursday, November 4, 2010, 7:27 PM
I prefer Jetty to run my application.
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!
On Thu, Nov 4, 2010 at 4:22 PM, Paul Stanton <pa...@mapshed.com.au> wrote:
> Hi all,
>
> I'm starting a new project, which will be in beta (non-prod) for some time
> and I'd like to start with the current cutting edge setup with the hope that
> it will be the standard or release phase down the track.
>
> I'd like to set up my development environment for rapid development.
>
> The project may need to be deployed to tomcat for hosting, but development
> could be done on Resin if necessary. I've never used Resin but if the
> development time advantages are sufficient I would consider this approach.
>
> I've always used Eclipse.
> Haven't used Tapestry 5.2 yet but would like to start..
> Don't really like Maven but have found it's a necessary evil if you want to
> develop with Tapestry 5.
>
> The quickstart tutorial seems a little outdated (
> http://tapestry.apache.org/tapestry5/tutorial1/env.html) - is there an
> updated version or a tutorial anywhere?
>
> also, there's been some discussion regarding tomcat not working well with
> the custom classloader in tapestry .. does anyone have a setup
> tutorial/guide on how to get these two working together?
>
> thanks, paul.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to learn
how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
Re: best stack ...
Posted by Howard Lewis Ship <hl...@gmail.com>.
I prefer Jetty to run my application.
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!
On Thu, Nov 4, 2010 at 4:22 PM, Paul Stanton <pa...@mapshed.com.au> wrote:
> Hi all,
>
> I'm starting a new project, which will be in beta (non-prod) for some time
> and I'd like to start with the current cutting edge setup with the hope that
> it will be the standard or release phase down the track.
>
> I'd like to set up my development environment for rapid development.
>
> The project may need to be deployed to tomcat for hosting, but development
> could be done on Resin if necessary. I've never used Resin but if the
> development time advantages are sufficient I would consider this approach.
>
> I've always used Eclipse.
> Haven't used Tapestry 5.2 yet but would like to start..
> Don't really like Maven but have found it's a necessary evil if you want to
> develop with Tapestry 5.
>
> The quickstart tutorial seems a little outdated (
> http://tapestry.apache.org/tapestry5/tutorial1/env.html) - is there an
> updated version or a tutorial anywhere?
>
> also, there's been some discussion regarding tomcat not working well with
> the custom classloader in tapestry .. does anyone have a setup
> tutorial/guide on how to get these two working together?
>
> thanks, paul.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to learn
how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
Re: best stack ...
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
On Thu, 04 Nov 2010 21:22:02 -0200, Paul Stanton <pa...@mapshed.com.au>
wrote:
> Hi all,
Hi!.
> The project may need to be deployed to tomcat for hosting, but
> development could be done on Resin if necessary. I've never used Resin
> but if the development time advantages are sufficient I would consider
> this approach.
Why not Jetty? I strongly recommend it for development. Starts in a couple
seconds, maybe even less. I use it for production too. It's used in the
Google Application Engine. It's now an Eclipse project.
I can't see any reason for using Tomcat in development. today
> I've always used Eclipse.
> Haven't used Tapestry 5.2 yet but would like to start..
> Don't really like Maven but have found it's a necessary evil if you want
> to develop with Tapestry 5.
Maven is not needed to work with Tapestry 5 at all. Of course, using it
you don't have to worry about dependencies. In Eclipse, m2eclipse helps a
lot.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org