[screaming hack]
OK, here's one idea.
Use Hudson.
Use Matrix build
Define one axis as the versions of the first dependency
Define second axis as the versions of the second dependency
etc...
Change your pom...
use a property to define the version of the first dependency
Have your standard values for each dependency set by default in the pom.
now AFAIR each build axis in a matrix build gets mapped to an environment
variable.... you could either use a profile which is activated if the
${env.AXIS_A} is defined and that profile overrides the property to the
environment variable.... or, you might be able to expand the environment
variable the the Maven goals section that you specify... in which case you
just define the property on the command line, and as properties from the
command line override... presto-chango
[/screaming hack]
Actually, not that much of a hack when I look at it
-Stephen
On Wed, Sep 17, 2008 at 6:05 PM, sverhagen <[EMAIL PROTECTED]> wrote:
>
>
> Brett Porter wrote:
> >
> > No, not without writing your own plugin to enumerate the available
> > versions and re-executing Maven or some tool to do so.
> > This is a good job for an external tool like a CI system and
> > substituting in the different dependency then re-running the build.
> > - Brett
> >
>
> This is pretty much what I expected, but would you already know any CI
> system that has this feature? Continuum doesn't, is what I learn from the
> discussion that Wendy directed us to.
> --
> View this message in context:
> http://www.nabble.com/Testing-all-versions-in-a-range-tp19523095p19536815.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
