Re: [hudson-dev] Suggest we remove maven2 job type in Hudson-3 initial r

[Winston Prakash <winston.prakash@xxxxxxxxx>]

Agree. While we hide it from the list in the "New Job" create page, the
one already created must continue to work.

- Winston

On 7/30/12 3:53 PM, Bob Foster wrote:
> Watching this thread and wondering... Are there people using Maven 2
> job type who are not having problems and would be surprised/unhappy if
> we tried to take it away from them? Forcing a user to migrate is
> usually not a good way to make friends. Just a thought.
>
> Bob
>
> On Mon, Jul 30, 2012 at 2:57 PM, Winston Prakash
> <winston.prakash@xxxxxxxxx> wrote:
>> Henrik,
>>
>>
>>
>>
>>
>>
>>
>> - Winston
>>
>>
>> On 7/30/12 2:42 PM, Henrik Lynggaard Hansen wrote:
>>
>> Winston,
>>
>> I haven't looked at the technical implications, all I am saying is that the
>> core team should seriously consider the user experience we are presenting
>> when people choose maven 2 job type.
>>
>> If a big part of people who try to use it run into problems, and you (core
>> team) don't have an plans to fix those issues, perhaps it was better to
>> disable maven 2 job type all together..
>>
>>
>> I'm all for disabling Maven2 Job type. But AFAIK, it is not part of core. It
>> appears in the list only if legacy-maven plugin is installed.
>>
>> Looking at the technical side I understand the static analysis plugins can
>> take advantage of the maven 2 job type but is it a requirement or just
>> optional benefit ? I think that will be what tips the scale
>>
>> Static plugins does not mark it as optional, so might not load with out it.
>>
>>
>> Secondly, This is something I need to confirm with m4, but I think I saw the
>> maven 2 job type present despite not having selected the maven 2 plugin...
>>
>>
>> Could you look at Plugin Center and see if it is available there when the
>> Maven 2 Job Type appears in the list. Thought maven plugin is not installed
>> directly, it could be installed by some other plugin as dependency.
>>
>> Other option is we could release legacy-maven plugin disabling Maven 2 Job
>> type and hide it so that it would not  appear in the Plugin Center directly
>> for install, but could be installed as a dependency. Since it won't have
>> Maven 2 Job type, it won't appear in the job types list either.
>>
>> - Winston
>>
>>
>> Best regards
>> Henrik
>>
>> On Jul 30, 2012 5:35 PM, "Winston Prakash" <winston.prakash@xxxxxxxxx>
>> wrote:
>>> Henrik,
>>>
>>>
>>> Maven2 Job type is available only if legacy maven plugin is installed.
>>> By removing the plugin do you mean no longer make  it available via
>>> update center? If so, though I would like to do that, unfortunately
>>> several plugins including static analysis plugin depend on that and
>>> would break with out it.
>>>
>>> Since  static analysis plugins are some of the most used plugin, we
>>> could rewrite them  to conform to Maven3 plugin eventually.
>>>
>>> Since we don't bundle any plugin, it is up to the user to install it. We
>>> could move legacy maven plugin from Featured plugin list to "Others"
>>> plugin list, thus giving less important to it.
>>>
>>> - Winston
>>>
>>>
>>>
>>> On 7/30/12 3:47 AM, Henrik Lynggaard Hansen wrote:
>>>> 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
>>
>> _______________________________________________
>> hudson-dev mailing list
>> hudson-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/hudson-dev
>>
> _______________________________________________
> hudson-dev mailing list
> hudson-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/hudson-dev