Hi Wendy,
Olivier, would you be able to make the change you describe below on
the deploy plugin trunk?
The "small change" is to switch back to using the Install Plugin to
stage the artifact under test into the IT repo. I hope Oliver doesn't
mind that I went for this ;-)
Or can you explain how to reproduce the problem *without* doing a
release, so I can tell that what I'm adding to the pom fixes it?
Steps to reproduce the problem on maven-deploy-plugin trunk:
- Enable snapshot repo for the ITs, e.g. add apache.snapshots to the
src/it/settings.xml
- Remove the execution of install:install-file I added in r681943
- Run "mvn clean verify"
- Check the target/its/mdeploy-45-test/build.log for this line
[DEBUG] maven-deploy-plugin: resolved to version 2.4-20080802.034406-6 from
repository apache.snapshots
which should have been
[DEBUG] maven-deploy-plugin: using locally installed snapshot
if MINVOKER-43 wouldn't exist.
In other words, the IT is not testing your locally build artifact. This
need not fail the tests as long as the snapshot erroneouly pulled in
from remote is good/recent enough, but the IT remains broken.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
