[hudson-dev] Suggest we remove maven2 job type in Hudson-3 initial relea

[Henrik Lynggaard Hansen <henrik@xxxxxxx>]

Hi

I have a suggestion for the initial Hudson 3 release. I think we
should remove the Maven2 job type instead of leaving it in in
deprecated state.

The reason is that I have seen users raise issues where Maven2 job
type has caused exceptions and other problems and the response has
been to suggest moving to freestyle+ m3 integration, but I haven't
seen much attention to fixing the issues. This is completely natural
given the deprecated nature.

If there are so many issues with the job type and no-one fixing them,
wouldn't it be better to remove the broken feature instead of letting
users attempt to make it work?

Best regards
Henrik