Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 340844

Summary: [releng] Introduce platform-specific plugins
Product: [Modeling] OCL Reporter: Ed Willink <ed>
Component: CoreAssignee: OCL Inbox <mdt-ocl-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3    
Version: 3.1.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows Vista   
Whiteboard:

Description Ed Willink CLA 2011-03-24 08:08:25 EDT 
The backward compatibility issues for Acceleo discussed in Bug 335459 suggest that we migrate the new query delegate functionality. This is the sole dependent on EMF 2.7. If we place it in a ...ecore.indigo plugin the Helios core plugins remain installable on Helios. I think we can do this after the API freeze because it is primarily an incoming rather than outgoing API interaction.
Comment 1 Adolfo Sanchez-Barbudo Herrera CLA 2011-03-25 14:14:04 EDT 
Ed,

Some comments:

1. Lately in Bug 335459 was clear that this is not a problem for Acceleo. This bug applies when trying to offer our backwards compatibility level (Helios platform compatibility, in this case) which we have not defined yet, BTW. We must also remember that other projects on which we depend, doesn't seem to offer said compatibility (I think that, not tested by me certainly).
2. I'm not sure that this change doesn't violate the API freeze. Removing (moving to a different plugin) OCLQueryDelegate class from org.eclipse.ocl.ecore clearly breaks our current M6 API. Maybe you could contrast this with Kenn, or PMC.
3. Without analyzing the code to figure out how the new functionality may be refactored, I also see other inconveniences. As a new feature, I guess we want to make it part of the official release train, that is, as part of the OCL SDK, probably Core SDK and Runtime. If we do so, our features are not helios compatible. So, we have the some alternatives:
    - Create an alternative feature with this enhancement, so that Indigo clients should manually install it if they wanted to benefit from it. Similar to examples feature.
    - Providing that our public repository and features contains the non-Helios repository one, we could also offer a new P2 repository, which contains Indigo MDT/OCL excluding those features non-Helios compatible, so that, Helios clients could use this repository to "upgrade" the Helios compatible features.

In both cases, it will require some kind of manual tasks from the user point of view. It looks like Acceleo approach seems easier to tackle and more transparent for our clients.

Due to these arguments, I'm resolving as won't fix. 

We still need to discuss and establish our backwards compatibility level, if any. Have we been required to do that, BTW ?.

Please, let's carry on the discussion in Bug 335459.

Best Regards,
Adolfo.
Comment 2 Ed Willink CLA 2011-05-27 02:58:06 EDT 
Closing WONTFIXes.
Comment 3 Ed Willink CLA 2012-05-29 13:21:56 EDT 
Closing all bugs resolved in Indigo.