Jupiter Upgrade

Although I don't have much time to work on Jupiter, it is the time to think of it. The Eclipse 3.3 is about to be released in late June. A user from Nike reported that the current version of Jupiter does not work for the milestone versions of Eclipse 3.3.

A couple of days ago, Philip forwarded an email from Adrian Price saying that there are many anti-pattern design issues of Jupiter. Philip suggested that we move Jupiter to Google open source hosting. The user community of Jupiter is growing, and we just can not keep up with new feature requirements, bug fixes, Eclipse upgrades, and so forth. All these might indicate that it is
the time to make Jupiter be completely open-sourced. I had a chart with Julie this morning. She was also excited about this.

But, I am not familiar with Google's project hosting services. Before importing Jupiter into Google, we need to investigate how we can do Jupiter release.

For now, we can create a Google project and start migrating Jupiter from CSDL repository to Google's repository gradually. As Julie suggested, we can maintain both repositories first and then retire the CSDL version.

The current plan is as following:

1. Upgrade Jupiter to Eclipse 3.3M6 (hongbing) , by May 15
   
2. Create a project for Jupiter at http://code.google.com/hosting/(Julie), by May 20

The jupiter-eclipse-plugin project is created and source code was imported. The project is now located at http://jupiter-eclipse-plugin.googlecode.com/
or http://code.google.com/p/jupiter-eclipse-plugin/