tag:blogger.com,1999:blog-19648744.post-9447514389929783442008-10-13T10:45:00.000-05:002008-10-13T10:45:00.000-05:002008-10-13T10:45:00.000-05:00dirk, <BR/> there are two things to mention here : <BR/>1. First double check that your "archiveClasses" option in the pom is set to "false". As dane pointed out in a previous comment, the default setting for the maven project is to package up the project into a war (which might cause you other problems)<BR/>2. The secondary (and probably more relevant to you) problem is that the Maven project type doesn't automatically compile your classes and move them into the maven build directory when you make the changes. Thus (unfortunately), when you make a change to your classes, you'd still need to run a build in NetBeans to have the classes copied out to the target directory. For some reason, I recall that the class reloading used to work for me in Jetty and in Glassfish, I had to do the build.akochnevhttp://www.blogger.com/profile/05519996133043093264noreply@blogger.com