| User: wstein | Rating: 5 | 2008-06-13 09:03:58 |
| |
When this plugin works it works quite good. It was not that what I am expected but quite a good job. But It was a annoing peace of work to get it run. First I updated my JVM but this didn't work so I had to download it, changed the manifest files and rebuilded it. My hints: Download over eclipse, checkout the modules as seperate projects, change every MF file to support at least JVM 1.5 and save them, select all projects in Ressource View and right click -> Export. There as Plugins and fragments (select a folder on the desktop) and build it. After that you have to extract the Jars to folders and copy them over the folders of the original plugin structure. Copy the plugin to eclipse plugin directory. Set the right group give rx privilegs and restart eclipse. So 9 Points for the plugin, minus 2 point because it does not work out of the box, minus two points that it can't be handled by eclipse plugin manager (download).
I don't want to frustrate the people behind the software because every one who supports the Open Source Project does a great job but this is a quality service and so I want to be honest. Please guys don't stop working you're quite far on the right way. Greez west
|
| User: Anonymous | Rating: 6 | 2008-05-15 17:09:36 |
| |
So far so good... but serious minus points for having to recompile it.
This plugin is compiled to Java 6, which isn't a bad thing on many platforms but some this is awful.
Because Apple is both slow and lazy, Java 6 there is 64 bit only and only for the latest OS X version. The Eclipse SWT library is 32 bit, so you can only run Eclipse with Java 1.5 on a Mac. Consequentially, any eclipse plugins not compiled to be Java 1.5 compatible will fail.
This plugin, like 99% of Java code today doesn't use any 1.6 exclusive features and all I had to do to resolve the problem is download the source from CVS (in eclipse), modify the build to be Java 5 build targets and compatibility (all the manifest files, and the project / workspace Java build compatibility target).
That works fine. Of course, that is a lot of work to expect people to do just because the developer wasn't paying attention and setting the build up correctly. The correct thing to do is set the java version compatibility of the class files to the lowest version they are compatible with. In this case, it might even be Java 1.4, if all the 1.5 generics warnings thrown off in the compile are a sign of anything.
|
| User: Anonymous | Rating: 5 | 2008-05-14 12:20:49 |
| |
Looks nice, but opening a file outside the workspace fails...
|
| User: Anonymous | Rating: 9 | 2008-05-09 07:54:34 |
| |
Great tool. To devaluate all the raters with the *Bad version number* problem: the plugin is compiled with Java 6!
|
| User: Anonymous | Rating: 7 | 2008-03-20 22:45:01 |
| |
I like it and recommend it. What I would also like, and this is for any editor, is a working outline view. That would get this plugin a 9 rating out of me (I never give a 10 ;).
|
| User: Anonymous | Rating: 1 | 2008-03-19 18:04:56 |
| |
Bad version number.....
|
| User: Anonymous | Rating: 1 | 2008-03-18 10:19:18 |
| |
Me too:
java.lang.UnsupportedClassVersionError: Bad version number in .class file
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:161)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(ClasspathManager.java:501)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(ClasspathManager.java:471)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassImpl(ClasspathManager.java:430)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:413)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:189)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:340)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:408)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:369)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:357)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:289)
at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:227)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1269)
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:160)
at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:788)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:51)
at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:252)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:248)
at org.eclipse.ui.internal.registry.EditorDescriptor.createEditor(EditorDescriptor.java:231)
at org.eclipse.ui.internal.EditorManager.createPart(EditorManager.java:841)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:606)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592)
at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:263)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2739)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2651)
at org.eclipse.ui.internal.WorkbenchPage.access$13(WorkbenchPage.java:2643)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2595)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2590)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2574)
at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:340)
at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:328)
at org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMenu.java:190)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1101)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3319)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
|
| User: error500 | Rating: 1 | 2008-03-14 12:59:25 |
| |
What i am do wrong?
---------------------
Error opening the editor.
Bad version number in .class file
|
| User: Anonymous | Rating: 10 | 2008-03-07 07:13:22 |
| |
Great plugin, good shell editor that just works as you'd expect!
|
| User: Anonymous | Rating: 9 | 2008-03-07 06:31:09 |
| |
Very nice to see a new update! One thing I would really like is to be able to manage downloads through the Eclipse Download Manager.
Thank you for your great work!
|
| User: Anonymous | Rating: 6 | 2008-03-03 16:14:30 |
| |
Great idea, tremendous potential to grow but I think lack of support, fix bugs quickly and zero documentation makes it not so favorite plug-in
|
| User: Anonymous | Rating: 8 | 2007-10-12 15:50:41 |
| |
Answer to my prayers! All in all an excellent plugin. Only wish is that the context sensitive help was active for programming structures like if for while etc...
|
| User: Anonymous | Rating: 10 | 2006-12-06 04:18:19 |
| |
I've been looking for an Eclipse shell script editor for ages. This plugin is superb - I love the man page information you get when hovering over a shell command, and also the smart indent. Great!
|
| User: Anonymous | Rating: 10 | 2006-11-10 06:10:33 |
| |
This is a great plugin - the syntax highlighting and content-assist is excellent, and having the man page information displayed as you hover over a shell command is really useful. Keep up the good work!
|
| User: Anonymous | Rating: 2 | 2006-05-26 09:03:15 |
| |
| It does not work when background is set to black - default font color is set to black and one cannot change it in preferences dialog.
|
| User: Anonymous | Rating: 9 | 2006-03-03 13:07:39 |
| |
This is brilliant!!
Please keep this plugin alive....
Ciao
|
| User: Anonymous | Rating: 10 | 2004-08-24 04:18:48 |
| |
This product is excellent, it met my need for a quick and easy help and assistance when writing both simple and complicated shell scripts. Well done.
|
