Error during debug launch in Vaadin 7 dev environment

Vaadin 6 / 7 / 8
1

(I don’t see any separate area to post Vaadin development questions, as opposed to developing applications with Vaadin, so I’m posting here.)

I have setup a Vaadin development environment to the best of my ability. I am following
this
 document. I get to step 9 - Configure and start the server. It tells me to setup a Debug launch configuration for a Java Application with com.vaadin.launcher.DevelopmentServerLauncher as the class. When I run it I get this message:

jetty-7.4.5.v20110725
started o.e.j.w.WebAppContext{,file:/C:/Users/ksnortum/workspace.indigo/vaadin/WebContent/},WebContent
FAILED jsp: java.lang.NoClassDefFoundError: org/apache/juli/logging/LogFactory
FAILED o.e.j.w.WebAppContext{,file:/C:/Users/ksnortum/workspace.indigo/vaadin/WebContent/},WebContent: java.lang.NoClassDefFoundError: org/apache/juli/logging/LogFactory
Started SelectChannelConnector@0.0.0.0:8888 STARTING
FAILED org.eclipse.jetty.server.Server@7433b121: java.lang.NoClassDefFoundError: org/apache/juli/logging/LogFactory

In a maven project I would start looking for missing dependency that contains the reported Java class, but I don’t know Ivy and there seems to be six “sub-ivy” files and I wouldn’t know where to put it. I did find
this
 on StackOverflow, but the solution involves adding a Tomcat jar and the Vaadin dev doc tell me this is a Jetty solution, so I’m confused.

Anyone know why I’m getting this error?

2

It does work for me without any tweaking of Ivy files. I do not have any “org.apache.juli” classes on my classpath and yet no such error messages are printed.

If you used the instructions from a while ago, note that you should now only configure the “ide” configuration (with the ivysettings.xml in the project). You should not directly add other Ivy configurations or files to your Eclipse configuration and no changes to any ivy files should be necessary.

The wiki was also missing the now required “-ea” (enable assertions) VM argument for the development server launcher, I just added it there.

One vague guess about what might be causing problems: maybe you have configured a runtime for the Vaadin project and its classpath containers have conflicting classes with additional dependencies. In my current Vaadin 7 development project, I have nothing selected in Project Properties → Targeted Runtimes. Try removing the runtime for the project or at least moving "ivy.xml [ide]
" above “Web App Libraries” and any JARs in the order of your build path entries.

3

That was a good guess! I had setup a runtime for Tomcat. That doesn’t make sense if you’re running Jetty! Thanks for the help.