maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Pöllath <>
Subject Re: [m2] Using the jetty6 plugin was: Using the tomcat plugin
Date Thu, 03 Nov 2005 10:06:43 GMT

I'm impressed! By following your instructions, I got jetty to run my  
webapp (using as mentioned by  
Greg - the old url did not work anymore).

Unfortunately, I didn't get very far because jetty doesn't know about  
my oracle drivers. With tomcat, I keep those in ${catalina.base}/ 
common/lib. I guess I could add them as dependencies tom my project  
so they end up in WEB-INF/lib, but then I could not deploy the war to  
tomcat anymore. Sounds like I should have different maven profiles  
fot these scenarios? Or does jetty look for additional jars in some  
location? That would make it a lot easier..

I also noticed that jetty expects my webapp at ${dasedir}/src/main/ 
webapp. Running mvn war:inplace works, but feels rather clumsy. I  
adds files to src that aren't sources, and I have to make sure I  
don't accidentally add them to svn.


On 02.11.2005, at 19:31, Jan Bartel wrote:
> Ralph,
> Try putting the following in your pom.xml:
>  <pluginRepositories>
>    <pluginRepository>
>      <id>mortbay-repo</id>
>      <name>mortbay-repo</name>
>      <url></url>
>    </pluginRepository>
>  </pluginRepositories>
> I should have the site doco for the plugin linked into the Jetty  
> website in the next day. In the meanwhile, all you should need to  
> do is to add these plugin config
> lines to your pom.xml:
>      <plugin>
>        <groupId>org.mortbay.jetty</groupId>
>        <artifactId>maven-jetty6-plugin</artifactId>
>        <configuration>
>          <scanIntervalSeconds>20</scanIntervalSeconds>
>        </configuration>
>      </plugin>
> That will cause the plugin to keep running and scan for class/lib  
> changes every 20secs. You
> can change it to whatever you prefer. There are also a couple of  
> other config options, but
> that should get you going.
> You can run it:
>   mvn org.mortbay.jetty:maven-jetty6-plugin:1.0:run
> You can shorten that to:
>   mvn jetty6:run
> but I'm not sure exactly how to do that other than as the plugin  
> developer (I followed the
> instructions at 
> java-plugin-development.html).
> Jason, is there any update on how we get the Jetty repository  
> mirrored to the central
> Maven2 repository?
> cheers
> Jan
> Ralph Pöllath wrote:
>> On 02.11.2005, at 16:55, Jan Bartel wrote:
>>> Ralph,
>>> Just a suggestion: if you want to run your webapp without having  
>>> to  create a war first,
>>> you could try the Jetty6 plugin. It is extremely lightweight, you
>>> don't have to have any external config files for it, plus it  
>>> will  automatically
>>> hot-redeploy your webapp whenever you change any class files or   
>>> dependencies. You can
>>> get it from scpexe://
>> Hi,
>> sounds great, but I can't figure out what to do with scpexe://  
>> I tried creating a   
>> pluginRepository in ~/.m2/settings.xml but can't get it to work.
>> Cheers,
>> -Ralph.
>>> Ralph Pöllath wrote:
>>>> Hi,
>>>> I've successfully compiled and installed the tomcat plugin from   
>>>> svn,  and tomcat:deploy works as expected. Now I'm wondering  
>>>> how  to best  use it.
>>>> For development, I'd like to avoid zipping up the war file for   
>>>> each  deployment. From gleaning at the source, I learned this   
>>>> means  deploying in local mode. I guess I have to pass a  
>>>> parameter  to the  tomcat plugin, but I can't figure out the  
>>>> parameter's  correct name (I  know, this question is related to  
>>>> plugins in  general, but I can't  find the documentation).
>>>> I tried
>>>> $ mvn -Dorg.apache.maven.plugins.maven-tomcat- 
>>>> plugin.mode=local   tomcat:deploy
>>>> and
>>>> $ mvn -Dorg.codehaus.mojo.tomcat.mode=local tomcat:deploy
>>>> but all I get is
>>>> [INFO] Deploying war remotely to /myProject on http://localhost:  
>>>> 8080/ manager
>>>> which means I'm running in the default remote mode.
>>>> I also noticed there's a mode called inplace, that uses a   
>>>> context.xml  file to deploy to tomcat, and requires the war  
>>>> plugin  to run in  exploded mode. What's the advantage of using  
>>>> inplace (I  assume you  get to use a path different from   
>>>>, and how  do I configure the war plugin?
>>>> How does everyone else use the tomcat plugin?
>>>> Thanks,
>>>> -Ralph.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message