Steve, there is a reference to org.hibernate.engine.Mapping in a
non-javadoc comment with a javadoc tag
("@see"): org.hibernate.spatial.dialect.oracle.SDOObjectProperty#getReturnType
Also: org.hibernate.spatial.dialect.oracle.SDOObjectMethod#getReturnType
Maybe you could try removing/fixing this co
Hi all,
we renamed the Git repository name, and the respective GitHub project,
from lucene-modules to lucene-jbossmodules.
Obviously "modules" alone was getting a bit too ambiguous.
We decided to not call them "WildFly modules" as these are not used
only for WildFly, and the modular technology i
Here is the version that triggered the Travis job:
https://github.com/sebersole/hibernate-core/blob/5.3/hibernate-spatial/src/main/java/org/hibernate/spatial/dialect/oracle/SDOObjectMethod.java
As you can see those (non-)references are removed. Same error.
On Wed, Jan 3, 2018 at 3:32 AM Yoann R
On Tue, Jan 2, 2018 at 2:42 PM, Steve Ebersole wrote:
> Scott, how would we register a listener for this event?
>
If we want a standard solution, we could ask for an earlier CDI pre-destroy
listener.
The problem we have had with most CDI "listeners" so far is that they are
> non-contextual, mea
What's even more strange is that if I build just spatial's javadoc it works
fine. If I try to build the aggregated javadoc is when I see this (even
though I've removed those lines)
On Wed, Jan 3, 2018 at 8:36 AM Steve Ebersole wrote:
> Here is the version that triggered the Travis job:
>
>
> ht
OK, I've wasted way too much time on this. I'm just going to remove Java 9
from the Travis script.
On Wed, Jan 3, 2018 at 10:22 AM Steve Ebersole wrote:
> What's even more strange is that if I build just spatial's javadoc it
> works fine. If I try to build the aggregated javadoc is when I see
So I just pushed to the ORM master branch, which has caused the following
jobs to be queued up:
- hibernate-orm-5.0-h2
- hibernate-orm-5.1-h2
- hibernate-orm-master-h2-main
Only one of those jobs is configured to "watch" master. So why do these
other jobs keep getting triggered?
I see
Hi Steve,
this rings a bell, we had this bug in the past and apparently it's
regressed again :(
The latest Jenkins bug seems to be:
- https://issues.jenkins-ci.org/browse/JENKINS-42161
I'll try the suggested workarount, aka to enable SCM poll without any frequency.
Thanks,
Sanne
On 3 January
I've made the change on:
- hibernate-orm-5.0-h2
- hibernate-orm-5.1-h2
- hibernate-orm-master-h2-main
Let's see if it helps, then we can figure out a way to check all jobs
are using this workaround.
On 3 January 2018 at 18:12, Sanne Grinovero wrote:
> Hi Steve,
>
> this rings a bell, w
Nice! Glad you found something. Thanks for making the changes.
On Wed, Jan 3, 2018 at 12:16 PM Sanne Grinovero wrote:
> I've made the change on:
>- hibernate-orm-5.0-h2
>- hibernate-orm-5.1-h2
>- hibernate-orm-master-h2-main
>
> Let's see if it helps, then we can figure out a way
If you have access to the specific ExtendedBeanManager/LifecycleListener,
that should already be enough. Those things are already properly scoped to
the SessionFactory, unless you are passing the same instance to multiple
SessionFactory instances.
On Wed, Jan 3, 2018 at 10:09 AM Scott Marlow wro
11 matches
Mail list logo
