|Re: [tycho-dev] tycho vs tycho-extras: what's the value?|
+1 for merging the two into one repo, the plan sound reasonable
I don't know why they were created separate (this dates from before I was committer) and de facto they are tightly coupled and have always been released together.
I think the name tycho-extras is more like a hint that these are optional add-ons that not every tycho build necessarily needs.
technically I would keep things the same on maven artifactId/groupId level and simply combine the two builds into on with a common parent.
As you already said this would probably get rid of some double-maintenance of version management of dependencies and other top-level pom settings.
So in effect building/releasing Tycho is simplified but for the user things stay the same.
So here is my proposal of execution
1. we move all the content of org.eclipse.tycho.extras into a top-level "tycho-extras" folder in the same repo
2. 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 builds
We wait for some time for some issues to be popping up and remediate them, and when we are happy with it
1. we refactor the pom: tycho root pom.xml references tycho-extras, the tycho-extras pom takes the root pom.xml as parent
2. we adapt jobs so the build of tycho & tycho-extras become only 1 step
And then, we'll be all set and we can improve things further continuously.
@Sievers, Jan specifically, as project lead, do you support this?
Back to the top