Unfortunately I think that is the limit of eclipses 'integration'. I
have a coworker who uses it as well, and yes, it does just do a
complete redeploy for every change, and yes it sucks up a lot of time.
One simple way to get around this is to not use Eclipse to do the
deploy/undeploy. If you have a build script already that makes a
directory that you then WAR that should be enough. Do a manual
'deploydir', adn when you have a change just run a build and update
the directory. If you have a class change you'll need to restart GF,
jsp changes should be seen automatically. It's still not optimal, but
it might help.
-Nick
p.s. You can deploy a directory through the admin console or through
the command line, both options I believe are covered in the docs, but
it is fairly straight forward to do.
>
> How to do it?
>
> I switched from Tomcat, and use Eclipse plugin to start GlassFish.
> Every time when I update a client file (html,js), Eclipse auto start to run
> deploydir. As Ryan de Laplante wrote,
> 'I waste a lot of time doing this'!
>
>
>
>
> --
> View this message in context: http://www.nabble.com/GlassFish-V3-planning---What-do-*you*-want-in-GlassFish-V3--tf4720672.html#a13810407
> Sent from the java.net - glassfish users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>