With maven you declare your dependency on specific files (jars etc) rather than anything found in a directory.
Yep.
Does this help? If not, give us some more info on what you need to do.
Not really. It my fault for not giving a full picture of what I'm trying to do. Here's the story.
There are various property and xml files that my project requires at runtime. Examples include log4j.xml, hibernate.xml etc. These files do not live in the source tree (src/java) so as to prevent developers commiting their preferences to CVS. Instead, each developer must put, for example, log4j.xml in their $HOME directory and tweak it according to their taste.
So the problem I have is that I would like maven to include $HOME in the path when it's running unit tests (in order to ensure that the various property/xml files are loaded). Since we also use Eclipse, it would be convenient if $HOME could be expressed as a <dependency> so that the Eclipse plugin would add it to the project classpath. In this way the same properties would apply regardless of whether the unit tests are being run from the command line or within Eclipse.
I guess this is related to the whole are of runtime dependencies.
Any ideas?
Thanks, ct
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
