You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polygene.apache.org by Paul Merlin <pa...@nosphere.org> on 2015/07/18 18:46:59 UTC
Rename git repository from zest-qi4j to zest-java?
Gang,
Shall/can we rename the git repository from zest-qi4j to zest-java
before going for the release?
Having it named `zest-qi4j` may bring confusion and even more if it
eventually gets renamed at some point. I'd prefer that it happens before
our next release rather than after.
WDYAT?
/Paul
Re: Rename git repository from zest-qi4j to zest-java?
Posted by Sandro Martini <sa...@gmail.com>.
ok, good to know :-) .
Paul, thanks for your tests.
Bye
2015-07-20 14:24 GMT+02:00 Paul Merlin <pa...@nosphere.org>:
> I just tried to push some commits to:
>
> - https://git.apache.org/zest-qi4j.git -> not supported
> - git@git.apache.org:zest-qi4j.git -> support only ssh pub keys, which I
> don't have, don't know if it support pushing
>
>
> Sandro Martini a écrit :
>> Sorry I don't know, maybe a check with Infra could give us right answers ...
>>
>> 2015-07-20 12:06 GMT+02:00 Niclas Hedhman <ni...@hedhman.org>:
>>> I am in transit at the moment and can't double-check, isn't one URL a
>>> read-only and the other the ACL controlled one?
>>>
>>> // Niclas
>>> On Jul 20, 2015 10:25, "Sandro Martini" <sa...@gmail.com> wrote:
>>>
>>>> Hi all,
>>>> just for info, currently I'm using the Zest repository from this url
>>>> (not the usual git-us) and all works good the same ...
>>>>
>>>> git://git.apache.org/zest-qi4j.git
>>>>
>>>> I found some reference to the original host "git-wip-us.apache.org" in
>>>> maven-compat.gradle, and in this page
>>>> "http://zest.apache.org/community/codebase.html", if you are doing a
>>>> rename maybe even this could be updated :-) .
>>>>
>>>> Bye
>>>>
>>>>
>>>> 2015-07-19 20:59 GMT+02:00 Paul Merlin <pa...@nosphere.org>:
>>>>> Hey Niclas,
>>>>>
>>>>> Niclas Hedhman a écrit :
>>>>>> Actually; Isn't it a matter of asking for a new one? We should be able
>>>> to
>>>>>> migrate the content ourselves, as in a few minutes.
>>>>>>
>>>>>> Or?
>>>>> I see no issue doing it either way.
>>>>>
Re: Rename git repository from zest-qi4j to zest-java?
Posted by Paul Merlin <pa...@nosphere.org>.
I just tried to push some commits to:
- https://git.apache.org/zest-qi4j.git -> not supported
- git@git.apache.org:zest-qi4j.git -> support only ssh pub keys, which I
don't have, don't know if it support pushing
Sandro Martini a écrit :
> Sorry I don't know, maybe a check with Infra could give us right answers ...
>
> 2015-07-20 12:06 GMT+02:00 Niclas Hedhman <ni...@hedhman.org>:
>> I am in transit at the moment and can't double-check, isn't one URL a
>> read-only and the other the ACL controlled one?
>>
>> // Niclas
>> On Jul 20, 2015 10:25, "Sandro Martini" <sa...@gmail.com> wrote:
>>
>>> Hi all,
>>> just for info, currently I'm using the Zest repository from this url
>>> (not the usual git-us) and all works good the same ...
>>>
>>> git://git.apache.org/zest-qi4j.git
>>>
>>> I found some reference to the original host "git-wip-us.apache.org" in
>>> maven-compat.gradle, and in this page
>>> "http://zest.apache.org/community/codebase.html", if you are doing a
>>> rename maybe even this could be updated :-) .
>>>
>>> Bye
>>>
>>>
>>> 2015-07-19 20:59 GMT+02:00 Paul Merlin <pa...@nosphere.org>:
>>>> Hey Niclas,
>>>>
>>>> Niclas Hedhman a écrit :
>>>>> Actually; Isn't it a matter of asking for a new one? We should be able
>>> to
>>>>> migrate the content ourselves, as in a few minutes.
>>>>>
>>>>> Or?
>>>> I see no issue doing it either way.
>>>>
Re: Rename git repository from zest-qi4j to zest-java?
Posted by Sandro Martini <sa...@gmail.com>.
Sorry I don't know, maybe a check with Infra could give us right answers ...
2015-07-20 12:06 GMT+02:00 Niclas Hedhman <ni...@hedhman.org>:
> I am in transit at the moment and can't double-check, isn't one URL a
> read-only and the other the ACL controlled one?
>
> // Niclas
> On Jul 20, 2015 10:25, "Sandro Martini" <sa...@gmail.com> wrote:
>
>> Hi all,
>> just for info, currently I'm using the Zest repository from this url
>> (not the usual git-us) and all works good the same ...
>>
>> git://git.apache.org/zest-qi4j.git
>>
>> I found some reference to the original host "git-wip-us.apache.org" in
>> maven-compat.gradle, and in this page
>> "http://zest.apache.org/community/codebase.html", if you are doing a
>> rename maybe even this could be updated :-) .
>>
>> Bye
>>
>>
>> 2015-07-19 20:59 GMT+02:00 Paul Merlin <pa...@nosphere.org>:
>> > Hey Niclas,
>> >
>> > Niclas Hedhman a écrit :
>> >> Actually; Isn't it a matter of asking for a new one? We should be able
>> to
>> >> migrate the content ourselves, as in a few minutes.
>> >>
>> >> Or?
>> > I see no issue doing it either way.
>> >
>>
Re: Rename git repository from zest-qi4j to zest-java?
Posted by Niclas Hedhman <ni...@hedhman.org>.
I am in transit at the moment and can't double-check, isn't one URL a
read-only and the other the ACL controlled one?
// Niclas
On Jul 20, 2015 10:25, "Sandro Martini" <sa...@gmail.com> wrote:
> Hi all,
> just for info, currently I'm using the Zest repository from this url
> (not the usual git-us) and all works good the same ...
>
> git://git.apache.org/zest-qi4j.git
>
> I found some reference to the original host "git-wip-us.apache.org" in
> maven-compat.gradle, and in this page
> "http://zest.apache.org/community/codebase.html", if you are doing a
> rename maybe even this could be updated :-) .
>
> Bye
>
>
> 2015-07-19 20:59 GMT+02:00 Paul Merlin <pa...@nosphere.org>:
> > Hey Niclas,
> >
> > Niclas Hedhman a écrit :
> >> Actually; Isn't it a matter of asking for a new one? We should be able
> to
> >> migrate the content ourselves, as in a few minutes.
> >>
> >> Or?
> > I see no issue doing it either way.
> >
>
Re: Rename git repository from zest-qi4j to zest-java?
Posted by Sandro Martini <sa...@gmail.com>.
Hi all,
just for info, currently I'm using the Zest repository from this url
(not the usual git-us) and all works good the same ...
git://git.apache.org/zest-qi4j.git
I found some reference to the original host "git-wip-us.apache.org" in
maven-compat.gradle, and in this page
"http://zest.apache.org/community/codebase.html", if you are doing a
rename maybe even this could be updated :-) .
Bye
2015-07-19 20:59 GMT+02:00 Paul Merlin <pa...@nosphere.org>:
> Hey Niclas,
>
> Niclas Hedhman a écrit :
>> Actually; Isn't it a matter of asking for a new one? We should be able to
>> migrate the content ourselves, as in a few minutes.
>>
>> Or?
> I see no issue doing it either way.
>
Re: Rename git repository from zest-qi4j to zest-java?
Posted by Paul Merlin <pa...@nosphere.org>.
Hey Niclas,
Niclas Hedhman a écrit :
> Actually; Isn't it a matter of asking for a new one? We should be able to
> migrate the content ourselves, as in a few minutes.
>
> Or?
I see no issue doing it either way.
Re: Rename git repository from zest-qi4j to zest-java?
Posted by Niclas Hedhman <ni...@hedhman.org>.
Actually; Isn't it a matter of asking for a new one? We should be able to
migrate the content ourselves, as in a few minutes.
Or?
On Sun, Jul 19, 2015 at 9:33 PM, Niclas Hedhman <ni...@hedhman.org> wrote:
>
> I think a repo rename is reasonable. I'll raise a ticket and see what
> infra says.
>
> Cheers
> Niclas
>
> On Sun, Jul 19, 2015 at 6:50 PM, Paul Merlin <pa...@nosphere.org> wrote:
>
>> Hey Sandro,
>>
>> Sandro Martini a écrit :
>> > Hi Paul,
>> > I think a rename now would be better now, but maybe the same rename
>> > should be done in many other places (docs, etc) to reduce possible
>> > confusion even there.
>> We already renamed everything except java packages for 2.1 (in order to
>> keep backward compatibility with 2.0).
>> See the `develop` documentation
>> at:https://zest.apache.org/java/develop/index.html .
>>
>> In 3.0 we will rename the java packages, see ZEST-40.
>>
>> To rename the git repository we need to open a INFRA issue.
>> Then we should impact builds.apache.org jobs configuration, and of
>> course, our git clones.
>> Am I right?
>>
>> Cheers
>>
>> /Paul
>>
>>
>
>
> --
> Niclas Hedhman, Software Developer
> http://zest.apache.org - New Energy for Java
>
--
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java
Re: Rename git repository from zest-qi4j to zest-java?
Posted by Niclas Hedhman <ni...@hedhman.org>.
I think a repo rename is reasonable. I'll raise a ticket and see what infra
says.
Cheers
Niclas
On Sun, Jul 19, 2015 at 6:50 PM, Paul Merlin <pa...@nosphere.org> wrote:
> Hey Sandro,
>
> Sandro Martini a écrit :
> > Hi Paul,
> > I think a rename now would be better now, but maybe the same rename
> > should be done in many other places (docs, etc) to reduce possible
> > confusion even there.
> We already renamed everything except java packages for 2.1 (in order to
> keep backward compatibility with 2.0).
> See the `develop` documentation
> at:https://zest.apache.org/java/develop/index.html .
>
> In 3.0 we will rename the java packages, see ZEST-40.
>
> To rename the git repository we need to open a INFRA issue.
> Then we should impact builds.apache.org jobs configuration, and of
> course, our git clones.
> Am I right?
>
> Cheers
>
> /Paul
>
>
--
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java
Re: Rename git repository from zest-qi4j to zest-java?
Posted by Paul Merlin <pa...@nosphere.org>.
Hey Sandro,
Sandro Martini a écrit :
> Hi Paul,
> I think a rename now would be better now, but maybe the same rename
> should be done in many other places (docs, etc) to reduce possible
> confusion even there.
We already renamed everything except java packages for 2.1 (in order to
keep backward compatibility with 2.0).
See the `develop` documentation
at:https://zest.apache.org/java/develop/index.html .
In 3.0 we will rename the java packages, see ZEST-40.
To rename the git repository we need to open a INFRA issue.
Then we should impact builds.apache.org jobs configuration, and of
course, our git clones.
Am I right?
Cheers
/Paul
Re: Rename git repository from zest-qi4j to zest-java?
Posted by Sandro Martini <sa...@gmail.com>.
Hi Paul,
I think a rename now would be better now, but maybe the same rename
should be done in many other places (docs, etc) to reduce possible
confusion even there.
Bye