I use eclipse.
Step 1: Put your rebel.xml in your classpath
Step 2: Add this to your JVM args -Drebel.log=true ${javarebel_args}
The logs will say JavaRebel: Starting logging to file:
/Users/jarmstrong/Downloads/javarebel-2.0.1/JavaRebel.log and you know
your in the right place. Whenever it reloads a class a message is
printed to the log (or log and console in eclipse).
John-
On Sun, Aug 9, 2009 at 9:23 AM, Russell
Simpkins<[email protected]> wrote:
>
> What do you use for a dev environment? I tried to get that working in a jboss
> env with no luck. JavaRebel sounded pretty cool. I was bummed it didn't work.
> Russ
>
> ----------------------------------------
>> Date: Sun, 9 Aug 2009 09:17:06 -0700
>> Subject: Re: jetty hot deployment
>> From: [email protected]
>> To: [email protected]
>>
>> I use JavaRebel in my dev environment and its solved almost all of my
>> hot-swap issues. I recommend it highly.
>>
>> John-
>>
>> On Sun, Aug 9, 2009 at 2:45 AM, Martijn
>> Dashorst wrote:
>>> You need to start the Start class using the debugger. Then it works
>>> with hot swap.
>>>
>>> Martijn
>>>
>>> On Sat, Aug 8, 2009 at 8:26 PM, Anantha Kumaran wrote:
>>>> hi johannes
>>>> i tried using mvn jetty:run
>>>>
>>>> but i am getting the following error
>>>>
>>>> Configuring Jetty for project: jqms
>>>> Webapp source directory = E:\Netbeans\MyProjects\maven\jqms\src\main\webapp
>>>> Reload Mechanic: automatic
>>>> web.xml file =
>>>> E:\Netbeans\MyProjects\maven\jqms\src\main\webapp\WEB-INF\web.xml
>>>> Classes = E:\Netbeans\MyProjects\maven\jqms\target\classes
>>>> 2009-08-08 23:51:47.251::INFO: Logging to STDERR via
>>>> org.mortbay.log.StdErrLog
>>>> Context path = /jqms
>>>> Tmp directory = determined at runtime
>>>> Web defaults = org/mortbay/jetty/webapp/webdefault.xml
>>>> Web overrides = none
>>>> Webapp directory = E:\Netbeans\MyProjects\maven\jqms\src\main\webapp
>>>> Starting jetty 6.1.14 ...
>>>> 2009-08-08 23:51:47.581::INFO: jetty-6.1.14
>>>> 2009-08-08 23:51:48.145::INFO: No Transaction manager found - if your
>>>> webapp requires one, please configure one.
>>>> 2009-08-08 23:51:48.196::WARN: Failed startup of context
>>>> org.mortbay.jetty.plugin.jetty6pluginwebappcont...@1270107
>>>> {/jqms,E:\Netbeans\MyProjects\maven\jqms\src\main\webapp}
>>>> java.util.zip.ZipException: error in opening zip file
>>>> at java.util.zip.ZipFile.open(Native Method)
>>>> at java.util.zip.ZipFile.(ZipFile.java:114)
>>>> at java.util.jar.JarFile.(JarFile.java:133)
>>>> at java.util.jar.JarFile.(JarFile.java:97)
>>>> at
>>>> org.mortbay.jetty.webapp.TagLibConfiguration.configureWebApp(TagLibConfiguration.java:168)
>>>> at
>>>> org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1231)
>>>> at
>>>> org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
>>>> at
>>>> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:460)
>>>> at
>>>> org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(Jetty6PluginWebAppContext.java:124)
>>>> at
>>>> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
>>>> at
>>>> org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
>>>> at
>>>> org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
>>>> at
>>>> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
>>>> at
>>>> org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
>>>>
>>>> But when i run the application using the start.java file i works perfectly
>>>> and as i stated earlier hot deployment is not working
>>>>
>>>> On Sat, Aug 8, 2009 at 10:30 PM, Johannes Schneider
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I strongly suggest starting Jetty using Maven
>>>>>
>>>>> mvn jetty:run
>>>>>
>>>>> I add the following configuration
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> org.mortbay.jetty
>>>>> maven-jetty-plugin
>>>>>
>>>>> 1
>>>>> manual
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Reloading is triggered manually from the console. I like that behviour
>>>>> (so I can recompile/copy resources without restarting).
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>> Johannes Schneider
>>>>>
>>>>>
>>>>> Anantha Kumaran wrote:
>>>>>> hi
>>>>>> currently i am using ant and tomcat server (netbeans) to build my wicket
>>>>>> application.
>>>>>> The deployment and testing is taking lot of time.so i created a wicket
>>>>>> project using
>>>>>> the wicket-quickstart archetype.The problem is that i cannot view the
>>>>>> changes
>>>>>> made by me without restarting the jetty server.
>>>>>>
>>>>>> then i googled the net and found that i have to add scanIntervals and
>>>>> some
>>>>>> other settings.
>>>>>> but i donn't know where to add this in the start.java file.
>>>>>>
>>>>>>
>>>>>> it will be helpful if anyone post the modified start.java file which
>>>>> support
>>>>>> the hot deployment
>>>>>>
>>>>>>
>>>>>>
>>>>>> thanks
>>>>>> Anantha Kumaran
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: [email protected]
>>>>> For additional commands, e-mail: [email protected]
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>>> Apache Wicket 1.4 increases type safety for web applications
>>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0
>>>
>>> ---------------------------------------------------------------------
>>> 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]
>>
>
> _________________________________________________________________
> Get free photo software from Windows Live
> http://www.windowslive.com/online/photos?ocid=PID23393::T:WLMTAGL:ON:WL:en-US:SI_PH_software:082009
> ---------------------------------------------------------------------
> 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]
