tracker issue : CFB-4167694

select a category, or use search below
(searches all categories and all time range)
Title:

"Active Profile" is lost and cannot not recorded by Workspacemechanic

| View in Tracker

Status/Resolution/Reason: Closed/Deferred/

Reporter/Name(from Bugbase): e-domizil License Team / Firstname Lastname (Alexander Hass)

Created: 06/24/2016

Components: Preferences

Versions: 2016

Failure Type: Enhancement Request

Found In Build/Fixed In Build: CFB2016_Update2 /

Priority/Frequency: Major / All users will encounter

Locale/System: ALL / Win 2012 Server x64

Vote Count: 0

Problem Description: The formatter profiles cannot recorded with workspacemechanic. This is below "ColdFusion > Profiles > Editor > Formatter". After resetting the workbench the formatter lists *no* active profile (empty item) and you need to reimport the profile.

Steps to Reproduce:

1. Install workspacemechanic and enable recording.
2. Add your own profile.
3. Stop recording
4. No changes recorded.

Actual Result: I cannot pre-configure CF Builder.

Expected Result: No data loss, record settings. This is not a bug of workspacemechanic. The issue is that Adobe is not using the normal eclipse infrastructure to save settings. It looks like the interface is Eclipse 3.x and has never upograded properly to 4.5.x. Do not require manual re-import of profiles.

Any Workarounds: Let me know, please


Workspace Mechanic can be installed from http://alfsch.github.io/eclipse-updates/workspacemechanic/

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4167694

External Customer Info:
External Company:  
External Customer Name: Firstname Lastname
External Customer Email:  
External Test Config: My Hardware and Environment details:

Attachments:

Comments:

"Eclipse" > "Preferences" > "Oomph" > "Setup Tasks" > also has a "Preference Recorder" and cannot see / record the changes. This is Eclipse build in and does not required Workspacemechanic.
Comment by External U.
26172 | June 27, 2016 05:11:41 AM GMT
Hi , Can you please share the active url of Workspacemechanic where I can apply plugin to eclipse . Thanks, Mukesh
Comment by Mukesh K.
26173 | June 27, 2016 09:37:56 AM GMT
Yes, the old URL got broken. You can use http://alfsch.github.io/eclipse-updates/workspacemechanic/ You can also use the Eclipse build-in feature in Preferences > Oomph > Setup Task > Preference Recorder. That is a newer build-in feature that need to work, too and allow users to transfer it's settings to other workspaces they create. So they do not need to manage hundreds of code style issues by hand.
Comment by External U.
26174 | June 27, 2016 10:10:40 AM GMT
@Firstname Lastname : Thanks for pointing this out. We looked into this and here are our findings : WorkspaceMechanic recorder basically picks any read/write operation occuring to preferences file (.prefs file inside workspace metadata) of the corresponding preference, which is the location of keeping any preferences in eclipse workbench. However, the formatter profile that we provide could not be saved in preferences file because of complexity involved by design, so we used slightly different mechanism for saving profiles.That's why, workspace mechanic is not able to pick changes within formatter profiles. Note: To take care of portability of profiles, we have provided import/export functionality.
Comment by Nikhil D.
26175 | September 20, 2016 08:02:13 AM GMT
That is exactly the bug. You are not using the eclipse infrastructure to save settings. This need to be fixed. Manual import/export settings is not possible. Eclipse itself also has a preference recorder and it is also not working here. Your few settings are not complex to safe. You only use a settings infrastructure from eclipse 3.x that is outdated. Please fix the bugs to make your product working well. Never try to reinvent the wheel. This is a clear failure.
Comment by External U.
26176 | September 20, 2016 08:10:13 AM GMT
Hi , This involves a big design change and has the potential to break few other things. Your point on moving to the eclipse infrastructure to 4.X is a valid one and we will consider moving to this in the next release. For now, we are deferring this bug. We will re-evaluate this in case we hear from more users on the same. Thanks
Comment by Mukesh K.
26177 | September 21, 2016 04:05:53 AM GMT
Oomph is an integral part of Eclipse. When will you fix this issue??? The bug causes DATA LOSS.
Comment by Alexander H.
26178 | September 07, 2017 03:13:29 PM GMT