I would agree that having dependencies in a POM project is curious, and cannot think of a good use case for them. Are you really looking for <dependencyManagement> where you can declare what versions should be used by inherited projects?
On Thu, Sep 16, 2010 at 10:11 AM, Antonio Petrelli <[email protected]> wrote: > 2010/9/16 Marcus Linke <[email protected]>: >> i 've the following problem releasing a multi-module project with the >> maven-release-plugin (Version 2.0). The top (parent) pom-style project >> defines a set of snapshot dependencies that are inherited to all of its >> submodules. When using the release plugin in interactive mode, the plugin >> prompts for the new versions of these snapshot dependencies. So far, so >> good. But when diving into the submodules this is repeated for each module >> again. This is really annoying me because i have 20 submodules in that >> project. Is this is a know problem or a type of misconfiguration. > > Sincerely having dependencies in a pom project is curious, definitely > I'd remove them. > I suppose that your modules have a precedence, i.e. a module depends on > another. > If you play with transitive dependencies I think you'll get a clean > (and real) dependency tree. > > Antonio > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
