-
Notifications
You must be signed in to change notification settings - Fork 161
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
Version RELEASE is incorrectly transformed when the gradle project is created #1777
Comments
Probably here: jbang/src/main/java/dev/jbang/cli/Edit.java Lines 454 to 468 in 826755c
Just before Let me know what you think. |
Hmm. Wasn't aware of gradles latest. Notion. Make sense todo or actually natively support gradles notion. |
@maxandersen If I want to contribute this to jbang, where should the translation between maven |
I would start with the place you pointed out in edit as no other place this would be needed afaics. |
Describe the bug
When the latest version is used with
RELEASE
(to get the latest version of a dependency) thebuild.gradle
file created byjbang edit -b
is incorrect.To Reproduce
Hello.java
file used to reproduce it:Run
jbang edit -b Hello.java
In the generated file
~/.jbang/cache/projects/Hello.java_jbang_<hash>/Hello/build.gradle
the dependency is marked as:Complete generated build.gradle file
Which prevent the project to work well in the IDE.
If you do a
gradle run
in the mentioned folder, it is failing complaining that the dependencych.qos.reload4j:reload4j:RELEASE
can't be found.Error log
Expected behavior
The notation
'ch.qos.reload4j:reload4j:RELEASE'
is wrong. It should be'ch.qos.reload4j:reload4j:latest.release'
See: https://docs.gradle.org/current/userguide/single_versions.html
JBang version
Tested with
jbang version 0.115.0
The text was updated successfully, but these errors were encountered: