The reactor mode would only help if you had a parent above A and B
that was aggregating both projects. Then all of them would be in the
reactor together and you'd be able to influence what gets built. (by
default it would build them in the correct order based on
dependencies).
On Tue, Aug 4, 2009
Hi
I have a problem, which might be solved using Maven's make-like reactor mode -
but I'm not sure if it is!
Consider the following projects/modules
Project A
+--- Module A1
+--- Module A2
Project B
+--- Module B1
+--- Module B2
Now, if A1 depends on B1, but B2 depends on A2, it's impossible t
eptember 29, 2005 11:39
To: Maven Users List
Subject: RE: Cross-project dependencies on unit test code
Answers:
1) There needs to be an API package so that the Impl and Test packages can both
depend on it (otherwise your base tests would depend on the impl classes, but
your impl depends on the ba
unit tests?
-Original Message-
From: Tim Dysinger [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 28, 2005 12:39
To: [EMAIL PROTECTED]; Brett Porter
Cc: Maven Users List
Subject: Re: Cross-project dependencies on unit test code
Ok. Let's say we did it that way. We are still
-Original Message-
From: Tim Dysinger [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 28, 2005 12:39 PM
To: [EMAIL PROTECTED]; Brett Porter
Cc: Maven Users List
Subject: Re: Cross-project dependencies on unit test code
> Ok. Let's say we did it that way. We are still fa
On Wed, 2005-09-28 at 09:39 -0700, Tim Dysinger wrote:
> Ok. Let's say we did it that way. We are still faced with the same
> problem with the maven-eclipse-plugin. Maven-eclipse-plugin does not
> like having your source and test directories the same.
>
> ${basedir}/src/java
> ${basedir}/src/
-
From: Tim Dysinger [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 28, 2005 12:39
To: [EMAIL PROTECTED]; Brett Porter
Cc: Maven Users List
Subject: Re: Cross-project dependencies on unit test code
Ok. Let's say we did it that way. We are still faced with the same
problem with the
Ok. Let's say we did it that way. We are still faced with the same
problem with the maven-eclipse-plugin. Maven-eclipse-plugin does not
like having your source and test directories the same.
${basedir}/src/java
${basedir}/src/java
I can't do this without using eclipse. The plugin, in this c
This has been asked 2 or 3 times this week. IIRC someone was going to
write up their experience doing it? Would anyone like to volunteer to
add it to the wiki?
- Brett
On 9/28/05, Raphaël Piéroni <[EMAIL PROTECTED]> wrote:
> Hi Tim,
>
> May you try with something like this :
> wrapper
> +- core-a
Hi Tim,
May you try with something like this :
wrapper
+- core-api
+- core-test (depend only on api)
+- core-impl (with some test cases - depends on core-api and core-test
the later with scope test)
+- use-core-1 (depend on core-impl, depends on core-test at scope test -
the test cases must not
I have a "best practices" question.
I have a multi-project setup with three sub-projects. Two of the
sub-projects have tests which subclass tests in the "core" project.
However, just having the sub-projects depend on "core" does not expose
the unit test code and the build fails with a compilati
11 matches
Mail list logo
