Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
"Delombok" entire project #249
All the failed builds were on Azure Pipelines, and it looks like it just had network problems. The Travis CI checks were successful, so everything's compiling, your changes are looking good.
As for adding an entire folder at once, are you not familiar with the command-line tool Git? Rather than uploading each file from the browser, you should be using Git on your local computer to add all changes at once, rather than each file individually.
Github has a series of guides for how to get started using Git and how it relates to Github (because they are not the same thing). In particular, the following guides would probably be the most helpful to start with:
You may also be interested in using Git from a desktop GUI client rather than the command-line, and I'm partial to GitKraken, but I've also been hearing good things about GitHub Desktop which is targeted more specifically towards beginners and the GitHub ecosystem.
Travis CI is the primary one right now, its tests on Linux and Mac, and also has the release workflow.
Appveyor tests on Windows.
Codacy handles code quality, like linting and test coverage reports.
And finally, Azure Pipelines is able to handle Windows, Mac, and Linux tests all in one place. Ideally, I would like to get rid of Travis CI and Appveyor and just run all tests and releases on Azure, but as you can see from those checks, there is some instability on that platform right now. I'm keeping it around in addition to Travis CI and Appveyor so I can continue to evaluate it.
I don't mind at all, I'm happy to answer your questions!
First, I just want to say that Java is a great language, and I really enjoy working in Java. It's perfectly fine to keep developing in the Java language, it's gonna be here for a long time. Even though the majority of code I write for the JVM is Kotlin, I still say Java is my favorite language because of the ecosystem built around it and its wealth of high-quality libraries and frameworks.
But Kotlin is also a great language, and it works incredibly well within the larger JVM ecosystem. I am primarily an Android developer at my day job, which is what got me interested in Kotlin initially (I never really touched it before Google's adoption of it on Android). But the more I use it, the more I like it. For the most part, I tend to write the same style of code as I do with Java 8 and Lombok, but Kotlin's reduction of boilerplate is not dependant upon the hacks that Lombok does.
In general, there are a few things that I greatly prefer in Kotlin that Java does not offer. Keep in mind that all of these are just syntactic sugar over features Java already has, and I just prefer the way Kotlin does it:
To be completely honest, my personal recommendation is that, for anyone interested in Kotlin/JVM, you should use it over Java. It's got seamless integration and can be incrementally migrated, you still get all the benefits of the Java ecosystem, but you also get more concise, easier-to-read and easier-to-maintain code.