Same solution for maven: <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-thymeleaf</artifactId> <version>1.5.1.RELEASE</version> <exclusions> <exclusion> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> </exclusion> </exclusions> </dependency>
It’s not included anymore due to licensing issues if I remember correctly. If you don’t need jms functionality you can exclude jms from log4j dependency: <dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> <version>1.2.15</version> <exclusions> <exclusion> <groupId>com.sun.jmx</groupId> <artifactId>jmxri</artifactId> </exclusion> <exclusion> <groupId>com.sun.jdmk</groupId> <artifactId>jmxtools</artifactId> </exclusion> <exclusion> <groupId>javax.jms</groupId> <artifactId>jms</artifactId> </exclusion> </exclusions> </dependency>
By “run the plugin”, I’m assuming you mean that the plugin is bound to a lifecycle phase, and you’d like to unbind it in some modules. First, you could consider changing your POM inheritance so that the modules that don’t need the plugins have one parent and the ones that do have a different parent. … Read more
UPDATE: as pointed out in the comments this is no more needed because since 2018 heroku changed its default behaviour and dev dependencies are automatically installed ORIGINAL ANSWER Heroku by default installs only the production dependencies, ignoring the development dependencies under devDependencies. Setting the npm production variable to false do the trick: heroku config:set NPM_CONFIG_PRODUCTION=false … Read more
Unity package isn’t a good example because you should use it only in one place called Composition Root. And Composition Root should be as close as it can be to application entry point. In your example it is CompanyName.SomeSolution.Application Apart from that, where I work now, exactly the same problem appears. And what I see, … Read more
You can do this with the Versions Maven Plugin. Check the following goals: versions:display-dependency-updates scans a project’s dependencies and produces a report of those dependencies which have newer versions available. versions:display-plugin-updates scans a project’s plugins and produces a report of those plugins which have newer versions available. Here is a sample output (taken from the … Read more
Upgrade all packages to latest version yarn upgrade –latest
Currently classifiers are not yet taken into account when it comes to resolutionStrategies. A workaround for you might excluding the transitive Guava library when declaring your dependencies and adding the Guava cdi1.0 version explicitly: dependencies { compile (“org.acme:someDependency:1.0”){ exclude group: ‘com.google.guava’, module: ‘guava’ } compile “com.google.guava:guava:15.0:cdi1.0” }
Once you’ve found your jar through mvnrepository.com, hover the “download (JAR)” link, and you’ll see the link to the repository which contains your jar (you can probably Right clic and “Copy link URL” to get the URL, what ever your browser is). Then, you have to add this repository to the repositories used by your … Read more
In addition to the comment, there is more important semantic difference: “Provided” dependencies are expected to be supplied by the container, so if your container gives you hibernate, you should mark hibernate as provided. Optional dependencies are mainly used to reduce the transitive burden of some libraries. For example: If you can use a library … Read more