From what I understood, there are the two subpackages and the
application itself depending on them, right?
So, based on this assumption, I sugest you create three modules in a
single CVS repository: one for each of the subpackages and the third for
the application itself; each will have its own pom.xml (beacause each is
a project on its own right). Mind that the application will have bo be
configured to use the dep's.
Once you install the generated jar (with "mvn install") from the
subpackages into your local repository (which is, for example,
$HOME/.m2/repository on *NIX systems), you can proceed to compile the
application with "mvn compile". If you were developping this project on
your own, that'd be the end of the story. As you're probably not...
You can setup a central maven repository and (in a timely and organised
fashion) upload the generated jars to that central repository. One
developping the app will have to checkout only the application code.
That has the added benefit that if, for example, I'm developping one of
the subpackages, you're developing the application and I accidentaly
intoduce a bug in the subpackage, you won't ge affected at all (provided
I did not upload the "buggy" jar).
NOTE: If the subpackage gets installed at
$HOME/.m2/repository/dirA/dirB/1.0, its configuration as a dependency
would look like:
> <dependency>
> <groupId>dirA</groupId>
> <artifactId>dirB</artifactId>
> <version>1.0</version>
> </dependency>
--
Sincerely,
Luiz Eduardo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
