On Tue, Aug 9, 2011 at 10:05 PM, Miguel Landaeta wrote:
> On Tue, Aug 9, 2011 at 3:26 PM, Torsten Werner wrote:
>> But maven-invoker-plugin was correct. Jtidy has changed its Maven
>> group from jtidy to net.sf.jtidy. Packages that Build-Depend on jtidy
>> and use Maven needs an updated maven rul
On Tue, Aug 9, 2011 at 3:26 PM, Torsten Werner wrote:
> But maven-invoker-plugin was correct. Jtidy has changed its Maven
> group from jtidy to net.sf.jtidy. Packages that Build-Depend on jtidy
> and use Maven needs an updated maven rule. Something like
>
> s/jtidy/net.sf.jtidy/ jtidy * *
I got i
reassign 637213 maven-invoker-plugin
thanks
On Tue, Aug 9, 2011 at 6:47 PM, Miguel Landaeta wrote:
> Whoops, I got it wrong, sorry for my mental lapse.
> I intended to report the bug on jtidy.
>
> This bug on jtidy affects to maven-invoker-plugin and probably
> another packages that build-depends
reassign 637213 src:jtidy 7+svn20110807-1
retitle 637213 jtidy: It doesn't install expected jtidy maven artifact
affects 637213 + src:maven-invoker-plugin
thanks
On Tue, Aug 09, 2011 at 05:46:05PM +0200, Torsten Werner wrote:
> I do not understand why do you file a bug report against
> maven-invok
Hi Miguel,
I do not understand why do you file a bug report against
maven-invoker-plugin instead of jtidy. What do you think is wrong in the
package?
Cheers,
Torsten
Am 09.08.2011 16:39, schrieb Miguel Landaeta:
> Package: maven-invoker-plugin
> Version: 1.3-2
> Severity: serious
>
> As title s
5 matches
Mail list logo
