or just use co-pilot status (no rewrite) and manually upgrade your pom.xml based on what is reported as outdated, current option if you need to keep your pom.xml formatting.start with co-pilot format pom, verify that the rewrite of the pom.xml is ok, commit, and from now on you will easily see the diff that co-pilot introduces with co-pilot upgrade.
co-pilot rewrites your pom.xml, so make sure you have your pom.xml committed before testing out co-pilot.Brings feature to the table, not found anywhere else, stay tuned!.Can be used as a library for other go-projects automating the upgrade process.Brings natural semantics and support for different types of dependencies to the table: Kotlin, 2party, spring-boot (curated dependencies), (other) 3party.No installs of maven-plugins required, so if you a working in a multi-repo developer environment with lots of 2party dependencies and repos, you can easily upgrade them with co-pilot upgrade 2party.
Upgrade your pom.xml dependencies to latest and greatest! A little "go help" for the Java/Kotlin developers using Maven.
0 kommentar(er)
