For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 1 reply, 2 voices, and was last updated 16 years, 5 months ago by
.
-
Posts
-
Hmm. I’m new to MyEclipseIDE and I’ll probably get flamed as my due diligence should have found where your bugzilla (or equivalent) server is. Asbestos suit donned, flame on . . ..
Bug report for the M2 drop follows.
During installation I asked the wizard to put the common code under ~/bin/mye/common. The following happened: the wizard installed the common code *from the distribution* into ~/Genuitec (seems wrong to me) and only when when I later added some more stuff (plugins, just for kicks) from inside the IDE then it dropped into ~/bin/mye/Common (good boy!).
Severity: Nothing dramatic, but still short of perfection.
Thought you might like to know. Cheers,
alsq
asquassabia,
During installation I asked the wizard to put the common code under ~/bin/mye/common. The following happened: the wizard installed the common code *from the distribution* into ~/Genuitec (seems wrong to me) and only when when I later added some more stuff (plugins, just for kicks) from inside the IDE then it dropped into ~/bin/mye/Common (good boy!).
Yes, currently this is how the installation copies the files. Files which are intrinsic to MyEclipse IDE are copied to ~\Genuitec. If you wish to change this. You can open .pulse2.locator file located at <USER-HOME> directory and change the path here. The installer (assuming you installed using the all-in-one) allows you to change two locations, the location of common files (all the plugins used by your various installations – this will be the meat of the installation in terms of size) and the location of the MyEclipse executable and configuration data. Behind the scenes, Pulse is also installed, but in a default location over which you have no control (AppData/Local/Genuitec/Pulse Explorer). I’m afraid we don’t allow users to change that location through the UI just yet (other than creating a .pulse.locator file before running the installer – which is not something we want users to have to do). This is something we are working on right now
