On 15 March 2011 09:48, Karl Heinz Marbaise <[email protected]> wrote:

> Hi,
>
> (Cedric: Updated to new TestNG version..Thanks for that hint)...
>
> But i'm currently in the situation where my tests still failing...with the
> following message:
>
> Failed tests:
>
>
> commandWorkspaceCreateTest(com.oneandone.devel.modules.pws.cli.PustefixWorkspaceCLIWorkspaceIT):
>
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> com.google.inject.ProvisionException: Guice provision errors:
>
> 1) Error injecting:
> org.apache.maven.repository.legacy.LegacyRepositorySystem
>  at ClassRealm[plexus.core, parent: null]
>  at ClassRealm[plexus.core, parent: null]
>  while locating org.apache.maven.repository.RepositorySystem
>
> 1 error
>      role: org.apache.maven.repository.RepositorySystem
>  roleHint:
>
>
> The cause seemed to be laying inside the following code part:
>
>    public ArtifactRepository getLocalRepository() throws
> ComponentLookupException {
>        try {
>            String localRepositoryPath = getLocalRepositoryPath();
>            if ( localRepositoryPath != null ) {
>                return getPlexusContainer().lookup( RepositorySystem.class
> ).createLocalRepository( new File( localRepositoryPath ) );
>            }
>            return getPlexusContainer().lookup( RepositorySystem.class
> ).createLocalRepository( RepositorySystem.defaultUserLocalRepository );
>        } catch ( InvalidRepositoryException e ) {
>            // never happened
>            throw new IllegalStateException( e );
>        }
>    }
>
> And the real cause is the following line:
>
>  return getPlexusContainer().lookup( RepositorySystem.class
> ).createLocalRepository( new File( localRepositoryPath ) );
>
> Does anybody has an idea or a hint about that?


Have you truncated the exception message? It should be followed by a
stacktrace that explains the reason why the lookup request failed.
( the most useful parts of an exception message are usually found around the
end, rather than the top message which is more high-level )

You might also want to enable debug logging.

PS. is this code public somewhere? ( makes it easier to help out than
debugging via email :)

Kind regards
> Karl Heinz Marbaise
>
> -----
> Kind regards
> Karl Heinz Marbaise
> ----
> http://www.soebes.de
> http://www.skmwiki.de
> http://supose.org/wiki/supose
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Integrate-Maven-Plugin-Code-Mojo-s-into-Application-tp3397120p3694803.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>


-- 
Cheers, Stuart

Reply via email to