Hello,
What about backporting the JCache module?
Since JCache is Java 1.6, that could make it available to more users.
I believe there have been small API changes between 5.1 and 5.2 but still
the porting should be easy enough and I am willing to help for that.
Regards,
Louis
On Tue, Jun 7, 2016
Hi,
Because 5.1 is the last version supporting 1.6, I think it's worth to
integrate as many fixes as we can that are now only available on the 5.2
branch.
Therefore, I collected a list of issues so that you can tell me which ones
you'd like me to cherry pick on 5.1:
https://hibernate.atlassian.n
We really no longer maintain ORM 4.x. Yet we still get Jira reports citing
4.x as the affected version. We have been asking the reporter to reproduce
with 5.0.
But in the interim it is easy to lose track of these issues. Ultimately
the "affects version" needs to be updated or the issue rejected
On Mon, Mar 09, 2015 at 09:26:34PM -0500, Steve Ebersole wrote:
> I tried using the feedback approach with Atlassian, lets see how that goes
> and whether we hear back. If I don't hear back in a few days, I will reach
> out to them directly.
+1 I guess this is related to their latest changes. May
I tried using the feedback approach with Atlassian, lets see how that goes
and whether we hear back. If I don't hear back in a few days, I will reach
out to them directly.
On Mon, Mar 9, 2015 at 5:35 PM, Steve Ebersole wrote:
> Ok, if I log out I get the same. We'll have to reach out to Atla
Ok, if I log out I get the same. We'll have to reach out to Atlassian
about this. Or maybe there is a setting as to whether this should be
publicly available.
On Mon, Mar 9, 2015 at 5:29 PM, Hardy Ferentschik
wrote:
> On Mon, Mar 09, 2015 at 05:13:14PM -0500, Steve Ebersole wrote:
> > Interest
On Mon, Mar 09, 2015 at 05:13:14PM -0500, Steve Ebersole wrote:
> Interesting. I can get to that link from your email (just clicked it) just
> fine.
Turns out, I can get to these links as well - provided I am logged in.
I think my session must had expired and I was not logged in when I tried.
I
Interesting. I can get to that link from your email (just clicked it) just
fine.
On Mon, Mar 9, 2015 at 4:52 PM, Hardy Ferentschik
wrote:
> Hi,
>
> I seem to have problems with Jira atm. If I select a link which refers to
> a specific version
> (eg https://hibernate.atlassian.net/projects/OGM/v
Hi,
I seem to have problems with Jira atm. If I select a link which refers to a
specific version
(eg https://hibernate.atlassian.net/projects/OGM/versions/19251), I keep
getting a 500 error
with the message "Sorry, we had some technical problems during your last
operation."
It does not seem to
On the admin side it also gives you many more options over what gets
emailed (what kind of events) and to whom.
On Wed 23 May 2012 11:50:29 AM CDT, Emmanuel Bernard wrote:
> Email notifications are indeed much better and faster to open.
>
> On 23 mai 2012, at 12:39, Hardy Ferentschik wrote:
>
>>
Email notifications are indeed much better and faster to open.
On 23 mai 2012, at 12:39, Hardy Ferentschik wrote:
> Now that the upgrade hiccups are mostly sorted out I have to say I like the
> new version.
> The integration with fisheye is now much better and I especially like the new
> email
Now that the upgrade hiccups are mostly sorted out I have to say I like the new
version.
The integration with fisheye is now much better and I especially like the new
email notifications. Sweet!
--Hardy
On May 22, 2012, at 7:43 PM, Steve Ebersole wrote:
> I have received the updated plugin fr
I think we have FishEye integration working again. Let me know if you
see problems with FishEye intg.
We will have to see about GitHub connector later.
On Tue 22 May 2012 02:46:39 PM CDT, Steve Ebersole wrote:
> Ok, we got the JBoss plugin installed and re-enabled and everything
> with pull req
Ok, we got the JBoss plugin installed and re-enabled and everything
with pull request fields looked good to me.
There is a problem with it connecting to FishEye (Source tab) at the
moment. They are also investigating whether the GitHub connector might
work now after upgrading.
On Tue 22 May
I have received the updated plugin from JBoss and have passed it along
to Atlassian. They will need to restart the instance at some point for
it to be picked up.
After that we will see what we need to do to get the pull request fields
showing up again.
On 05/21/2012 05:50 PM, Steve Ebersole
49 ?
I m so sorry :s
Niko
2012/5/22 Steve Ebersole
> ok, i am going to disable the custom plugin for now...
>
>
>
> On Mon 21 May 2012 05:42:05 PM CDT, Sanne Grinovero wrote:
>
>> Nicolas,
>> it seems you opened 49 duplicate issues on HSEARCH; I can't blame you,
>> I guess you were clicking an
ok, i am going to disable the custom plugin for now...
On Mon 21 May 2012 05:42:05 PM CDT, Sanne Grinovero wrote:
> Nicolas,
> it seems you opened 49 duplicate issues on HSEARCH; I can't blame you,
> I guess you were clicking and debugging while attempting to create
> "HSEARCH-1131 Implement the
Nicolas,
it seems you opened 49 duplicate issues on HSEARCH; I can't blame you,
I guess you were clicking and debugging while attempting to create
"HSEARCH-1131 Implement the programatic API for @Spatial "
I tried to bulk-close them as duplicate, but the TOKENIZED problem
resulted me in blowing up
All of the remaining issues with the JIRA instance seem to be related
to that custom field. The custom field is used for associating pull
requests with the issue.
JBoss is planning the same upgrade, so they are planning on working on
getting that plugin upgraded. I spoke with the developer an
We even know what it means ;)
It's a constant from Lucene, most notably older JIRA was using this
very old Lucene version which still had the old name; looks like they
finally upgraded Lucene in JIRA 5, but the version of Lucene being
used now breaks the custom field type for pull requests.
Basical
Ah, ok.
On Mon 21 May 2012 09:29:02 AM CDT, Nicolas Helleringer wrote:
> Since this morning I am trying to create sub task to HSEARCH-923 and
> when I click More Actions=>Create Sub tasks it open a modal box.
> The create button of that dialog do an ajax call that I spied in
> Chrome integrated de
Since this morning I am trying to create sub task to HSEARCH-923 and when I
click More Actions=>Create Sub tasks it open a modal box.
The create button of that dialog do an ajax call that I spied in Chrome
integrated dev tools (should be the same with FireBug in FireFox).
I catched there the respon
Nicolas, where did you see this stack trace? When I try to create an
issue, it just sits on that create screen...
On 05/21/2012 08:46 AM, Nicolas Helleringer wrote:
> When I try to create a sub task issue I got the following :
>
>>>
>
> [image: Hibernate JIRA]
> Not Found (404)
> Could not
I even don't see there is a "Resolve" Button
On May 21, 2012, at 9:36 PM, Sanne Grinovero wrote:
> I can't resolve them :/
>
> Anybody able to click "resolve" on
> https://hibernate.onjira.com/browse/OGM-183 ?
>
> I just looked at permissions, and all seems right.. but I likely
> missed somet
When I try to create a sub task issue I got the following :
>>
[image: Hibernate JIRA]
Not Found (404)
Could not execute action
[QuickCreateIssue]:TOKENIZEDjava.lang.NoSuchFieldError:
TOKENIZED at
org.jboss.labs.jira.plugin.custfieldtypes.searchimpl.MultiURLCustomFieldIndexer.addDocumentFiel
On May 21, 2012, at 3:36 PM, Sanne Grinovero wrote:
> I can't resolve them :/
>
> Anybody able to click "resolve" on
> https://hibernate.onjira.com/browse/OGM-183 ?
not me :-(
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lis
I can't resolve them :/
Anybody able to click "resolve" on https://hibernate.onjira.com/browse/OGM-183 ?
I just looked at permissions, and all seems right.. but I likely
missed something.
On 21 May 2012 14:21, Steve Ebersole wrote:
> I do not experience a problem creating issues at all, so cann
I do not experience a problem creating issues at all, so cannot say.
On Mon 21 May 2012 03:19:25 AM CDT, Strong Liu wrote:
> yeah, just send out another email about this to the hibernate-all, and
> another big issue is I can't create new jira.
>
> On May 19, 2012, at 10:45 PM, Steve Ebersole wrote
yeah, just send out another email about this to the hibernate-all, and another
big issue is I can't create new jira.
On May 19, 2012, at 10:45 PM, Steve Ebersole wrote:
> They are still there as far as I can see. If you go to the direct URL
> you can see them. But there is something funky abo
They are still there as far as I can see. If you go to the direct URL
you can see them. But there is something funky about searches and
other bulk views of issues.
I have told Atlassian. We just have to wait to hear back.
On Sat 19 May 2012 07:36:46 AM CDT, Hardy Ferentschik wrote:
> Hi,
>
>
Hi,
what's up with https://hibernate.onjira.com?
There projects are there, but no issues? I think we were going to upgrade Jira
version, right?
Are we still in some sort of intermediate state or what is going on?
--Hardy
___
hibernate-dev mailing list
We are planning to release Hibernate core 3.5.4 on Wednesday next week
(7/21/10).
If you are working on issues for 3.5.4, then please change the fix
version from 3.5.x to 3.5.4.
If your fix is relevant to both Branch_3_5 and trunk (3.6), then please
commit your fix to both branches and make su
We are planning to release Hibernate core 3.5.3 on Wednesday this week
(6/16/10).
If you are working on issues for 3.5.3, then please change the fix
version from 3.5.x to 3.5.3.
If your fix is relevant to both Branch_3_5 and trunk (3.6), then please
commit your fix to both branches and make su
33 matches
Mail list logo
