Re: [egerrit-dev] Major EGerrit Changes

[Pascal Rapicault <pascal@xxxxxxxxxxxx>]

The fact that ChangeInfo was API was not a sign of confidence nor a commitment from our part, but just an oversight. IMO this should have never been made API in the first place. And in fact, I don't think anything in EGerrit should be API at this point.

In the long term it may be possible that the model and the command will be APIs but I think this is too early and there are many other things that we'd like to fix / improve before this.

That said, this should not prevent you from using the internal packages since they are exported by the bundles.

Pascal

On 16-02-23 07:49 AM, Steve Elsemore wrote:

The 0.3.0 changes are great, but unfortunately for me the refactoring that took place as part of the transition to EMF makes it no longer possible to integrate EGerrit into my own Eclipse application.  This application makes Gerrit interaction pluggable, currently supporting EGerrit and the Mylyn Gerrit connector as alternative providers, where the provider handles executing Gerrit queries and opening Gerrit changes in an internal editor.

In earlier versions, it was possible to use QueryChangesCommand to perform built-in and custom queries, and it was possible to construct a ChangeDetailEditorInput and open the ChangeDetailEditor from within my own plugin.  Now, however, mainly because ChangeInfo has been moved to an internal package, this is no longer possible.

Is there any chance that these actions might be exposed again?

Thanks,

Steve

_______________________________________________
egerrit-dev mailing list
egerrit-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/egerrit-dev