-
Notifications
You must be signed in to change notification settings - Fork 90
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
invalid version range in java8-and-higher profile #23
Comments
+1 after a complete server rebuild and finding the old imageio is not to be found with maven, I came across this github port.... but now the Java 8 issue is blasting me out of the water.... |
+1 I had the same problem when building it with Maven 2: The fix is very simple - simply add a closing ) in your pom as below:
Some of our projects can't be changed to use later Maven versions yet for various reasons. So could you please fix this ASAP? Many thanks, |
Repair Issue: invalid version range in java8-and-higher profile #23
Thanks to @butchhoward for #25 - sorry for missing this. I will try to make a new release this Easter, meanwhile would any of you care to test the latest |
@stain : Nice to see the fix. When you are planning to release 1.3.2 ? |
Certain versions of maven fail to include this jar as a dependency because they can't parse the version string `[1.8,`. Those builds fail with the following error: ``` Unable to resolve artifact: Unable to get dependency information: Unable to read the metadata file for artifact 'com.github.jai-imageio:jai-imageio-jpeg2000:jar': Invalid JDK version in profile 'java8-and-higher': Unbounded range: [1.8, for project com.github.jai-imageio:jai-imageio-jpeg2000 ``` To fix this I replaced the version string by `[1.8,)`. Note that we also needed to update to jai-image-io version 1.4.0 because 1.3.x contains the same issue. Also see jai-imageio/jai-imageio-core#23
the version range in the java8-and-higher is missing the closing
)
The invalid range may cause issues with certain versions/implementations of Maven.
see also
google/gson#596
deeplearning4j/deeplearning4j-examples#76
The text was updated successfully, but these errors were encountered: