Good, and relieved to see that 2.0.5 is backward compatible after all.
On 04/04/07, Jonathan Anstey <[EMAIL PROTECTED]> wrote:
Rupert, So, there is no problem with the Qpid mainline after all! See my previous email. :) Thanks for your help. As for Maven 2.0.5, we jumped on the upgrade because of a number of bug fixes (check out MNG-1908, for instance... glad to see that one gone!). Cheers, Jon Rupert Smith wrote: > The junit-toolkit-maven-plugin version 0.5 is available on the maven > central > repo. The dependency for it is declared in the top level pom. The > snapshot > repository for the plugin in perftests/pom.xml can be deleted, I think > (the > plugin generates shell scripts to run perf tests). The snapshot > repository > for the toolkit itself is needed at the moment to get 0.6-SNAPSHOT. > > I think this is something with changes in the way maven 2.0.5 works > compared > with 2.0.4. If it compiles on trunk with the 0.5 toolkit version, I won't > object to you checking that in, as I'm mostly working with > 0.6-SNAPSHOT on > the M2 branch. > > Maven 2.0.5 is fairly new isn't it? Try 2.0.4, if you aren't already > locked > into 2.0.5, or promote the idea of getting everyone to move onto 2.0.5. I > haven't even tried 2.0.5 yet. > > Maven 2... what a mess! > > Rupert > > On 04/04/07, Jonathan Anstey <[EMAIL PROTECTED]> wrote: >> >> Rupert, >> >> I'm using Maven 2.0.5. After clearing out my m2 repo, the build failed >> looking for uk.co.thebadgerset:junit-toolkit-maven-plugin:pom:0.5. >> Actually, after looking at the comments above this plugin (in >> perftests/pom.xml), I think it should be commented out altogether :) >> >> Cheers, >> Jon >> >> >> Rupert Smith wrote: >> > What version of Maven are you using? I changed the depdency version of >> > junit-toolkit to [1.2.8,) so as not support versions 1.2.8 or later >> > and not >> > force dependees onto 1.2.8. >> > >> > I'm on maven 2.0.4 which supports this syntax. Are you on an older or >> > newer >> > version of Maven than this? >> > >> > Maybe you could try deleting your local repository (from >> > uk.co.thebadgersetdownwards and log4j downwards too) and see if that >> > might help. >> > >> > Rupert >> > >> > On 04/04/07, Jonathan Anstey <[EMAIL PROTECTED]> wrote: >> >> >> >> Hi guys, >> >> >> >> Is anyone else having trouble building the performance tests? I >> copied >> >> the error I'm getting below. BTW changing junit-toolkit back to >> version >> >> 0.5 allows the build to proceed. >> >> >> >> Thanks, >> >> Jon >> >> >> >> >> >> [EMAIL PROTECTED] perftests]$ mvn >> >> [INFO] Scanning for projects... >> >> [INFO] >> >> >> >> >> ---------------------------------------------------------------------------- >> >> >> >> >> [INFO] Building Qpid Performance Tests >> >> [INFO] task-segment: [install] >> >> [INFO] >> >> >> >> >> ---------------------------------------------------------------------------- >> >> >> >> >> [INFO] [resources:resources] >> >> [INFO] Using default encoding to copy filtered resources. >> >> [INFO] >> >> >> ------------------------------------------------------------------------ >> >> [ERROR] BUILD ERROR >> >> [INFO] >> >> >> ------------------------------------------------------------------------ >> >> [INFO] Failed to resolve artifact. >> >> >> >> No versions are present in the repository for the artifact with a >> range >> >> [1.2.8,) >> >> log4j:log4j:jar:null >> >> >> >> from the specified remote repositories: >> >> central (http://repo1.maven.org/maven2), >> >> junit-toolkit.snapshots >> >> ( >> http://junit-toolkit.svn.sourceforge.net/svnroot/junit-toolkit/snapshots/ >> >> >> >> >> ) >> >> >> >> >> > >> >> >
