I am unsure. I had problems detecting my test classes while running inside a jetty. I solved this issue by using some kind of a directory bundle (lame name but hadnt found something better yet). Since I saw this in the plastic IOC part I guess tapestry also can deal with fragmented classpath directories.
I will see it tomorrow or sunday I guess. I just wanted to ensure that there is nothing blocking me and I waste time trying to fix it... . So I will be confident and report back my findings. 2013/10/18 Thiago H de Paula Figueiredo <thiag...@gmail.com> > On Fri, 18 Oct 2013 11:22:40 -0300, Martin Kersten < > martin.kersten...@gmail.com> wrote: > > I have the problem that all those projects render the classes to: >> >> parent.project/classes >> web.project/classes >> >> using maven jetty:run gets all those classes copied to a new location >> what makes the startup dead slow (several seconds). I use an emebedded jetty >> where I just give the webapp directory location. I have no way to copy >> all those classes automatically to this location only the main project (not >> the parent one). >> >> So I need information if someone using the parent+web spliting is using >> another mechanism to run jetty and how it behaves. >> > > Ordinary classpath settings are the solution, as you're running Jetty > embedded or via RunJettyRun. You don't actually need to copy everything to > a single place: you just have to put everything in the classpath in one way > or another. > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.com.br > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org> > For additional commands, e-mail: users-h...@tapestry.apache.org > >
