RE : RE : [m2.0.1] trouble with mojo report with maven-reporting-impl with version 2.0.1

2005-12-13 Thread Olivier Lamy
I can't remove it.
Because it's an abstract method in
org.apache.maven.reporting.AbstractMavenReport and I need to extend it
to made a mojo report.

- Olivier

-Message d'origine-
De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] 
Envoyé : mardi 13 décembre 2005 16:59
À : Maven Users List
Objet : Re: RE : [m2.0.1] trouble with mojo report with
maven-reporting-impl with version 2.0.1


Can you try to remove your getSiteRenderer method and change package of
SiteRenderer in your import?

Emmanuel

Olivier Lamy a écrit :
> Can you explain more ?
> Because my mojo report needs to extends 
> org.apache.maven.reporting.AbstractMavenReport
> This contains the abstract method : 
> org.codehaus.doxia.site.renderer.SiteRenderer getSiteRenderer()
> 
> That's why my mojo field is :
> /**
>  * @component
>  * @required
>  * @readonly
>  */
> private SiteRenderer siteRenderer;
> 
> I implements the simple method :
> 
> /** 
>  * @see
> org.apache.maven.reporting.AbstractMavenReport#getSiteRenderer()
>  */
> protected SiteRenderer getSiteRenderer()
> {
> return siteRenderer;
> }
> 
> I have certainly miss something in the mojo's field configuration or 
> in the getSiteRenderer implementation ??
> 
> Thanks,
> - Olivier
> 
> -Message d'origine-----
> De : Emmanuel Venisse [mailto:[EMAIL PROTECTED]
> Envoyé : mardi 13 décembre 2005 16:17
> À : Maven Users List
> Objet : Re: [m2.0.1] trouble with mojo report with
maven-reporting-impl
> with version 2.0.1
> 
> 
> doxia is now in org.apache.maven.doxia
> 
> Olivier Lamy a écrit :
> 
>>Hi,
>>A reporting mojo worked with 2.0 now failed with 2.0.1 (by updating
>>maven-reporting-impl with version 2.0.1). The following stack trace 
>>(not full)  : ause the requirement
>>ComponentRequirement{role='org.codehaus.doxia.site.renderer.SiteRend
>>rer', roleHint='null', fieldName='siteRenderer'} was missing
>> 
>>Mojo field :
>>
>>/**
>> * @component
>> * @required
>> * @readonly
>> */
>> 
>>I have updated my pom to use maven-reporting-api and
>>maven-reporting-impl with version 2.0.1. The second update generate 
>>the trouble. I need to revert it to 2.0. Do I miss something ?
>> 
>>- Olivier
>> 
>>
>>
>>This e-mail, any attachments and the information contained therein
>>("this message") are confidential and intended solely for the use of
> 
> the addressee(s). If you have received this message in error please 
> send it back to the sender and delete it. Unauthorized publication, 
> use, dissemination or disclosure of this message, either in whole or 
> in part is strictly prohibited.
> 
>>**
> 
> 
>>Ce message electronique et tous les fichiers joints ainsi que  les
> 
> informations contenues dans ce message ( ci apres "le message" ), sont

> confidentiels et destines exclusivement a l'usage de la  personne a 
> laquelle ils sont adresses. Si vous avez recu ce message par erreur, 
> merci  de le renvoyer a son emetteur et de le detruire. Toutes 
> diffusion, publication, totale ou partielle ou divulgation sous 
> quelque forme que se soit non expressement autorisees de ce message, 
> sont interdites.
> 
>>**
> 
> 
>>
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



This e-mail, any attachments and the information contained therein ("this 
message") are confidential and intended solely for the use of the addressee(s). 
If you have received this message in error please send it back to the sender 
and delete it. Unauthorized publication, use, dissemination or disclosure of 
this message, either in whole or in part is strictly prohibited.
** 
Ce message électronique et tous les fichiers joints ainsi que  les informations 
contenues dans ce message ( ci après "le message" ), sont confidentiels et 
destinés exclusivement à l'usage d

Re: RE : [m2.0.1] trouble with mojo report with maven-reporting-impl with version 2.0.1

2005-12-13 Thread Emmanuel Venisse

Can you try to remove your getSiteRenderer method and change package of 
SiteRenderer in your import?

Emmanuel

Olivier Lamy a écrit :

Can you explain more ?
Because my mojo report needs to extends
org.apache.maven.reporting.AbstractMavenReport
This contains the abstract method :
org.codehaus.doxia.site.renderer.SiteRenderer getSiteRenderer()

That's why my mojo field is :
/**
 * @component
 * @required
 * @readonly
 */
private SiteRenderer siteRenderer;

I implements the simple method :

/** 
 * @see

org.apache.maven.reporting.AbstractMavenReport#getSiteRenderer()
 */
protected SiteRenderer getSiteRenderer()
{
return siteRenderer;
}

I have certainly miss something in the mojo's field configuration or in
the getSiteRenderer implementation ??

Thanks,
- Olivier

-Message d'origine-
De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] 
Envoyé : mardi 13 décembre 2005 16:17

À : Maven Users List
Objet : Re: [m2.0.1] trouble with mojo report with maven-reporting-impl
with version 2.0.1


doxia is now in org.apache.maven.doxia

Olivier Lamy a écrit :


Hi,
A reporting mojo worked with 2.0 now failed with 2.0.1 (by updating 
maven-reporting-impl with version 2.0.1). The following stack trace 
(not full)  : ause the requirement

ComponentRequirement{role='org.codehaus.doxia.site.renderer.SiteRend
rer', roleHint='null', fieldName='siteRenderer'} was missing

Mojo field :

   /**
* @component
* @required
* @readonly
*/

I have updated my pom to use maven-reporting-api and 
maven-reporting-impl with version 2.0.1. The second update generate 
the trouble. I need to revert it to 2.0. Do I miss something ?


- Olivier



This e-mail, any attachments and the information contained therein 
("this message") are confidential and intended solely for the use of


the addressee(s). If you have received this message in error please send
it back to the sender and delete it. Unauthorized publication, use,
dissemination or disclosure of this message, either in whole or in part
is strictly prohibited.


**




Ce message electronique et tous les fichiers joints ainsi que  les


informations contenues dans ce message ( ci apres "le message" ), sont
confidentiels et destines exclusivement a l'usage de la  personne a
laquelle ils sont adresses. Si vous avez recu ce message par erreur,
merci  de le renvoyer a son emetteur et de le detruire. Toutes
diffusion, publication, totale ou partielle ou divulgation sous quelque
forme que se soit non expressement autorisees de ce message, sont
interdites.


**








-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: RE : [m2.0.1] trouble with mojo report with maven-reporting-impl with version 2.0.1

2005-12-13 Thread Emmanuel Venisse

Hmm, it's seems there is a missing component description in plexus descriptor 
of maven-reporting-impl


  org.codehaus.doxia.site.renderer.SiteRenderer
  
org.apache.maven.doxia.site.renderer.DefaultSiteRenderer
  

  
org.apache.maven.doxia.site.module.manager.SiteModuleManager
  siteModuleManager


  org.apache.maven.doxia.Doxia
  doxia

  



Emmanuel

Olivier Lamy a écrit :

Can you explain more ?
Because my mojo report needs to extends
org.apache.maven.reporting.AbstractMavenReport
This contains the abstract method :
org.codehaus.doxia.site.renderer.SiteRenderer getSiteRenderer()

That's why my mojo field is :
/**
 * @component
 * @required
 * @readonly
 */
private SiteRenderer siteRenderer;

I implements the simple method :

/** 
 * @see

org.apache.maven.reporting.AbstractMavenReport#getSiteRenderer()
 */
protected SiteRenderer getSiteRenderer()
{
return siteRenderer;
}

I have certainly miss something in the mojo's field configuration or in
the getSiteRenderer implementation ??

Thanks,
- Olivier

-Message d'origine-
De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] 
Envoyé : mardi 13 décembre 2005 16:17

À : Maven Users List
Objet : Re: [m2.0.1] trouble with mojo report with maven-reporting-impl
with version 2.0.1


doxia is now in org.apache.maven.doxia

Olivier Lamy a écrit :


Hi,
A reporting mojo worked with 2.0 now failed with 2.0.1 (by updating 
maven-reporting-impl with version 2.0.1). The following stack trace 
(not full)  : ause the requirement

ComponentRequirement{role='org.codehaus.doxia.site.renderer.SiteRend
rer', roleHint='null', fieldName='siteRenderer'} was missing

Mojo field :

   /**
* @component
* @required
* @readonly
*/

I have updated my pom to use maven-reporting-api and 
maven-reporting-impl with version 2.0.1. The second update generate 
the trouble. I need to revert it to 2.0. Do I miss something ?


- Olivier



This e-mail, any attachments and the information contained therein 
("this message") are confidential and intended solely for the use of


the addressee(s). If you have received this message in error please send
it back to the sender and delete it. Unauthorized publication, use,
dissemination or disclosure of this message, either in whole or in part
is strictly prohibited.


**




Ce message electronique et tous les fichiers joints ainsi que  les


informations contenues dans ce message ( ci apres "le message" ), sont
confidentiels et destines exclusivement a l'usage de la  personne a
laquelle ils sont adresses. Si vous avez recu ce message par erreur,
merci  de le renvoyer a son emetteur et de le detruire. Toutes
diffusion, publication, totale ou partielle ou divulgation sous quelque
forme que se soit non expressement autorisees de ce message, sont
interdites.


**








-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE : [m2.0.1] trouble with mojo report with maven-reporting-impl with version 2.0.1

2005-12-13 Thread Olivier Lamy
Can you explain more ?
Because my mojo report needs to extends
org.apache.maven.reporting.AbstractMavenReport
This contains the abstract method :
org.codehaus.doxia.site.renderer.SiteRenderer getSiteRenderer()

That's why my mojo field is :
/**
 * @component
 * @required
 * @readonly
 */
private SiteRenderer siteRenderer;

I implements the simple method :

/** 
 * @see
org.apache.maven.reporting.AbstractMavenReport#getSiteRenderer()
 */
protected SiteRenderer getSiteRenderer()
{
return siteRenderer;
}

I have certainly miss something in the mojo's field configuration or in
the getSiteRenderer implementation ??

Thanks,
- Olivier

-Message d'origine-
De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] 
Envoyé : mardi 13 décembre 2005 16:17
À : Maven Users List
Objet : Re: [m2.0.1] trouble with mojo report with maven-reporting-impl
with version 2.0.1


doxia is now in org.apache.maven.doxia

Olivier Lamy a écrit :
> Hi,
> A reporting mojo worked with 2.0 now failed with 2.0.1 (by updating 
> maven-reporting-impl with version 2.0.1). The following stack trace 
> (not full)  : ause the requirement
> ComponentRequirement{role='org.codehaus.doxia.site.renderer.SiteRend
> rer', roleHint='null', fieldName='siteRenderer'} was missing
>  
> Mojo field :
> 
> /**
>  * @component
>  * @required
>  * @readonly
>  */
>  
> I have updated my pom to use maven-reporting-api and 
> maven-reporting-impl with version 2.0.1. The second update generate 
> the trouble. I need to revert it to 2.0. Do I miss something ?
>  
> - Olivier
>  
> 
> 
> This e-mail, any attachments and the information contained therein 
> ("this message") are confidential and intended solely for the use of
the addressee(s). If you have received this message in error please send
it back to the sender and delete it. Unauthorized publication, use,
dissemination or disclosure of this message, either in whole or in part
is strictly prohibited.
> **

> Ce message electronique et tous les fichiers joints ainsi que  les
informations contenues dans ce message ( ci apres "le message" ), sont
confidentiels et destines exclusivement a l'usage de la  personne a
laquelle ils sont adresses. Si vous avez recu ce message par erreur,
merci  de le renvoyer a son emetteur et de le detruire. Toutes
diffusion, publication, totale ou partielle ou divulgation sous quelque
forme que se soit non expressement autorisees de ce message, sont
interdites.
> **

> 
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [m2.0.1] trouble with mojo report with maven-reporting-impl with version 2.0.1

2005-12-13 Thread Emmanuel Venisse

doxia is now in org.apache.maven.doxia

Olivier Lamy a écrit :

Hi,
A reporting mojo worked with 2.0 now failed with 2.0.1 (by updating
maven-reporting-impl with version 2.0.1).
The following stack trace (not full)  :
ause the requirement
ComponentRequirement{role='org.codehaus.doxia.site.renderer.SiteRend
rer', roleHint='null', fieldName='siteRenderer'} was missing
 
Mojo field :


/**
 * @component
 * @required
 * @readonly
 */
 
I have updated my pom to use maven-reporting-api and

maven-reporting-impl with version 2.0.1.
The second update generate the trouble. I need to revert it to 2.0.
Do I miss something ?
 
- Olivier
 



This e-mail, any attachments and the information contained therein ("this 
message") are confidential and intended solely for the use of the addressee(s). If 
you have received this message in error please send it back to the sender and delete it. 
Unauthorized publication, use, dissemination or disclosure of this message, either in 
whole or in part is strictly prohibited.
** 
Ce message electronique et tous les fichiers joints ainsi que  les informations contenues dans ce message ( ci apres "le message" ), sont confidentiels et destines exclusivement a l'usage de la  personne a laquelle ils sont adresses. Si vous avez recu ce message par erreur, merci  de le renvoyer a son emetteur et de le detruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressement autorisees de ce message, sont interdites.
** 






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]