Installation works fine but now features or plugin show up

[palantir]

Installation works fine but now features or plugin show up

[belov-gr]

Try enable the builder:

1. Right-click on a project containing TypeScript files
2. Select Configure->Enable TypeScript Builder

[barakka]

Hi,

the point is that there is no "Enable TypeScript Builder" in the configure menu.

Anyway, I've downloaded and compiled the code and I've found out what's the problem: the plugin assumes a Java 1.7 environment and I'm running under 1.6.

I've modified the plugin descriptors, recompiled and run the plugin in debug mode. In the test eclipse that is launched I can the see the configure option and I'm able to edit ts files (while before it was complaining for the java version and for .class version incompatibilities).

I've then run the maven clean install in order to generate the repository, and installed the plugin from the generated repository in my normal eclipse, but the result is still the same: the plugin is listed as installed but no plugin feature is active. There is no binding for ts files, nor the option to enable or activate the TypeScript builder. The error log is clean.

[barakka]

I've also started the plugin in debug mode against my usual eclipse workspace, and in that case the plugin works as expected (more or less). However, if I start a normal eclipse instance against the same workspace, the plugin is disabled.

[barakka]

It looks like I was generating the update site using the same build number (as I did not commit the change and the build number is taken from git history). Once I made the commit, republished the repository and re-installed, it started to work as expected. I now see the configure option in my normal eclipse and I'm able to edit ts files.

So, it seems the plugin work fine under Java 1.6, it only needs a small change to the manifest file in order to reduce the java platform version requirements.

[derekcicerone-zz]

I suspect the code currently works under java 6 because we aren't using any java 7 specific library features (such as the Objects class introduced in java 7). However, we may not be so careful in the future. Do you know why your eclipse doesn't use java 7? Is java 7 installed? We targeted java 7 because java 6 is now out of public support so its becoming a bit of a security liability for our developers to keep it installed on their machines since public patches are no longer being delivered.

[barakka]

It uses Java 6 'cos we have to use that version for our projects, as we depend on libraries that don't work under Java 7. And for simplicity we run eclipse as well under Java 6 (instead of having to install two JVM on each developer machine). I get your point, anyway, although I believe Java 6 is still quite widespread in enterprise environments.

Why don't you reduce the dependency to Java 6 until you need any Java 7 specific feature? Or, in any case, at least put a notice with the java version requirement in the documentation.

[derekcicerone-zz]

I think we'll just reduce the version requirement: I suspect that many organizations are still on java 6. We tried java 7 optimistically (hoping most groups using typescript would be on more recent versions of java) but since its already causing issues I think the prudent thing to do is just relax the requirements.

[derekcicerone-zz]

A new release should be up shortly (within 5 minutes assuming our build system didn't run out of space again), please let me know if it works in your Java 6 environment.

[derekcicerone-zz]

Ok, the new release should be up now.

[barakka]

It looks like it is working fine now. Thanks.

R.

[derekcicerone-zz]

Cool, thanks for the thorough diagnosis in your bug report - it made the fix super simple.