ok :)
What I need is to be able to test the behavior of my code when the jar
is attached to the classpath instead of the classes folder.
Because, I have a code that parse the content of the jar where it stands
to find xml files or use getResourceAsStream to get the folder.
So the code checks if the context is jar or not, then execute the
corresponding code. The code using getResourceAsStream is well tested
but the other cannot because surefire adds the folder target/classes to
the classpath rather than (in my case) the built jar.
Sorry if it wasn't clear, or still not clear.
If it doesn't make sense, what can I do (other than : created a project
having a dependency on the to-be-tested project...)
Thanks
ap
Wayne Fay a écrit :
ping ^^
I think no one replied because your message does not make any sense
(to me at least). Can you try re-writing the email and focus on what
you have, what you need, and how you think Maven can help get you from
A to B? Also mention what you've tried and why that didn't work or was
insufficient.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
