|Re: [tycho-dev] tycho vs tycho-extras: what's the value?|
So here is my proposal of executionPhase 11. we move all the content of org.eclipse.tycho.extras into a top-level "tycho-extras" folder in the same repo2. From org.eclipse.tycho (non-extras) Git repo, we fetch the top of tycho.extras and merge it-> This should result in a merge commit with 2 branches of history: one about tycho-core and the other about tycho-extras, so history is still there-> the tycho-extras folder is not part of tycho-core
_______________________________________________3. we tweak the existing core CI jobs to build tycho and then build tycho-extras (like it's already done in https://ci.eclipse.org/tycho/job/tycho-build-with-maven-snapshots/ , and we disable tycho-extras buildsWe wait for some time for some issues to be popping up and remediate them, and when we are happy with itPhase 21. we refactor the pom: tycho root pom.xml references tycho-extras, the tycho-extras pom takes the root pom.xml as parent2. we adapt jobs so the build of tycho & tycho-extras become only 1 stepAnd then, we'll be all set and we can improve things further continuously.Any objection?@Sievers, Jan specifically, as project lead, do you support this?
tycho-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Back to the top