Hi,
It seems that lib.repo is used both for the jar that are needed by the
build process and also for the jars that are needed for the source
compilation. Is that correct ?
I'm not especially too keen with this as it mixes both jars. Also, there
are some issues of clash between jars needed by build tasks and jars
used for application runtime.
Is this customizable ? (doesn't appear from looking at the sources)
Are you all happy to mix these 2 types of jars ?
Also, some of our projects generate jars and we do not want to check
them in our CVS, and we would prefer not to have to move them to the
lib.repo directory (they are generated in each project dist/lib
directory). How to cope with this ?
Of course one solution that comes to mind is to have all our
<dependencies> entries relative to lib.repo
For example :
<dependency>
<jar>../common/dist/lib/common.jar</jar>
[...]
and the following directory structure :
root
|_ common
|_ dist
|_ lib
|_ common.jar
|_ repo
|_ (some external jars)
Also, some time the common project may not have been run (or a clean may
have happened on it removing the dist directory). Then Maven will try to
download the missing jars ... argh ... We would like the build to tell
us that the file is missing but not to download it ...
Any solution ?
Lots of questions.
Thanks
-Vincent
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
