Thanks to good reports, we were able to fix a handful of problems found in 3.0. If nobody complains, I intend to do the next release by the end of the week. Regards, Hervé
Great idea!
I still have an issue with the HelpMojo class, which ends up under both
target/generated-sources/plugin and target/classes with the default
package in the source.
Might be a Win-thing, I'll have a look at it.
-RobertOp Mon, 25 Jun 2012 00:20:59 +0200 schreef Hervé BOUTEMY
:
> Thanks to good reports, we were able to fix a handful of problems found
> in 3.0.
> If nobody complains, I intend to do the next release by the end of the
> week.
>
> Regards,
>
> Hervé
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
Thanks Hervé ! @Robert this looks weird. Do you have this issue with the release plugin ?2012/6/25 Robert Scholte : > Great idea! > I still have an issue with the HelpMojo class, which ends up under both > target/generated-sources/plugin and target/classes with the default package > in the source. > Might be a Win-thing, I'll have a look at it. > > -Robert > > Op Mon, 25 Jun 2012 00:20:59 +0200 schreef Hervé BOUTEMY > : > > >> Thanks to good reports, we were able to fix a handful of problems found in >> 3.0. >> If nobody complains, I intend to do the next release by the end of the >> week. >> >> Regards, >> >> Hervé >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: >> For additional commands, e-mail: > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > For additional commands, e-mail: >
I think I see the problem:
HelpGeneratorPlugin:
return new PluginHelpGenerator().setHelpPackageName( helpPackageName
).setVelocityComponent( this.velocity );
PluginHelpGenerator:
properties.put( "helpPackageName", helpPackageName == null ? "" :
helpPackageName );
If the value of @Parameter is "" by default instead of null as it used to
be, we have a problem...
-RobertOp Mon, 25 Jun 2012 18:54:00 +0200 schreef Olivier Lamy :
> Thanks Hervé !
>
> @Robert this looks weird. Do you have this issue with the release plugin
> ?
>
> 2012/6/25 Robert Scholte :
>> Great idea!
>> I still have an issue with the HelpMojo class, which ends up under both
>> target/generated-sources/plugin and target/classes with the default
>> package
>> in the source.
>> Might be a Win-thing, I'll have a look at it.
>>
>> -Robert
>>
>> Op Mon, 25 Jun 2012 00:20:59 +0200 schreef Hervé BOUTEMY
>> :
>>
>>
>>> Thanks to good reports, we were able to fix a handful of problems
>>> found in
>>> 3.0.
>>> If nobody complains, I intend to do the next release by the end of the
>>> week.
>>>
>>> Regards,
>>>
>>> Hervé
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail:
>>> For additional commands, e-mail:
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
>>
>
>
Yup but normaly the class is rename and remove later. Because at this stage with annos we don't know the base package of the mojo.
On Mon, 25 Jun 2012 00:20:59 +0200
Hervé BOUTEMY wrote:
> Thanks to good reports, we were able to fix a handful of problems found in 3.0.
> If nobody complains, I intend to do the next release by the end of the week.
>+1 I really wants to use the java annotations for license-m-p and MPLUGIN-213 was a blocker for MLICENSE-41.
Good works guys ;)
tony.
Hi,
I've discovered the cause of the HelpMojo plugin, Olivier has fixed it
(thanks!).
I have verified all the issues I've mentioned before and can confirm these
have been fixed by Hervé and work as expcted (thanks too!).
But I found one funny bug: MPLUGIN-217. Not a showstopper, but IMHO should
be fixed as well.
Looks like it is possible to start the vote soon.
-RobertOp Mon, 25 Jun 2012 19:12:15 +0200 schreef Tony Chemit
:
> On Mon, 25 Jun 2012 00:20:59 +0200
> Hervé BOUTEMY wrote:
>
>> Thanks to good reports, we were able to fix a handful of problems found
>> in 3.0.
>> If nobody complains, I intend to do the next release by the end of the
>> week.
>>
> +1 I really wants to use the java annotations for license-m-p and
> MPLUGIN-213 was a blocker for MLICENSE-41.
>
> Good works guys ;)
>
> tony.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
On Mon, 25 Jun 2012 23:36:51 +0200
"Robert Scholte" wrote:
> Hi,
>
> I've discovered the cause of the HelpMojo plugin, Olivier has fixed it
> (thanks!).
> I have verified all the issues I've mentioned before and can confirm these
> have been fixed by Hervé and work as expcted (thanks too!).
> But I found one funny bug: MPLUGIN-217. Not a showstopper, but IMHO should
> be fixed as well.I just attach a fix for this.
hope somebody will apply it before release 3.1
tony.
Just applied. Thanks ! -- Olivier2012/6/26 Tony Chemit : > On Mon, 25 Jun 2012 23:36:51 +0200 > "Robert Scholte" wrote: > >> Hi, >> >> I've discovered the cause of the HelpMojo plugin, Olivier has fixed it >> (thanks!). >> I have verified all the issues I've mentioned before and can confirm these >> have been fixed by Hervé and work as expcted (thanks too!). >> But I found one funny bug: MPLUGIN-217. Not a showstopper, but IMHO should >> be fixed as well. > > I just attach a fix for this. > > hope somebody will apply it before release 3.1 > > tony. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > For additional commands, e-mail: >