Re: Class reloading in custom component library

2010-06-04 Thread paha
any additional work when using embedded jetty -- View this message in context: http://old.nabble.com/Class-reloading-in-custom-component-library-tp28766834p28779827.html Sent from the Tapestry - User mailing list archive at Nabble.com. ---

Re: Class reloading in custom component library

2010-06-04 Thread Thiago H. de Paula Figueiredo
On Fri, 04 Jun 2010 09:28:45 -0300, Henrik Schlanbusch wrote: The problem is that the compiled classes are not always picked up by tapsetry, so I have to look a bit more into this. As long as the classes are recompiled and the .class files are put in some folder included in the classpath,

Re: Class reloading in custom component library

2010-06-04 Thread Henrik Schlanbusch
Inge Solvoll gmail.com> writes: > > I'm using file synch in eclipse to copy the newly compiled files to > webapp/WEB-INF/classes. If the class is found there, it overrides the one in > the jar. > > On Fri, Jun 4, 2010 at 7:56 AM, Nicolas Bouillon bouil.org> wrote: > > > I'm very interested t

Re: Class reloading in custom component library

2010-06-04 Thread Inge Solvoll
I'm using file synch in eclipse to copy the newly compiled files to webapp/WEB-INF/classes. If the class is found there, it overrides the one in the jar. On Fri, Jun 4, 2010 at 7:56 AM, Nicolas Bouillon wrote: > I'm very interested too if there is a solution to this problem. > > On Thu, 3 Jun 20

Re: Class reloading in custom component library

2010-06-03 Thread Nicolas Bouillon
I'm very interested too if there is a solution to this problem. On Thu, 3 Jun 2010 12:33:50 + (UTC), Henrik Schlanbusch wrote: > Hi > > I have setup a project in maven 2 where the lowest project > (parent) has two sub modules, one with the webapp > (tapestry 5) and one with a separate cust

Class reloading in custom component library

2010-06-03 Thread Henrik Schlanbusch
Hi I have setup a project in maven 2 where the lowest project (parent) has two sub modules, one with the webapp (tapestry 5) and one with a separate custom made component library. This means that I have three modules to build (parent, webapp and components). Webapp has a dependency to compon