We get Gradle to add that to the pom on release. Good point. Yeah not
sure its a real problem. Too bad GitHub does not redirect on rename
the way JIRA does :(
On Tue 03 Jan 2012 12:39:52 PM CST, Emmanuel Bernard wrote:
Sounds good. One tiny issue you might have is that if Gradle builds
the release like Maven, it need the URL to the git repo somewhere in the configuration.
That means older builds like 4.0 will contain an obsolete URL.
I don't think that's a problem in practice but I wanted to point it out.
On 3 janv. 2012, at 18:35, Steve Ebersole wrote:
> Cool, thanks for following up.
> So then I'd vote we rename the hibernate-core respository to hibernate-orm. I
actually think that hibernate-core as a module and artifact name is ok. Additionally
I'd say we do that just before branching 4.0 (just after 4.0.1 release)
>
> Thoughts?
>
> On Tue 03 Jan 2012 09:02:44 AM CST, Emmanuel Bernard wrote:
>> To answer the last question, rename of a github repo is fine. I am not sure forks
are carried over but they can easily be remade.
>> The local repo on the developer machine simply need to remove the old remote, add
the new one and do a fetch.
>> That's not disruptive.
>>
>> Emmanuel
>>
>> On 3 janv. 2012, at 15:56, Steve Ebersole wrote:
>>
>>> [08:56]<jbott> Meeting ended Tue Jan 3 14:55:46 2012 UTC.
Information
>>> about MeetBot at
http://wiki.debian.org/MeetBot . (v 0.1.4)
>>> [08:56]<jbott> Minutes:
>>>
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2012/...
>>> [08:56]<jbott> Minutes (text):
>>>
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2012/...
>>> [08:56]<jbott> Log:
>>>
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2012/...
>>>
>>> --
>>> steve(a)hibernate.org
>>>
http://hibernate.org
>>> _______________________________________________
>>> hibernate-dev mailing list
>>> hibernate-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>
> --
> steve(a)hibernate.org
>
http://hibernate.org