On Tue, 04 Aug 2015 10:27:01 -0300, Svein-Erik Løken <sv...@jacilla.no>
wrote:
>> 4) You can't use Tapestry's Live Class Reloading on any class in the
>> common
>> JAR (e.g. Tapestry IOC service implementation classes).
>
> I think 4) is the biggest downside in a multi-module project. Do you
> think Tapestry can do a Live Class Reloading of the common JAR
included
> with contributeCoreLibComponentClasses?
If this is about Eclipse (I'm not sure about other IDEs, since I haven't
used any besides Eclipse for many years), if you have all the projects
open at the same time, you can use live class reloading on all of them
at
the same, and I do this all the time.
Really! I am using IntelliJ IDEA Ultimate and NEED this functionality.
Today I need to recompile all maven projects and restart jetty for every
change to components and JavaScript modules (all resources) in the
common JAR.
If you're including your common project as a JAR in the classpath of your
main project, live class reloading will never work. On the other hand, if
you include your common project's target folder (where the .class files
are generated) in the classpath of your main project, it should work. I'm
sure there's a way of doing that in IDEA. There has to be one. IDEA would
suck if there wasn't, and apparently IDEA is the opposite of suck. :)
--
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
