Re: t5: debugging with jetty

2008-08-22 Thread Filip S. Adamsen
I use IntelliJ IDEA as well. But I simply create a Maven configuration 
that runs mvn jetty:run and launch it as a debugging session.


-Filip

On 2008-08-22 17:32, César Lesc wrote:

I set MAVEN_OPTS, launch jetty with maven and just attach the debugger's IDE,
in IntelliJ IDEA is called Remote Debug

my debug script es like this:

export MAVEN_OPTS="-Xdebug -Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,address=5005,server=y,suspend=n"

mvn jetty:run



César.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: t5: debugging with jetty

2008-08-22 Thread César Lesc
I set MAVEN_OPTS, launch jetty with maven and just attach the debugger's IDE,
in IntelliJ IDEA is called Remote Debug

my debug script es like this:

export MAVEN_OPTS="-Xdebug -Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,address=5005,server=y,suspend=n"

mvn jetty:run



César.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: t5: debugging with jetty

2008-08-22 Thread limonn

Hi Thank you for your replay.

But if I do debug as I don't think I have the jetty option, only the server
that is tomcat, m I missing any plugin ?

Regards

Raul Rosenzvaig



Jonathan Barker wrote:
> 
> I use Jetty 5 Plus run in Eclipse via the JettyLauncher plugin.
> 
> I occasionally use the Debug As in Eclipse, but most of the time I just
> Run
> and use the great T5 error reporting.
> 
> When using Debug As, Eclipse will often grumble that it can't replace the
> (running) code.  I frequently find that I can keep going and everything is
> OK, but a restart is advisable and usually fast.
>  
> I should also comment that what I find when I use Debug As is usually
> stuff
> that would have easily been caught had I written the unit test that I
> should
> have started with.
> 
> Jonathan
> 
> 
>> -Original Message-
>> From: limonn [mailto:[EMAIL PROTECTED]
>> Sent: Friday, August 22, 2008 09:19
>> To: users@tapestry.apache.org
>> Subject: t5: debugging with jetty
>> 
>> 
>> How do you guys debug using jetty, any guidance steps for that ?
>> 
>> How that affects the feature of no need to restart jetty for changes to
>> show
>> ?
>> 
>> Thank s in advance
>> --
>> View this message in context: http://www.nabble.com/t5%3A-debugging-with-
>> jetty-tp19107119p19107119.html
>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>> 
>> 
>> -
>> 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]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/t5%3A-debugging-with-jetty-tp19107119p19108221.html
Sent from the Tapestry - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: t5: debugging with jetty

2008-08-22 Thread Tobias Wehrum

Hi limonn,

to start Jetty, we use an org.mortbay.jetty.Server object started in a 
simple public static void main - so we can debug our program like any 
other java program too.
The "no restart needed"-Feature is enhanced by debugging the application 
this way: When simply run, "no restart needed" applies on to the 
Tapestry package, but when we are in Debugging mode, we can (nearly) 
change any other area of the application runtime.


- Tobias

limonn schrieb:

How do you guys debug using jetty, any guidance steps for that ?

How that affects the feature of no need to restart jetty for changes to show
?

Thank s in advance
  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: t5: debugging with jetty

2008-08-22 Thread Jonathan Barker
I use Jetty 5 Plus run in Eclipse via the JettyLauncher plugin.

I occasionally use the Debug As in Eclipse, but most of the time I just Run
and use the great T5 error reporting.

When using Debug As, Eclipse will often grumble that it can't replace the
(running) code.  I frequently find that I can keep going and everything is
OK, but a restart is advisable and usually fast.
 
I should also comment that what I find when I use Debug As is usually stuff
that would have easily been caught had I written the unit test that I should
have started with.

Jonathan


> -Original Message-
> From: limonn [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 22, 2008 09:19
> To: users@tapestry.apache.org
> Subject: t5: debugging with jetty
> 
> 
> How do you guys debug using jetty, any guidance steps for that ?
> 
> How that affects the feature of no need to restart jetty for changes to
> show
> ?
> 
> Thank s in advance
> --
> View this message in context: http://www.nabble.com/t5%3A-debugging-with-
> jetty-tp19107119p19107119.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
> 
> 
> -
> 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]