How to fix error “Updating Maven Project”. Unsupported IClasspathEntry kind=4?

Reposting an answer to this problem.

Disable the maven nature for the project (via the right-click menu), run mvn eclipse:clean (while your project is open in STS/eclipse), and then re-enable the maven nature. 

http://stackoverflow.com/questions/10564684/how-to-fix-error-updating-maven-project-unsupported-iclasspathentry-kind-4

GWT + Maven + Eclipse = Pain

GWT was definitely not designed with Maven in mind, and getting it all to work within Eclipse is a nightmare. I have managed to get this mostly working, here is what I have so far.

Please install Eclipse with the m2eclipse and GWT plugins.

Start by using the GWT archetype, sadly, this will not produce a project that works, but at least gets you pointed in the right direction.

mvn archetype:generate \
 -DarchetypeRepository=repo1.maven.org \
 -DarchetypeGroupId=org.codehaus.mojo \
 -DarchetypeArtifactId=gwt-maven-plugin \
 -DarchetypeVersion=2.4.0

This will request some details, including a module name. Go ahead and enter in all the fields, but the first thing you will need to do is a search on the entire project in eclipse for literally ${module} and replace that with the actual name of your new module. You should at least find this problem in the org.eclipse.wst.common.component xml file.

You will also notice that the pom.xml file has some compilation issues. I have not figured out how to resolve other than commenting out the offending lines. This doesn't seem to hurt anything, but you will need to manually generate the Async interfaces.

Next up, you will need to create a Run Configuration, most easily done by right clicking your project -> run as -> (G) Web Application. This will throw some error about needing to include the module name in the arguments. So go find the Run Configuration that it created and tack on the end the full path to your endpoint (eg. com.myapp.MyEndPoint)

Now you should be able to get the server standing by following the run as step above again.

You will notice that there are still some funky warnings being spat out, which I have not totally figured out yet, but hopefully this will help someone out.

m2eclipse: Add archetypes to create maven project

Ran into an issue where I could not use an archetype from within Eclipse. In order to do so, a new catalog will need to be created, then Eclipse simply needs to be told where it is.

• Navigate to your .m2/repository in your console
• Enter the command 'mvn archetype:crawl'

This will create the file archetype-catalog.xml

In Eclipse create a new Maven project, when you get to the screen with the catalog drop down box, click configure and add a Local Catalog pointing to the xml file created above. Ok out.

This catalog will now be added to the drop down box and can be selected.

Enjoy.

Installing the Aptana plugin in Eclipse makes Quick Diff colors unreadable

When I install this plugin my Quick Diff colors change, making it near impossible to read an SVN compare.

I have found that there are a couple potential fixes, or combinations thereof:

1. Go to Preferences -> General -> Editors -> Text Editors -> Quick Diff.

• Changes ->  H:80 S:240 L:240 R:221 G:225 B:221
• Additions ->  H:80 S:240 L:240 R:221 G:225 B:221
• Deletions ->  H:0 S:240 L:232 R:255 G:238 B:238

2. Go to Aptana Studio -> Themes. Ensure Eclipse is chosen from the drop down box.

Debug Virgo from Eclipse

Eclipse Setup

1. In Eclipse's Debug Perspective, click on the Run -> Debug Configurations menu
2. Find "Remote Java Application" and then click New and fill out the information

Virgo Setup

1. Start the server using the "-debug" & "-suspend" attributes

Magic

1. Start Virgo, then start the configuration in Eclipse
2. It may ask you to associate the code before step threw can happen, simply choose the code in your workspace that is appropriate.

See Also

• http://www.eclipse.org/forums/index.php?t=tree&th=175831&S=b1238fc3cb00d7869e6ca58cf5213481#page_top
• http://www.eclipse.org/virgo/documentation/virgo-documentation-2.1.0.M04-incubation/docs/virgo-user-guide/htmlsingle/virgo-user-guide.html#d0e330
• http://dev.eclipse.org/newslists/news.eclipse.platform/msg25518.html