+1 Arnaud
On Fri, Sep 12, 2008 at 3:01 PM, Mauro Talevi <[EMAIL PROTECTED]>wrote: > +1 > > > Brian E. Fox wrote: > >> Attempt #2. I reworked the poms to get things lined up with the new site >> and help generation. >> >> >> The plugin is staged here: >> >> http://people.apache.org/~brianf/stage/<http://people.apache.org/%7Ebrianf/stage/> >> >> >> The site is staged here: >> >> http://people.apache.org/~brianf/site-stage/plugins/maven-enforcer-plugi<http://people.apache.org/%7Ebrianf/site-stage/plugins/maven-enforcer-plugi> >> n/ >> >> NOTE: due to MSITE-358, the images are messed up in the banner but will >> be correct when it gets moved. >> >> ing that though. >>well if you downloaded wtp, just dump that eclipse and extract it again, > > you keep your workspace and it should just work. When i get "arb" stuff i > > delete my servers in eclipse and just create them again. I think I downloaded an EE version of Eclipse which had it pre-packaged. I've tried re-creating the server in Eclipse but I still get the same error. :( >> did you enable a firewall at some point. your error looks like > > the debugger is unable to open a socket to the instance tomcat. I wish it were that simple. I didn't touch any firewall - and it gives the same error when running without attaching the debugger. Boo! Thanks for the input - I will probably try and re-setup Eclipse. --- In [email protected], "Johannes Nel" <[EMAIL PROTECTED]> wrote: > > inline. > > On Sun, Sep 14, 2008 at 8:33 AM, ansury2 [EMAIL PROTECTED] wrote: > > > I'm having one of those infamous "IT WTH?!" moments. You know, the > > kind where "you have no idea what you did to break it"? I have no > > idea what I did to break this apparently fragile as hell project > > setup. > > > > I'm using Eclipse's "Servers view" functionality to startup Tomcat. > > Everything worked fine for say two months until suddenly I found that > > I was unable to shutdown Tomcrap. No idea why, maybe I started/ > > stopped too quick or something, but when I tried to shut it down, > > Eclipse just sat there for awhile and it timed out: "unable to > > shutdown server" or whatever rubbish. > > > > > > > > > >> just ignore that, it does not shutdown sometimes, a little red button in > > eclipse does force it. > > > > Eclipse restart didn't help, I think at that point I was getting > > this error message (instead of a timeout). So I figured I'd reboot - > > still NO good. Still getting this stupid error message. Uhoh. I have > > to think about this? @#$%! > > > > Apparently I made a mistake trusting this "magic" setup to work > > without fully understanding HOW it works. (The Eclipse docs are > > worthless for understanding what it's doing.) Instead of deploying > > the application to Tomcat's webapps directory in it's normal > > installed location, how a normal person would design this feature, it > > deploys everything into some bizzare folder in your workspace > > metadata and somehow it just works. (\EclipseWS\.metadata\.plugins > > \org.eclipse.wst.server.core\tmp0\wtpwebapps) (HUH? WTH? Why?) > > > > > > >> this is the way eclipse works, you might not want to deploy to your > > actual web server, even when developing plugins eclipse works like this. > > this allows you to use separate config files for your development and your > > local webserver as well. > > > > > > > > Sorry for sounding pissed, but I am - I've wasted basically two days > > on this trash with no idea where to go from here. Do I re-install > > Tomcat? Eclipse? Setup my workspace again? Why should I have to do > > all that? This is the kind of stuff in IT that makes you want to say > > "screw it all" and just go into management so the other poor suckers > > have to lose their hair doing stuff like this! lol > > > > > > >>well if you downloaded wtp, just dump that eclipse and extract it again, > > you keep your workspace and it should just work. When i get "arb" stuff i > > delete my servers in eclipse and just create them again. > > > > I doubt anyone can help with this bizzare problem (it's probably more > > of an Eclipse issue but it only spews this error when I deploy my > > Flex project!) but here's the console output. Note the > > NullPointerException within NioEndpoint: > > > > >> did you enable a firewall at some point. your error looks like > > the debugger is unable to open a socket to the instance tomcat. > > >
