On Wednesday 04 April 2007 09:51, Rupert Smith wrote:
> 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.
Um Maven 2.0.6 was released last weekend. Thus, 2.
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
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:
T
Spot on Dan. The internal proxy doesn't contain the latest junit-toolkit
stuff. Mainline Qpid builds fine when I disabled all proxies.
Thanks,
Jon
Daniel Kulp wrote:
Jon,
Are you using the IONA internal mirrors/proxies of all the repositories?
If so, you might want to disable the mirrors i
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 reposi
Jon,
Are you using the IONA internal mirrors/proxies of all the repositories?
If so, you might want to disable the mirrors in your settings.xml
temporarily and see if that helps.
Dan
On Wednesday 04 April 2007 08:47, Jonathan Anstey wrote:
> Rupert,
>
> I'm using Maven 2.0.5. After clearin
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
R
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 t
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]
