Community
Participate
Working Groups
-> RegisterGeneratedPackage sub menu -> PackageManagerDialog
Re-assigning to Vik in preparation of his new committer state...
Eike, I've been looking a bit a this bug. However, I can't find any way to determine if a session has legacy support enabled. Could we add something to CDOSession.options() like "isLegacyEnabled()"? Should I add dependency to: 247226: Transparently support legacy models https://bugs.eclipse.org/bugs/show_bug.cgi?id=247226
Yes, I think the CDOSession:isLegacySupportEnabled() method is hidden somewhere in the bug #247226 patch ;-( I reduced the prio to P4
Rebasing all unresolved enhancement requests to 3.0
Martin, I think this doesn't make much sense since the legacy on/off flag is in the CDOView scope. If you agree then please close this bug as WONTFIX.
Guessing the scope of this bugzilla from the title and the short description this is already done because legacy is switched of by default. But I think that our UI namely the CDOSessionsView should be able to handle legacy. Either by switching it always 'on' or by implementing a button for changing the behavior. We could use this bugzilla for the task or raise a new one. In the latter case I agree with closing this one. What do you think about?
My concern is more that EPackages are to be registered against a CDOSession, whereas the new legacy configuration is effective in the scope of CDOViews. I think this bugzilla is just senseless now.