The job for building the web-site failed because it couldn't retrieve the
hibernate-core POM from Nexus (see [1], not sure why, maybe you did the
web-site push before releasing the artifact in Nexus?).
I've re-triggered the build and it gets past this issue now, but it now
fails apparently to to l
2015-04-01 2:21 GMT+02:00 Steve Ebersole :
> Just to clarify... I *think* that as long as we run the build with Java 8
> and set the bootclasspath to 6 or 7 we should be fine.
>
Yes, setting the boot classpath to 6 (or 7) makes sure you only use classes
present in that JDK (be it explicitly or i
Hi,
On Wed, Apr 01, 2015 at 09:26:08AM +0200, Gunnar Morling wrote:
> The job for building the web-site failed because it couldn't retrieve the
> hibernate-core POM from Nexus (see [1], not sure why, maybe you did the
> web-site push before releasing the artifact in Nexus?).
FYI, part of the site
> Currently, AnimalSniffer is in place to prevent this very category of
error and I'm wondering why it didn't detect the "usage" of KeySetView.
Looked at this a bit closer. Turns out, AnimalSniffer *will* detect this
issue if it actually is run. The problem is that AS apparently is not
executed by
Did entity updating changed in HS5 / Lucene4?
(aka Document updating)
Since this used to work for us (with HS4, Lucene3):
---
@Test
public void testProjectionQueriesHandleEntityModificationProperly() throws
Exception {
Entity e = createEntity("test", 1)
.withProperty("prop", Arrays.a
Hi Ales,
I expect our Update routines to still work. I don't know what the code
you're showing does though, as those are not our APIs.
If you could share a test using our APIs I'll look at it.
The only thing I can think of is that now there's an explicit FLUSH
type of Work, if you miss that you m
One other thing I noticed:
hibernate-core-5 depends on
org.jboss.logging
jboss-logging
3.2.1.Final
and if you have hibernate-validator 5.1.3.Final (the last stable), it will
depend on
org.jboss.logging
jboss-logging
3.1.4.GA
So you will get an exception of method not found on some jboss-logging
> I expect our Update routines to still work. I don't know what the code
> you're showing does though, as those are not our APIs.
>
> If you could share a test using our APIs I'll look at it.
What about if you run our test? :-)
(it should be easy -- once you have all CD projects checked-out and b
Oh,
and one last thing: I don't think this is fixed:
https://hibernate.atlassian.net/browse/HHH-8805
Here's my mapping:
@ManyToMany(targetEntity = AbstractFilterModel.class, cascade = {
CascadeType.PERSIST,
CascadeType.MERGE,
CascadeType.REFRESH
}, fetch = FetchTy
Hi Petar,
the version issue of jboss-logging is a known limitation; I've
described some details on the wildfly-dev mailing list.
I was expecting for people to choose the most up to date version of
jboss-logging in case of conflicting versions though, or manage the
version explicitly rather than lea
On 1 April 2015 at 11:39, Ales Justin wrote:
>> I expect our Update routines to still work. I don't know what the code
>> you're showing does though, as those are not our APIs.
>>
>> If you could share a test using our APIs I'll look at it.
>
> What about if you run our test? :-)
> (it should be e
Frankly I don't know if it is enabled or how to enable it :) I'm using
spring-boot with log4j2 as a logging implementation and It was working
perfectly fine with hibernate 4.3.8.Final and hibernate-validator
5.1.3.Final
2015-04-01 13:45 GMT+03:00 Sanne Grinovero :
> Hi Petar,
> the version issue
>>> I expect our Update routines to still work. I don't know what the code
>>> you're showing does though, as those are not our APIs.
>>>
>>> If you could share a test using our APIs I'll look at it.
>>
>> What about if you run our test? :-)
>> (it should be easy -- once you have all CD projects
And no, we generally do not reopen issues from Closed state. And here,
given the different branches, I'd be more inclined to create a different
issue referencing the original.
On Wed, Apr 1, 2015 at 6:18 AM, Steve Ebersole wrote:
> Hmm, it seems I inadvertently set the wrong fix version on HHH-
No. You know why it could not find the POM ;)
On Wed, Apr 1, 2015 at 2:26 AM, Gunnar Morling wrote:
> The job for building the web-site failed because it couldn't retrieve the
> hibernate-core POM from Nexus (see [1], not sure why, maybe you did the
> web-site push before releasing the artifact
Hmm, it seems I inadvertently set the wrong fix version on HHH-8805. It is
fixed in our metamodel branch which is 6.0. I pulled the necessary
metamodel (org.hibernate.mapping) changes back to master (5.0), but only
the hbm.xml form of naming the FK "none" (magic value) is supported to
truly disab
Hi,
On Wed, Apr 01, 2015 at 11:45:55AM +0100, Sanne Grinovero wrote:
> the version issue of jboss-logging is a known limitation; I've
> described some details on the wildfly-dev mailing list.
> I was expecting for people to choose the most up to date version of
> jboss-logging in case of conflicti
Sorry, wrong class... XmlElementRef, not XmlElement:
/home/sebersole/projects/hibernate/hibernate-orm/hibernate-core/target/generated-src/jaxb/main/org/hibernate/boot/jaxb/hbm/spi/JaxbHbmFilterType.java:57:
error: cannot find symbol
@XmlElementRef(name = "aliases", namespace = "
http://www.hi
Baseline on Java 8? Hmm... Well thanks for tempting me :)
What do you mean by "be able to experiment with significant API
improvements"?
On Tue, Mar 31, 2015 at 7:18 PM, Sanne Grinovero
wrote:
> I wouldn't disagree on requiring Java 7.
> I probably wouldn't disagree with Java 8 either, after a
https://hibernate.atlassian.net/browse/HHH-8805?focusedCommentId=66093&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-66093
On Wed, Apr 1, 2015 at 6:20 AM, Steve Ebersole wrote:
> And no, we generally do not reopen issues from Closed state. And here,
> given the d
https://hibernate.atlassian.net/browse/HHH-9704
On Wed, Apr 1, 2015 at 6:20 AM, Steve Ebersole wrote:
> And no, we generally do not reopen issues from Closed state. And here,
> given the different branches, I'd be more inclined to create a different
> issue referencing the original.
>
> On Wed,
Increase your Gradle-fu we must young apprentice :)
AnimalSniffer is still run. I simply converted it to be a plugin. Check
out org.hibernate.build.animalsniffer.AnimalSnifferPlugin in ORM's
/buildSrc project
AnimalSniffer will apparently not detect this :)
On Wed, Apr 1, 2015 at 4:32 AM, Gunn
I saw the plug-in, Steve. But how/when is it executed?
Running "./gradlew build" used to execute AnimalSniffer and would have
revealed that accidental usage of KeySetView. That's not the case anymore.
It would be nice if that new plug-in could be applied automatically after
compileJava as it used
OK, maybe I'm doing something wrong. I also tried setting the foreign key
name to "none" like this:
@ManyToMany(targetEntity = AbstractFilterModel.class, cascade = {
CascadeType.PERSIST, CascadeType.MERGE, CascadeType.REFRESH }, fetch =
FetchType.LAZY)
@JoinTable(inverseJoinColumns = {
Gunnar, it is applied. Add something that is java 8 specific and see...
On Apr 1, 2015 7:59 AM, "Gunnar Morling" wrote:
> I saw the plug-in, Steve. But how/when is it executed?
>
> Running "./gradlew build" used to execute AnimalSniffer and would have
> revealed that accidental usage of KeySetVi
Hum, you are not April-fooling me, right ;)
There is something Java-8-specific in already: the usage of
ConcurrentHashMap#keySet() (in
SessionFactoryImpl#iterateEntityNameResolvers()) which - when compiled on
Java 8 - adds a reference to the Java-8-only type KeySetView to the class
file of Session
On Wed, Apr 01, 2015 at 06:22:22AM -0500, Steve Ebersole wrote:
> No. You know why it could not find the POM ;)
LOL. It keeps amazing me what a time sink Nexus is.
--Hardy
pgpORUB6rPYNs.pgp
Description: PGP signature
___
hibernate-dev mailing list
h
Ok, Sanne did the required set-up and the job has succeeded now:
http://ci.hibernate.org/view/Website/job/www.hibernate.org/ I can see the
Beta1 download, doc links etc.
Generally best is to check this job for failures if an expected change to
the web site does not show up on prod.
--Gunnar
20
I'm not going to argue with you man. AnimalSniffer *is* run. If you don't
believe that and don't want to verify it for yourself, oh well, nothing I
can do about that...
On Wed, Apr 1, 2015 at 8:32 AM, Gunnar Morling wrote:
> Hum, you are not April-fooling me, right ;)
>
> There is something Ja
Sanne, I went back and tried applying this -target flag but have not had
any luck with it. I applied it through the XJC2Task Ant task:
ant.xjc(
destdir: "${jaxbTargetDir}",
binding: hbmXjb.path,
schema: hbmXsd.path,
extension
30 matches
Mail list logo
