On Wed, 04-Oct-2017 13:43, Yoann Rodiere wrote:
> Hush, it's a sensitive topic :) Let's just say it's on purpose, and it
> could have been... harsher. The current style is already a compromise.
Interesting. I got more interested now, but maybe better to leave it at this.
;-)
--Hardy
Hi,
I like the new layout and navigation. Well done. One thing I am wondering though
is the rectangular "box" around the two lines in the header? Is this intended?
I find it quite harsh. I first thought it is a browser issue, but it seems
to render the same way with any browser or device.
Hi,
On Wed, 08-Jun-2016 10:37, Emmanuel Bernard wrote:
> My modest contribution
>
> https://hibernate.atlassian.net/browse/HHH-10813
> https://github.com/hibernate/hibernate-orm/pull/1408
A truly tricky one ;-) - sorry could not resist.
--Hardy
signature.asc
Description: PGP signature
Hi,
On Mon, 25-Apr-2016 11:13, Gunnar Morling wrote:
> The strategy approach sounds nice on first thought, but it also adds
> complexity.
+1
> I think the underlying question is: What's the long-term strategy around
> the "Classic API"? Should it remain in place for all times as a complete
>
Hi,
> Yet it is a good idea nowadays to have LuceneWorkSerializer extend
> Service, as we dropped that level of flexibility. This implies that
> there's a single type of serializer (at most)
Ok
> and it's totally fine to expose this as:
>SearchIntegrator#getLuceneWorkSerializer()
How is
Hi,
>3. Baseline on Java 8
I did not vote on the other thread, so I do it here +1 :-)
> Another one I'd like to discuss is the consolidation of the hibernate-core
> and hibernate-entitymanager modules into a single module
+1 I would love to see this finally happening. There were several
Hi,
> I'd like to propose an alternative approach for proxy generation which
> would avoid version issues with Javassist.
>
> The idea is to generate proxies which are fully "self-contained", i.e.
> their byte code contains no references to a library such as Javassist,
> but instead invocations
Hi,
Ahh, it's just the one under stable which is missing.
For now I am copying the latest 5.2.3 docs in while we keep discussing
the doc server changes.
--Hardy
On Sun, Feb 14, 2016 at 08:40:38PM +0100, Hardy Ferentschik wrote:
> Hi,
>
> The Validator docs are again vanished from
Hi,
> Ok, then I will drop the 'en-US' part from the path.
+1
> But to be consistent, I think we should rename the "html" in these asciidoc
> paths to "html_single".
but why even make this distinction? Just 'html' would work for me as well.
--Hardy
pgp0HN7837BKS.pgp
Description: PGP
Hi Guillaume,
Awesome to see so much activity, especially in an area which I used to work
on so much. I think it is great that we get some more eyes on the code now.
What you say makes sense from a birds eye perspective. I am hoping that
I will find some time soon to have a closer look at your
Hi,
On Wed, Feb 03, 2016 at 09:15:31AM +0100, Emmanuel Bernard wrote:
> It's probably a bug, Hardy, you confirm?
Sounds like an oversight. I would add it, make sure tests still pass and
add some new ones ;-)
--Hardy
>
> On Tue 2016-02-02 15:40, Guillaume Smet wrote:
> > Hi,
> >
> > While
Hi,
On Thu, Jan 14, 2016 at 10:37:42AM +0200, Vlad Mihalcea wrote:
> I see that the production and the staging are out of sync now and trying to
> merge the upstream production leads to a merge commit.
>
> How do we normally handle the cases when the production branch history
> diverges from
Hi,
> Personally, when using staging, I always try to leave it set to (or
> fast-forwardable to) production when I am done with a given authoring
> job. So the next guy coming after me doesn't have to care about any
> non-published commits on staging.
You are such a nice guy ;-)
--Hardy
Hi,
> Do we have to rewrite the staging history to match production and force
> push it?
If you want staging to look like production, just push the production branch
onto staging.
$ git push -f origin production:staging
--Hardy
pgpFwAg64gDPO.pgp
Description: PGP signature
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 into
> AsciiDoc documents. We do that in the HV reference guide, e.g. at [1].
> That way you are 100% sure your examples actually compile (and pass
>
Hi,
> Would it be feasible to raise a warning or error in cases where
> mapping annotations are given on an element not matching the default
> access type for that entity and @Access has not been given explicitly
> either?
Sure, but I think it would need some doing. AFAIR the code determines the
Hi,
On Thu, Jan 07, 2016 at 02:17:29PM +, Steve Ebersole wrote:
> Second, is that really the intent for "stable"? When we first starting
> doing "stable" the intent was to have stable URLs for bookmarking etc.
> What you describe, and how we actually handle it (at least on the ORM
> side),
Hi,
> +1 from me on the concept.
Same here. What would you write about?
We tried several times to ramp up on the number and posts we publish on
in.relation.to and failed so far. I guess lack of time played a big role here.
If we can ramp up the blogging effort that would be great.
--Hardy
On Thu, Dec 17, 2015 at 01:06:14PM +, Steve Ebersole wrote:
> FYI...
> http://meta.stackoverflow.com/questions/312708/stackoverflow-teams-sign-up
Interesting.
--Hardy
pgpejtNbnxaR7.pgp
Description: PGP signature
___
hibernate-dev mailing list
Hi,
On Wed, Dec 09, 2015 at 09:58:01PM +, Sanne Grinovero wrote:
> This seems a nice precedent:
> -
> https://groups.google.com/forum/#!topic/google-collections-users/m8FnCcmtC88
Right, this is pretty much what I had in mind as well. Whether one would create
a dedicated mailing list like
Hi,
> > So basically I would suggest:
> >
> > - Put the forum into a read only mode
> > - Add a banner explaining the move to Stackoverflow (similar in content to
> > what's in the post
> > mentioned above)
> > - Create a Hibernate Team on Stackoverflow
> > - Make sure all Hibernate related
Hi,
I think one thing not mentioned on this thread is the fact that we are not
controlling
the root of the webserver (afaik). The docs are hosted on docs.jboss.org and I
think we
only have write access to the hibernate sub-folder. And even if we had access
to the root
and could modify
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 confused. Is the whole forum not about community as well? I would assume
that
there are many questions which are discussed and solved by the community itself
Hi,
On Wed, Dec 09, 2015 at 03:12:54PM +0200, Vlad Mihalcea wrote:
> Is there any change we host the docs on hibernate.org and simply redirect
> the old pages from
>
> http://docs.jboss.org/hibernate
>
> to
>
> http://hibernate.org/orm/documentation
That would be an option I guess. Host the
Hi,
On Wed, Dec 09, 2015 at 02:00:06PM +, Steve Ebersole wrote:
> Interesting about the SO Teams feature, I had not seen that yet. I'll
> have to look at it.
It is quite new. Only around for a few weeks. I think the Stackoverflow team
is not 100% sure how things will work out in the long
Hi,
On Wed, Dec 09, 2015 at 05:18:23PM +0100, Emmanuel Bernard wrote:
> To complement some of the sentiment, SO is awesome to answer questions on the
> project.
> But not to get interactions with the users to get the right use case,
> exchange on potential
> bugs to later open JIRAs etc.
Hi,
On Wed, Dec 02, 2015 at 01:28:59PM +0200, Vlad Mihalcea wrote:
> I started migrating the 5.0 docbook documentation to asciidoctor, and,
> because there wasn't any converter for such a task, I wrote a small shell
> script which uses pandoc.
There is a converter -
Hi,
On Wed, Nov 11, 2015 at 02:36:13PM +, Steve Ebersole wrote:
> I think it makes sense to host these on hibernate.org *after* we figure out
> the version-specific content issues I brought up in Barcelona.
What issues are you talking about. I know you want to link to different
versions of
Hi,
> For sure we could try and further lower the bar to contribution (e.g.
> by adding "edit" links which then get you to the source on GitHub, as
> some other projects do).
> But I'd prefer to leave the rendered output
> on jboss.org, alongside with all other JBoss project's docs.
+1 - this
> > Last but not least, afaik the plan was that hibernate.org becomes the place
> > where things would get consolidated.
>
> I'd really like to see them on hibernate.org: have a better
> integration (including look& feel), better control the metadata to
> make sure people actually find the latest
On Thu, Nov 05, 2015 at 08:46:45AM +0100, Gunnar Morling wrote:
> Sanne, all,
>
> Could we please drop the 5.5 branch in the upstream repo. It matches
> exactly master (apart from the POM versions), so there is really no
> good reason to have it at this point IMHO.
+1
--Hardy
Hi,
> This ties in with an uneasiness that has been growing on me tbh... We have
> too many places users have to look for potential information. The
> website, the JBoss wiki, the GitHub wiki, README.mds, CONTRIBUTING.mds.
> It's hard to keep straight :)
That has always been my concern.
>
On Mon, Oct 05, 2015 at 02:03:54PM +, Steve Ebersole wrote:
> Bueller..?
>
> Any thoughts?
I am not familiar of the whole concept of AttributeConverter, but if you need
full type resolution of a generic type, ClassMate is the way to go.
That's what we use in Hibernate Validator and that is
Hi,
On Thu, Sep 24, 2015 at 09:23:20AM +0200, Gunnar Morling wrote:
> Either way, you should mark the field to sort on with @SortableField
> which will cause that field to get indexed as doc value field, making
> sorting much faster (see [1] and [2] for the details):
>
> @Id
>
On Wed, Sep 23, 2015 at 03:54:30PM +, Steve Ebersole wrote:
> https://hibernate.atlassian.net/browse/HHH-10121
Nice +1
--Hardy
pgpQZEyT1BtEG.pgp
Description: PGP signature
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
On Thu, Sep 24, 2015 at 10:28:14AM +0200, Gunnar Morling wrote:
> > I don't think that just adding @NumericField will do, since it is just a
> > companion
> > annotation to @Field.
>
> It does work (at least as of 5.5 where we fixed some issues around
> @NumericField); It applies to the implicit
Hi,
On Wed, Sep 23, 2015 at 02:36:05PM +, Steve Ebersole wrote:
> Its really a different discussion Hardy. The discussion here is
> whether EntityManagerFactory().getProperties() should return values that
> were not passed in the Map when building the EntityManagerFactory.
Sure. Different,
> Yes, EntityManagerFactoryBuilder#withValidatorFactory() is called (see
> https://github.com/wildfly/wildfly/blob/10.0.0.CR1/jpa/subsystem/src/main/java/org/jboss/as/jpa/service/PersistenceUnitServiceImpl.java#L150,
> I see it actually happening in the debugger), so I suppose Hibernate
> ORM has
Hi,
So if we don't want to use ~ here, I am fine with that.
+1
However I do not want this used for full text searching.
+1 I find it a bad match as well. First I think the type of integration we
would need between ORM and Search is far off in the future. If it even
makes sense.
Also
Agreed on the name being sub-par for that usage pattern most of us
apparently have in mind. So yes, if there was another uniformly-to-use
method for equality I wouldn't mind limiting the current one to string
fields.
Cool
--Hardy
___
hibernate-dev
On Thu, Aug 27, 2015 at 11:34:19AM +0100, Sanne Grinovero wrote:
Regarding strong reason, my doubt is just that the method seems
wrong for the purpose: keyWORD(), and it seems to imply we override an
explicit user choice.
Right. I also think some sort of understanding is necessary. Obviously
On Thu, Aug 27, 2015 at 10:53:29AM +0100, Sanne Grinovero wrote:
So.. questions:
1# Deprecate?
I'll have to fix the inconsistency for now and make it produce a
working query in all cases... but do we want to deprecate this and
have it produce a WARN to state that you really shouldn't use a
On Wed, Aug 26, 2015 at 09:58:39PM +0100, Sanne Grinovero wrote:
Assuming you build a Lucene Query the following way:
queryBuilder.keyword().onField( age ).matching( 5 ).createQuery();
What is your expectation, if the age field is being indexed as a
NumericField?
I would say that
I would say that this throws an exception. At least atm. Numeric encoded
fields needs to be targeted by a range query. One could imagine to
transparently
create a range query in this case. I guess by the metadata we could tell
that we have
a numeric field. However, that's a a lot of
in the forum [1] a user runs into a variant of the old problem where
boolean searches on different fields of the elements of an embedded
association return wrong results due to hits in different elements of
the collections.
What is our recommendation/answer to this type of question? I've
Hi,
On Tue, Aug 25, 2015 at 01:33:46PM +0200, Emmanuel Bernard wrote:
I'd like to keep them around
:-) Funny, I thought I was the only one who wants to keep them around.
For me they are kind of part of the project history.
we could avoid the maven fetch dance for
display=false releases.
Hi,
On Tue, Aug 25, 2015 at 12:24:21PM +0200, Gunnar Morling wrote:
Can we delete all the non-displayed release files from
https://github.com/hibernate/hibernate.org/tree/staging/_data/projects
for Search and Validator?
+1 I can take care of this. I noticed the time it takes as well.
I kind
Hi,
actually I was wrong, the fix is trivial. We have all the information to
check whether the release is displayed.
I created a pull request - https://github.com/hibernate/hibernate.org/pull/97
I would have pushed it already, but it seems there is a problem with the
CI environment. I pushed to
On Tue, Aug 25, 2015 at 02:33:41PM +0200, Hardy Ferentschik wrote:
I would have pushed it already, but it seems there is a problem with the
CI environment. I pushed to staging and the build failed due to a missing
Ruby/Rake setup. Not sure whether this is related to the recent changes/
work
Hi,
On Sat, Aug 22, 2015 at 02:22:01PM +, Steve Ebersole wrote:
I went ahead for now with your first (1) option. So for ORM, the left-hand
Documentation link now becomes 3: Documentation (5.0), Documentation
(4.3), Documentation (4.2).
Right, definitely the easiest.
Not ideal long
Hi,
I am not a great expert on the templating side either, but I can tell you how it
is put together atm.
The left hand menu items for the different projects (About, Downloads,
Documentation, etc)
are actually generated from the site config.
If you look into _config/site.yml, you see that
On Thu, Aug 20, 2015 at 08:48:36AM +0200, Gunnar Morling wrote:
Wouldn't a better approach be to either a) run the NoSQL store in
question on another port or b) configure Byteman to use another port?
I guess both options work, but given that ports are anyways configurable in
the OGM build, a)
Hi all,
I just pushed some changes to the hibernate.org site. The changes allow you to
run
the hibernate.org Awestruct environment within a Docker container while still
being able to
make changes locally. The obvious benefit is that in case of environmental
problems
due to native extension
On Tue, Aug 18, 2015 at 08:59:28AM +0200, Gunnar Morling wrote:
One possible workaround is to enforce the indexNullAs value to match the
underlying field type, at the
moment it is always a string.
Interesting idea, but the user would need to provide which value
he's ok to give up, as
Hi,
sorry, I am late to the game, but I here are some more thoughts on this.
I think the consensus so far is that
# Date/time types which represent an instant in time are treated as usual.
They can be string encoded (per default MMddHHmmssSSS) or numerically
in which case the numeric
On Mon, Aug 10, 2015 at 12:34:33PM +0100, Davide D'Alto wrote:
I'm not sure there is an easy way to convert Instant and DateTime to a
numeric value.
The problem is that the resolution for temporal types is nanoseconds, the
following datetime is valid:
year: -999.999.999
month: 12
day: 31
Hi,
Hibernate Validator 5.2.1.Final was just released. Most important
new feature is Java 8 support, but there is more -
http://in.relation.to/2015/07/30/hibernate-validator-521-final/
All artifacts are available in the Maven repositories (JBoss and Maven
Central), but distribution
bundle
Hi,
On Sat, Jul 25, 2015 at 12:11:41AM -0400, Gail Badner wrote:
I am finished with the 4.2.20.Final release, except for uploading
distributions due to problems at SourceForge.
FYI, I am having the same issue. I am waiting for a week now to upload the
Validator release.
Initially, there were
On Fri, Jul 24, 2015 at 09:56:24AM +0200, Emmanuel Bernard wrote:
I have been adding a facet to GridDialect and found it surprisingly hard:
What is a facet in this context. I've seen you guys using this term on IRC as
well,
but I am not sure what you mean with it in relation to a GridDialect.
Hi,
On Mon, Jul 20, 2015 at 05:36:30PM +, Steve Ebersole wrote:
As far as the default type, I don't feel that strongly. Like I said, to
me neither is a really compelling way to map enums; names are only slightly
better that ordinals imo. I am ok with the consistency aspect.
+1 for
On Wed, Jul 08, 2015 at 04:06:42PM +, Steve Ebersole wrote:
I would assume part of that is the Atlassian Connector for IntelliJ that I
use. Which sucks because now I would have to use the non-community version
of the IDE to use tasks stuff.
Out of curiosity, how does everyone else using
On Tue, Jul 07, 2015 at 04:50:36PM -0400, Scott Marlow wrote:
To recreate the WildFly ORM 5 issue on WildFly (if you want to see it
yourself), steps are:
For the record, I see the same test failures locally. I have not looked any
further regarding their cause.
@Scott, on a high level what are
Hi,
http://pastebin.com/4X0h1VPA is the call stack in. We are in the second
bootstrap phase, which is good. The validator factory is passed into the
integration properties but we are only checking the persistence unit
properties in ORM 5. Since we are not looking in the integration
Hi,
The same test works with the WildFly master branch, which is using ORM
4.3.x. The Bean Validation integration code is unchanged in my WildFly
branch, as is the Bean Validator. The only thing different, is the ORM 5
integration code and the ORM 5 persistence provider.
Just fishing here,
On Tue, Jul 07, 2015 at 04:50:36PM -0400, Scott Marlow wrote:
Hardy,
It seems that the ValidatorFactoryBean#createConstraintValidatorFactory is
getting called too late for some reason. http://pastebin.com/WrdD91Hr shows
the call stack for
Hi,
On Wed, Jul 08, 2015 at 07:17:07PM +, Steve Ebersole wrote:
As I said, I had trouble writing this blog in the new asciidoctor stuff. I
had some trouble getting ruby etal set up locally
Can you provide any more info than that? I am happy to help you setting
this up, but I need some
As I said, I had trouble writing this blog in the new asciidoctor stuff. I
had some trouble getting ruby etal set up locally. Sanne had mentioned
that I could just push to staging branch and CI would automatically build
it for me and I could check it that way. Well the CI job clearly saw my
Hi,
This means we might need to drop our Dynamic Analyzer feature:
http://docs.jboss.org/hibernate/search/5.4/reference/en-US/html_single/#_dynamic_analyzer_selection
I think that seems rather harsh.
So, the alternatives I'm seeing:
# Dropping the Dynamic Analyzer feature
# Cheat and
Hi,
On Thu, Jul 02, 2015 at 12:20:46PM +0100, Sanne Grinovero wrote:
Ideally we should provide something similar to the Dynamic Analyzer
feature but which also multiplexes an entity property into multiple
fieldnames;
for example
property title
- title_en analyzer en
- title_de
Hi all,
just a thumbs up that the revamped in.relation.to site is now live!
If you want/need to blog, it is time to read through
http://in.relation.to/README/
In particular you want to setup the site on your local machine
(http://in.relation.to/README/#installation) and once that is done you
On Wed, Jun 17, 2015 at 01:01:43PM +0100, Davide D'Alto wrote:
I've changed the workflow.
@hardy You seem to have the same permisison I have (I just gave a quick
look). Is there something in particular you cannot do?
I think you created a wrong issue which you actually wanted to delete, but
Hi,
it seems thath the worflow for WEBSITE on JIRA does not include the state
PULL REQUEST SENT (like in Search and OGM, for example)
I'd like to have it so that I can have a quick overview from JIRA of the
issues that are almost done.
Would it be ok to add it?
+1 from my side.
While
Hi,
On Fri, Jun 12, 2015 at 07:56:28PM +0100, Sanne Grinovero wrote:
Ok, so the staging website is up and running at:
- http://staging.in.relation.to
[provided you tune your hosts file to have that domain name point to
the same IP as ci.hibernate.org]
Sweet. Works for me.
It takes more
On Fri, Jun 12, 2015 at 02:08:44PM +0100, Sanne Grinovero wrote:
I copied this script from the job which builds www.hibernate.org, but
I guess the incantation needs to be different in this case?
Correct. I think there will be more changes coming, since I am adjusting the
build script. Also as
Hi,
just wondering whether there are reasons or preferences for choosing
GitHub vs CloudFront for hosting the new blog site?
See also https://hibernate.atlassian.net/browse/WEBSITE-311
--Hardy
pgpuY07sIEpoO.pgp
Description: PGP signature
___
On Thu, May 28, 2015 at 11:33:22AM -0500, Steve Ebersole wrote:
Anyone have any input here? Or should I just start scheduling them how I
want?
I think all goals sound good. I would say schedule as you seem fit, maybe
with a focus of giving users something tangible asap (a bit of what Emmanuel
On Thu, May 28, 2015 at 05:28:15PM +0200, Emmanuel Bernard wrote:
On 28 May 2015, at 16:06, Steve Ebersole st...@hibernate.org wrote:
The next gen blog has been coming for years. That's not a dig at
anyone, just a simple point that I'd rather plan based on options I have
today
On Wed, May 27, 2015 at 10:01:51PM -0400, Brett Meyer wrote:
+1 from me. Although, on the other hand, do we really need to keep
maintaining that to begin with? I guess I never thought simply having users
go to the JIRA release notes was a big deal. Just my $.02.
Same for me on both
Hi,
On Wed, May 27, 2015 at 11:34:44PM -0500, Steve Ebersole wrote:
The simplest potentially effects other HCANN consumers, so we'd obviously
all need to agree. Anyway, the simplest approach is to use the ClassLoader
for annotation @interface Class rather than the TCCL. I do not see a
Hi,
Hibernate Validator used initially the same style as ORM. I am saying used
to since the file attached to this url -
http://hibernate.org/validator/contribute/ -
seems to differ a fair bit from the file you are referring to.
A lot of the difference might just be indentation and re-ordering
On Mon, May 18, 2015 at 03:07:08PM -0500, Steve Ebersole wrote:
Hardy, do you happen to still have your sed script for updating these file
headers?
I do, they are attached to the JIRA issue -
https://hibernate.atlassian.net/browse/HV-926.
You will need to adjust them to your needs. I used find
Hi,
In case we are talking about Context.PROVIDER_URL, then this is a
JNDI configuration property. He should be able to set it via hibernate.jndi.url.
--Hardy
On Tue, May 12, 2015 at 10:43:08AM +0100, Sanne Grinovero wrote:
Hi all,
I'm having an interesting conversation on the forums:
-
This might help as well -
https://docs.jboss.org/author/display/WFLY8/JNDI+Reference
On Tue, May 12, 2015 at 01:12:38PM +0200, Hardy Ferentschik wrote:
Hi,
In case we are talking about Context.PROVIDER_URL, then this is a
JNDI configuration property. He should be able to set it via
Hi,
On Wed, May 06, 2015 at 03:16:16PM +0200, Gunnar Morling wrote:
By introducing @UnitOfWork, you forgo all the integration between
application frameworks and transactions. Here you offer a solution for CDI
but we would need one for Java EE non CDI and one for Spring and one for
Grails
Hi,
On Wed, May 06, 2015 at 11:01:29AM +0200, Gunnar Morling wrote:
When talking to people about OGM, there is always that awkward moment when
you need to explain that TX demarcation is required also for
non-transactional data stores.
While it makes sense for our purposes (we use the TX
Hi,
On Wed, May 06, 2015 at 10:13:38AM +0100, Sanne Grinovero wrote:
I do agree with you that it's kind of weird that people write code
without making transactional requirements explicit in the code, but it
seems that the trend is to abstract from that and use the
Transaction term as a Unit
On Tue, May 05, 2015 at 08:36:27AM -0500, Steve Ebersole wrote:
Why? Why even deprecate methods then?
+1
--Hardy
pgplBvr0yyAdf.pgp
Description: PGP signature
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
Hi,
On Mon, May 04, 2015 at 09:11:06AM +0200, Gunnar Morling wrote:
+1 for merging this work and making the changed behaviour very apparent in
the migration notes / announcement.
+1 as well.
As I mentioned on the pull request, this is such a long standing issue and
a topic which we keep
Hi there,
Steve and I are having a discussion around the intended behavior of
EntityManagerFactory#unwrap.
See also HHH-9665[1] and the corresponding pull request [2].
At the moment the implementation in EntityManagerFactoryImpl allows to unwrap
into the implementation
class itself. This way
On Fri, Apr 24, 2015 at 02:20:55PM -0500, Steve Ebersole wrote:
Also I wanted to clarify that, as I told you on IRC, I am fine to change
this expectation if that is the general consensus as long as it is all done
by next Wednesday.
Sure, I got that.
I know that sounds short notice, but in
On Tue, Apr 21, 2015 at 01:09:53PM -0500, Steve Ebersole wrote:
Ok, silence will be taken as a vote to do whatever I feel is best
regardless of impact on these integration impls... So anyone?
Sorry, I forgot about this one. TBH, I have not much useful to say on
what the best way to do this is.
Hi,
I seem to have a odd build problem and wondering whether someone could verify
the problem
or in any ways enlighten me regarding what's going on.
I can build the Validator master branch w/o problem ('mvn clean install'), but
a 'mvn deploy' (SNAPSHOT deploy)
fails (output below). The funny
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
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 conflicting
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
On Tue, Mar 24, 2015 at 08:40:05AM -0500, Steve Ebersole wrote:
AnimalSniffer is causing us a lot of headaches in conjunction with Java 8.
Ahh, right. I forgot about this. I somehow thought that was resolved by now.
Gunnar suggested overriding the ASM version used, but that did not help for
On Wed, Mar 25, 2015 at 12:20:27PM -0500, Steve Ebersole wrote:
I can get behind that.
Anyone else?
+1
--Hardy
pgpsAu_1TGhVe.pgp
Description: PGP signature
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
Hi,
On Sat, Mar 21, 2015 at 10:55:58AM -0500, Steve Ebersole wrote:
For me its a matter of consistency. Put simply a Service comes from a
ServiceRegistry. That's consistent. This idea that some particular
Service might come from here or there or this other place is not
consistent. To me.
Hi,
On Sun, Mar 22, 2015 at 10:11:32PM -0500, Steve Ebersole wrote:
Ran across an interesting proof-of-concept project for setting up a Gradle
build to use multiple JDKs: https://github.com/rwinch/gradle-multi-jdk
Curious what y'all think of this approach versus what we do know with
A few options:
1) Forego OffsetDateTime, OffsetTime and ZonedDateTime support and just
stick with LocalDateTime, LocalDate and LocalTime.
2) Use the timezone/offset to pass along to the driver (for proper
conversion); when reading back we'd have to read back based on the default
timezone.
1 - 100 of 918 matches
Mail list logo
