Brett Porter wrote:
I'm sorry ,maybe its just because I'm pre-coffee, but I don't really
understand what you are referring to.
Sorry - I'll try to elaborate a little more:
process-[test-]resources copies with targetPath to
target/[test-]classes, which is added to the classpath. So it should
all be correct.
That's fine - but all this stuff will be added to the test-jar (I'm
using attached tests - so that I can reuse the same tests later - see
http://maven.apache.org/guides/mini/guide-attached-tests.html).
When I run the test phase with surefire in the my main artifact I need
some spring-config, log4j-config etc available on the classpath - but I
do *not* want these to end up in my tests which are jar'ed together for
reuse in other artifacts.
So, what I want to achieve is:
target/test-classes (only .class files - to be added to
<myartifact>-<version>-tests.jar
target/some-test-resources (only available on classpath during execution
of tests).
(The same would hold for the main artifact and resources).
I assume you are talking about modifying the manifest Class-Path:
entry in the JAR plugin, which you can do either by:
a) filtering the manifest (this is already possible using normal
filters, it has nothing to do with the JAR plugin)
b) using ${project.*} variables or others in the manifest elements on
the jar plugin configuration.
The clue is to avoid these resources to end up in the archive - but
still have them available on the classpath while executing the tests.
--
David J. M. Karlsen - +47 90 68 22 43
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
