How to remove maven dependencies downloaded by a particular build?
Like, I have some deps in local repo, then create (clone) a new project, build it (id downloads plethora of deps), then I want to remove the project I’ve cloned and also remove downloaded maven deps from local repo – those downloaded by that build.
I know some of those could be used by oter local projects, but is there a way to manage it? Maybe storing those deps in project dir only like with NPM projects?
How to remove maven dependencies downloaded by a particular build?
Like, I have some deps in local repo, then create (clone) a new project, build it (id downloads plethora of deps), then I want to remove the project I’ve cloned and also remove downloaded maven deps from local repo – those downloaded by that build.
I know some of those could be used by oter local projects, but is there a way to manage it? Maybe storing those deps in project dir only like with NPM projects?
How to remove maven dependencies downloaded by a particular build?
Like, I have some deps in local repo, then create (clone) a new project, build it (id downloads plethora of deps), then I want to remove the project I’ve cloned and also remove downloaded maven deps from local repo – those downloaded by that build.
I know some of those could be used by oter local projects, but is there a way to manage it? Maybe storing those deps in project dir only like with NPM projects?
Maven process got stuck
I launched “mvn clean install” on a multi-module project but after a long period of activity it finally got stuck for no obvious reason. The last displayed line says: [main] WARN o.s.j.e.a.AnnotationMBeanExporter:849 – Bean with key ‘…’ has been registered as an MBean but has no exposed attributes or operations. Any clue for further investigation?
How to override a plugin parent dependency in Maven from the command line?
Running maven at 3.9.8 using the following command which applies maven-dependency-plugin:
How to use Maven Resolver “Trusted Checksums” to ensure artifact integrity?
Recent Maven Artifact Resolver versions have a “Trusted Checksums” feature. As mentioned for example in this Reddit comment it seems that feature can be used to ensure artifact integrity and protect against some aspects of supply chain attacks. And it seems to be more secure than external Maven plugins trying to provide this functionality, since there the plugin itself (and other plugins) are downloaded before integrity verification can be performed.
maven for packaging type ear, is maven-ear-plugin optional in pom.xml
In my pom.xml, the packaging is ear
Spring/Java multiple shared modules for different databases
I’m implementing a software based on the micro-service architecture using Spring/Java. Each micro-service connects to either a PostgreSQL or a MongoDB database. Is it standard practice to have a shared module that contains database-agnostic components (e.g. entity classes, models, and common repository/service interfaces used by both databases) and then have two other shared modules (one for Postgres and the other for MongoDB) importing the first shared module and implement database-specific implementation of those common components?
What’s the value in exposing the dependencies you used for your tests?
In Java, there’s the fairly ubiquitous notion of a POM file which provides the dependencies of your modules.
Multiple Profiles in pom.xml do not build into multiple jars
I have the following project structure