This pb appears because maven use an old wagon version and continuum use the latest 1.0-beta-2.
The jetty plugin doesn't fork the process and use the old version instead of the one declared in continuum pom.

All works fine with maven 2.0.5.

Emmanuel

Marcelo Fukushima a écrit :
> hello devs (here i am yet another annoying email)
> 
> it all started while i was trying to fix a bug
> (http://jira.codehaus.org/browse/CONTINUUM-1103)... while i was doing
> that, ive found out that the jpox 1.1.1 created wrong queries (its
> even commented as a weird thing)
> after upgrading its version to 1.1.3, it passes the TestCase but
> continuum would not run... after spending some time with it, ive
> noticed that the error has nothing to do with jpox, but its rather
> related to a plexus config file:
> 
> Caused by: 
> org.codehaus.plexus.component.repository.exception.ComponentRepositoryException: 
> 
> Component descriptor role:
> 'org.apache.maven.wagon.providers.ssh.knownhost.KnownHostsProvider',
> implementation:
> 'org.apache.maven.wagon.providers.ssh.knownhost.FileKnownHostsProvider',
> role hint: 'file' has a hint, but there are other implementations that
> don't
> 
> weird... but after going back to 1.1.1, i get the very same error...
> and after checking out the code from trunk, i still get the same
> error...
> 
> i went to that config file (inside wagon-ssh), and ive found this:
> 
>    <component>
>      
> <role>org.apache.maven.wagon.providers.ssh.knownhost.KnownHostsProvider</role> 
> 
>      <role-hint>file</role-hint>
>      
> <implementation>org.apache.maven.wagon.providers.ssh.knownhost.FileKnownHostsProvider</implementation> 
> 
>      <instantiation-strategy>per-lookup</instantiation-strategy>
>      <configuration>
>        <hostKeyChecking>ask</hostKeyChecking>
>      </configuration>
>    </component>
>    <component>
>      
> <role>org.apache.maven.wagon.providers.ssh.knownhost.KnownHostsProvider</role> 
> 
>      <role-hint>null</role-hint>
>      
> <implementation>org.apache.maven.wagon.providers.ssh.knownhost.NullKnownHostsProvider</implementation> 
> 
>      <instantiation-strategy>per-lookup</instantiation-strategy>
>      <configuration>
>        <hostKeyChecking>ask</hostKeyChecking>
>      </configuration>
>    </component>
> 
> 
> im thinking that that might be the problem (the nullHostProvider), but
> im not sure as i dont know much about plexus...
> is noone else having the same problem? have anyone else ever had that 
> problem?
> sorry for the long mail...