+1
On 27-Sep-08, at 6:33 PM, Oleg Gusakov wrote:
wagon API has a very strange method in it: resourceExists(). And
although it is optional -
org
.apache
.maven
.integrationtests
.MavenITmng3703ExecutionProjectWithRelativePathsTest
.testForkFromReport() fails if that method is not present.
Jan and I have been weighting pro and contra of this method in the
Mercury transport API and decided against it as we cannot see where
it gives any advantage over direct GET resource. Indeed - if read
resource fails, it's that same as resourceExists() fails. If read
succeeds, then it's equivalent to sequence: resourceExists();
readResource(); But the latter has a way more network roundtrips
compared to just readResource().
I propose to rewrite the integration test so that it does not fail,
if (optional!) Wagon.resourceExists() is not present. Thus we can
avoid rather costly resourceExists().
Thanks,
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
A man enjoys his work when he understands the whole and when he
is responsible for the quality of the whole
-- Christopher Alexander, A Pattern Language
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
