[VOTE][RESULTS] Change Pluto 2.0 maven groupid to org.apache.portals.pluto

[Ate Douma <at...@douma.nu>]

The below vote has passed with +8 binding and no 0 or -1 votes.

Thanks everyone for the support.

I'll create a JIRA issue to track the groupid change shortly.

Regards,

Ate

Ate Douma wrote:
> We're finally getting very close to releasing Pluto 2.0, but there are a 
> few lose ends I'd like to clear up and fix first.
> 
> One of these is aligning the Pluto maven groupid to that of the other 
> projects here at the Apache Portals.
> Pluto currently (probably from historical reason, dating back from pre 
> maven 1.0 times) uses a maven groupid org.apache.pluto.
> 
> I propose changing this *now* before the 2.0.0 release to 
> org.apache.portals.pluto.
> 
> This will have hardly any impact for end-users/integrators of Pluto 
> willing to upgrade from Pluto 1.1.x to 2.0 as their upgrade path and 
> tasks is already quit elaborate and changing (only) a simple groupid in 
> a maven pom is hardly any effort in comparison.
> 
> In addition, we're also investigating moving repository deployment to 
> Nexus (see: https://issues.apache.org/jira/browse/INFRA-1980) and I 
> expect it will help migrating to that for all Portals as well to have a 
> common parent groupid (besides a common portals super-pom).
> 
> Please cast your vote:
> 
> +1 Change Pluto 2.0 maven groupid to org.apache.portals.pluto
>  0 no opinion, I don't care
> -1 Stick to the current maven groupid org.apache.pluto (please provide 
> your arguments)
> 
> Regards,
> 
> Ate Douma
>