The way I do this is to use my IDE's dependency analysis to have my
IDE do a "Make" (which rebuilds all the downstream changes)... then
before I commit I will do a "mvn clean verify" to make sure that my
changes are good
Yes my IDE does the analysis too.
The problem is in my colleague.
He
javac will only recompile classes that have changed. it does not do
dependency analysis, so a breaking change will only cause a compile
failure until you do clean
Thank you for clarification.
Is there any way (except explicit 'clean') to turn on dependency
analysis during compilation.
The
Hi Wayne,
The app version is '1.0-SNAPSHOT'.
The Maven is:
$ mvn --version
Apache Maven 3.0.3 (r1075438; 2011-02-28 19:31:09+0200)
Maven home: /opt/maven
Java version: 1.6.0_29, vendor: Sun Microsystems Inc.
Java home: /opt/jdk1.6.0_29/jre
Default locale: en_US, platform encoding: UTF-8
OS name:
Hi All,
It seems that my question has an obvious answer. Unfortunately googling
didn't give me a good one.
Prerequisites:
I have a classical multi-module project. The root POM declares two
modules: 'api' and 'impl'.
These modules have references to the parent.
The module 'api' contains defi
