Hi Allan,
On Apr 29, 2008, at 9:01 PM, Allan Lewis wrote:
hdockter wrote:
Here is how I understand your dependencies.
The maven-plugin has a compile dependency on generator and modeling.
The maven-plugin contains the actuals tests. The tests project just
triggers those tests. The generator and modeling project are
independent.
Is this right?
Are the tests in the Maven plugin JUnit or TestNG tests?
I just want to be sure before I get into any details.
- Hans
Just about. Here is some more detail:
- generator and modeling have no dependencies (aside from commons,
etc).
They are independent of each other
- maven-plugin has a compile dependency on both generator and
modeling.
there are no tests in the maven-plugin project
- the tests project contains a number of JUnit tests, along with
the config
files needed to configure and use the generator and modeling
components.
The tests POM configures execution(s) of maven-plugin within its build
section by pointing maven-plugin at the needed config files. The
execution(s) of maven-plugin happen before compilation in the
generate-sources phase of the tests project to generate the sources
which
are tested by my JUnits.
Thanks for the info. Now I understand your layout. I have a solution
in mind which would work with the current Gradle release.
Unfortunately I'm busy for the next 5 hours. I gonna give this a try
late.
You definitely have a use case which was not taken into consideration
in the design of Gradle. I'd like to discuss this later on.
- Hans
--
View this message in context: http://www.nabble.com/Advice-on-multi-
project-build-source-setup-tp16960881p16967820.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
