Maven multi-module projects

[LMnet]

I'm trying to use spring-loaded on maven multi-module project. Simplified structure:

parent
|-- war project
`-- jar project

War project has jar project in maven dependencies. War project deployed in Tomcat with spring-loaded java agent. IDE - Intellij IDEA.
When I modify code in war project, IDE compile *.java files in *.class files and place this files in 'classes' folder and spring-loaded successfully reload this code. But when I modify code in jar project, hot reload didn't work, because jar project locate in 'lib' folder in builded war as *.jar file. I know, that spring-loaded can't reload jar files, but maybe I can modify my build somehow? Any tips?

[rvowles]

Don't use multi-module builds? Thats an easy one.

[LMnet]

It's not an option for me. My project is very old and I can't change it structure.

[padcom]

First of all not using multiple modules for any application bigger than a hello-world is kinda insane from maintainability perspective - so good that you have it separated. I think it'd be a great feature of spring loaded to support reloading classes from set of predefined (or automatically-guessed maybe? Maven/Gradle?) locations instead of just from the single folder that it does at the moment.

[rvowles]

Multi-module != multiple module. Multi-module is a specific reactor abuse
anti pattern endemic to Maven and encouraged in Gradle.

Spring loaded does load from multiple locations? Anything on the class path?
On 16 Jul 2014 23:19, "Matthias Hryniszak" notifications@github.com wrote:

First of all not using multiple modules for any application bigger than a
hello-world is kinda insane from maintainability perspective - so good that
you have it separated. I think it'd be a great feature of spring loaded to
support reloading classes from set of predefined (or automatically-guessed
maybe? Maven/Gradle?) locations instead of just from the single folder that
it does at the moment.

—
Reply to this email directly or view it on GitHub
#70 (comment)
.

[LMnet]

Almost all java projects builds with maven use multi-module projects. You can love it or not, but it's reality. And now, we talking about spring-loaded, not about maven.

By the way - JRebel can handle multi-module projects.

[rvowles]

He asked for solutions, the easiest one is to not used a bad practice.

JRebel you pay for. Spring Loaded is free - there is no reason you can't
create a patch.

On Thu, Jul 17, 2014 at 2:44 PM, LMnet notifications@github.com wrote:

Almost all java projects builds with maven use multi-module projects. You
can love it or not, but it's reality. And now, we talking about
spring-loaded, not about maven.

By the way - JRebel can handle multi-module projects.

—
Reply to this email directly or view it on GitHub
#70 (comment)
.

---

Richard Vowles,
Groovy, Java, Javascript, AngularJS

ph: +64275467747, web: www.google.com/+RichardVowles

[presoft]

I propose a workaround if you are using a Linux machine:
i.e. if you have two modules core and website

you can run
lsyncd -delay 0 -rsync /path-to-core/target/classes /path-to-website/target/website-extracted/WEB-INF/classes

This will keep syncing you class files from core to website.

Next thing you can add below line to /path-to-tomcat/bin/setenv.sh

rm /path-to-website/target/website-extracted/WEB-INF/lib/core-BUILD-0.1.jar

This would remove the jar file before apache tomcat starts.

Hope this helps.

[todoubaba]

The issue is still open, it really slow me down

[padcom]

I propose we stop complaining about this and create a pull request to
implement this. Otherwise JRebel (I'm not affiliated but I am an active
user and I'm loving it) does the job.

2015-03-24 2:12 GMT+01:00 todoubaba notifications@github.com:

The issue is still open, it really slow me down

—
Reply to this email directly or view it on GitHub
#70 (comment)
.

[yohanliyanage]

+1 for this enhancement.

[aclement]

1.2.4 dev builds now support a basic form of watching and reloading from jar files. Use the option watchJars. For example:

-Dspringloaded=watchJars=foo.jar:bar.jar

will cause classes loaded from foo.jar and bar.jar to be considered reloadable and those jars will be watched. If the timestamps of the classes being watched within those jars changes, they will be reloaded. Note jars are not fully qualified paths.

[amuniz]

Nice! Thanks!

[tmattsson]

If you're using IntelliJ and developing a web project you can configure the output layout of your artifact to put the compile output of your jar module into WEB-INF/classes. They'll then be seen by spring loaded and reloaded.

File > Project Structure... > Artifacts > select your artifact > on the Output Layout tab remove the module form WEB-INF/lib and add it to WEB-INF/classes.

When you reimport maven projects, after adding dependencies for instance, IntelliJ configures the artifact again and the change is lost, so you need to remember to redo it afterwards.