Hi David,

While I do not use Eclipse (I use Intellij Idea), I am pretty confident that 
this would apply to eclipse as well.

I have used remote debugging with the integration tests (via 
-Dmaven.surefire.debug) and I am pretty confident that it would work well with 
your use case. It seems to be a recommended way debugging Jetty based 
applications.
http://www.eclipse.org/jetty/documentation/current/debugging-with-eclipse.html

Abe

> On Oct 13, 2015, at 8:52 PM, David Robson <[email protected]> 
> wrote:
> 
> Hi Jarcec/Colin,
> 
> I had Eclipse setup with Tomcat before where I could debug the code easily. 
> So I ran Tomcat in debug mode from Eclipse, then when I changed a file in 
> Eclipse it would automatically redeploy the app, and I could continue 
> debugging.
> 
> I can't work out how to do this with Jetty yet - do you have a document on 
> how to setup Eclipse to debug Sqoop?
> 
> I tried to run "org.apache.sqoop.server.SqoopJettyServer" from Eclipse - 
> after much messing around with classpaths I got it to run but then it won't 
> run the actual job. It says "failed to find jar for class: 
> org.apache.sqoop.common.MapContext". I guess because Eclipse is running it 
> off the class files rather than jar files.
> 
> Can you please advise the best way to set this up?
> 
> Thanks,
> 
> David
> 
> -----Original Message-----
> From: Jarek Jarcec Cecho [mailto:[email protected]] On Behalf Of Jarek Jarcec 
> Cecho
> Sent: Thursday, 1 October 2015 2:09 AM
> To: [email protected]
> Subject: Re: Heads up: Migration from Jetty to Tomcat will happen soon 
> (SQOOP-910)
> 
> SQOOP-910 was just committed. Please don’t hesitate and let me or Colin now 
> if you see any issues.
> 
> Jarcec
> 
>> On Sep 29, 2015, at 8:00 AM, Jarek Jarcec Cecho <[email protected]> wrote:
>> 
>> I wanted to gave heads up to Sqoop dev community - Colin is working on 
>> SQOOP-910 that will switch Sqoop from Tomcat to Jetty. The patch is almost 
>> ready to go and I’m expecting that I’ll commit it in a day or two. The “user 
>> visible” commands had remained, so I’m not anticipating huge impact, but 
>> nevertheless :)
>> 
>> Jarcec
> 

Reply via email to