may end up simply completely removing it from there.
[1]
https://docs.jboss.org/hibernate/orm/3.3/reference/en/html/performance.html#performance-cache-mapping
On Fri, Nov 13, 2015 at 3:41 PM Steve Ebersole wrote:
> I worry that this stuff may just not work too. The tests that tested thi
Regarding HHH-10267...
5.1 will include a new feature allowing users to specify groups for
(bytecode enhanced) lazy attribute loading. In the original support
accessing one of these lazy attributes forced them all to be loaded[1].
For example...
@Entity
public class Company {
...
@Basic(
It was to work around certain containers (not just EE containers) that
implement "resource containment" checks. The Hibernate Session defers
getting a JDBC Connection until it actually needs one, which can lead to
cases like the following where 2 beans share a Session/EM:
Bean1: get Session, but
the lazy fetch profiles. Previously it
> > required the Blob to be moved to a different table.
> >
> > Vlad
> >
> >
> >
> > Vlad
> >
> > On Mon, Nov 16, 2015 at 11:09 PM, Steve Ebersole
> > wrote:
> >
> >> Regarding HHH-10267
This is a list for the discussion of HIbernate development. Your question
is not a Hibernate development discussion, its a user question. In the
future, please refrain from asking usage questions on a developer list.
Thanks.
I will address this one quickly though...
Unfortunately that method is
As John pointed out the 39 are from attempting to apply a perf patch to
5.0.
The hibernate-infinispan tests have been an ongoing issue, which is why I
disabled them. In fact I think after 5.0.4 we ought to stop accepting
patches against hibernate-infinispan until the tests are fixed.
On Wed, Nov
On Wed, Nov 18, 2015 at 6:08 AM Vlad Mihalcea
wrote:
> Hi Gunnar,
>
> The best article on this subject is this one:
>
>
> http://www.anyware.co.uk/2005/2012/11/12/the-false-optimism-of-gorm-and-hibernate/
To be honest I stop reading after I read things like
This is because Hibernate caches th
So if I understand correctly, I just inverted the 2 booleans arguments when
trying to apply this to 5.0?
On Wed, Nov 18, 2015 at 4:27 AM John O'Hara wrote:
> Gail,
>
> Tests on hibernate-core in 5.0 branch are failing due to
>
> https://github.com/hibernate/hibernate-orm/commit/7633d2fce540a979
omething that
> was there for quite some time.
>
> If anyone (Galder?) is willing to look into it, please feel free to play
> with [1].
>
> Radim
>
> [1] ci.hibernate.org/job/hibernate-orm-infinispan-testsuite-rvansa
>
> On 11/18/2015 03:20 PM, Steve Ebersole wrote:
> In the tests where lazyPropertiesAreUnfetched is set to true, the
> disableVersionIncrement was inadvertently being set to true for
> MutableEntitEntry's and therefore the version was not being incremented.
> That was causing the tests to fail as the Entity version was not
> incremented during the tes
NT.
> I'll keep you posted with the final results.
>
> Do you think we should update the docs to explain that this is rather
> required by Java EE containers, and it might be fine with stand-along JTA
> transaction managers?
>
> Vlad
>
>
>
> On Wed, Nov 18, 2015
vious state
> is lost and so you won't be able to use the previous state in the WHERE
> clause so to detect an entity change. One workaround is the EXTENDED
> PersistenceContext, but that's usually associated o Java EE (Spring doesn't
> really offer it right out of the box).
Per $subject
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
http://in.relation.to/2015/11/18/hibernate-orm-504-final-release/
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Maybe we should just go "all the way" and have a per-column version? ;)
Anyway, like I said...
Personally I am inclined to vote -1 to this at the moment, but I am
interested to hear what others might think.
On Wed, Nov 18, 2015 at 11:35 PM Vlad Mihalcea
wrote:
> Actually both merge() and upda
Vlad, back to your original question... What specifically did you mean?
Are you talking about something like https://github.com/integrations/gitbook
?
On Fri, Nov 13, 2015 at 3:39 PM Steve Ebersole wrote:
> On Fri, Nov 13, 2015 at 3:30 PM Hardy Ferentschik
> wrote:
>
>> Hi,
&g
m
>
> What do you think?
>
> Vlad
>
> On Thu, Nov 19, 2015 at 4:16 PM, Steve Ebersole
> wrote:
>
>> Vlad, back to your original question... What specifically did you mean?
>> Are you talking about something like
>> https://github.com/integrations/gitbook ?
&g
As far as the #7 PR, corry I personally have no idea. The problem is all
the "other" consumers of HCANN I am always told about when I want to change
things in HCANN. I have no idea of the type of impact it might have on
some consumers I know nothing about. For ORM, we do essentially the same
che
y.DynamicBatchingEntityLoaderBuilder#multiLoad
>
>
>
> So in new API for multiple load we lose at least 2 possible extension
> points: onLoadEvent, Persister.load (here we could customize loader -
> specify our own instead hardcoded one)
>
>
>
> From my p
The annotation binder code does this checking. Ultimately (unfortunately)
the binding code does need to understand whether to build a
o.h.mapping.Set, o.h.mapping.List, etc. It makes the reasonable assumption
that the custom collection type (ceylon.collection.MutableSet) at least
implements one o
This has always made me nervous ever since it happened a few times
inadvertently after first moving to git. Thanks for pointing out that
they finally added support for that.
For reference...
https://github.com/blog/2051-protected-branches-and-required-status-checks
On Tue, Nov 24, 2015, 10:24 A
nments.
> I wonder if today's Java EE application servers still require the
> aggressive release as an workaround to their connection leak detection
> algorithms.
>
> Vlad
>
> On Wed, Nov 18, 2015 at 5:49 PM, Steve Ebersole
> wrote:
>
>> Yes, I think that's
I'd prefer to just not do the docbook phase; it's just unnecessary overhead
during a build.
I'd be very surprised if the asciidoctor tool chain does not allow us to
plugin CSS as well. Granted we'd have to adjust the CSS for the
styles/classes used by the asciidoctor output. I'll ask around.
On
Ok, I am now for real starting the release ;)
On Wed, Dec 2, 2015 at 11:41 AM andrea boriero wrote:
> Per $subject
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
___
http://in.relation.to/2015/12/02/hibernate-orm-505-final-release/
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
SQM needs information about the domain model being queried. In the
initial original Antlr redesign work I did, I opted for a completely new
"type system" specific to the parsing. The main reason for this was to
allow for "other consumers" (besides Hibernate ORM) of its services. By
and large we
My understanding is that "Postgres Plus", "Postgres Advanced"
and "Postgres Plus Advanced" are really all the same thing.
But really, I have no idea. I think we should lobby these folks to make
these database names more obtuse ;)
On Thu, Dec 3, 2015 at 1:52 AM Gail Badner wrote:
> I see that
s not very consumption friendly"
>
> Thanks
>
>
>
> On 3 December 2015 at 15:38, Steve Ebersole wrote:
>
>> SQM needs information about the domain model being queried. In the
>> initial original Antlr redesign work I did, I opted for a completely new
>> "
On Fri, Dec 4, 2015 at 4:50 AM Sanne Grinovero wrote:
> Hi Luis,
> thanks for this proposal, I was looking forward to see more
> improvements in the area.
>
> Adding more properties sounds good to me, although I'd not use the
> prefix "hibernate.enhance" as it sounds like it's about enhancing
> H
This all sounds good to me. For runtime enhancement I am ok with
deprecating that setting, as long as in the meantime until its removal we
continue to treat it as enabling all the enhancement features in addition
to logging that warning.
On Fri, Dec 4, 2015 at 12:29 AM Luis Barreiro wrote:
> Hi
On Fri, Dec 4, 2015 at 5:43 AM Steve Ebersole wrote:
> Hm, there is a problem in the doc generation apparently :( For some
> reason this chapter is not pulled in
> https://github.com/hibernate/hibernate-orm/blob/master/documentation/src/main/docbook/userGuide/en-US/chapters/en
Luis, I am trying to remember if there is any reason I only added this to
master (5.1). Was there a reason to not add it to 5.0 as well? Aside from
the parts about lazy groups that is :)
On Fri, Dec 4, 2015 at 6:28 AM Steve Ebersole wrote:
> On Fri, Dec 4, 2015 at 5:43 AM Steve Ebers
Per the discussion Luis and I had on IRC we will go with the prefix
"hibernate.enhancer..". "enhancer" makes it more than clear what the
intended target is.
On Fri, Dec 4, 2015 at 4:50 AM Sanne Grinovero wrote:
> Hi Luis,
> thanks for this proposal, I was looking forward to see more
> improvem
Ok, I am going to apply SQM-28-2 upstream.
On Thu, Dec 3, 2015 at 10:36 AM Steve Ebersole wrote:
> I mean that getting information out of them is not easy. Especially
> EntityPersister - specifically getting sub/super information, attribute
> information, etc.
>
>
> On Thu,
x27;m not sure the use case there is well-defined enough to warrant doing the
split up front, let alone whether that is even a use case we want to
support...
On Fri, Dec 4, 2015 at 10:28 AM Steve Ebersole wrote:
> Ok, I am going to apply SQM-28-2 upstream.
>
> On Thu, Dec 3, 2015 at
ge - or at least
> not make it harder - for people to experiment in that direction.
> But of course, if the cost is high for you maybe that's better
> addressed at later stage.
>
> Thanks
> Sanne
>
> On 6 December 2015 at 20:42, Steve Ebersole wrote:
> > Relatedly I
On Sat, Dec 5, 2015 at 11:46 PM Vlad Mihalcea
wrote:
> HI,
>
> I always wandered why the identity generator needs to assign an identifier
> prior to flushing.
>
In general, how else do you propose to obtain the identifier with which we
can associate the entity into the PersistenceContext? That
WDYM by "Hibernate-native Batching API"?
On Mon, Dec 7, 2015 at 12:57 PM Vlad Mihalcea
wrote:
> I'm sure it require a significant change since the persistence context is
> very much tied to the entity identifier.
> Theoretically, it could work because the identifier is required for
> database o
I've started discussions about this in general wrt the hibernate.org
webpage. There is a lot of version-specific information there. Hosting
this specifically for documentation on the doc site would be one option.
Note however that we have limited forms of access to that docs site which
makes it l
Well if you read closely I said we support it on the
EntityManager/Session. As far as I know we have never supported that on
the EntityManagerFactory/SessionFactory.
On Tue, Dec 8, 2015 at 11:50 AM Vlad Mihalcea
wrote:
> Hi,
>
> I stumble don this question on the forum:
>
> https://forum.hibern
Interesting about the SO Teams feature, I had not seen that yet. I'll
have to look at it.
On Wed, Dec 9, 2015, 7:43 AM Hardy Ferentschik wrote:
> Hi,
>
> > I also think we should keep the forum it's a way to reach the actual dev
> > team. On SO, you get answers for the community.
>
> I am con
We could leave the ones that are on docs.jboss.org in place and just move
the current stable ones. I see no benefit to moving ORM 3.2 docs over e.g.
On Wed, Dec 9, 2015 at 10:08 AM Sanne Grinovero wrote:
> On 9 December 2015 at 13:54, Hardy Ferentschik
> wrote:
> > Hi,
> >
> > On Wed, Dec 09,
You know my thoughts on the forum. I think forum versus mailing list is
just very much a personal preference. Some people really like one or the
other. Why not split the middle and use mailing list + nabble?
On Thu, Dec 10, 2015, 7:35 AM Hardy Ferentschik wrote:
> Hi,
>
> > > So basically I w
looked into creating a Hibernate SO Team. Are we thinking one
team? Or one per project (ORM, OGM, etc)?
On Thu, Dec 10, 2015 at 9:20 AM Steve Ebersole wrote:
> If anyone is unfamiliar with Nabble... Here is the Nabble-ized form of
> this very mailing list: http://hibernate-development.74
I am not really sure what "have their headers patched to declare that the
new guides are the canonical version" means in practical terms...
On Wed, Dec 9, 2015 at 10:55 AM Sanne Grinovero wrote:
> On 9 December 2015 at 16:36, Steve Ebersole wrote:
> > We could leave t
Thu, Dec 10, 2015 at 7:41 AM Steve Ebersole wrote:
> You know my thoughts on the forum. I think forum versus mailing list is
> just very much a personal preference. Some people really like one or the
> other. Why not split the middle and use mailing list + nabble?
>
> On Thu, Dec
On Thu, Dec 10, 2015 at 11:43 AM Sanne Grinovero
wrote:
> On 10 December 2015 at 15:24, Steve Ebersole wrote:
> > BTW, there is already a hibernate-users mailing list hosted on the JBoss
> > Mailman instance. Back when we moved to JBoss Mailman they used to set
> up a
>
I just sent the request.
On Thu, Dec 10, 2015 at 12:26 PM Sanne Grinovero
wrote:
> On 10 December 2015 at 17:48, Steve Ebersole wrote:
> > On Thu, Dec 10, 2015 at 11:43 AM Sanne Grinovero
> > wrote:
> >>
> >> On 10 December 2015 at 15:24, Steve Ebersole
>
se ALWAYS, especially if they mix Hibernate
> with native queries.
>
> What do you think? Should we add a Jira issue for this issue or we should
> leave this responsibility to the application layer?
>
> Vlad
>
> On Tue, Dec 8, 2015 at 7:58 PM, Steve Ebersole
> wrot
at can be specified and
> dispatched by all the layers.
> (c) DistinctLimitQuery: Let's hibernate can do the real paging
> query with collection fetches when the database is Oracle.
>
>
> As Steve Ebersole said, the JPA part is not smooth. Yes, he's right,
&
Just to follow up on this.. for ORM I went ahead and protected master, 5.0,
4.3 and 4.2 branches.
On Tue, Nov 24, 2015 at 10:33 AM Steve Ebersole wrote:
> This has always made me nervous ever since it happened a few times
> inadvertently after first moving to git. Thanks for pointing ou
It's hard to say without understanding the scenario where you are seeing
this as a problem. I have some guesses as to what may be the problem, but
without understanding more about why you see this as a problem in the first
place it is hard to give you an answer. For example, I wonder if for
envi
Sanne, you just described the general approach of "short naming" for config
options overall :)
On Mon, Dec 14, 2015 at 6:28 PM Sanne Grinovero wrote:
> On 14 December 2015 at 17:10, Vlad Mihalcea
> wrote:
> > Hi,
> >
> > We really need to test it thoroughly because the current pooled optimize
It's very possible that code comments may no longer be pertinent.
On Mon, Dec 14, 2015 at 10:26 AM Sanne Grinovero
wrote:
> Hi all,
> while reviewing an improvement by Stale about reducing
> synchronization, I'm having the impression that the synchronization
> could be completely removed.
>
> Bu
I'm confused. Sanne was talking about a completely different piece of code
from optimizers. Maybe you are mixing this and the other current
hibernate-dev discussion?
On Mon, Dec 14, 2015 at 11:10 AM Vlad Mihalcea
wrote:
> Hi,
>
> We really need to test it thoroughly because the current pooled
I did not add those comments; they were just in some code I copied over
into that class.
On Tue, Dec 15, 2015, 4:02 AM Sanne Grinovero wrote:
> On 15 December 2015 at 01:46, Steve Ebersole wrote:
> > It's very possible that code comments may no longer be pertinent.
>
> Ri
tly failing some new unit tests, which are cloned from
> existing PooledLoOptimizer tests which might be part of the problem.
>
> Scott
>
> [1]
> https://github.com/scottmarlow/hibernate-orm/tree/pooled-optimiser-hack
>
> On 12/14/2015 10:12 PM, Scott Marlow wrote:
> >
Yes, this points back to a discussion we had here wrt allowing Java 8 for
tests and the problems that causes for IDE imports.
On Tue, Dec 15, 2015 at 2:52 PM andrea boriero wrote:
> i think you are using java 7 instead of java 8..
>
> On 15 December 2015 at 20:32, Scott Marlow wrote:
>
> > Hi,
thread local
> blocks were smaller than the incrementSize, so not every thread local
> allocation would require a DB call. Your patch changes that approach but I
> don't think it actually matters that much, the overall performance should
> still be similar, and it has the advantag
FYI...
http://meta.stackoverflow.com/questions/312708/stackoverflow-teams-sign-up
On Thu, Dec 10, 2015 at 3:07 PM Steve Ebersole wrote:
> I just sent the request.
>
>
> On Thu, Dec 10, 2015 at 12:26 PM Sanne Grinovero
> wrote:
>
>> On 10 December 2015 at 17:48, Steve
I had planned to support this JSR when I thought it would be part of the
JDK. But as it is, supporting this properly would mean a whole new
module/artifact just to add these few types + the dependency (similar to
hibernate-java8). I am not a fan of the fact that it would require a
separate depend
oo, where we provide additional constraint
> validator types based on what's available in the runtime environment.
>
> Why do you consider it as not proper?
>
>
> 2015-12-22 17:03 GMT+01:00 Steve Ebersole :
> > I had planned to support this JSR when I thought it would
; > +1
> >
> > > Why do you consider it as not proper?
> >
> > Same question for me. It might not be perfectly well defined in terms
> > of Maven dependencies, still I think the practical benefit for users
> > far outweights the cons.. if that's what y
nstraint validators, and it works well, I can't remember of any
> related issue or complaint. I suppose it'd help if you could point to
> that resource describing potential issues with optional.
>
> 2015-12-22 20:31 GMT+01:00 Steve Ebersole :
> > Well the Bitronix use-
I'd prefer that IDENTITY never be the native generator any time we add a
new Dialect. Native is a Hibernate-only concept and so we can really
choose whatever we want for native generators. Also native is an outdated
concept, replaced by AUTO and SequenceStyleGenerator. IMO we should never
be cho
+1 from me on the concept.
Of course the problem is always the resources needed keep that going. But
if you are offering... I huge +1 from me.
On Thu, Dec 24, 2015 at 4:50 AM Emmanuel Bernard
wrote:
> That’s a good idea.
> We actually also discussed something a bit different. Every month or so
ptable for the user having to depend on another submodule
> or not. If you think that's ok, then go for it ;)
>
>
> 2015-12-22 23:09 GMT+01:00 Steve Ebersole :
> > You mean in addition to Maven's own documentation? Quote[1]:
> >
> > "Optional dependencies are
For sure we will support it in some fashion. The discussion is simply
about the how
On Mon, Jan 4, 2016 at 1:04 AM Petar Tahchiev wrote:
> Any updates on this? What has been decided? Can we see some hibernate
> support for this JSR?
>
> 2015-12-26 19:13 GMT+02:00 Steve Ebersole :
I thought we had agreed to try what that linked post calls "Newly
Registered Users Group"? Specifically:
phpBB 3.0.6 also sees the introduction of the "Newly Registered Users"
group. This feature, which may be enabled via the User Registration
Settings page of the Administration Control Panel (A
Sorry Scott, I am not sure I understand exactly what you are asking. I
will try to answer what I think you are asking as best I can..
On Tue, Jan 5, 2016 at 9:35 AM Scott Marlow wrote:
> I missed adding the WildFly clustering configuration for the Hibernate
> immutable-entity cache. I opened
On Tue, Jan 5, 2016 at 12:42 AM Gail Badner wrote:
>
>
>> Native is a Hibernate-only concept and so we can really choose whatever
>> we want for native generators. Also native is an outdated concept,
>> replaced by AUTO and SequenceStyleGenerator. IMO we should never be
>> choosing IDENTITY fo
HHH-9548[1] presents an interesting conundrum in terms of how to handle
null parameter values in regards to stored procedures and specifically in
terms of any argument defaults that might be defined on the database. At
the moment our support decides to not pass along the null in the desire to
not
HHH-10307[1] is another issue we need to get some consensus on. Initially
we had removed JTA as a transitive dependency, but that is not really
valid. We need to discuss alternatives and options.
[1] https://hibernate.atlassian.net/browse/HHH-10307
___
Awesome! Although I find it strange that a mere 13% decrease in the number
of registered users would have such a big impact on overall performance of
the forum.
On Wed, Jan 6, 2016 at 9:53 AM Vlad Mihalcea
wrote:
> Hi,
>
> Among all 75000 registered users, 1 used to be inactive ones
> (regi
(a) just the api
On Wed, Jan 6, 2016 at 10:20 AM Gunnar Morling wrote:
> To get some clarification: When using solely JDBC, what is required at
> runtime:
>
> a) the JTA API packages only
> b) JTA API and implementation
> c) none of the above
>
> ?
>
>
>
&
; Since the Hibernate core relies on the JTA dependency, I think we
> shouldn't provide that dependency.
> When someone doesn't want it he should explicitly mark that (e.g. Maven
> exclude).
> This way we can also address the parent issue:
> https://hibernate.atlassian.
on
> either: hibernate-wildfly, hibernate-geronimo, etc?
>
> Vlad
>
> On Wed, Jan 6, 2016 at 6:36 PM, Steve Ebersole
> wrote:
>
>> Vlad, the issue is not "someone doesn't want it". In fact, for the most
>> part because of our decision to use the JTA contr
it is sensibly doable),
> followed by 2a) followed by 2b). Granted, 1) may be hard to test and
> also I am not sure whether that behaviour I described is guaranteed by
> the spec or only is exposed by specific JVMs.
>
> --Gunnar
>
>
>
> 2016-01-06 17:59 GMT+01:00 Steve Ebers
I'll put it this way Gunnar, as a user would you prefer:
1) org.hibernate.Transaction#addCallback( org.hibernate.TransactionCallback
)
2) org.hibernate.Transaction#addCallback( javax.transaction.Synchronization
)
?
On Wed, Jan 6, 2016 at 11:34 AM Steve Ebersole wrote:
> The JTA
Just a heads up that I tentatively set Jan 27th as the release date for
5.1. Please let me know if that does not work for anyone. Also please
keep that date in mind if there is anything you want to get into 5.1.
___
hibernate-dev mailing list
hibernate-
Depending on exactly how you are testing that, that sounds like a bug. Are
you (inadvertently) using bytecode enhancement?
On Fri, Jan 8, 2016 at 9:09 AM Vlad Mihalcea
wrote:
> Hi,
>
> I remember that for a bidirectional @OneToOne relationship, the optional =
> false attribute could instruct H
HHH-9491[1] is a report that discusses problems when requesting global
quoting (what JPA calls delimited identifiers). My last comment[2]
discusses 2 options for handling this. I'd like to get others thoughts.
[1] https://hibernate.atlassian.net/browse/HHH-9491
[2]
https://hibernate.atlassian.ne
I don't see a Jira to upgrade Javassist as part of 5.1...
On Fri, Jan 8, 2016 at 1:35 PM Scott Marlow wrote:
> Should we upgrade to javassist latest in 5.1 still?
>
> On 01/08/2016 10:08 AM, Steve Ebersole wrote:
> > Just a heads up that I tentatively set Jan 27th as
>> problem on WildFly. If it is, I'm not sure why. :)
>>
>> Scott
>>
>> [1]
>>
>> https://gist.github.com/scottmarlow/4e23e62962101b740a4a#file-gistfile1-txt-L1
>>
>> [2] https://gist.github.com/scottmarlow/dc7ebfea654984f84e2e
>>
>&
On Fri, Jan 8, 2016 at 9:00 PM Scott Marlow wrote:
> Should we also look at changing Hibernate to not require Javassist
> classes be on the deployment classpath?
I just don't see how that is ever going to be realistically possible. If
you have specific suggestions, we are all ears ;)
_
The use of Java 8 features in Hibernate ORM is starting to expand. Luckily
it is still constrained to just tests.
However these usages make development in an IDE more and more difficult.
Previously this was isolated to hibernate-infinispan. Now[1] this has
crept into hibernate-entitymanager. We
ntime in user apps?
>
>
> 2016-01-11 19:49 GMT+01:00 Steve Ebersole :
> > The use of Java 8 features in Hibernate ORM is starting to expand.
> Luckily
> > it is still constrained to just tests.
> >
> > However these usages make development in an IDE more and mo
Create the issue and use the 'jandex-binding' version in Jira
On Tue, Jan 12, 2016 at 5:57 AM Sanne Grinovero wrote:
> +1 this is a very common mistake for beginners.
>
> But I'm with Hardy in not trying to shoehorn such support in our
> current metadata handling, but rather to keep it in mind w
I was just guessing about leaving it blank. I do not know for sure whether
the matrix plugin allows to not specify the Dialect explicitly. That is a
worthwhile feature (to test Dialect resolution), but it would certainly
seem like the plugin does not handle it well now. So yes, leave it
explicit
orm/pull/1080 for 5.1?
>
> I'll revisit the PR tomorrow to fix the conflicts.
>
> --
> Guillaume
>
> On Tue, Jan 12, 2016 at 5:08 PM, Scott Marlow wrote:
>
>>
>>
>> On 01/11/2016 11:04 AM, Steve Ebersole wrote:
>> > On Fri, Jan 8, 2016 at 9:00 PM
Gunnar Morling wrote:
> There you go: https://hibernate.atlassian.net/browse/HHH-10440
>
> 2016-01-12 16:08 GMT+01:00 Steve Ebersole :
> > Create the issue and use the 'jandex-binding' version in Jira
> >
> > On Tue, Jan 12, 2016 at 5:57 AM Sanne Grinovero
>
we have no other choice.
> > >> For testing, I think that 1.6 is just fine and I could easily change
> > those
> > >> tests to remove the 1.8 dependency.
> > >>
> > >> So I vote for using the same JDK for both main and test in a
> pa
gt; > They are also a form of regression testing, so that we are alerted if
> some
> > future change will break the expectations we made while writing the
> > documentation code snippets.
> >
> > The reader can fork the repo and try them, if he wishes.
> >
> >
I agree completely with this.
And yes he did, but then we are moving to Asciidoc :)
On Wed, Jan 13, 2016 at 10:32 AM Hardy Ferentschik
wrote:
> Hi,
>
> > slightly related and just in case you are not aware of this feature
> > yet: You can include (parts of) actual source code files straight i
Trying to push and verify my announcement blog post for 5.0.7 release, but
Jenkins fails to build it[1]. Apparently command `rake` not found.
So what now?
[1] - http://ci.hibernate.org/view/Website/job/staging.in.relation.to/145/
___
hibernate-dev mail
Whatever you did seems to have done the trick:
http://ci.hibernate.org/view/Website/job/staging.in.relation.to/146/
Thanks
On Wed, Jan 13, 2016 at 1:32 PM Sanne Grinovero wrote:
> Could you try again now please?
>
> On 13 January 2016 at 19:26, Steve Ebersole wrote:
> > Try
ce)
On Wed, Jan 13, 2016 at 1:45 PM Steve Ebersole wrote:
> Whatever you did seems to have done the trick:
> http://ci.hibernate.org/view/Website/job/staging.in.relation.to/146/
>
> Thanks
>
>
> On Wed, Jan 13, 2016 at 1:32 PM Sanne Grinovero
> wrote:
>
>&g
Per Hardy this might be due to a bad post uploaded to staging by Max. I
just deleted that file from staging and am trying build again
On Wed, Jan 13, 2016 at 1:50 PM Steve Ebersole wrote:
> Sorry, spoke too soon...
>
> RROR: Running Awestruct failed.
> /mnt/jenkins-workd
Ok, that fixed this last problem
On Wed, Jan 13, 2016 at 2:17 PM Steve Ebersole wrote:
> Per Hardy this might be due to a bad post uploaded to staging by Max. I
> just deleted that file from staging and am trying build again
>
> On Wed, Jan 13, 2016 at 1:50 PM Steve Ebers
016-01-12-jboss-community-asylum-hibernate-strikes-back-episode-v..erb
>
> instead of
>
> /2016-01-12-jboss-community-asylum-hibernate-strikes-back-episode-v.*html*
> .erb
>
> On 13 January 2016 at 20:22, Steve Ebersole wrote:
>
>> Ok, that fixed this last problem
>
601 - 700 of 1413 matches
Mail list logo
