On Sep 4, 2007, at 3:20 PM, Wayne Fay wrote:
So what is the point of having modules at all? If you have to install
them anyway, why aren't they all just separate projects?
For all intents, they are (completely) separate projects.
Ok, lets say I install the Core project, is there a way in my
Integration-Tests to get a filename for that project? Core creates a
tar.bz2 file, and my integration tests need to extract the tar.bz2 to
a temp directory, then run some programs and verify the expected
output.
Explain this more, and perhaps we'll have some suggestions for how to
handle it. How/when does "core create a tar.bz2 file" -- during
compile, test, when? There are lots of things you can do with the
assistance of buildhelper, assembly, and dependency plugins.
ok, so "mvn package" in core creates a target/MyProj-XXXX.tar.bz2 file.
In integration-test, I'd like to take this tar.bz2 file and do the
following (programmatically):
tar jxvf MyProj-Core.tar.bz2
MyProj-Core/bin/runProgram
And then validate the output of runProgram. Ideally, I would write
Java code (as a junit test) to call System.exec() which would monitor
MyProj-Core/bin/runProgram.
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.
Does that explain what I'm trying to do?
Thanks,
Josh
--
Joshua ChaitinPollak
Software Engineer
Kiva Systems
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
