Microsoft Azure is the first public cloud provider to offer Clear Linux, and we’re really excited about what it means for Linux users in the cloud and the community at large,” says Jose Miguel Parrella, Open Source Product Manager, Microsoft.
That’s a job title I never expected anyone to have…
I’ve finally got around to setting up an email server on my personal server (the same one that hosts this website). No more hosted email, it is now entirely under my control which is satisfying (and saves some money). But it was a far from trivial task; I’ve written up everything I learned on the way in this article.
I recently had to decide what version-numbers to assign to development releases of an upcoming product which uses the Maven build-tool. The software is being developed in a series of “sprints”, so my first thought was to use version-numbers 2.0-sprint-3, 2.0-sprint-4 then 2.0. But in Maven, is 2.0-sprint-4 really before 2.0? The Maven docs were unclear, so I researched the topic.
Spoiler: no, it is not; I had to settle for 2.0-beta-* as my naming scheme.
For Java development, I use either Intellij or Eclipse. Both have strengths and weaknesses. I did encounter one very annoying issue with Intellij recently, and apparently it is one that JetBrains have been aware of for over two years, and haven’t shown the slightest interest in fixing. Given that my employer pays for Intellij licences, I feel justified in feeling rather disappointed.
The Intellij/maven integration is generally excellent - much faster and more stable than with Eclipse. However when running Java code from within the IDE, Intellij completely ignores any dependencies declared in the Maven pom with scope=provided. This particularly bites people who (like me) are trying to use Spring Boot, which provides tools that generate maven poms with all necessary dependencies declared. The resulting code compiles fine from the Maven commandline, and can be started via Spring-boot-specific commands. But running the code from the IDE doesn’t work - some required dependencies are not loaded.
This has been reported but is not being taken at all seriously at JetBrains.
It’s a rather tricky problem to work around; a few useful suggestions are made in the above issue-report, but none are perfect.