thanks Mark, fixed that.

When using tomcat:run , it picks up changes to jsps ok which is great,
but using the jetty:run plugin I found that I could also rebuild a
serverside jar (which for a WAR would have been in web-inf/lib) using
'mvn install' it would then go into my local repo, which Jetty had on
its classpath (you can see this at jetty start up - all jars come from
local repository) , so when new jar gets installed, jetty picks up the
change and redeploys.  Where as I think the tomcat launch is using the

target\myWebapp\WEB-INF\lib

folder for these jars?

I guess it's not possible for tomcat to pick up the jars from local
repo ? it would be great if it could.

If not, I need a way to refresh it JAR, I tried a 'mvn package' on the
WAR project, when tomcat:run is still open in another window. I can
see the jar timestamps change, but tomcat doesn't realise. So then I
thought maybe I could use Tomcat manager to reload e.g.
http://localhost:8080/manager/reload?path=/myWebapp
but I don't think the manager is available in this Tomcat configuration?

I tried changing the tomcat-users.xml  , added

<user username="admin" password="" roles="tomcat,manager,admin"/>

then   mvn tomcat:run but manager still not available

Any thoughts on how to ease rapid development with Tomcat appreciated.

Pete

Pete

On 07/02/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
Hi Pete,

On 07/02/07, Pete <[EMAIL PROTECTED]> wrote:
> 1) I'm trying to use the tomcat-maven-plugin  all is fine using
>
> mvn tomcat:deploy
>
> however if I try the new
>
> mvn tomcat:run
>
> which I understand is supposed to be like the  jetty:run, I get an
> error, see end of email.

Looks like your webapp is using a different version of servlet-api,
hence a class cast exception when tomcat tries to cast your filter.
Ensure you're using servlet-api 2.4 which tomcat 5.5 uses.

> 2) I assume this puts a tomcat instance in  target/tomcat
>
> however I notice the tomcat manager isn't enable in the
> target\tomcat\conf\tomcat-users.xml

Nope, tomcat manager isn't deployed using tomcat:run.  Feel free to
raise an issue if you need this functionality.  I didn't think this
was too useful since the container is rather transient.

> 3) Is there any documentation on this tomcat:run goal ?  none at
> http://mojo.codehaus.org/tomcat-maven-plugin/

See:

http://mojo.codehaus.org/tomcat-maven-plugin/deployment.html#Running%20a%20WAR%20project
http://mojo.codehaus.org/tomcat-maven-plugin/run-mojo.html

Cheers,

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to