Community
Participate
Working Groups
Expose these classes in the API to let other vendors extend the command line generator without needing to implement the entire thing. This topic is extracted from bug 571405 comment 9.
@Jonah: How do I proceed to make these classes part of the public API? I did not put a target milestone for this ticket as I'm not sure if it can be done in the 10.2 scope.
Short answer is I don't know. I guess easy thing is to just move the files from the internal package to a non-internal one. However that has the side-effect of breaking existing extenders (like embed-cdt) that are using the internal one. One option is to make the entire package non-internal (remove x-internal from manifest) but leave the name as is. Have a look at https://wiki.eclipse.org/Evolving_Java-based_APIs to see if there is anything there. PS I added the new versions and target milestones to bugzilla if you want to target 10.3.0 (it is probably too late for 10.2.0 if there is anything in the change that risks breaking adopters)
Maybe the clean solution is to create a copy outside the internal package and then just mark the one in the internal package as deprecated and point to the public one? Then in an upcoming version of CDT, we simply purge the internal copy.
That sounds very reasonable.
New Gerrit change created: https://git.eclipse.org/r/c/cdt/org.eclipse.cdt/+/176745
Gerrit change https://git.eclipse.org/r/c/cdt/org.eclipse.cdt/+/176745 was merged to [master]. Commit: http://git.eclipse.org/c/cdt/org.eclipse.cdt.git/commit/?id=0ca137e8540f773f6ab8d0190d5802c70fc7f456
Updated the summary as the ManagedCommandLineInfo was not put as API.