dependency-management

Having yarn outdated is quite informative but I'd like to avoid running over package by package doing yarn upgrade . From yarn's documentation, just yarn upgrade without arguments is said to upgrade all dependencies but there's no change in my project's package.json and yarn outdated shows the same packages versions than before. Is there some command or argument that just bumps all my dependencies? If not, is the practice discouraged in some way? You can update your packages to the latest version specified in the package.json using yarn upgrade without any args. This is taken from the docs :

Below shows the hierarchy of my POMs. You can see that we have a company parent-pom for spring boot projects. This POM has spring-boot-starter as it's parent, and it imports our own dependency-management BOM. [INFO] --- hierarchy-maven-plugin:1.4:tree (default-cli) @ user-service --- [INFO] PARENT com.MY_COMPANY.platform:user:3.20.14-SNAPSHOT [INFO] PARENT com.MY_COMPANY.platform:spring-boot-parent:3.20.12-SNAPSHOT [INFO] PARENT org.springframework.boot:spring-boot-starter-parent:1.5.12.RELEASE [INFO] PARENT org.springframework.boot:spring-boot-dependencies:1.5.12.RELEASE <<<< This pom defines

While I'm familiar with the basics of composer.json and specifying dependencies under the require key I haven't quite understood the purpose of require-dev — Composer's documentation states: require-dev (root-only) Lists packages required for developing this package, or running tests, etc. The dev requirements of the root package are installed by default. Both install or update support the --no-dev option that prevents dev dependencies from being installed. In the abstract it makes sense, but I'm having a hard to imagining the situations when I'd need this functionality. What are the practical

Concerning the pom.xml Maven file: Is there any specific rule to apply to the ordering of declared sections? Does it have any importance or impact on the build? Shall I follow any official convention? Although in most of the cases it is irrevant whether one section is declared before another, readeabilty could be indeed impacted when choosing a weird layout (e.g. Maven coordinates at the end). But that's not the most important point, because yes , ordering of certain elements can impact your build . Order of plugin declarations The order of plugin sections wihtin the build / plugins section

Lets say we have 3 layers project. DB, Business, Web and aggregating pom. Project |-DB | |-pom.xml |-Business | |-pom.xml |-pom.xml All modules are ment to be released and branched together, so Aggregator pom is configured to assign the same version to all submodules. We have the following versions: DB-0.1-SNAPSHOT Business-0.1-SNAPSHOT which depends on DB-0.1-SNAPSHOT Web-0.1-SNAPSHOT which depends on Business-0.1-SNAPSHOT When doing release:prepare , all versions updated to 0.1, but prepare fails because there is no DB-0.1 in dependency yet. One solution is to create different projects for

I'm running a project that has a dependency on groovy 1.7-beta-1. The gmaven plugin uses groovy version 1.6 as a dependency. In my pom, I specify in the dependency management section the grooyv-all version as : <dependencyManagement> <dependencies> <dependency> <groupId>org.codehaus.groovy</groupId> <artifactId>groovy-all</artifactId> <version>1.7-beta-1</version> </dependency> </dependencies> </dependencyManagement> Yet when I run maven in debug mode I see that groovy 1.6 is being used for a dependency to the gmaven plugin. I thought my dependency management section would override this so