Yes, that's what I was suggesting. We contribute the handful of fixes in
Rob's fork back to the master repo on git.eclipse.org, build it on a HIPP,
and contribute it into Photon.0.M6.

If someone nominates me as a committer to TM/RSE, I'll make this happen.

On Wed, Jan 31, 2018 at 12:13 PM, Mickael Istria <mist...@redhat.com> wrote:

>
>
> On Wed, Jan 31, 2018 at 6:01 PM, Nick Boldt <nbo...@redhat.com> wrote:
>
>> Should we want to re-include RSE in Photon, we could do so for M6 if
>> someone grants me a place to publish it & permission to do so. We've got a
>> fork [1] that updates the old Oxygen-based TM/RSE build to Tycho 1.0, and
>> it currently builds against Photon.0.M4. This could easily be moved to an
>> Eclipse HIPP, such as this one [2], if I can get permission to edit jobs
>> there & publish to download.eclipse.org.
>>
>
> It's not much allowed to build and publish external (non-Eclipse.org)
> sources on Eclipse.org infrastructre.
> The only way forward, should we want to re-include RSE in Photon, would be
> that Rob and you get the patches you authored merged in the actual TM/RSE
> repository at Eclipse.org.
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> 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

Senior 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>
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
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