-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move testsuite into the BOM repository #87
Comments
That is correct. I am not convinced however that moving the testsuite is the best idea |
Why not? |
I just think the repository should be BOM only. |
I think it would be nice to get rid of all the bash magic in the CI configuration. Now we needs to clone, modify the pom.xml in different ways to align the version, build it etc. It might make runs faster too. We could move all of it to the |
I personally wouldn't do it, but I do see some merit no doubt :). Whatever you prefer. |
I'm not married to the idea, just thought of it yesterday while trying to make CI work with 2.2.5. Just wanted to get others input on this. |
I see merits in both points of view. Let's decide on this at the next weekly. |
I think I prefer Gytis' proposition but I've not played enought with this to have a strong advice |
Correct me if I'm wrong, but the testsuite is only used to test the BOM, right? So maybe it would be more logical to move it under the same repository as the BOM? What do you think?
@cmoulliard @metacosm @geoand @iocanel @aureamunoz @jacobdotcosta
The text was updated successfully, but these errors were encountered: