Skip to main content

How to search all maven pom.xml for a specific dependency


I was facing some issues with a maven dependency, then I found the the right command to get the specific module pom.xml I was looking for.
As usually I copy it here as a reminder for the future (granted taht we have one, given the situation in North Korea)

$ find . -name pom.xml -exec grep -l jackson {} \;

Comments

Unknown said…
If this command is intended for linux environment, you can add at the end of line this:

2> /dev/null

to suppress noising error messages that can arise for directories producing errors when going into
3/30/2018 09:01:00 PM
Post a Comment

Popular posts from this blog

Multiple controllers with Spring Boot

Remember, when you want to have multiple controllers with Spring Boot, you should always name them differently in the annotation, otherwise they will not work So these two together will NOT work (or just one of them will work) These two instead WILL work.
2 comments
Read more

Can't use the newest npm when node is installed with brew (MacOs)

Even though I installed and reinstalled node with brew, with last versione 11.8.0, apparently it kept using the last version fdecollibus$ npm install --global gatsby-cli npm WARN npm npm does not support Node.js v11.8.0 npm WARN npm You should probably upgrade to a newer version of node as we npm WARN npm can't make any promises that npm will work with this version. npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9. npm WARN npm You can find the latest version at https://nodejs.org/ /usr/local/Cellar/node/11.8.0/bin/gatsby -> /usr/local/Cellar/node/11.8.0/lib/node_modules/gatsby-cli/lib/index.js + gatsby-cli@2.4.8 npm -v gave me back version 5.6.0. I've therefore noticed that  /usr/local/lib/node_modules had wrong permissions assigned to root:wheel. A chown did not fix the problem: I've had to manually delete the content of the folder (cd / usr/local/lib/node_modules and -careful - type rm -rf ...
Post a Comment
Read more