On 26 Aug 06, at 6:59 AM 26 Aug 06, Dennis Lundberg wrote:
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.
So far you are the only one who's probably even tried it. It's
generally the case that the person doing the release is going solo
unfortunately. So I'm glad you tried it. But I generally build
everything from source, snapshots certainly can't hurt and if they
help testing that's cool. Ultimately an instance of Continuum will be
the arbiter. You not being able to build something doesn't mean
anything either.
I will start in the order I built stuff i.e. the dependency order:
plexus-archiver:
- builds for me
- http://ci.codehaus.org:8001/continuum/servlet/continuum/target/
ProjectBuild.vm?view=ProjectBuild&buildId=50887&id=10
- The problem here appears to be running the tests without a clean.
Seem to fail the second time around.
- snapshot deployed for you
maven-archiver:
- builds for me
- http://ci.codehaus.org:8002/continuum/servlet/continuum/target/
ProjectBuild.vm?view=ProjectBuild&buildId=8421&id=178
- snapshot deployed for you
maven-jar-plugin:
- builds for me
- http://ci.codehaus.org:8002/continuum/servlet/continuum/target/
ProjectBuild.vm?view=ProjectBuild&buildId=8069&id=47
- snapshot deployed for you
I try not to be a retard when preparing releases, but I definitely
make my fair share of blunders. It all seemed fine to me. I deployed
snaps for everything so it should be easier.
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.
Not sure why you built them in the backward order. Sorry it was a
pain in the ass for you, but I always make the assumption people
build from source. Easy enough to change as what you request makes
sense.
I have reported test failure in plexus-archiver in http://
jira.codehaus.org/browse/PLX-226
--
Dennis Lundberg
---------------------------------------------------------------------
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]
