Sisu does not print component lookup exceptions by default, you need to
run jvm with -Dsisu.debug system property to see them (and ton of other
sisu debug information).

-- 
Regards,
Igor

On Sun, Sep 4, 2016, at 08:17 AM, Karl Heinz Marbaise wrote:
> Hi,
> 
> currently I'm trying to implement an extension which uses the 
> maven-artifact-transfer component...
> 
> But unfortunately if I start using the maven-artifact-tranfer component 
> or to be more concrete:
> 
> Having the following code:
> 
> 
> @Named
> @Singleton
> public class XYZ
>      extends AbstractEventSpy
> {
>      private final Logger LOGGER = LoggerFactory.getLogger( getClass() );
> 
>      @Inject
>      private ArtifactDeployer deployer;
> 
>      public XYZ()
>      {
>      }
> 
>      @Override
>      public void init( Context context )
>          throws Exception
>      {
>          super.init( context );
>          LOGGER.info( "Hello world.");
>      }
> 
> 
> So the culprit seemed to be the line:
> 
>      @Inject
>      private ArtifactDeployer deployer;
> 
> 
> If I use those two line in the extension, the extension is not started 
> anymore so ....so no output line "Hello world" anymore...But I can't 
> find any execption etc ?
> 
> any ideas thoughts ?
> 
> Thanks in advance...
> 
> 
> Kind regards
> Karl Heinz Marbaise
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to