Merge branch 'hotfix/1.0'

Author: michaelajr

README.md

@@ -1,5 +1,5 @@
 ## Example Child JAR
-An example JAR project showcasing the Parent POM's pipelining capabilities. For details, see our companion article <a href="https://medium.com/eonian-technologies/maven-for-pipelining-part-1-8b850d10a7ee" target="_blank">Maven For Pipelining</a>.
+An example JAR project showcasing the the <a href="https://github.com/eonian-technologies/example-parent-pom">parent POM's</a> pipelining capabilities. For details, see our companion article <a href="https://medium.com/eonian-technologies/maven-for-pipelining-part-1-8b850d10a7ee" target="_blank">Maven For Pipelining</a>.
 
 ## Discrete Pipeline Steps
 The plugins that make up these steps are bound to the Maven Lifecycle by the Parent POM. So a command like `mvn install` will execute them by default. But when pipelining, we want to execute a series of smaller, more granular steps, and make judgments on whether or not to proceed based on their output. A lifecycle goal like `mvn install` does too much. If the CI job running the command breaks there are several things that could have gone wrong. Could it not compile? Could it not run tests? Did the tests fail? Which tests failed, unit tests or integration tests? So when setting up the project’s CI pipeline we won’t use a single step that runs a command like mvn install. Instead we’ll create discrete pipeline steps which directly call their corresponding Maven plugins.