On 26 Aug 06, at 8:51 AM 26 Aug 06, Barrie Treloar wrote:
> Just build them from source and you can give it a whirl.
Of course, this is always an option, but it's not an ideal one.
Having
to build the snapshots required to test some piece of software takes
away time from the testing itself. If the person that wants
something to
be tested can provide as much as possible up front to the persons
doing
the testing, then more people will actually test it. If the
dependency
is sufficiently tested to warrant a [vote] thread for the product
depending on it, then a snapshot of the dependency should be
published
in my opinion.
This is an excellent example of when this fails. I did the site
update
for this plugin and have a pretty good knowledge of how it works, so
testing should be a breeze, right? Well, it's not.
1. Try building maven-jar-plugin - failed because the latest snapshot
for maven-archiver does not include the stuff used by maven-jar-
plugin
2. Check out maven-shared and try to build maven-archiver - failed
because the latest snapshot of plexus-archiver does not include the
stuff used by maven-archiver
3. Check out plexus-components and try to build plexus-archiver -
failed
because of a test that failed.
Here I am, stuck, one hour later, unable to do what I was supposed
to -
test maven-jar-plugin.
I think it would be good to get continuum setup to deploy snapshots
constantly.
+1
This is ultimately what we need.
This will require enhancing continuum to re-build projects whose
dependencies have also changed.
I think that's in the pipe.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Jason van Zyl
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
