"Hardy Ferentschik"
>> Cc: "Hibernate"
>> Sent: Friday, January 13, 2012 5:07:42 AM
>> Subject: Re: [hibernate-dev] Minor issues/questions about Hibernate Core/ORM
>> documentation
>>
>>
>> On 01/13/2012 01:58 AM, Hardy Ferentschik wrote
r 4.1?
Regards,
Gail
- Original Message -
> From: "Steve Ebersole"
> To: "Hardy Ferentschik"
> Cc: "Hibernate"
> Sent: Friday, January 13, 2012 5:07:42 AM
> Subject: Re: [hibernate-dev] Minor issues/questions about Hibernate Core/ORM
>
On 01/13/2012 01:58 AM, Hardy Ferentschik wrote:
>>
>> I agree, we should do a redirect. I had not planned on changing the
>> physical dir until 4.1 as that is when the new docs would be getting used.
>> 6 in one... if you feel the itch, go for it.
>
> Changing the directory name is easy. For
Interesting. I was trying `git log --grep=HHH-6906` but getting nothing
back.
`git reflog | grep HHH-6906` returns:
39d47c4 HEAD@{89}: commit: HHH-6906 - Clean up javadoc warnings
I only use my fork for "on going" work, especially if it has to be
collaborated. I never used my fork for this wo
ginal Message -
> From: "Steve Ebersole"
> To: "Hardy Ferentschik"
> Cc: "Hibernate"
> Sent: Thursday, January 12, 2012 1:48:46 PM
> Subject: Re: [hibernate-dev] Minor issues/questions about Hibernate Core/ORM
> documentation
>
>
&g
I've checked the repos as well and came to same conclusions as Scott,
which is we need to recover the patch from Steve's local repository;
but also I'd recommend to check for all changes as tracked in JIRA
around the suspected timeframe and verify if they are in practice
included in the current mas
>>> I also noticed that the Javadoc includes test classes. It would be nice to
>>> exclude those.
>>
>> right, even the aggregated docs seem to include test classes. I would create
>> a jira and we reconfigure the task for the next release
>
> Hmm, I spent a lot of time getting those right.
>
On Jan 12, 2012, at 10:48 PM, Steve Ebersole wrote:
>
> On Thu 12 Jan 2012 03:19:29 AM CST, Hardy Ferentschik wrote:
>> Answers inline
>>
>> On Jan 12, 2012, at 9:50 AM, Gail Badner wrote:
>>
>>> I've uploaded the 4.0.1.Final documentatation to
>>> http://docs.jboss.org/hibernate/core/4.0/.
>
I took a quick look at and didn't see a likely branch. You might look
in the output from "git reflog" (in your local personal Hibernate fork
folder) for "HHH-6906 - Clean up javadoc warnings". I think that will
contain the changes, even if your fork no longer has the branch that
referenced it
Are the doc commits visible on your personal Hibernate fork still? I
know that "gitk" will visualize the master branch or whatever branch.
Maybe you can see the doc commits on the master and a merge that took
them out (or not ;).
We should be able to "git cherry-pick commit-id" the commits fro
Can anyone with better git-fu than me tell me where those changes went?
On Thu 12 Jan 2012 08:44:19 PM CST, Steve Ebersole wrote:
> Actually wrt aggregateJavadocs, some how all those edits to
> release.gradle are gone on master :(
>
>
> On Thu 12 Jan 2012 03:48:46 PM CST, Steve Ebersole wrote:
Actually wrt aggregateJavadocs, some how all those edits to
release.gradle are gone on master :(
On Thu 12 Jan 2012 03:48:46 PM CST, Steve Ebersole wrote:
>
> On Thu 12 Jan 2012 03:19:29 AM CST, Hardy Ferentschik wrote:
>> Answers inline
>>
>> On Jan 12, 2012, at 9:50 AM, Gail Badner wrote:
>>
>
On Thu 12 Jan 2012 03:19:29 AM CST, Hardy Ferentschik wrote:
> Answers inline
>
> On Jan 12, 2012, at 9:50 AM, Gail Badner wrote:
>
>> I've uploaded the 4.0.1.Final documentatation to
>> http://docs.jboss.org/hibernate/core/4.0/.
>>
>> Maybe this was already discussed but, should the switch from
Answers inline
On Jan 12, 2012, at 9:50 AM, Gail Badner wrote:
> I've uploaded the 4.0.1.Final documentatation to
> http://docs.jboss.org/hibernate/core/4.0/.
>
> Maybe this was already discussed but, should the switch from "core" to "orm"
> affect the URL for the 4.0 documentation (i.e.,
>
14 matches
Mail list logo
