Instead of droppping it, it could be used for nightly builds. We are currently switching our application to Johnzon which implies producing several fixes to make it work, and it would be a good thing to have nightly builds. We can setup that on our server, but I wonder if Team Johnzon wouldn't like to simply use Travis for that, so everybody has that benefit, not just us?
-----Ursprüngliche Nachricht----- Von: Romain Manni-Bucau <rmannibu...@gmail.com> Gesendet: Freitag, 27. September 2019 10:00 An: dev@johnzon.apache.org Betreff: Re: Travis or not travis? up? any issue to drop it? Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le mar. 24 sept. 2019 à 10:40, Romain Manni-Bucau <rmannibu...@gmail.com> a écrit : > Hi everyone, > > we have an old travis.yml in johnzon source code base we don't maintain. > Markus started to work to fix it but the question of the usage popped out. > > AFAIK, nobody uses travis so we could drop it but before pushing that > way I'd like to ensure it is actually the case (but since the setup > was broken since months I guess so ;)) and if it is ok to drop that file for > everybody. > > Side note: don't hesitate to stop and shout you are interested in > using it and we'll make it back ready to work, I just don't want to > keep a maintenance on something which is useless for the community. > > Hope it makes sense > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <https://rmannibucau.metawerx.net/> | Old Blog > <http://rmannibucau.wordpress.com> | Github > <https://github.com/rmannibucau> | LinkedIn > <https://www.linkedin.com/in/rmannibucau> | Book > <https://www.packtpub.com/application-development/java-ee-8-high-perfo > rmance> >
