I tracked down the issue and found that it is caused by MPIR-223
regards,
Hervé
Le jeudi 28 avril 2011, Dennis Lundberg a écrit :
> Hervé BOUTEMY skrev 2011-04-27 23:39:
> > could the first point be the same as MJAVADOC-302?
> > I'll try to have a look.
>
> I looked at that issue and it might b
Hervé BOUTEMY skrev 2011-04-27 23:39:
> could the first point be the same as MJAVADOC-302?
> I'll try to have a look.
I looked at that issue and it might be the same problem. There isn't
much info in that issue though.
>
> About releasing 2.8, I was hoping to make a release shortly since
> MJAVA
could the first point be the same as MJAVADOC-302?
I'll try to have a look.
About releasing 2.8, I was hoping to make a release shortly since MJAVADOC-284
is known as really blocking: the question is whether we try to fix other issues
before or if I should start the release process ASAP
Regards
Dennis,
I noticed similar problems when someone tried to release the cobertura-m-p-2.5.
He rolled back the release, made a jira-issue[1], changed the configuration of
the m-javadoc-p[2] and retried the release.
I didn't have time to investigate this yet (this should be fixed in the
mojo-parent
Hi Daniel,
I'll take a look at your problem.
Arnaud
> -Message d'origine-
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Envoyé : samedi 9 octobre 2004 13:28
> À : [EMAIL PROTECTED]
> Objet : Javadoc plugin problems
>
> Hi folks,
> I've added a component (i18n) to the co
