Wim,

The org.eclipse.e4.rcp feature depends on EMF like this:

   <requires>
      <import feature="org.eclipse.emf.common" version="2.7.0" match="compatible"/>       <import feature="org.eclipse.emf.ecore" version="2.7.0" match="compatible"/>
   </requires>

I believe that is what allows these EMF features to be independently updated within the compatible range while ensuring that installing that feature also installs these EMF features.   (Note how very, very old the lower bound is, given EMF 2.23 just released.)

Regards,
Ed


On 19.09.2020 15:59, Wim Jongman wrote:
Hi,

I see that all our wb features are in the release train, which can be confusing. Should I make a top-level feature just for the RT depending on the current RT features? If so can the features then be individually updated?

Thanks,

Wim

image.png





On Sat, Sep 19, 2020 at 10:06 AM Wim Jongman <wim.jong...@gmail.com <mailto:wim.jong...@gmail.com>> wrote:

    Thanks, Ed. It was worth a try.

    On Sat, Sep 19, 2020 at 9:00 AM Ed Merks <ed.me...@gmail.com
    <mailto:ed.me...@gmail.com>> wrote:

        Wim,

        I suppose one alternative is to respin the train repo, but
        that's a big undertaking, especially trying to get it to have
        consistently the same contents as what it current has, other
        than the updated Window Builder.

        Another alternative might be to compose your release
        repository into the train composite.   But you have categories
        in your update site and those would likely become visible.  So
        probably not a good idea either.

        I suspect there is no good/feasible solution at this late
        point.  :-(

        Regards,
        Ed

        On 18.09.2020 19:47, Wim Jongman wrote:
        Hi,

        Due to an API break, the version of windowbuilder in the
        release train is not working anymore.

        Can this be fixed in some way?

        I have a release that works.

        Best regards,

        Wim

        _______________________________________________
        cross-project-issues-dev mailing list
        cross-project-issues-dev@eclipse.org  
<mailto:cross-project-issues-dev@eclipse.org>
        To unsubscribe from this list, 
visithttps://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
        _______________________________________________
        cross-project-issues-dev mailing list
        cross-project-issues-dev@eclipse.org
        <mailto:cross-project-issues-dev@eclipse.org>
        To unsubscribe from this list, visit
        https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to