Eugene,
this question is more about how to setup the project and M2E "Best
Practices". One of the many things I like about Maven is that the
binaries are in repositiories and not in CVS. For normal Jars this works
perfect but DLLs and .so files are often also packed in jars and then
put into the repositories. These jars have to be unpacked before they
can be used. My old way to use these DLLs was to put them into the
project root (single module) and then put everything in CVS. When s.o.
was checking this out with Eclipse from CVS everything worked and the
project could be run directly. I can do the same now with M2E projects
but it feels wrong to put the DLLs in the CVS and to not use the repo
for that. My question was and is how people are handling this "problem".
The idea is that when someone joins the team he can checkout the project
and start it right away (without the DLLs being in CVS).
Thanks Jan
Eugene Kuleshov schrieb:
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
--
****************************************************************
Jan Schoppenhorst
GDV
Gesellschaft für geografische Datenverarbeitung mbH
Binger Straße 49-51
55218 Ingelheim
Tel.: 06132/7148-19
Fax.: 06132/7148-28
www.gdv.com
www.gdv-mapbuilder.de
Sitz der Gesellschaft: Ingelheim
Amtsgericht Mainz HRB 23123
Gerichtsstand Mainz
Geschäftsführer: Thomas Riehl, Dirk Hübener
****************************************************************
begin:vcard
fn:Jan Schoppenhorst
n:Schoppenhorst;Jan
org:GDVmbH
adr;dom:;;Binger Str. 49-51;Ingelheim;;55218
email;internet:[EMAIL PROTECTED]
url:http://www.gdv.com
version:2.1
end:vcard
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
