WOW! Multi-module in Tapestry with Live Class Reloading is fantastic! Thanks 
for pointing me in the right direction Thiago!

To get live class reloading work for the common module in IntelliJ: Open 
Project Structure, Project Settings > Modules. Select the common module > Paths 
> Compiler output. Set Output path to the same path as the main project output 
path.

I have created a multi-module maven demo project for test and documentation. A 
page in the main project includes a component-class from the common module. I 
have demo of using assets (img and js-modules) and IoC service. Everything 
works with Live Class Reloading.

I am using a top-level pom (dependencyManagement, pluginManagement, 
properties), a modules pom (maven-root), the main project (war), and the common 
module (jar).

The main project and common module is both created from mvn 
-DarchetypeArtifactId=quickstart ..., with necessary modification.

I have documented all steps to make everything working in IntelliJ (plugin 
configuration etc).


> 
> As long as the compiler target folder of the included
> library/module/subproject is included in the classpath of the main
> project, regardless of what tool you're using, live class reloading will
> work after a class in the library/module/subproject is recompiled. Maybe
> Eclipse makes it easier because it compiles automatically on save. I don't
> know how IDEA handles this.
> 
> 
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to