On Mon, May 4, 2015 at 9:05 AM, jieryn wrote:
> Yes, sorry I wasn't clear. I meant if the groupId=codehaus.org is an
> Apache issue without owning/controlling actual dns-a=codehaus.org,
> then the easiest and fastest solution, for both users and devs, is
> just to own the dns-a record. I am not t
Yes, sorry I wasn't clear. I meant if the groupId=codehaus.org is an
Apache issue without owning/controlling actual dns-a=codehaus.org,
then the easiest and fastest solution, for both users and devs, is
just to own the dns-a record. I am not talking about any complex
mirrorOf or relocating packages
I think he was suggesting Apache would be the caretaker of the domain, on
behalf of both Codehaus projects that move to Apache and those that don't,
and just the www.codehaus.org main page would redirect to an Apache page
(though I'd prefer to redirect to an Apache page that describes the
Codehaus
On Mon, May 4, 2015 at 8:40 AM, Benson Margulies
wrote:
>
>
> On Mon, May 4, 2015 at 8:35 AM, jieryn wrote:
>
>> Apache, and Apache Maven, should just purchase the codehaus.org domain
>> name and set a permanent redirect to Apache Maven site.
>>
>
> Why? Who cares? There's no important relations
On Mon, May 4, 2015 at 8:35 AM, jieryn wrote:
> Apache, and Apache Maven, should just purchase the codehaus.org domain
> name and set a permanent redirect to Apache Maven site.
>
Why? Who cares? There's no important relationship between a Maven gid and a
DNS domain name. Codehaus.org contained t
Apache, and Apache Maven, should just purchase the codehaus.org domain
name and set a permanent redirect to Apache Maven site.
Maybe Ben would be willing to give that last gift to the community and
transfer ownership to Apache. It expires on 2016-02-26 anyway..
On Mon, May 4, 2015 at 8:20 AM, And
Anyone who knows if it actually possible for us to keep the groupId when
moving, as we don't own the codehaus.org domain? I think that most of us
can agree on it's best (at least in short term) and easier to keep the same
groupId. But can we really do that?
/Anders
On Mon, May 4, 2015 at 2:07 PM,
+1 keep codehaus.org for existing plugins
perhaps prepare a new groupId with required resources (central sync ..) for
new plugins and add it in the default list of plugins groups for future
maven releases
On Mon, May 4, 2015 at 1:12 PM, Olivier Lamy wrote:
> Agree. We must take take it easy for
Agree. We must take take it easy for users.
Folks who managed central knows the situation. So IMHO this will not be a
big problem.
On 4 May 2015 at 20:27, Trygve Laugstøl wrote:
> I think it is best to just keep the group id for all existing Mojos.
> Repackaging the code and having all clients i
I think it is best to just keep the group id for all existing Mojos.
Repackaging the code and having all clients is a lot of hassle for no gain. For
new plugins, I guess they could use the new group id.
--
Trygve
On Mon, May 04, 2015 at 09:48:59AM +, Julien HENRY wrote:
> Hi guys,
> Sorry
10 matches
Mail list logo
