Update Java2Script by Eclipse Update Manager
Update Java2Script by Eclipse Update Manager
- Aug 20, 2006
Abstract
This article will describe how to update Java2Script using Eclipse update manager.
Prerequisites
In this article, we assume you have already successfully installed Eclipse SDK 3.1.* or 3.2.0. And we also assume you know a little about Eclipse Platform.
Steps for Updating Java2Script
Here is the steps for you to follow.
Step 1:
.
Step 2:
.
Step 3:
.
Step 4:
.
The update URL ishttp://j2s.sourceforge.net/update. Then check the update site and press "Finish" button.
Step 5:
.
Select a proper mirror site, so downloading the feature package would be some faster for you.
Step 6:
.
Attention:If you're using Eclipse 3.1.*, you have to uncheck the option "Show the latest version of a feature only" to show version 1.0.0 M3 for Eclipse 3.1.
Step 7:
.
You should always accept the Eclipse Public Licence 1.0 before continue to install Java2Script.
Step 8:
.
And select the correct location (always no need to change), and then press "Finish" button.
Step 9:
.
Make sure that you do want to install the feature.
Step 10:
.
You are recommended to restart Eclipse for full support of Java2Script compiler.
Step 11:
.
After Eclipse restarted, you can check the plugin details to make sure Java2Script plugin is correctly installed.
Now You Have Java2Script!
Now you can follow Getting Started Tutorial for your tour of Java2Script world.
Know Bugs for Updated Version of Java2Script
After you try to install Java2Script by Eclipse Update Manager, you should know that the installed copied Java2Script plugin from given update URL is marked as version "1.0.0.v310" or "1.0.0.v320", while the standard version should be marked as "1.0.0". In such a result, you have to manage the Java2Script libraries manually.
That is to say, if there are a project running well under standard "1.0.0" Java2Script environment, and you want import the project in your "1.0.0.v310/v320" environment, you must first remove all the project's existed Java2Script libraries, and then re-add the same libraries to the project before you would run those existed applications. If you are not in such a situation, this bug won't bother you.
This bug should be kicked off in the next update.
http://j2s.sourceforge.net/