Ah, seems I've mis-described my situation; I'm not performing a multi-module build. The hierarchy is that of dependencies (submodules, and shared, are listed as dependencies in pom.xml, not as modules). The default site for non-reactor builds only contains Project Dependencies, which does not list provided dependencies.
/jonas -----Ursprungligt meddelande----- Från: Tom Huybrechts [mailto:[EMAIL PROTECTED] Skickat: den 30 oktober 2006 16:51 Till: Maven Users List Ämne: Re: Version validation of "provided" dependencies I don't know the dependency convergence report handle provided dependencies, but it's worth a try. If you build a default site, this report will be included. An example can be seen at http://maven.apache.org/ref/current/dependency-convergence.html Tom On 10/30/06, Jonas Olsson <[EMAIL PROTECTED]> wrote: > > I'll try to visualise the issue: > > > pom.xml (top level artifact, "the deliverable") > | > +- submodule A 1.0 > | | > | +- shared 1.0 [provided] > | > +- submodule B 1.1 > | | > | +- shared 1.1 [provided] > | > +- shared 1.0 [runtime] > > > I want a way for maven to tell me, when packaging the top level artifact, > that submodule B is in conflict with the shared 1.0 we chose to include. > Currently this is not done (provided dependencies are ignored, probably on > the assumption that they are EXTERNALLY provided). > > /jonas > > -----Ursprungligt meddelande----- > Från: Tom Huybrechts [mailto:[EMAIL PROTECTED] > Skickat: den 30 oktober 2006 16:18 > Till: Maven Users List > Ämne: Re: Version validation of "provided" dependencies > > Hi Jonas, > > I'm not sure if this is what you're asking, but the dependencyManagement > section of the pom makes it a lot easier to ensure your versions stay in > sync between different projects. Just specify each dependencies' version > once in that section of the top-level POM... > > Tom > > On 10/30/06, Jonas Olsson <[EMAIL PROTECTED]> wrote: > > > > Hi! > > > > We're introducing Maven to our multi-artifact product build and we'de > > really like to get full usage of the dependency mechanism. We've got > > many shared libraries as "provided" dependencies which are also included > > in the top level artifact to complete the assembly, but "normal" Maven > > version validation does not include "provided" dependencies, so > > out-of-the-box we don't keep feed-back on if all artifacts are OK with > > the actual shared library versions we're including. > > Is there a way (or plugin) to perform this "deeper" kind of version > > validation or are we wrong in asking? > > > > Thank you for input! > > > > -- > > Jonas Olsson > > System Designer > > Cambio Healthcare Systems > > > > > **************************************************************************** > > Detta e-mail har blivit undersökt av http://www.virus112.se > > > > > **************************************************************************** > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > **************************************************************************** > This e-mail has been scanned for viruses by http://www.virus112.se > > **************************************************************************** > > **************************************************************************** > Detta e-mail har blivit undersökt av http://www.virus112.se > > **************************************************************************** > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > **************************************************************************** This e-mail has been scanned for viruses by http://www.virus112.se **************************************************************************** **************************************************************************** Detta e-mail har blivit undersökt av http://www.virus112.se **************************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
