Thanks, Nick for the answer. I opened
https://bugs.eclipse.org/bugs/show_bug.cgi?id=538540 unfortunately I see no
stack trace or error message, so it does not provide a lot of details.

On Thu, Aug 30, 2018 at 10:35 PM, Nick Boldt <[email protected]> wrote:

> Lars,
>
> Try the staging site, that's where the new version updated to compile
> against Eclipse 4.9 lives. The release site has M2, which still contains
> the old Photon-based release.
>
> http://download.eclipse.org/staging/2018-09/
> or
> http://download.eclipse.org/tm/updates/4.5.0-SNAPSHOT/repository/
>
> If it doesn't work, please open a BZ with more details than "does not work
> for me anymore". :D
>
> If you're unable to install from the site, it could be this problem:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=536800#c7
>
> Nick
>
>
> On Thu, Aug 30, 2018 at 3:00 PM Lars Vogel <[email protected]> wrote:
>
>> Hi Nick,
>>
>> FYI - IIRC the Terminal (Console) View is part of Target Management. I
>> just installed into from http://download.eclipse.org/releases/2018-09
>> and this does not work for me anymore.
>>
>> Best regards, Lars
>>
>>
>> On Wed, Aug 29, 2018 at 10:25 PM, Nick Boldt <[email protected]> wrote:
>>
>>> Today, I completed a long-standing request [0] to merge the TM.Terminal
>>> and TM.RSE builds into a single git repo, mvn reactor, jenkins job [1], and
>>> update site [2].
>>>
>>> [0] https://bugs.eclipse.org/bugs/show_bug.cgi?id=536507
>>> [1] https://ci.eclipse.org/tm/job/tm-terminal-rse_master/
>>> [2] http://download.eclipse.org/tm/updates/4.5.0-SNAPSHOT/repository/
>>>
>>> As part of this change, ALL the artifacts in TM and RSE have been
>>> upversioned to 4.5.0, so that everything in the repo is consistently
>>> versioned. This includes the 0.x, 1.x, 2.x, 3.x, and 4.x artifacts from the
>>> Photon release.
>>>
>>> The result of this is that if your project depends on some 
>>> *org.eclipse.dstore,
>>> org.eclipse.tm <http://org.eclipse.tm>, or org.eclipse.rse* bundle or
>>> feature with a version limited to *< 4.0*, your build will fail when
>>> you move up to this new version. But because the only changes I've done
>>> have involved reorganization & update site merging, *not API changes*,
>>> it's entirely safe to move your dependency up from 3.0.0 or [3.0,4.0) to
>>> simply *4.5.0*.
>>>
>>> As an example of how to make this change, here's a proposed fix for DLTK
>>> [2]:
>>>
>>> https://git.eclipse.org/r/#/c/128331/ (dltk.core & target platform)
>>> https://git.eclipse.org/r/#/c/128335/ (dltk.releng)
>>>
>>> [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=538397
>>>
>>> After that fix is applied and built, DLTK 5.10 should be contributed to
>>> simrel instead of 5.9rc4, which is in there right now.
>>>
>>>   <repositories location="http://download.eclipse.org/technology/dltk/
>>> updates-dev/milestone/5.9rc4/" description="DLTK 5.9">
>>>
>>> These changes should fix the failure I'm seeing when trying to build the
>>> simrel site against the new TM 4.5.0-SNAPSHOT update site:
>>>
>>> Dynamic Languages Toolkit - Remote Development Support 5.9.0.201806080529 
>>> (org.eclipse.dltk.rse.feature.group 5.9.0.201806080529) requires 
>>> 'org.eclipse.equinox.p2.iu; org.eclipse.rse.core.feature.group 
>>> [3.0.0,4.0.0)' but it could not be found
>>>
>>>
>>> Once all the projects that depend on RSE, TM, or dstore plugins/features
>>> have been updated, I can then merge this PR without breaking the simrel
>>> site.
>>>
>>> https://git.eclipse.org/r/#/c/128322/
>>>
>>> If you need help migrating your project over, I'm happy to contribute a
>>> BZ and PR.
>>>
>>> Cheers,
>>>
>>> --
>>>
>>> Nick Boldt
>>>
>>> Principal Software Engineer, RHCSA
>>>
>>> Productization Lead :: JBoss Tools & Dev Studio
>>>
>>> IM: @nickboldt / @nboldt / http://nick.divbyzero.com
>>> <https://red.ht/sig>
>>> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>>> @ @redhatnews <https://twitter.com/redhatnews>      Red Hat
>>> <https://www.facebook.com/RedHatInc>
>>> <https://www.facebook.com/RedHatInc>
>>>
>>>
>>> “The Only Thing That Is Constant Is Change” - Heraclitus
>>>
>>> _______________________________________________
>>> wtp-dev mailing list
>>> [email protected]
>>> To change your delivery options, retrieve your password, or unsubscribe
>>> from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>>>
>>
>>
>>
>> --
>> Eclipse Platform project co-lead
>> CEO vogella GmbH
>>
>> Haindaalwisch 17a, 22395 Hamburg
>> Amtsgericht Hamburg: HRB 127058
>> Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
>> USt-IdNr.: DE284122352
>> Fax (040) 5247 6322, Email: [email protected], Web:
>> http://www.vogella.com
>> _______________________________________________
>> cross-project-issues-dev mailing list
>> [email protected]
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
>
> --
>
> Nick Boldt
>
> Principal Software Engineer, RHCSA
>
> Productization Lead :: JBoss Tools & Dev Studio
>
> IM: @nickboldt / @nboldt / http://nick.divbyzero.com
> <https://red.ht/sig>
> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
> @ @redhatnews <https://twitter.com/redhatnews>      Red Hat
> <https://www.facebook.com/RedHatInc>
> <https://www.facebook.com/RedHatInc>
>
>
> “The Only Thing That Is Constant Is Change” - Heraclitus
>
> _______________________________________________
> cross-project-issues-dev mailing list
> [email protected]
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>



-- 
Eclipse Platform project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: [email protected], Web:
http://www.vogella.com
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to