Can't build Hibernate ORM 5.1 documentation
by Gail Badner
I'm getting ready to release 5.1.17, but I'm having trouble building the
documentation.
I can't even build the documentation using 5.1.16 tag. It worked fine when
I released 5.1.16.Final in August.
A new property was added for HHH-13011, and I need to get that documented
in the user guide for 5.1.17.
Here is what I'm seeing when I execute `./gradlew buildDocs`:
:documentation:renderDocBook_mappingGuide_en-US_html
rendering Book(mappingGuide) en-US/html
Extending script classloader with the jdocbookXsl dependencies
redirecting console output to file
[/home/gbadner/git/hibernate-orm-5.1-copy/documentation/target/docbook/work/mappingGuide/log/console-en-US-html.log]
Error on line 1 column 1 of http://docbook.org/xml/5.0/dtd/docbook.dtd:
Error reported by XML parser: The markup declarations contained or pointed
to by the document type declaration must be well-formed.
Resetting console output
:documentation:renderDocBook_mappingGuide_en-US_html FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task
':documentation:renderDocBook_mappingGuide_en-US_html'.
> error rendering [org.xml.sax.SAXParseException; systemId:
http://docbook.org/xml/5.0/dtd/docbook.dtd; lineNumber: 1; columnNumber: 1;
The markup decl
arations contained or pointed to by the document type declaration must be
well-formed.] on Hibernate_Mapping_Guide.xml
The log file (/home/gbadner/git/hibernate-orm-5.1-copy/documentation/target/docbook/work/mappingGuide/log/console-en-US-html.log)
was empty.
I'm attaching the console log from executing `./gradlew buildDocs --debug
--info`.
Any ideas???
Thanks,
Gail
7 years, 4 months
Re: [hibernate-dev] ORM 6 branch
by Davide D'Alto
+1 for the creation of the branch upstream and everything Yoann said.
One curiosity, once there is an alpha, why would you delete the whole branch?
Couldn't you change everything on the existing branch without deleting it?
It's unusual to rewrite the history of upstream branches but we have
done it before.
PS: Sorry if you received this email twice, I made a mistake
On Tue, Nov 27, 2018 at 1:20 PM Davide D'Alto <daltodavide(a)gmail.com> wrote:
>
> +1 for creating the branch upstream and everything Yoann said.
>
> One curiosity, once there is an alpha, why would you delete the whole branch?
> Couldn't you change everything on the existing branch without deleting it?
> While it's unusual to rewrite the history of upstream branches, we
> have done it before.
>
>
>
> On Tue, Nov 27, 2018 at 12:50 PM Steve Ebersole <steve(a)hibernate.org> wrote:
> >
> > I'd also be fine with moving to upstream as wip/6.0 with the understanding
> > that this branch can be re-written and will eventually be deleted.
> >
> >
> >
> > On Tue, Nov 27, 2018, 1:13 AM Yoann Rodiere <yoann(a)hibernate.org> wrote:
> >
> > > I think it would be better to at least move the code to a 6.0 branch on
> > > the main repository, just so that the code is a little easier to find for
> > > external contributors/users. Even if it's named "6.0-wip" to mention that
> > > you may end up rewriting history on that branch. If we release binaries,
> > > then the code is official and should be in plain sight.
> > >
> > > But if it's not an option, just pushing the 6.0.0.Alpha1 tag to the main
> > > repository would be a step in the right direction.
> > >
> > > Yoann Rodière
> > > Hibernate NoORM Team
> > > yoann(a)hibernate.org
> > >
> > >
> > > On Tue, 27 Nov 2018 at 00:25, Sanne Grinovero <sanne(a)hibernate.org> wrote:
> > >
> > >> On Mon, 26 Nov 2018, 23:39 Gail Badner <gbadner(a)redhat.com wrote:
> > >>
> > >> > That's fine with me.
> > >> >
> > >>
> > >> +1 But could you push the release tag to the reference repo? Just to make
> > >> sure we have it for future reference.
> > >>
> > >> Thanks
> > >>
> > >>
> > >> > On Mon, Nov 26, 2018 at 11:29 AM Steve Ebersole <steve(a)hibernate.org>
> > >> > wrote:
> > >> >
> > >> > > This Wednesday we plan to release 6.0 Alpha1 and I thought it best to
> > >> > start
> > >> > > discussing how to best handle the 6.0 and master branches.
> > >> > >
> > >> > > I think we should keep 6.0 a little while longer in my fork and 5.4 as
> > >> > > master until 6.0 becomes more stabilized to make it easier for 5.4
> > >> > > maintenance. And reconsider as we approach Beta1.
> > >> > >
> > >> > > But this affects everyone, so wanted to see what others thought...
> > >> > > _______________________________________________
> > >> > > hibernate-dev mailing list
> > >> > > hibernate-dev(a)lists.jboss.org
> > >> > > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> > >> > >
> > >> > _______________________________________________
> > >> > hibernate-dev mailing list
> > >> > hibernate-dev(a)lists.jboss.org
> > >> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> > >> >
> > >> _______________________________________________
> > >> hibernate-dev mailing list
> > >> hibernate-dev(a)lists.jboss.org
> > >> https://lists.jboss.org/mailman/listinfo/hibernate-dev
> > >>
> > >
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
7 years, 4 months
ORM 6 branch
by Steve Ebersole
This Wednesday we plan to release 6.0 Alpha1 and I thought it best to start
discussing how to best handle the 6.0 and master branches.
I think we should keep 6.0 a little while longer in my fork and 5.4 as
master until 6.0 becomes more stabilized to make it easier for 5.4
maintenance. And reconsider as we approach Beta1.
But this affects everyone, so wanted to see what others thought...
7 years, 4 months
Reconfiguration of bounce processing on this mailing list
by Sanne Grinovero
Hi all,
I reconfigured some details of Mailman regarding this list, following
advice from Red Hat sysadmins. This is unlikely to solve the problems
but should help us get some diagnostic data which is sadly missing at
this moment.
Please do not make any change, or reach out to me in case of such need.
Thanks,
Sanne
7 years, 4 months
Moderation of in.relation.to
by Sanne Grinovero
Apparently I stopped receiving notifications from Discus about needing
to approve a comment, and it looks like you all did?
I just noticed as someome mentioned "while my other comment is not
approved" and I thought "wait, what? I know nothing about other
pending comments.." and didn't see any clue on the UI either.
I eventually found the comments approval queue, and there were a dozen
comments waiting; some >8 months old. Embarassing :(
Let's make sure that at least some of us receive a timely
notification. Any volunteers to register for this? I will register
myself, hoping that some more of you will join on this.
Thanks,
Sanne
7 years, 4 months
Hibernate 5.2.18
by Guillaume Smet
Hi,
I started the release process but our Nexus' Lucene indexes are apparently
broken.
Can't close the repository and release it.
Will follow up next week.
--
Guillaume
7 years, 4 months
CI - Default Maven settings
by Yoann Rodiere
Hello,
Because of recurring issues, I will remove the default Maven settings that
include the JBoss Nexus coordinates from our CI.
Be prepared for build failures on Maven projects (I don't think Gradle
projects will be impacted), and please let me know if you can't solve them.
Generally a failing build can easily be fixed by adding "-s
settings-example.xml" to the Maven arguments, where "settings-example.xml"
is a file in your git repository that should be there for new contributors'
sake anyway.
There are also ways to get rid of the custom settings completely for
non-release builds, but that will require one or two days worth of work,
due to all the places in our builds relying on these settings (Karaf,
Wildfly, ...). If you are interested, just ping me and I can explain what
we did on Search.
As to why:
The idea is that anyone checking out our projects should be able to run
`mvn clean install` and it should "just work"; to check that, our CI builds
should be as similar as possible to a random contributor's environment,
i.e. it should be as little customized as possible.
With that in mind, having custom Maven settings applied by default to all
projects does not make much sense to me, and even seems harmful. In my case
it's harmful because I expected all the necessary configuration, including
the URL of the JBoss Nexus, to be included in Search's POM files, and I
expected the build to fail if anything was missing, allowing me to see that
Search is not contributor-friendly and should be fixed. As it turns out,
because of our CI, it was not the case.
Yoann Rodière
Hibernate NoORM Team
yoann(a)hibernate.org
7 years, 4 months
Hibernate ORM 5.4.0.CR1 released
by Guillaume Smet
Hi,
We just released Hibernate ORM 5.4.0.CR1, the first candidate release of
5.4.0.
5.4 is the direct continuation of 5.3 and we will encourage everyone to
upgrade to it to benefit from the latest fixes.
Thus thoroughly testing this release candidate is especially important.
It brings EntityGraph improvements, out of the box JDK 11 support, bug
fixes and other minor improvements.
More information in the announcement post:
http://in.relation.to/2018/11/15/hibernate-orm-540-cr1-out/ .
Feedback very welcome!
--
Guillaume
7 years, 4 months
