I've forgot to mention that I'm using the Jetty eclipse version:
[quote]
<packaging>war</packaging>
<name>Some Security Shiro-jsp Apache Click Webapp</name>
<build>
<plugins>
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>jetty-maven-plugin</artifactId>
<version>7.0.1.v20091125</version>
<configuration>
<reload>manual</reload>
</configuration>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>tomcat-maven-plugin</artifactId>
<!--configuration>
<url>http://www.mydomain.com:1234/mymanager</url>
</configuration-->
</plugin>
</plugins>
</build>
[/quote]
Gilberto
On Tue, Aug 24, 2010 at 2:50 PM, Beto <[email protected]> wrote:
> Hi Luther,
>
> I'm using Netbeans as well and found the same problem. But the Alex
> Kotchenev's post[1] help me a lot.
>
> Hth,
>
> Gilberto
>
> [1]
> http://www.troymaxventures.com/2009/05/rad-w-tapestry-5-netbeans-67-maven-and.html
>
>
> On Tue, Aug 24, 2010 at 12:34 PM, LutherBaker <[email protected]>wrote:
>
>>
>> My question is about just general workflow development. I'm having a hard
>> time changing files and having Jetty pick up the changes without a manual
>> restart and I'm sure I must be missing something.
>>
>> Assuming Netbeans, I've created a maven project, included the Click
>> dependencies and invoked jetty via maven command "jetty:run". Jetty starts
>> up just fine and all the "quickstart guide" pages show up. If I change
>> text
>> on a page, I don't see the changes unless I shutdown and restart jetty.
>> The
>> same goes for IntelliJ - changing the *htm files isn't visible without a
>> restart. I also changed and saved the Home page class file - still, no
>> restart or change in page appearance.
>>
>> I fired up Eclipse and imported the same Maven project and it did not
>> detect
>> changes to the htm files ... but it DID detect changes to the class file -
>> after which, it restarted and the page was reloaded.
>>
>> My jetty plugin config includes <scanIntervalSeconds>:
>>
>> <plugin>
>> <groupId>org.mortbay.jetty</groupId>
>> <artifactId>maven-jetty-plugin</artifactId>
>> <version>6.1.10</version>
>> <configuration>
>> <scanIntervalSeconds>4</scanIntervalSeconds>
>> <stopKey>foo</stopKey>
>> <stopPort>9999</stopPort>
>> <webAppConfig>
>> <contextPath>/projx</contextPath>
>> <tempDirectory>src/main/webapp</tempDirectory>
>>
>>
>> <defaultsDescriptor>src/main/config/jetty/webdefault.xml</defaultsDescriptor>
>> </webAppConfig>
>>
>> <jettyConfig>src/main/config/jetty/jetty.xml</jettyConfig>
>> <connectors>
>> <connector
>> implementation="org.mortbay.jetty.nio.SelectChannelConnector">
>> <port>9090</port>
>> <maxIdleTime>60000</maxIdleTime>
>> </connector>
>> </connectors>
>> </configuration>
>> </plugin>
>>
>> Is there some suggested workflow best practice? Which IDE works best out
>> of
>> the box ... and what is the best way to build/work on a project - use the
>> native WTP and download all the JARS? or can I leverage maven ... or is
>> there a hybrid approach that I am missing.
>>
>> Also, if this is velocity, is it possible that Velocity will cache these
>> files? Is there a parameter I can supply that forces velocity not to do
>> this? I was surprised that Eclipse detected changes to the classpath files
>> -
>> but not maven's webapp directory.
>>
>> Thanks in advance for any suggestions (looking for solutions other than
>> zeroturnaround ... but if that is required ....)
>>
>> -Luther
>>
>> --
>> View this message in context:
>> http://click.1134972.n2.nabble.com/Optimal-Development-Cycle-tp5457365p5457365.html
>> Sent from the click-user mailing list archive at Nabble.com.
>>
>
>
