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:
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]
