I think pre-final releases fit into the same pattern. they are simply
the "latest" for a given major.minor. All along we could have been
pushing 3.5 docs to docs.jboss.org/hibernate/core/3.5
i actually wanted to upload them too as myself and others had documented
other non-jpa things. the is
We have spent the last two weeks on documentation for JPA 2 :) so that's
coming. But yes we screwed up a bit on the doc side for this release for early
adopters.
On 6 mars 2010, at 12:03, Sanne Grinovero wrote:
> It would be a nice to have for all other projects too, especially core and EM.
> R
It would be a nice to have for all other projects too, especially core and EM.
Right now you've done so much work on JPA2 but - aside from
downloading CR2 and reading blogs - there's no clue about
documentation: not very motivating for early adopters and testers.
Sanne
2010/3/6 Emmanuel Bernard :
yes, major.minor is good enough, you are right.
For trunk, I was not really planning on a nightly build. I was more thinking of
(manually) pushing the docs as they are in the project trunk if there is a
noticeable difference with the latest stable. But as Sanne said, he is more
interested in pus
Wrt https://www.hibernate.org/5.html.. the plan is to eventually use
index pages on docs.jboss.org/hibernate. We have not to date simply
because its way too difficult managing resource on that site.
Yes i would like to see is just the most recent docs indexed. No clue
how/if possible.
WRT
Hi
If I may throw in my 2 cents...The approach that you mentioned Emmanuel is ok
(as someone who uses the documentation). I understand that google won't know
the difference but at the end of the day it is down to the user to verify which
version of Hibernate Search they are using and use the
As Emmanuel mentioned, we are currently only publishing the docs for GA
releases.
We used to have also the beta docs online, but stopped that due to the way
the
different docs would get indexed by Google.
I agree with Sanne that we should upload the documentation for the beta
releases.
http:
I like http://docs.jboss.org/hibernate/project/version
most, as I guess I could browse available versions at
http://docs.jboss.org/hibernate/project/
and see which modules do exist under http://docs.jboss.org/hibernate/
and so I'd vote for http://docs.jboss.org/hibernate/search/3.2.0-BETA1
but hav
That reminds me, I don't think we ever settled on the doc scheme
http://docs.jboss.org/hibernate/stable/project
vs
http://docs.jboss.org/hibernate/project/version
On 5 mars 2010, at 11:00, Emmanuel Bernard wrote:
> They have never been published AFAIK, we tend to not publish docs on non
> final.
They have never been published AFAIK, we tend to not publish docs on non final.
They are bundled in the distro though.
We could change that provided we think it's useful and define some publication
scheme:
- http://docs.jboss.org/hibernate/search/x.y.z for stable versions
- http://docs.jboss.o
The docs lives in
http://docs.jboss.org/hibernate/stable/search/reference/en/html_single/
http://docs.jboss.org/hibernate/stable/search/reference/en/
And the link is here https://www.hibernate.org/5.html#A21
Am I missing something?
On 5 mars 2010, at 10:26, Sanne Grinovero wrote:
> Hello,
> I a
11 matches
Mail list logo
