Over the years, badges have become a way for open source maintainers to show the state of their product.
Badges can give a quick overview of the code quality, test coverage or build health of an open-source product.
The problem with code coverage is, however, that a high coverage doesn’t mean the tests are any good.
If only there was a way to show the quality of the test suite…
Together with four “AwesomeSauce” colleagues from Info Support, I’m attending DevNexus this year.
For me, it’s the second time I’m here, as I spoke here in 2018, too.
Next to delivering my own “React in 50 minutes” session I’m attending some sessions to update with new technology advancements.
Shipping a new release of software usually involves quite a few steps.
Depending on the type of software, this may be something you rarely do.
Thus, it often involves manual steps.
This is not necessary!
Maven has had its “Release Plugin” since approximately April 2007; yes, that’s over 12 years!
It has served both the Maven project and many other software projects.
On this second day at Code One I have again visited interesting sessions.
One on security by Jim Manicode and one on cash (or the lack thereof) in Sweden.
This year I’m returning to Oracle Code One (formerly JavaOne) for the third time.
I’m planning to write some notes on interesting sessions or other content.
When you’re writing Java applications, chances are you’re using Maven for dependency management.
It lets you declare the artifacts you need to build your application.
Those artifacts also depend on other artifacts.
This means you have transitive dependencies - dependencies you didn’t declare yourself but you need them anyway.
From yesterday until tomorrow I’m attending Devoxx Poland (or Devoxx PL for short). It’s the second largest conference in the Devoxx family with around 2700 people attending. The conference is held in the ICE Kraków Congress Centre, a large venue with an amazing primary room.
Entrance of the ICE The main reason I’m here is to give a talk about GraalVM on Wednesday morning. Apart from that, it’s a nice opportunity to network, meet old friends and make new ones.
— Read more... →
Recently, Twitter brought the renaming of Ozark to Krazo to my attention. It pulled my attention: I had never heard of either projects, and I wondered what they would be about. Ozark (or Krazo) will be the Reference Implementation of the new Model-View-Controller Specification. This MVC specification, also known as JSR 371, was planned for inclusion in Java EE 8, but eventually dropped. Apparently, this didn’t kill the effort. I was curious to see where the specification (and it’s implementation) would be now.
— Read more... →
There are many situations when you need to write a SOAP-based webservice. Maybe you are writing a test dummy, or maybe you got the interface from some kind of architect. (Yes, there are other reasons, too.) And chances are you’ll be using Spring-WS to do this.
Recently I was doing that, and I found the following inside the interface definition (WSDL):
<element name="faultMessage" type="common:FaultMessage"/> <message name="faultMessage"> <part name="faultMessage" element="tns:faultMessage"/> </message> <portType name="someName"> <operation name="searchOrder"> <input message="tns:searchOrderRequest"/> <output message="tns:searchOrderResponse"/> <fault name="faultMessage" message="tns:faultMessage"/> </operation> </portType> That was a rather challenging thing!
— Read more... →
