TM committers,
As the releng guy for TM, I've got a few ideas for what we can do to reduce the overhead for running CI builds and managing versions.
Here's what I'd like to do:
a) move Terminal's RSE Adapter from Terminal repo to RSE repo, and mark deprecated.
b) bump the version of the Terminal and RSE features to 4.5 (so both projects are consistently upversioned from their previous releases)
c) create a job that builds BOTH RSE and Terminal in the same operation, and publishes to a SNASPHOT URL (or optionally a non-SNAPSHOT URL when it's release time).
We could also merge both the RSE and Terminal repos into a single one, driven by a single root pom. That would allow three build modes:
* cd root-folder; mvn clean install # build everything (as on Jenkins)
* cd root-folder/rse; mvn clean install # build only RSE (for people wanting to contribute to RSE only, needing a local verification build)
* cd root-folder/terminal; mvn clean install # build only Terminal (for people wanting to contribute to Terminal only, needing a local verification build)
I will assume that silence == agreement and proceed with this plan for the 2018-09 M2 or M3 milestone (no time to do so for M1).
Thanks,
--
Nick Boldt
Principal Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
IM: @nickboldt / @nboldt / http://nick.divbyzero.com
“The Only Thing That Is Constant Is Change” - Heraclitus
