-
Notifications
You must be signed in to change notification settings - Fork 27
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.
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
Need MySQL 5.7.16 package for JCABI #84
Comments
We did some more investigation of MySQL 5.7.14/16 on Windows Box and below are our findings: 1). In the etc\hosts file I have the entry: 3.204.166.180 [the hostname of my machine] 2). Then when I run the 'maven install' command at the target --> --- jcabi-mysql-maven-plugin:1.0r2:start (mysql-test) @ InMemDb --- At the line it throws following error:: 3). When I run the same command through Command Prompt, with hostname as the name of my machine it works fine. it says: The usage of 127.0.0.1 is hardcoded in the the jcabi-mysql-maven-plugin. Probably can we change it with usage of hostname -- or something that works. I have tried many other things like: bind-adrress setting, host file keeping 127.x.x.x entry --- but none of them worked. Request an early response. In the https://github.com/jcabi/jcabi-mysql-maven-plugin/blob/cf29b4469634c5ac70365ef0ca043292242d8a0c/src/main/java/com/jcabi/mysql/maven/plugin/Instances.java the 127.x ip is hardcoded. Instead we can use: InetAddress.getLocalHost().getHostName() |
@shrutiujjwal thanks for reporting it |
@amihaiemil it's yours, please help |
@shrutiujjwal Is this still urgent? Unfortunately, I don't have time to take care of it this week, only next one (I'm on the road all week). Should I let it to someone else? Many thanks and sorry for the inconvenience! |
For now since we wanted to quickly unblock our test team, we have handled the MySQL 5.7.x installation procedure in our codebase. Pls do give the fix at your earliest convenience, so that we can move on to that. Steps that we coded for:
|
@shrutiujjwal I see. Please don't turn off notifications from this issue, as I might be asking some questions later when I take on this. Also, in the end, you should be the one to close this ticket (that's part of our work model). Many thanks again, |
Sure Mihai. |
@dmarkov need more time pls. Will take it up this week. |
@amihaiemil sure, thanks for telling me, take your time |
@dmarkov Assign someone else pls - no more time :( |
Any updates on this issue resolution? |
@shrutiujjwal I caught some time to look more into it now, and as I understand you need a ZIP archive with However, I'm not sure how to create and publish such an archive - from what I know zip archives used in pom.xml also need to contain some metadata for maven but I might be wrong (I didn't work on this project before) Maybe @yegor256 knows? |
@yegor256: Your inputs be helpful? Any timelines we are looking at providing this support? |
@amihaiemil 30 points deducted from your rating |
@amihaiemil OK, I will try to assign someone else |
Hello, Did this ever happen? If not can someone suggest any alternative to test using mysql 5.7? @dmarkov |
@shrimalmadhur There is no one maintaining the project at the moment, unfortunately. However, if you have the time and want to submit a Pull Request with the solution, we'll be grateful! Don't talk to dmarkov, he is a chatbot so he won't reply to you :) |
Thanks @amihaiemil for update. I didn't realize he is a chatbot. I will try if I can when I have some free cycles. Thanks. |
Need MySQL 5.7.16 package for JCABI (on Windows OS). Running into many issues while generating it. Will appreciate if you could provide the same at the earliest as my test team is blocked with pre-integration test. We basically want to use the MySQL JSON data saving/retrieval feature of 5.7.* in using in-memory capability.
Please note that when I try using MySQL 5.7.14 (on Windows) that Mike has provided it gives following error:
When i use 5.6.14, the all works fine.
ErrorLog.txt
Need to get this adddressed asap. Any help / inputs will be appreciated.
The text was updated successfully, but these errors were encountered: