-
-
Notifications
You must be signed in to change notification settings - Fork 213
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
Config.Sources with ~ doesn't create a valid URI on Windows #123
Comments
Thanks for the bug report. I'll verify it soon and fix it asap. |
I think it's fixed on master branch. I packaged a zip file for your convenience if you would like to test it. |
Awesome! I will test it in a few hours and give you feedback - but looking at your commit, it seems to solve the issue. When are you planning to release 1.0.9? Of course, I would prefer to just use it as a Maven dependency - if you want to wait with 1.0.9, which is fine, I can add the custom build from master branch as well. |
Asap (release). I wish I had more time to do more development on this library, but since I got hired in a company my free time is reduced. |
I deployed latest snapshot on this repo: https://oss.sonatype.org/content/repositories/snapshots/ Eventually you can configure your project to use the snapshot repository until next release. Here you could find some help, eventually: http://stackoverflow.com/questions/7715321/how-to-download-snapshot-version-from-maven-snapshot-repository I am not familiar with this, but you can try and see if this works for you. |
You did a great job already! Thanks for your support. I just tested the snapshot, with success. |
Today I release OWNER 1.0.9. Sorry for the long delay. |
Just to confirm: I stumbled over this same issue on windows. Using the latest version 1.0.9 solves it. |
If you execute the following simple example on Windows, you will see an URISyntaxException when creating the Config.
The problem is that
System.getProperty("user.home")
returns a path sepererated by backslashes on Windows, which isn't allowed in URIs.There is quite a simple (but ugly) workaround available - just replacing backward- with forward slashes in
${sys:user.home}
Am I overlooking something, or do I really have to tinker with system properties to use ~ expansion in
Sources
on Windows, like I did in the commented line inmain
?If somebody confirms this bug, I'll try to create a pull request for it.
The text was updated successfully, but these errors were encountered: