Hibernate Core now uses Git as the version control system.
You can access it at http://github.com/hibernate/hibernate-core
Core on Git
We have imported the SVN history (at least what GIT could extract) and pushed
the SVN trunk, branch 3.5 and branch 3.3. If you need more of the legacy
branches
So far, only :
- emmanuel
- steve
- max
- hardy
- adam
have read-write access to hibernate-core on GitHub
If you used to have access to SVN and actually use it ;), please email me your
github acocunt and I will grant you access. You can also ping me on IRC.
Emmanuel
On 7 oct. 2010, at 11:
We cannot forget to update the info on hibernate.org and the wiki.
I was just about to find the pages in need of updated, but it seems
the wiki is down :(
--Hardy
On Thu, 07 Oct 2010 11:30:11 +0200, Emmanuel Bernard
wrote:
> Hibernate Core now uses Git as the version control system.
> You c
The problem is that magnolia is set up with a decidedly SVN-slant. I set up
what I think is most reasonable.
On Thursday, October 07, 2010 05:11:31 am Hardy Ferentschik wrote:
> We cannot forget to update the info on hibernate.org and the wiki.
> I was just about to find the pages in need of upd
I would fence on the conservative side here, even for isActive and raise an
exception. If it's UNKNOWN, well then we don't know and we can't answer true
nor false. Kind of a Gödelian dilemma ;)
On 29 sept. 2010, at 19:53, Steve Ebersole wrote:
> On Wed, 2010-09-29 at 14:26 +0200, Emmanuel Berna
Adding to the favorite git tools:
Command completion support (git-completion.bash) is pretty good if your
a command shell type person. The script is available via Git project
source and other places (included in Fedora). If you read the below
mentioned progit book (just ordered my copy last week
Z-Shell also has good native (?) command completion for git and ships
with both GNU/Linux and OS X... And for users of both platforms (like
myself), zsh feels more consistent between Linux and OS X whereas bash
does not (for whatever reason).
-CB
On 10/07/2010 09:32 AM, Scott Marlow wrote:
>
Hi,
following suite I am planning to move Hibernate Validator to git as well.
Given that some of contributors are already
working with Validator branches on GitHub it only makes sense to move the
master to there as well.
I'll be tagging the current state of the svn repo and then disable write
Hi all,
I think this is a good thing to have Hibernate on github. I just forked and did
a few modifications (I'm learning git at the same time). I also did my first
pull request ;) to validate the process. This is very minor modification so I
didn't open an issue on JIRA.
Regards,
Julien
-
We do not make changes outside the context of a JIRA. :)
On Thursday, October 07, 2010 09:12:19 am Julien HENRY wrote:
> Hi all,
>
> I think this is a good thing to have Hibernate on github. I just forked and
> did a few modifications (I'm learning git at the same time). I also did my
> first pul
OK, second try :)
I didn't find how to rename my branch so I removed it and created a new one and
also did a new pull request. The first pull request was not automatically
deleted (was still referring to my deleted branch???) and I din't find a way to
delete it, but only to close it.
I hope I
[basically Hardy's email + s/Validator/Search/]
Hi,
Following suite I am planning to move Hibernate Search to git as well.
Given that some of contributors are already
working with Validator branches on GitHub it only makes sense to move the
master to there as well.
I'll be tagging the current
On Thursday, October 07, 2010 04:30:11 am Emmanuel Bernard wrote:
> If you want to contribute a fix or new feature, either use the pure Git
> approach, or use the GitHub fork capability (see
> http://help.github.com/forking/ and http://help.github.com/pull-requests/
> ) The benefit of the GitHub ap
On Thursday, October 07, 2010 01:51:52 pm Steve Ebersole wrote:
> On Thursday, October 07, 2010 04:30:11 am Emmanuel Bernard wrote:
> > If you want to contribute a fix or new feature, either use the pure Git
> > approach, or use the GitHub fork capability (see
> > http://help.github.com/forking/ an
2010/10/6 Emmanuel Bernard
>
> Too sad, that javax.validation.ValidatorContext is not defined as
>
> public interface ValidatorContext > {
>
> }
>
> If it were, we wouldn't need a dedicated method
> HibernateValidatorFactory#usingHibernateContext(), but
> HibernateValidatorFactory could be define
I missed the behind-the-scenes discussion. Why was SVN booted? And can
I still submit SVN diff patches?
On Thu, Oct 7, 2010 at 4:20 PM, Steve Ebersole wrote:
> On Thursday, October 07, 2010 01:51:52 pm Steve Ebersole wrote:
>> On Thursday, October 07, 2010 04:30:11 am Emmanuel Bernard wrote:
>> >
On Monday, October 04, 2010 09:59:14 am Emmanuel Bernard wrote:
> @InjectService
> Why not JSR-303's @Inject with a qualifier if you really need some
> additional metadata?
I am not against the idea so much. The problems I had were twofold:
1) Personally I have no idea how to define these "quali
On Monday, October 04, 2010 09:59:14 am Emmanuel Bernard wrote:
> Not commenting on the idea of an Hibernate specific registry
Good because the time for that was almost a year ago when I asked y'all to
review the designs I was working on for 4 :)
--
Steve Ebersole
http://hibernate.org
hello git gurus,
here a question:
how to perform a partial checkout? in our testsuite hudson job, we only need
the testsuite module, and the purpose for this job is testing the artifacts
that upstream core job deployed.
of course check out the whole project is an option, but this will force the
19 matches
Mail list logo
