OMG! found my issue and boy do I feel stupid! I thought the plugin was crashing which was why I wasn't seeing connection attempts to my radius server...them maybe I thought it was my properties ...so I check them against what I found in the jira and it looked right...radius-server: xxx.xxx.xxx.xxx...then I figured I would look through the code and to my surprise the property name that I should have been using is radius-hostname. Still feeling dumb! I'm so sorry that I've wasted your time, but that you for trying to help me!
On Sun, Dec 2, 2018 at 3:51 PM Not Speedy <notspeed...@gmail.com> wrote: > afraid not. With your branch and with the updated pom.xml, I still got > the version mismatch..looking at the dependacies, it still pulled down > 1.5.8. no joy. For fun, I built jradius 1.1.6 snapshot using the > 1.7.7..that more or less got rid of my version mismatch error, but still no > luck on getting the radius plugin to work on my end. > > On Sun, Dec 2, 2018 at 3:37 PM Nick Couchman <vn...@apache.org> wrote: > >> On Sun, Dec 2, 2018 at 4:32 PM Not Speedy <notspeed...@gmail.com> wrote: >> >>> Thanks Nick. For whatever reason I still can't get this to work. Its >>> likely an issue on my end. Are there any nightly builds I could try? >>> Otherwise, It looks like I'll have to wait until the 1.0.0 >>> beta/rc/release.... thanks again for your time. >>> >>>> >>>> >> You can try this branch: >> https://github.com/necouchman/guacamole-client/tree/jira/670 >> >> It has the changes necessary to force loading a specific version of >> slf4j. Be very interested to see if it works for you. >> >> -Nick >> >
