- This topic has 5 replies, 3 voices, and was last updated 17 years, 1 month ago by
.
-
Posts
-
Robert,
I think Nipun may have misunderstood your request, but MyEclipse definately supports debugging apps that it doesn’t handle deploying. You just have to make use of the Remote Debugging feature in MyEclipse, doc outlined here:
http://www.myeclipseide.com/documentation/quickstarts/remotedebugging/Also you will want to make sure your <javac> target in your Ant script is building your source with debugging turns on AND all 3 levels of debugging information available (please see Ant docs on the exact args… I think it’s source/lines and something else).
Is there any build tool that MyEclipse will support in this manner? Any way to allow MyEclipse to deploy my project but specify rules for that deployment? MyEclipse deployment seems static in this regard, though I wish I am wrong about it.
What kind of rules?
Thank you so much. I think this is what I’m looking for. I knew there had to be someway to debug without deploying through MyEclipse.
Regarding the rules comment, I just meant something like deploy setting aside from external deploys or custom locations that I didn’t know about. I’ve been using MyEclipse for 5 years and I’m still learning about the features.
Appreciate the heads up on the Ant args too. 🙂
-Robert
Regarding the rules comment, I just meant something like deploy setting aside from external deploys or custom locations that I didn’t know about. I’ve been using MyEclipse for 5 years and I’m still learning about the features.
If you check under your project properties, under MyEclipse > Web and the Deployment tab, you can setup all sorts of library packaging rules and things like that, but arbitrary rules, no we don’t support that.
Also, you *may* have problems debugging your JSP pages if your project is not a Web Project that MyEclipse can map the JSP source locations back to. So if it’s a plain Java project, you probably aren’t going to be able to debug JSPs.
