This is exactly what I am doing - an integration test. I decided to create a
separate test subproject that is a peer to the tested subprojects. I
hoped that by declaring the same parent in my test subproject and inheriting
all the project's dependencies I will be able to avoid version
Have a look at the build-classpath goal of the dependency plugin:
http://maven.apache.org/plugins/maven-dependency-plugin/build-classpath-mojo.html
-Olivier
On Tue, 2008-05-13 at 11:23 -0700, vicki wrote:
Hello,
I have a maven's subproject that runs tests against the artifacts of its
piers
Olivier, thank you very much for the advice. Unfortunately, my quick test of
build-classpath did did not solve my runtime classpath problem. First of
all, the examples of the build-classpath goal that I saw, show how to output
the project's classpath to a file. What I need is to add project
On Tue, May 13, 2008 at 11:23 AM, vicki [EMAIL PROTECTED] wrote:
I have a maven's subproject that runs tests against the artifacts of its
piers subprojects. Obviously, In other words, to run my tests I need to
create dependencies on the artifacts produced by the other subprojects. I
run
On Wed, 14 May 2008 11:18:54 Wendy Smoak wrote:
On Tue, May 13, 2008 at 11:23 AM, vicki [EMAIL PROTECTED] wrote:
I have a maven's subproject that runs tests against the artifacts of its
piers subprojects. Obviously, In other words, to run my tests I need to
create dependencies on the
: Modify Classpath
Olivier, thank you very much for the advice. Unfortunately, my quick
test of
build-classpath did did not solve my runtime classpath problem. First of
all, the examples of the build-classpath goal that I saw, show how to
output
the project's classpath to a file. What I need is to add
in my particular case i needed the code for integration tests so was
borderline as to whether the artifact was actually separate or not...
but in general i would agree
On Wed, 14 May 2008 12:02:13 Brian E. Fox wrote:
If you have classes that you need outside a war, the correct way is to
make
