Install Instructions
ProRefactor is an Eclipse plug-in, and Eclipse provides a user interface to make the installation and updates of plug-ins easy. If you have ever used Eclipse's Feature Updates wizard in the past, then you probably do not need to read this section at all.
Java
ProRefactor and Eclipse require a recent version of Java. Java can be freely downloaded and installed from java.sun.com.
Eclipse
ProRefactor requires a recent version of Eclipse. Eclipse can be freely downloaded and installed from www.eclipse.org.
Note:ProRefactor creates a prorefactor subdirectory in your Eclipse working directory. Your project settings are stored there, and ProRefactor writes various additional files and directories there.
ProRefactor
Start Eclipse and choose Help > Software Updates > Find and Install... and use the following URL: http://prorefactor.oehive.org/update/.
Linux and Unixes
The Proparse shared libraries are not distributed with ProRefactor, and those must be installed separately. Proparse comes with its own install notes, but there are a few additional items worth mention with regards to ProRefactor. The shared libraries and the DLL symlink may be installed into one of two places: either into the org.prorefactor.core plug-in directory, or else into your LD_LIBRARY_PATH (or equivalent). Since there is a new org.prorefactor.core plug-in directory with each new ProRefactor release, it probably only makes sense to install Proparse's shared libraries into your LD_LIBRARY_PATH.
Note: Linux provides a shared library loading mechanism via the /etc/ld.so.conf file. This does not (at present) work for loading shared libraries into Java or Eclipse.
All Done
You should now be able to select the ProRefactor perspective from Eclipse's Window menu.
- Printer-friendly version
- Login to post comments
Comments
Can't launch wizard in 10.1B
I downloaded Java 6 and used the software updates feature inside Eclipse to download / install the plug in. All of that seemed to go great. I also downloaded and ran the configuration procedure.
When I attempt to create a new Prorefactor project, I get this error message:
"The selected wizard could not be started.
Reason:
Plug-in org.prorefactor.eclipse was unable to load class
org.prorefactor.eclipse.wizards.ProjectWizard"
I am very new to Architect (and all of this), so it's hopefully something simple that I did wrong during the installation? Any help is appreciated!
Thanks
Re: Can't launch wizard in 10.1B
Hi Steve,
Sorry I took so long to reply - I've just returned from a road trip.
Unfortunately, I'm not able to install OE Architect on my computer *at all*. It's an issue I'm trying to work through with PSC.
In the meantime, the best I can suggest is trying to install ProRefactor into a separate, clean copy of the Eclipse SDK.
Are there any other errors? You could send me the error log if you like. It should be accessible via Help -> About -> Configuration Details -> View Error Log, which should open the text file in your web browser.
Other people have reported success using ProRefactor with OEA, so ultimately, we should be able to get it working for you.
Kind regards,
John
smc wrote:
> I downloaded Java 6 and used the software updates feature inside Eclipse
> to download / install the plug in. All of that seemed to go great. I
> also downloaded and ran the configuration procedure.
>
> When I attempt to create a new Profactor project, I get this error message:
>
> "The selected wizard could not be started.
>
> Reason:
> Plug-in org.prorefactor.eclipse was unable to load class
> org.prorefactor.eclipse.wizards.ProjectWizard"
>
> I am very new to Architect (and all of this), so it's hopefully
> something simple that I did wrong during the installation? Any help is
> appreciated!
>
> Thanks
>
>
can't install in OEA 10.1B
I would like to have a go with Prolint in OpenEdge Architect so I tried to follow the installation instructions for ProRefactor.
I am not afraid to admit that Java and Sun are confusing to me: there is Java SE, Java EE and Java ME and they don't give a clue which one is Java. I picked "Java SE Development Kit (JDK) 6" and installed it, and then rebooted the PC.
Then I copied the OpenEdge Architect shortcut end removed the -vm parameter.
When trying to install from "http://prorefactor.oehive.org/update/" I get a message "Resulting configuration does not contain the platform" so nothing happened.
I don't know what to do.
Re: can't install in OEA 10.1B
Hi Jurjen,
I'll try to take a look. Unfortunately, OEA 10.1B (first release) completely fails to run on my computer, and PSC tech support was never able to figure out why. (The ball was left in my court - I was supposed to set up my computer so that they could connect to it and poke around, but I never got around to it.)
I'll try downloading the latest 10.1B patch and see if I'm able to run it, and if that works, then I should be able to try to reproduce the issue you are reporting.
You picked the right Java. "Standard Edition" is the base, Java "Enterprise Edition" has a whole bunch more libraries geared toward enterprise Java programming like JavaBeans, etc. "Micro Edition" is for writing games and apps for cell phones and such.
I can't remember if I'm running Java 5 or Java 6, but that shouldn't make a difference - 6 should work.
You might as well have the Development Kit (rather than just the Java Runtime Environment, even if you think you won't be compiling any java code... it's handy to have it there just in case.
You might try installing another plugin (one with an update site), other than ProRefactor. Maybe there's something wrong with OEA with Java 6, or some other issue that isn't related to ProRefactor.
Re: can't install in OEA 10.1B
You're right as usual: there may be something wrong with OEA. Nothing updates in OEA!
After that experiment I have downloaded and installed a fresh Eclipse 3.2 and installed ProRefactor into it... no problem. It have seen a SUBSTITUTE refactor in action and Prolint found a statement with noeffect. Nice!
Let's see if the PSDN has some info on installing plugins in OEA.
I don't know if this will
I don't know if this will apply here, but there is a problem with OEA 10.1B language settings which prevents some users from completing the RTB plug-in installation. The problem is that the OEA plug-in is not being seen by Eclipse as being correctly installed, and therefore the pre-requisites set by the RTB plug-in (OE plugin dependency) are not being seen as met.
A work-around this problem, is simply to change the language setting in the feature.xml file for OEM 10.1B. The file contain a language setting which are set to en-us which is wrong for someone that is on a machine that is not typically in America - it should just be removed all together from the feature.xml file or changed to the suitable language. This enabled our non-US users to download the RTB plug-in from our update site. I believe there is a kbase for this.
This was corrected with OE 10.1B01.
Roundtable Product Architect
www.roundtable-tsms.com
Re: can't install in OEA 10.1B
I installed 10.1B service pack 1, and that didn't help. Sigh. I'll have to get back in touch with PSC tech support.
If you really want to get it going in OEA, you could try copying those ProRefactor feature and plugins files/folders from eclipse/features and eclipse/plugins over to the OEA eclipse directory, restart OEA, and see what happens. (Don't forget to copy the Prolint plugin along with the ProRefactor plugins.)
If there's something broken about using OEA to access update sites, then I might want to repackage ProRefactor in an easy zip file download.
Re: can't install in OEA 10.1B
Yep, that did it. Copying the feature and plugins stuff. It works now. Pretty cool, actually.
Strange, there is a topic on this on PSDN. I have followed the steps in http://www.psdn.com/library/thread.jspa?threadID=2780&tstart=15 but that did not help: the only thing that got added was the OpenEdge Meta Catalog Explorer.
I still don't understand the Java version 6 thing. The Eclipse website says they need Java 1.4
Isn't that a very big difference?
Re: can't install in OEA 10.1B
Great! I'm glad it's working OK in OEA.
Java version numbering has some historical baggage.
You'll see "J2SE 1.4", meaning Java 2 version 1.4, whatever that means. Here's how I keep it straight:
1.2 (I think this is when they started the "Java 2" name)
1.3
1.4
1.5 = Java 5
Java 6
So, only two major updates from version 1.4 to version 6. ;)
Happily, I haven't had any trouble with any backward compatibility issues. I've never had trouble just keeping my machine up to date with the latest Java and running .class files that were compiled with any old version of the Java compiler.
The only time I have trouble is when I use, say, Java 1.5 to build .class files and then try to deploy those to some old unix machine still running Java 1.3.
I know it's a prominent FAQ somewhere on their site, but I'm too lazy to go find it. :)