From 2bff48e16a187ed935c9cbdea679d5c2b41f3d85 Mon Sep 17 00:00:00 2001 From: cesarsotovalero Date: Tue, 9 Mar 2021 22:28:21 +0100 Subject: [PATCH] Prepare for major release 2.0.0 --- README.md | 10 ++++------ depclean-core/pom.xml | 4 ++-- depclean-maven-plugin/pom.xml | 7 +++---- pom.xml | 2 +- 4 files changed, 10 insertions(+), 13 deletions(-) diff --git a/README.md b/README.md index e099498d..1d0c25de 100644 --- a/README.md +++ b/README.md @@ -13,10 +13,8 @@ [![Duplicated Lines (%)](https://sonarcloud.io/api/project_badges/measure?project=castor-software_depclean&metric=duplicated_lines_density)](https://sonarcloud.io/dashboard?id=castor-software_depclean) [![Technical Debt](https://sonarcloud.io/api/project_badges/measure?project=castor-software_depclean&metric=sqale_index)](https://sonarcloud.io/dashboard?id=castor-software_depclean) - [comment]: <> ([![Coverage](https://sonarcloud.io/api/project_badges/measure?project=castor-software_depclean&metric=coverage)](https://sonarcloud.io/dashboard?id=castor-software_depclean)) - ## What is DepClean? DepClean is a tool to automatically remove dependencies that are included in your Java dependency tree but are not @@ -52,7 +50,7 @@ You can configure the `pom.xml` file of your Maven project to use DepClean as pa se.kth.castor depclean-maven-plugin - 1.1.3 + 2.0.0 @@ -86,7 +84,7 @@ For example, to fail the build in the presence of unused direct dependencies and se.kth.castor depclean-maven-plugin - 1.1.3 + 2.0.0 @@ -105,7 +103,7 @@ Of course, it is also possible to execute DepClean with parameters directly from can be executed directly as follows: ```bash -mvn se.kth.castor:depclean-maven-plugin:1.1.3:depclean -DfailIfUnusedDirect=true -DignoreScopes=provided,test,runtime,system,import +mvn se.kth.castor:depclean-maven-plugin:2.0.0:depclean -DfailIfUnusedDirect=true -DignoreScopes=provided,test,runtime,system,import ``` ## Installing and building from source @@ -133,7 +131,7 @@ Once the plugin is installed, you can execute the `depclean` plugin goal directl mvn compile mvn compiler:testCompile # Then, executed DepClean -mvn se.kth.castor:depclean-maven-plugin:1.1.3:depclean -DcreatePomDebloated=true -DcreateResultJson=true +mvn se.kth.castor:depclean-maven-plugin:2.0.0:depclean -DcreatePomDebloated=true -DcreateResultJson=true ``` This is an example of the output (note the dependencies are ordered according to the JAR size): diff --git a/depclean-core/pom.xml b/depclean-core/pom.xml index f493690d..6a180ad4 100644 --- a/depclean-core/pom.xml +++ b/depclean-core/pom.xml @@ -8,12 +8,12 @@ se.kth.castor depclean-parent-pom - 1.1.3 + 2.0.0 depclean-core - 1.1.3 + 2.0.0 jar Core library of DepClean depclean-core diff --git a/depclean-maven-plugin/pom.xml b/depclean-maven-plugin/pom.xml index da59235f..c81a27e9 100644 --- a/depclean-maven-plugin/pom.xml +++ b/depclean-maven-plugin/pom.xml @@ -6,13 +6,12 @@ se.kth.castor depclean-parent-pom - 1.1.3 + 2.0.0 depclean-maven-plugin - 1.1.3 - + 2.0.0 maven-plugin depclean-maven-plugin @@ -51,7 +50,7 @@ se.kth.castor depclean-core - 1.1.3 + 2.0.0 diff --git a/pom.xml b/pom.xml index df5fa885..b309871c 100644 --- a/pom.xml +++ b/pom.xml @@ -6,7 +6,7 @@ se.kth.castor depclean-parent-pom - 1.1.3 + 2.0.0 pom 4.0.0