Travelling in Hosur Road … Better Gmail - a Wow Firefox Extension
Apr 25

The first time I heard about Google Web Toolkit, I was excited. I immediately downloaded it; wrote few samples and found that it was really a nice piece of software. But it lacked one thing - IDE integration. Although “GWT was intentionally designed to work well in any IDE”, there was no direct support for GWT in any IDE. I thought how about writing an Eclipse plugin for that? I’m not an Eclipse plugin developer. I was a pure C++ guy who has jumped into several layers of J2EE and .NET and settled as a mainline developer in a top SOA product. Eclipse plugin development is something I’ve to learn. I decided to give a try.

Result? Googlipse. That is my first plugin. With over 25,000 downloads and counting, it generated a good amount of interest. So I get bugs (yeah, sometimes I write embarrassing code) and people extend it. It was a wonderful experience in learning Eclipse and gave me a better understanding about the Open Source from the contributing perspective. Googlipse has shifted my career and now my day job is also plugin development. Besides all this, I’ve to kill Googlipse. Why? Because of the name!

I was over enthusiastic that I coined the name by joining two names: Google+Eclipse. The logo is also the same way, Google colored text in an Eclipse background. I thought who cares about the name. I was wrong.

Google’s legal department had “some trademark concerns about the name”. I was pointed to Google Branding Guidelines. So I decided to change the name and logo. Hmmmm. That means its virtually creating a new product (at least to the users who don’t worry about the code!) That is what I’ve done now. I’ve created a brand new product called “Cypal Studio for GWT“. It is hosted @ Google Code. Its essentially the same code base (with the same Apache 2.0 license) but with little changes and few bug fixes.

So what happens to Googlipse now? Its dead. Means there will be no more bug fixes, no more features. The existing downloads & code base will remain there @ SourceForge. The home page will be soon pointing to new product’s site (which is under development). Thus ends the story of my first Eclipse Plugin.

written by Prakash G.R.

14 Responses to “Googlipse is dead, long live Cypal Studio for GWT”

  1. Mark Volkmann Says:

    I installed “Cypal Studio” by downloading the zip from http://code.google.com/p/cypal-studio/, unzipping it, copying the features files to my Eclipse features directory, and copying the plugins files to my Eclipse plugins directory. I then restarted Eclipse and selected Window…Preferences…, but no entry for configuring Cypal Studio appears there. Any idea what I’m missing?

  2. Martin Says:

    I have the same problem…

  3. Pranni Says:

    Can you please log an issue @ http://code.google.com/p/cypal-studio/issues/list and provide more details like your Configuration Details (Help->About Eclipse->Configuration Details)

  4. Yuki Says:
  5. Klemen Says:

    Had same problems in windows environment using cypal:

    Check this:
    c:\eclipse\plugins\in.cypal.studio.gwt.core_1.0.0.200704260132\plugin.xml

    you should have following lines:

  6. Klemen Says:

  7. Klemen Says:

  8. Klemen Says:

    Pasted xml code and it doesn’t apear… Check link: http://code.google.com/p/cypal-studio/issues/detail?id=13&can=2&q=

  9. Tran Minh Says:

    you need to enable the plugin via Help->Software updates->Manage Configuration. then choose so view all disabled plugin. Choose cypal and enable it. Restart your ide and you can config cypal for sure.

  10. Gabriele Prandini Says:

    i did everything written here: http://grprakash.googlepages.com/gwttutorialwithgooglipse
    install the plug in (it seams to work)
    created the new project
    created the new module
    edit the html
    edit the javafile
    but then i get this error when i’m tring to run under “GWT Hosted mode application” (i selected the project and the module)

    Exception in thread “main” java.lang.NoClassDefFoundError: org/apache/juli/logging/LogFactory
    at org.apache.catalina.core.StandardService.(StandardService.java:56)
    at com.google.gwt.dev.shell.tomcat.EmbeddedTomcatServer.(EmbeddedTomcatServer.java:189)
    at com.google.gwt.dev.shell.tomcat.EmbeddedTomcatServer.start(EmbeddedTomcatServer.java:62)
    at com.google.gwt.dev.GWTShell.startUp(GWTShell.java:742)
    at com.google.gwt.dev.GWTShell.run(GWTShell.java:539)
    at com.google.gwt.dev.GWTShell.main(GWTShell.java:321)

    it seams it check a main class… but with gwt we don’t need a main class… where’s the error?

  11. Glen Edmonds Says:

    My guess would be that you don’t have Apache logging in your class path. It can be found in commons-logging-api.jar that can be downloaded here http://commons.apache.org/downloads/download_logging.cgi

  12. Lou Wohlmuth Says:

    I had the same problem as Glen. I downloaded the commons-logging-1.1.1.jar.jar file, added it to my path, and it made no difference.

    Please help.

    ___________

    I’m using Eclipse Platform Version: 3.3.0 Build id: M20070921-1145
    gwt-windows-1.4.61, and
    a freshly downloaded version of Cypal.

  13. Michel Says:

    You can remove the Tomcat library in your build path and it´s gonna work!

  14. CI Says:

    As Michel suggested, I removed the Tomcat library and my app worked, i.e. I didn’t get “org/apache/juli/logging/LogFactory” related exception. However, this isn’t really a good solution is it, since eventually I’m likely to write code that needs that library. Comments please. Thanks

Leave a Reply