ok, so mvn package in core creates a target/MyProj-.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
On Sep 5, 2007, at 10:31 AM, Wayne Fay wrote:
ok, so mvn package in core creates a target/MyProj-.tar.bz2
file.
First, a question, why are you creating a tar.bz2 instead of a jar?
Just wondering.
Our application has many additional files required in addition to the
jar, including
Hello,
I am trying to setup a project like this:
MyProj/
+---pom.xml
+---MyProj-Core/pom.xml
+---MyProj-Integration-Tests/pom.xml
MyProj-Core and MyProj-Integration-Tests are both modules of and
MyProj. What I would like to do is setup MyProj-Integration-Tests so
that
You need to run mvn install to put the artifacts in your local cache
from MyProj-Core. Then you can depend on it in
MyProj-Integration-Tests (just like any other dependency) and it will
pull the file out of the cache and use it during its own execution ie
mvn test etc.
As for calling mvn compile
On Sep 4, 2007, at 3:05 PM, Wayne Fay wrote:
You need to run mvn install to put the artifacts in your local cache
from MyProj-Core. Then you can depend on it in
MyProj-Integration-Tests (just like any other dependency) and it will
pull the file out of the cache and use it during its own
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
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
