Awesome! This is what worked for me too... mvn jetty:run
<build>
<plugins>
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<configuration>
<contextPath>/sis-webapp</contextPath>
<webApp>${basedir}/target/sis-webapp-0.2-incubating-SNAPSHOT.war</webApp>
</configuration>
<executions>
<execution>
<id>start-jetty</id>
<phase>pre-integration-test</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
<scanIntervalSeconds>0</scanIntervalSeconds>
<daemon>true</daemon>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
Would everyone like to see a combo of these added to trunk? I find that Jetty
is quick and easy when deploying an application for testing/demo purposes.
Adam
On Feb 11, 2012, at 12:55 PM, Alan D. Cabrera wrote:
> Greg is correct. Here's what works for me for this project
>
> <build>
> <plugins>
> <plugin>
> <groupId>org.mortbay.jetty</groupId>
> <artifactId>maven-jetty-plugin</artifactId>
> <version>6.1.21</version>
> <configuration>
> <!-- Uncomment this if you want recompilation from your
> IDE to trigger reloading the app -->
> <scanIntervalSeconds>10</scanIntervalSeconds>
> <contextPath>/sis</contextPath>
> <systemProperties>
> <systemProperty>
> <name>org.apache.commons.logging.Log</name>
>
> <value>org.apache.commons.logging.impl.Jdk14Logger</value>
> </systemProperty>
> <systemProperty>
> <name>java.util.logging.config.file</name>
>
> <value>./src/test/resources/logging.properties</value>
> </systemProperty>
> </systemProperties>
> </configuration>
> </plugin>
> </plugins>
> </build>
>
> Hit:
>
> http://localhost:8080/sis/demo.jsp
>
>
> Regards,
> Alan
>
> On Feb 11, 2012, at 9:32 AM, Greg Reddin wrote:
>
>> I'm not a Jetty expert but I wonder if it would help to move the config down
>> to the sis-webapp project instead of trying to do it from the parent
>> project.
>>
>> Sent from my mobile device.
>>
>> On Feb 11, 2012, at 11:19 AM, Adam Estrada <[email protected]> wrote:
>>
>>> All,
>>>
>>> I would like to deploy the SIS web application with Jetty. Maven and Jetty
>>> work together well if you know what you are doing. I have limited knowledge
>>> of how Maven works so this is my stab at it. The idea here is to mvn
>>> jetty:deploy-war (or jetty:run/start) to launch the web app.
>>>
>>> <plugin>
>>> <groupId>org.mortbay.jetty</groupId>
>>> <artifactId>maven-jetty-plugin</artifactId>
>>> <configuration>
>>>
>>> <webApp>${basedir}/sis-webapp/target/sis-webapp-0.2-incubating-SNAPSHOT.war</webApp>
>>>
>>> <webAppSourceDirectory>${basedir}/sis-webapp/target</webAppSourceDirectory>
>>>
>>> <webXml>${basedir}/sis-webapp/target/sis-webapp-0.2-incubating-SNAPSHOT/WEB-INF/web.xml</webXml>
>>> <contextPath>/sis-webapp</contextPath>
>>> </configuration>
>>> <executions>
>>> <execution>
>>> <id>start-jetty</id>
>>> <phase>test-compile</phase>
>>> <goals>
>>> <goal>deploy-war</goal>
>>> </goals>
>>> <configuration>
>>> <daemon>true</daemon>
>>> <reload>manual</reload>
>>> </configuration>
>>> </execution>
>>> </executions>
>>> </plugin>
>>>
>>> When Jetty runs, its still looking for sis-parent. Can anyone lend a hand
>>> so that I can deploy the web app using Maven?
>>>
>>> Adam
>
