Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

HRCPP-275 javascript now uses the namedCache #223

Closed
wants to merge 1 commit into from
Closed

HRCPP-275 javascript now uses the namedCache #223

wants to merge 1 commit into from

Conversation

rigazilla
Copy link
Contributor

Since 9.0.0.Alpha2 server forbids the use of unnamed cache to js.

@rigazilla rigazilla force-pushed the HRCPP-275/js_use_named_cache branch from 04a47dd to 2547ae7 Compare June 13, 2016 09:01
@infinispanrelease
Copy link

SUCCESS - TeamCity HotRod C++ Client :: Pull requests monitor - RHEL Build 624 for 2547ae7
Tests: 0, 0 failed (0 new), 0 ignored. Build time: 00:08:25

@infinispanrelease
Copy link

SUCCESS - TeamCity HotRod C++ Client :: Pull requests monitor - WIN_S2012 Build 477 for 2547ae7
Tests: 0, 0 failed (0 new), 0 ignored. Build time: 00:34:23

@rigazilla rigazilla changed the title HRCPP-275 javascript now uses the default cache HRCPP-275 javascript now uses the namedCache Jun 15, 2016
@tristantarrant
Copy link
Member

Pushed to master, thanks

@infinispanrelease
Copy link

SUCCESS - TeamCity HotRod C++ Client :: Pull requests monitor - RHEL Build 631 for 2547ae7
Tests: 0, 0 failed (0 new), 0 ignored. Build time: 00:05:55

@infinispanrelease
Copy link

FAILURE - TeamCity HotRod C++ Client :: Pull requests monitor - WIN_S2012 Build 492 for 2547ae7
Tests: 0, 0 failed (0 new), 0 ignored. Build time: 00:14:54

Process exited with code 255

@rigazilla rigazilla deleted the HRCPP-275/js_use_named_cache branch October 12, 2017 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@rigazilla @infinispanrelease @tristantarrant