logo ${project.artifactId}

Once upon a time i had to define the deployment in each of my applications. The pom.xml's and bash scripts didn't stop growing with build instructions which my app doesn't care about. I needed thousands commits for hacky testing of my CI/CD systems even if i just want to do defaults like tagging or semantic versioning. So i started this project to keep the build instructions in my environment and have the plugin already tested. Now i can run with auto configuration my deployments daily. The plugin will even take care of updating all dependencies as semantic versioning. And all lived happily ever after. This plugin will autoconfigure "every" default for you. Pom file descriptions are not need anymore. For example: * Auto configuration * semantic versioning * update dependencies and plugins * maven plugins, * Readme.md variables and placeholder, * Tagging, * [...] and much more while you can still use the original maven userProperties and/or systemProperties (ignoring ".", "_", "-") to configure the plugins

homepage:
fresh index:
last release: 2 weeks ago, first release: 11 months ago
packaging: maven-plugin
get this artifact from: central
see this artifact on: search.maven.org

How to exclude this artifact from Spring Boot JAR



How much is this artifact used as a dependency in other Maven artifacts in Central repository and GitHub:


This artifact is a Maven plugin. How to use it in Maven project.

© Jiri Pinkas 2015 - 2020. All rights reserved. Admin login To submit bugs / feature requests please use this github page
related: JavaVids | Top Java Blogs | Java školení
Apache and Apache Maven are trademarks of the Apache Software Foundation. The Central Repository is a service mark of Sonatype, Inc.