On 19 Jun 07, at 6:20 AM 19 Jun 07, Mark Hobson wrote:
On 15/06/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> On 15/06/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>> If you install the artifacts you'll be fine. The invoker plugin
broke
>> which is why they are not installed. You can't simply run the ITs,
>> you must install the plugins and artifacts that are used as
part of
>> the ITs.
>>
>> As I go through and find them I update them, but there is still a
>> mixture of some old in there. Ideally the goal is to be able to
start
>> with nothing, install the artifacts required for running the
ITs, and
>> then run the ITs. So if you see things that aren't updated then
fix
>> them.
>>
>> This should ultimately become self-contained:
>>
>> http://svn.apache.org/repos/asf/maven/core-integration-testing/
trunk/
>>
>> Without any requirement for anything to be installed in a remote
>> repository. See the IT problem notes for details.
>
> Right. Should the rest of it0002 not be aligned with the new
group id
> too?
Yes, just align them if you see they are wrong.
I'm still unsure quite how it0002 is meant to pass without
core-integration-testing-support being deployed to the remote repo
under the new groupId. I run:
You have to run the outter build first and what we want ultimately is
use a test remote repository before the ITs run. We have a problem
with them being coupled to the real central. The ITs should
ultimately be completely self contained. So that's what I'm moving
toward so there are for certain some inconsistencies while I move
that way.
Anything you see like that the plan is to start from nothing,
populate the test remote repository with the IT plugins and artifacts
and then run the ITs. The old versions of the ITs artifacts were
deployed to central and the new ones I did not so you're going to
find some glitches. The overriding concern is the make it self
contained. To use a file based remote repository first, then the next
stage would be to use the ITs with a test web-based repository, then
FTP ... you see where I'm going. Get the base ITs going and then test
all our transports, test all our SCM providers ... Take a look at the
notes in the IT directory. We have production plugins coupled with
many ITs and in each of those listed cases test plugins should be
made. Specific tests of a give plugin should be ITs in that
particular plugin.
I'm sure you're going to find some problems but that's the general
plan. So even if you sketch out a bash/ruby script to setup the test
repo before running that's the kind of work we need to get done.
core-integration-testing/core-integration-testing-support/build.sh
core-integration-testing/run-its.sh
And it0002 fails since it cannot download
org.apache.maven.its:maven-core-it-support:jar:1.0. This is
understandable since the test deletes the copy in the local repo
installed by build.sh, and then expects it to be downloaded from the
remote repo which doesn't exist:
http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/maven/its/
Should we not redeploy core-integration-testing-support to the
remote repo?
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
