You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by GitBox <gi...@apache.org> on 2020/11/17 15:27:32 UTC

[GitHub] [accumulo] ctubbsii commented on issue #1463: Investigate the need for commons-beanutils dependency

ctubbsii commented on issue #1463:
URL: https://github.com/apache/accumulo/issues/1463#issuecomment-729002994


   @dlmarion So, it seems like you might be using Maven a bit wrong, and it may be the reason you're seeing inconsistent results. `mvn test` generally only works in a multi-module project if all the modules are of `jar` or `pom` packaging type. That's not the case for all Accumulo modules. You should use `mvn package` which includes the `test` phase, in order to ensure all the modules have access to their sibling artifacts. It also works if you first do `mvn install`, but I would avoid that, because that taints your local maven repository with SNAPSHOT artifacts that can cause your subsequent builds to resolve local artifacts that are stale from a previous build rather than the current sibling artifacts in your multi-module project. There are cases where you need to use `mvn install` (to make a SNAPSHOT version of a dependency available to a separate project's build), but that's an edge case. Most of your builds should use `mvn package` or `mvn verify` as your build target in the [Ma
 ven build lifecycle](https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html).


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org