Ok, this should be all done as far as I know. I left access in place for most
non-core projects. If any needed accesses are messed up, give me a shout (or
Max or Emmanuel) .
The tag was created at rev 20781 in case any one needs that information.
On Wednesday, October 06, 2010 05:48:03 pm St
I am just now tagging SVN for the move to Git. The tag is really just for
posterity sake... Immediately after I will be shutting off write access to the
/core portion of the repo. So please do not commit work to /core from this
moment forward in SVN.
I'll send a follow up when everything i
Was a tag created for this release? The closest I can find is CR1, I
need the sources to the GA release.
Thanks,
--tom
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
You need to use hibernate core from branch_3_2, not from trunk
On Aug 25, 2007, at 7:33 AM, Scott Marlow <[EMAIL PROTECTED]
> wrote:
Emmanuel Bernard wrote:
663 commits later the migration to the new structure is done. All
projects are top level:
core (Branch_3_2)
jpa-api
commons-annotati
Emmanuel Bernard wrote:
663 commits later the migration to the new structure is done. All
projects are top level:
core (Branch_3_2)
jpa-api
commons-annotations
annotations
entitymanager
validator
search
tags have been migrated and normalized (ie HibernateExt is out), I had
to keep Branch_3_2
On Aug 16, 2007, at 02:39, Hardy Ferentschik wrote:
Great work!
This was a big step forward in making the whole code base easier to
understand and maintain. It will also make a maven migration much
easier :)
That was the plan, part of it at least :)
I checked out Hibernare Search and
Great work!
This was a big step forward in making the whole code base easier to
understand and maintain. It will also make a maven migration much easier :)
I checked out Hibernare Search and it builds fine. It seems the svn:ignore
properties are not set anymore (build, intextemp, lucenedirs
663 commits later the migration to the new structure is done. All
projects are top level:
core (Branch_3_2)
jpa-api
commons-annotations
annotations
entitymanager
validator
search
tags have been migrated and normalized (ie HibernateExt is out), I
had to keep Branch_3_2 as is because of the pr
I wil be performing the SVN migration tomorrow for those projects.
Please refrain from commiting code in them until it's finished
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
This weekend I will begin migrating the SVN stuff pertaining to core to
use the new discussed layout (and my sandbox stuff too).
Basically:
1) trunk/Hibernate3 -> core/trunk
2) tags/xyz/Hibernate3 -> core/tags/xyz
3) branches/ABC/Hibernate3 -> core/branches/ABC
During this time, I will also fin
Sorry for sending this first to the wrong person. It was actually supposed
for the mailing list :)
To enable keyword substitution on all Java files I would do something like
this from the command line:
find . -name "*.java" | xargs svn propset svn:keywords "Id"
This should fix up all the j
Emmanuel,
Assuming that 'list.txt' is the file you want to have SVN Id expanded in,
all that is necessary is to issue the command:
$> svn propset svn:keywords "Id" list.txt
As long as the # $Id$ directive is in the list.txt file SVN will expand the
Id when the file is co
12 matches
Mail list logo
