On 17/12/2008, at 1:59 PM, Brian E. Fox wrote:
- we have deployment of the IT plugins to a repository even as
snapshots, though I thought it was required to be pre-installed based
on the bits below?
Everything is ready now for them to be deployed as releases to a repo
that is separate from Central to avoid the clashes that people saw
before.
Great.
I wonder, is the test still valuable enough if we kick off a Jetty
instance and host the repo locally rather than relying on an external
resource being up/accessible?
Upsides: that would also help with avoiding repo manager interference
in the results, tests would be faster
Downsides: a bit more complicated test set up. If it were started from
the POM, it disadvantages IDE running, if it were started from the
tests it adds a bit of complication in there.
WDYT?
John and I came up with this solution because it was frustrating
always
trying to chase either the maven snapshot or the it snapshot when
things
were committed. By putting it into the bootstrap, we now have a single
execution that builds both Maven and the Its and then run them
together.
A single atomic unit. I still see some value in the unpack-and-run
approach personally but I also think having multiple ways to run Its
is
annoying to explain to new users. I think the bootstrap one is easy.
It might be nice to investigate a CI plugin that can always keep those
builds together and take another look in the future.
There are still some things that make me a bit uneasy about it:
- the "dummy" POM (2.0.x)... seems like this should be functionality
right in the top level POM or a "proper" module.
- it seems awkward to work on , you'd need to revert to running mvn
from your working directory for the IT instead since you have to
commit for the other changes to take, or reconfigure itDir
- it's sad that the main way to build Maven is not with Maven :)
I also think it makes sense to release the integration tests that
were
used to verify a particular release of Maven so we always have that
locked in. Otherwise as the ITs change, we have a different measure
of
what worked in 2.0.x and what didn't. The runner approach is much
better suited to this rather than checking it out from a tag each
time.
Agreed.
Cool. I see this change still supports that through a tagged checkout.
Will we release the ITs for 2.0.10, or is that too soon?
Cheers,
Brett
--
Brett Porter
br...@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
