Em Mon, 27 Oct 2008 18:32:07 -0300, Alex Kotchnev <[EMAIL PROTECTED]>
escreveu:
Maybe one of the more experienced folks on the list can chime in on
how best to handle the development workflow with a module that's still
under
development.
1) Use Jetty for development. When tested in Jetty, test in Tomcat or
Glassfish or JBoss or whatever. I haven't had almost any issues this way.
2) In Eclipse, I use Sonatype's m2eclipse. It has the really helpful
feature that, when one project A has B as a dependency and both are
projects, when I open project B, it is automatically added to A's
classpath. When B is closed, A's classpath is automatically changed to
include B's jar from the local Maven repository.
3) The module is a project, the web app is another. While developing, I
keep both open and I use @Submodule(TheModule.class) in the web app's
AppModule, as the module JAR is not in the classpath.
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
Consultor, desenvolvedor e instrutor em Java
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
