Sorry, I don't understand Stefan. The parent project is not defined
strictly as a dependency, it is defined as both a parent and a
dependency (I had to define it as a dependency as I was getting
classpath errors running unit tests for the child project when it was
only defined as a parent). I would have thought that the fact that it is
defined as a parent would allow me some way to run the unit tests for
the parent - as the parent is a pom packaged project, I can't run the
tests using mvn test from the home directory of the parent project (I
get a 'No goals needed for project - skipping' error). Are you basically
saying that a parent project needs to have modules to allow unit tests
to be run?
Thanks
Denis
Stefan Magnus Landrø wrote:
Hi there,
As far as I know, you have to use modules to achieve this.
Just as an example - do you really want to run apache axis tests when you
include axis as a dependency?
Stefan
Denis McCarthy <[EMAIL PROTECTED]> skrev 16.08.2006 16:52:59:
Hi,
One of my projects depends on a second project. As a result, I've
defined the first project as being packaged as a pom, with an associated
dependency in the second package. However, when I run 'mvn test' on the
pom packaged project no tests are run (which I think is normal for
pom-packaged projects with no modules). What should I do to run tests
for a pom packaged project - do I really require a module? Indeed, am I
approaching maven intra-project dependency management skew-ways?
TIA
Denis
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
