Hi, La 09.06.2020 16:33, Matthieu Baechler a scris: >> I propose we make integration tests OPT-IN behind a maven profile ?! > I hate maven profiles because everything becomes unpredictable very > quickly when we use them. > > However, I agree that few people want a long testsuite to run when > building a software and it should be OPT-IN. We invented CI for a thing > after all. > > I suggest we just change the default behavior of surefire maven plugin > to not run tests by default and document how to run tests when wanted. You have my +1 for that. But since you mentioned Gradle see my reply bellow. >> I propose we document how people can OPT-IN FOR them. >> >> What are other ways of making a James build slimmer ?! > There are many ways: we did experiments with gradle and the results > were very promising (around 1 minute on my computer) but postponed the > adoption for now.
I'm willing to put some effort into moving the project to gradle if we decide we want to do that. It has benefits for larger builds. We can have both builds side by side until we make the switch. We can announce it on the mailing list and we can start right after 3.5 is out. > We could also, for component relying on stable APIs, move these > components in their own git repository to avoid building them with the > main codebase. > > Cheers, Working with multiple git repositories is not the best experience. It tends to slow things down. I did not have a chance to look at gradle composite builds https://docs.gradle.org/current/userguide/composite_builds.html . I did not try it but I suspect we can: - have our library repositories - move the application parts in another git repo - using a composite build to bring libraries and James App together -- Eugen Stan +40720 898 747 / netdava.com
<<attachment: eugen_stan.vcf>>
signature.asc
Description: OpenPGP digital signature
