You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by sverhagen <ve...@sander.com> on 2008/09/17 02:02:50 UTC
Testing all versions in a range
Hi, are there any strategies known to test all versions in a range?
E.g. component A defines to be dependent on versions [0.0.4,0.1.0) of
component B for which version 0.0.4, 0.0.5 and 0.0.6 actually exist. Is
there a way to have Maven automatically test A consecutively with B-0.0.4
AND B-0.0.5 and B-0.0.6?
--
View this message in context: http://www.nabble.com/Testing-all-versions-in-a-range-tp19523095p19523095.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Testing all versions in a range
Posted by Wendy Smoak <ws...@gmail.com>.
On Tue, Sep 16, 2008 at 5:02 PM, sverhagen <ve...@sander.com> wrote:
> Hi, are there any strategies known to test all versions in a range?
>
> E.g. component A defines to be dependent on versions [0.0.4,0.1.0) of
> component B for which version 0.0.4, 0.0.5 and 0.0.6 actually exist. Is
> there a way to have Maven automatically test A consecutively with B-0.0.4
> AND B-0.0.5 and B-0.0.6?
I don't know what happened with this, but we had someone on the
Continuum list a while back doing something similar:
"The focus is on determining whether a new version of a module breaks
the build of old clients or builds successfully. One possible approach
is to continuously integrate the clients with the new implementation."
http://markmail.org/message/q4hfly22hjquoz47
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Testing all versions in a range
Posted by Wayne Fay <wa...@gmail.com>.
Not that I am aware of. You would need to lock down each version and
test them individually.
Wayne
On Tue, Sep 16, 2008 at 5:02 PM, sverhagen <ve...@sander.com> wrote:
>
> Hi, are there any strategies known to test all versions in a range?
>
> E.g. component A defines to be dependent on versions [0.0.4,0.1.0) of
> component B for which version 0.0.4, 0.0.5 and 0.0.6 actually exist. Is
> there a way to have Maven automatically test A consecutively with B-0.0.4
> AND B-0.0.5 and B-0.0.6?
> --
> View this message in context: http://www.nabble.com/Testing-all-versions-in-a-range-tp19523095p19523095.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Testing all versions in a range
Posted by Stephen Connolly <st...@gmail.com>.
[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 <ve...@sander.com> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Testing all versions in a range
Posted by sverhagen <ve...@sander.com>.
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Testing all versions in a range
Posted by Brett Porter <br...@gmail.com>.
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
2008/9/17 sverhagen <ve...@sander.com>
>
> Hi, are there any strategies known to test all versions in a range?
>
> E.g. component A defines to be dependent on versions [0.0.4,0.1.0) of
> component B for which version 0.0.4, 0.0.5 and 0.0.6 actually exist. Is
> there a way to have Maven automatically test A consecutively with B-0.0.4
> AND B-0.0.5 and B-0.0.6?
> --
> View this message in context: http://www.nabble.com/Testing-all-versions-in-a-range-tp19523095p19523095.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org