You may need to run mvn -Pprep-its
before trying to run the IT's There may be one or two IT's which did not have the default plugin versions locked down, and so might fail due to some dependencies not being downloaded into your local repo. On 30 March 2010 13:12, Robert Scholte <[email protected]> wrote: > You should use the verify-phase and the run-its profile, so : > mvn verify -Prun-its > this will trigger the invoker. > There's probably a good reason why this profile isn't active by default. > On my machine some IT's fail as well. > > - Robert > > > Date: Tue, 30 Mar 2010 07:04:22 -0500 > > From: [email protected] > > To: [email protected] > > Subject: [mojo-dev] [jira] Commented: (MVERSIONS-101) Add > processDependencies and processDependencyManagement parameters to > display-dependency-updates goal > > > > > > > [ > http://jira.codehaus.org/browse/MVERSIONS-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216043#action_216043] > > > > Erik Schepers commented on MVERSIONS-101: > > ----------------------------------------- > > > > I'm currently looking into it. The invoker plugin is new to me. So I > started by trying to get the existing integration tests running. > > But, when I run {{mvn invoker:install invoker:run}}, 8 integration tests > fail (including both tests for display-dependency-updates). > > > > Am I doing something wrong? Or is it okay that these tests fail? > > > > > Add processDependencies and processDependencyManagement parameters to > display-dependency-updates goal > > > > ----------------------------------------------------------------------------------------------------- > > > > > > Key: MVERSIONS-101 > > > URL: http://jira.codehaus.org/browse/MVERSIONS-101 > > > Project: Maven 2.x Versions Plugin > > > Issue Type: New Feature > > > Affects Versions: 1.1, 1.2 > > > Reporter: Erik Schepers > > > Priority: Minor > > > Attachments: MVERSIONS-101.patch > > > > > > > > > We are using the {{display-dependency-updates}} goal to check for > version-updates of dependencies. > > > However, our dependencyManagement-sections typically contain much more > dependencies, than we actually have dependencies. This is due to the fact > that we import large BOM (Bill-of-material) poms (see [ > http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies]<http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies%5D> > ). > > > Due to the large amount of managed-dependencies, the > {{display-dependency-updates}} goal takes very long to finish, checking > versions of managed-dependencies we are not using anyway. > > > I noticed that there are some goals that support the > processDependencyManagement and processDependencies parameters. > > > It would really help us to have these parameters for the > {{display-dependency-updates}} goal available as well. > > > > -- > > This message is automatically generated by JIRA. > > - > > If you think it was sent incorrectly contact one of the administrators: > http://jira.codehaus.org/secure/Administrators.jspa > > - > > For more information on JIRA, see: > http://www.atlassian.com/software/jira > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > > ------------------------------ > Express yourself instantly with MSN Messenger! MSN > Messenger<http://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/> >
