I'm using eclipse, but it's a big legacy project with lots of custom build needs. So it isn't too easy to setup a smooth integrated build environment...
I suddenly realized that it shouldn't be too hard decorating the ClassNameLocator and strip away duplicates from its result. Seems logical when this is a requirement that is very specific to our setup. Thanks for the hints anyway :) Inge On Sun, Jul 11, 2010 at 5:03 PM, Thiago H. de Paula Figueiredo < [email protected]> wrote: > On Sun, 11 Jul 2010 11:45:24 -0300, Inge Solvoll <[email protected]> > wrote: > > As I said, it's convenient. Our application consists of many different >> maven projects that need to be assembled into one web container as jars. >> It's a >> complex aggregated application, and it would require extra work to provide >> a specific setup for development that doesn't use jar files. Espescially >> since it works the way we do it now, and it doesn't seem like the biggest >> hack in the world to me. The classloader was probably built like this >> (handling >> duplicates by priority) for a reason :) >> > > Using m2eclipse, I can open all the projects that comprise my application, > edit the sources of each one of them and have the changes being picked up > instantly. > If you're not using Eclipse, I can see that your setup is needed. > > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
