Hi Ed,

We have made an emergency release and all is good now.

Thanks for helping.

Cheers,

Wim



On Sun, Sep 20, 2020 at 9:20 PM Ed Willink <[email protected]> wrote:

> Hi
>
> It would be nice to avoid WindowBuilder going the same way as VE the
> Visual Editor.
>
> IIRC I managed to resurrect a VE build to make it useable for a couple of
> extra years, by which time WindowBuilder came to the rescue. That seems so
> long ago (2008) that I can find no sign of my rescue with Google; probably
> because VE has been erased (archived).
>
> If you can identify the API breakage we can maybe persuade the platform to
> revert.
>
>     Regards
>
>         Ed Willink
>
>
> On 19/09/2020 14: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: image.png]
>
>
>
>
>
> On Sat, Sep 19, 2020 at 10:06 AM Wim Jongman <[email protected]>
> wrote:
>
>> Thanks, Ed. It was worth a try.
>>
>> On Sat, Sep 19, 2020 at 9:00 AM Ed Merks <[email protected]> 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 [email protected]
>>> To unsubscribe from this list, visit 
>>> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>>
>>> _______________________________________________
>>> cross-project-issues-dev mailing list
>>> [email protected]
>>> To unsubscribe from this list, visit
>>> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>>
>>
> _______________________________________________
> cross-project-issues-dev mailing [email protected]
> To unsubscribe from this list, visit 
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>  Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
> <#m_-6430110532328476351_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> _______________________________________________
> cross-project-issues-dev mailing list
> [email protected]
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to