On Tue, 2003-02-25 at 11:31, Chris Butler wrote:It may be sneaky, but I think it's nicer than the jar override, since the version of the artifact still gets to be specified.
Apologies for that. I misread the problem. My problem was that a dependency can no longer only be specified by:
<dependency>
<jar>somelibrary.jar</jar>
</dependency>
If you actually got away with this before that was an error ... more than likely caused by myself.
I believe that now the entity must be specified more completely:Yes, all doco'd now in the user guide.
<dependency>
<id>somelibary</id>
<version>unused</version> <jar>somelibrary.jar</jar>
</dependency>
We used to dump our local jars (non-IBiblio) into one repo dir calledYou can still do this using the maven jar override facility or you can
/jars which is where the previous dependency checking looked.
use the sneaky trick of using a file URL in your list of remote
repositories.
Chris, you can use a maven.repo.remote setting like this (in your project.properties or properties file in your user dir:
# override remote repo since we want to also point to a cvs based remote repo
# to get some jars not found at ibiblio
maven.repo.remote=http://www.ibiblio.com/maven,file:${basedir}/../../shared/repository
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
