Hey, mvn tomcat:run is always an option!
Daniel Jue wrote:
I have run the Jetty plugin from the t5 simple archetype with great
success. I tried it again just now, and it didn't work, because my
plugin
code was like this:
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<configuration>
<requestLog>
<append>true</append>
</requestLog>
</configuration>
</plugin>
I switched it to your code and now it works fine again. I was wary about
Jetty's JNDI support, and since I deploy to Tomcat for production, I had
grown accustomed to using it in development. But I'll give it a whirl.
I ended up tweaking mine a bit, changing the port number and timeout. I
learned that here:
http://www.mortbay.org/maven-plugin/howto.html
So now mine looks like:
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<configuration>
<connectors>
<connector implementation="
org.mortbay.jetty.nio.SelectChannelConnector">
<port>8000</port>
<maxIdleTime>60000</maxIdleTime>
</connector>
</connectors>
</configuration>
</plugin>
On 5/24/07, Martin Strand <[EMAIL PROTECTED]> wrote:
If you don't have to run your app in tomcat, there's a maven plugin for
jetty. Add this to your pom
<build>
<plugins>
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
</plugin>
</plugins>
</build>
and then start jetty with "mvn jetty:run".
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
