> ok, so "mvn package" in core creates a target/MyProj-XXXX.tar.bz2 file.
First, a question, why are you creating a tar.bz2 instead of a jar? Just
wondering.
I assume you are using assembly plugin to generate this tar.bz2 file. If so,
you should install this artifact into your repo. (Or you could throw away the
normal way of doing things in Maven and just hard-code paths like
../core/target/MyProj-Core.tar.bz2. But I prefer to "mvn install" things.)
Tim just posted a sample config to attach assembly to your project lifecycle in
this thread:
From: Tim Kettler
To: Maven Users List
Subject: Re: Cannot deploy a parent 'tar.gz' assembly
Date: Wed, 05 Sep 2007 10:00:09 +0200
> So what I'm looking for is a way for maven to take a tarball, and
> extract it to a known location before calling the integration-test
> phase. Heck, even a suggestion of how my Java code could get a handle
> on the path to the filename of a specific dependancy (MyProj-Core) so
> it would know what file to extract, would be a big help.
I would write a plugin. You should be able to do all this and more easily with
a plugin as you can write the plugin in normal Java code, and Maven will
automatically populate some fields for you (${localRepository} etc) which will
help.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
