You could try "mvn eclipse:eclipse" , then maven should generate an eclipse project, based on the pom. Or "mvn idea:idea" to create an IntelliJ idea project, Or use IDEA 7.x, which supports maven projects out-of the-box. regards Maarten On Jan 8, 2008 2:22 PM, Matt Fowles <matt.fowles@gmail.com> wrote:
Ceki~
What I mean by compile on the command line is that I was able to use maven at the command line to compile the code and run the tests.
I am able to use `mvn package` to compile the code and run tests. Are there separate targets that I can use for doing those two things independently?
Matt
On Jan 8, 2008 5:52 AM, Ceki Gulcu <listid@qos.ch> wrote:
Welcome to the logback project, Matt.
The various logback modules have varying dependencies which seem to be reported by Eclipse. I don't see how you were able to get the code to compile on the command line. What do you mean by that?
By the way, are you familiar with Maven? That's what we use to automatically resolve dependencies.
HTH,
Matt Fowles wrote:
All~
I am new to the project and am having trouble setting up an eclipse workspace for the project. I can get logback to compile fine at the command line, but when I import the directory into an eclipse project I get a whole bunch of errors from failed imports like junit, org.dom4j, javax.jms, javax.mail, org.apache, and probably a few more.
I suspect this is a stupid problem on my end, but any pointers would be appreciated.
Thanks, Matt
-- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch _______________________________________________ logback-dev mailing list logback-dev@qos.ch http://qos.ch/mailman/listinfo/logback-dev
_______________________________________________ logback-dev mailing list logback-dev@qos.ch http://qos.ch/mailman/listinfo/logback-dev