Jan,
You don't have to explain your issue again. I got it. But like I said,
it need to work for the command line Maven first and m2eclipse mailing
list is really bad source for such expertise, or else someone already
responded to you. So, I still believe your best bet is to ask how to
build and test such projects from command line Maven in the Maven Users
list.
regards,
Eugene
Jan Schoppenhorst wrote:
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
