Jan,
What I am trying to say is that if your code that need those DLLs
don't work in Maven command line (CLI), it is not going to work in the
IDE too.
Think about simple JUnit test that calls some code from DLL. Once you
get that working in Maven CLI we can see what need to be fixed to make
it work in the IDE (if it won't work out of the box).
regards,
Eugene
Jan Schoppenhorst wrote:
What I want to know is how do you handle Maven projects that need DLLs
(not being installed already on your machine), which are packed in
jars in Maven repositories, in Eclipse? I am not talking about
assemblying but project setup and regular running/debugging the
project within Eclipse. Since m2e is definitely Eclipse related and
the plugin which will have to do whatever has to be done in this case,
I think this is the right place to ask.
Eugene Kuleshov schrieb:
Jan,
You better ask this question in the Maven Users mailing list. See
http://maven.apache.org/mail-lists.html
regards,
Eugene
Jan Schoppenhorst wrote:
Hi, we have a project where we need to have some DLLs in the project
root directory. Usually in this case we put the DLLs in CVS so that
when people checkout the project everything is in its place. Since
binaries in CVS is bad and all the DLL (packed in jars) dependencies
are defined in the pom with <scope>provided</scope>, I was wondering
if there is not a way to keep the stuff away from CVS. I guess its
probably possible to unpack the stuff during process-resources in
the project directory. Is that the way to go or is there maybe
already a "Best Practice"?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
