Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
Improve this question
I have been working configuring a number of projects for use with Maven.
Most projects contains multiple modules (POMs) and these are all based on a few POMs I pulled from another project.
While the structure is generally fine, there are a number of redundant elements included in some files.
Is there a tool that I can use to scan for elements that are duplicates, not ever referenced, should be moved up a level etc.
I have been looking at Maven POM Lint Plugin, which looks like it might do the job. Is there anything else I should be considering?
Maven POM Lint Plugin can help you a bit in maintaining your POMs to be clean and short. For me however, what is usually far more important, is to manage declared dependencies right. I like to have only those dependencies declared that are really used and also I like to explicitly depend on what I use without getting stuff transitively. For these things I recommend Maven Dependency Plugin with its dependency:analyze goal.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 1 year ago.
Improve this question
While we creating a new spring boot project in Spring Initializr or in Eclipse or in Intelliz why do we choose Maven Project over Gradle Project?
It isn't related to Spring Boot in fact but rather to your general preference - whether you prefer Maven or Gradle for your project, regardless of the fact that Spring Boot is used.
Both: Maven and Gradle are well supported by Spring Boot, i.e. there are plugins for both of them to support Spring Boot projects so considering this framework - you don't lose anything regardless of your choice.
You can easily find a plenty of comparisons between these two to decide which one you prefer. Generally speaking - Gradle is newer with its advantages (flexibility given by Groovy syntax, performance etc.) and disadvantages (there are more docs and tutorials for Maven).
You dont , you can do both ways . both have their pros and cons .
Here is a gradle.org comparison .
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
Improve this question
What tools are recommended for comping LESS files into CSS within a Spring Boot web app? I am using Thymeleaf and Maven and I am setting up a sample project. I wanted to import my current project's LESS files in to this sample project. Thanks for any recommendations.
You're asking about the compilation, however, Spring boot is a runtime framework.
I understand that you should compile *.less files into *.css files during the build and then just package the CSS files into spring boot application and make the application serve the static content.
Another option is not to pack the static files into the application but place them somewhere else (here the list of options will vary from some webserver like apache or Nginx to S3 bucket or even CDN) so that the java server won't deal with the static content and instead will totally concentrate on backend processing.
So, given maven is a build tool of your choice and you want to use maven to compile less into CSS, you should look for plugins doing this.
Quick googling shows This plugin (disclaimer - I've never used it by myself).
Now in order to make spring boot serving your static content, this question has been already answered in SO Here
Basically, you should place the code into some pre-defined directory in build time and you're good to go.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
Hello I've been looking for a step by step guide on how to create a webjar of an existing project. My Front-End project is currently using Angular 2 + webpack, I understand the files need to go in a specific directory META-INF/resources/webjars and that there should be a starter Maven pom file somewhere in the project. The thing is I'm not sure where or how to start implementing this inside my project and so I'm asking here if anyone could help me out or knows where I can find a step by step guide for this.
I plan to use the webjar as a dependency for another project built using Spring Boot. Any help is greatly appreciated.
WebJars is really just a packaging of JS / CSS libs that can easily be used as dependencies in Java builds. By putting the contents of these libraries in the META-INF/resources they are automatically available as static resources in most Java web servers. So to create your own JAR that has static resources in the META-INF/resources you can create a JAR however you like. This is usually done with a build tool like Maven or Gradle. If you want to publish that JAR somewhere that anyone can consume as a dependency then most people use Maven Central.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I've always wondered what these are. I've read the Maven documentation about this and I don't think I really understand it. Could somebody please explain this? Thanks.
Optional dependencies are used when it's not really possible (for whatever reason) to split a project up into sub-modules. The idea is that some of the dependencies are only used for certain features in the project, and will not be needed if that feature isn't used. Ideally, such a feature would be split into a sub-module that depended on the core functionality project...this new subproject would have only non-optional dependencies, since you'd need them all if you decided to use the subproject's functionality.
However, since the project cannot be split up (again, for whatever reason), these dependencies are declared optional. If a user wants to use functionality related to an optional dependency, they will have to redeclare that optional dependency in their own project. This is not the most clear way to handle this situation, but then again both optional dependencies and dependency exclusions are stop-gap solutions.
Reference: http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 years ago.
Improve this question
Is there a maven plugin which I can use to check if there was a commit since the project had been released the last time?
I want to enforce people to keep up with the project documentation and therefore I want to check during the build process if there have been commits to the documentation docbook project since the last release. If there aren't any the build should fail, because there has been no update of the documentation.
Or do you have other approaches to automatically assure that people keep documenting?
I don't know of a single Maven plugin to do what you want. There are a couple of plugins that might work together though. maven-scm-plugin has goals diff and changelog. diff may be configured to write its output to a file; maybe you could examine the file contents with the gmaven plugin or maven enforcer plugin. The latter has a goal that will fail the build if a file is not within a size range. You may also write custom enforcer rules if the existing ones don't quite do it.