The most stable way of ensuring this is to have your build based on maven or some build framework like it. This way you always have a way of ensuring what you deploy.
Regards Søren Den 11/09/2010 kl. 09.59 skrev Grzegorz Krugły <g...@karko.net>: > W dniu 11.09.2010 05:44, Joaquin Valdez pisze: >> Thank you! A simple cleaning seemed to do the trick. I always do a clean >> and build when developing, but apparently that stopped working. I use >> NetBeans. > > Yeah, NetBeans and its bad days - does anyone have a way to force it to > see all classes again in cases such as this one? It can sometimes stop > "seeing" a class that IS there until I open it up in the editor > (manually finding it since Ctrl-O neither doest find it). What's really > annoying is that it's then also not seen by Glassfish where the app is > deployed. For me it gets so bad sometimes (I fix one class, NB doesn't > see another) that I have to checkout a fresh copy of my project from SVN > to have it working again. > > Regards, > Grzegorz > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > Stripes-users mailing list > Stripes-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/stripes-users ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Stripes-users mailing list Stripes-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/stripes-users
