Community
Participate
Working Groups
Build Identifier: Build id: 20100617-1415 I use Maven for setting up the Project structure for my Web project. Archetype: maven-archetype-webapp The maven commands that I use are as follows: mvn clean install mvn -Dwtpversion=2.0 eclipse:eclipse After the above command the following are generated in my project .project .classpath .settings (folder) I import the project in Eclipse Helios. I add Tomcat 6.0.33 as Server I add my project to Tomcat 6.0.33 Problem Description: When I start Tomcat 6.0.33, I end up with errors saying that java.lang.ClassNotFoundException Reason: C:\Eclipse Workspaces\MAVEN_WSPACE\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps\MYWAR\WEB-INF\classes is not completely published. Out of approximately 200 ".class" files only a few (around 25 ".class" files are published). So the error java.lang.ClassNotFoundException. Also sometimes the "lib" folder is not published. Only after repeating the Server Start+Stop+Clean for 15-20 times, the publish is done completely. This is impacting the development a lot. Can someone please help me with this. Thanks, Ashish Reproducible: Always Steps to Reproduce: 1. Explained in the Details Section 2. 3.
I see that this new bug is not being endorsed. There has not been any response by any of the technical team members. So, does that mean that Eclipse does not support its products when a new Product has been released ? Does the release of Eclipse Indigo mean that users with Eclipse Helios are not left with any other alternative rather than to upgrade to Indigo ?
I have encountered only a few people who have experienced this "mysterious doesn't publish" problem. So far, in each instance after working with the user, the problem mysteriously resolved itself and I never heard what may have fixed the problem. I will be happy to travel the same "path" with you and see what we can find out. Since it happens to so few people, I'm reducing the priority to "major". I would first recommend you make sure you are not using WTP 3.2.0 (your build id suggests you are using 3.6.0). Though I don't recall this issue reported against it, it has other publishing performance issues that it would be good to remove as a possible cause. If necessary, upgrade to WTP 3.2.1 or later, or even try an installation of the latest Helios 3.6.2. Assuming the problem is still present following this, then let's begin the collection of clues with: 1. Are there any entries in the Error Log view that appear to be related? 2. Can you create a small maven webapp project that duplicates this behavior? 3. If #2 is successful, can you create a standard Dynamic Web Project and copy the content from the small maven project to appropriate locations in this project and still duplicate this behavior?
Marking as WORKSFORME for now. If this is still a problem and more information can be provided, we can re-open and investigate further.
