You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When working in JJava with classes from a Maven projet under construction, i.e. with a SNAPSHOT version, JJava imports the version from ~/.ivy2 directory without refreshing it.
It is very Very VEry VERY confusing 🤪.
It makes deleted classes non existent and new classes unknown to JJava.
Workaround: manually delete outdated versions of the project in the ~/ivy2/cache directory.
I joined a simple 2 classes Maven project to demonstrate the bug. jjava-bug-1.tar.gz
The text was updated successfully, but these errors were encountered:
Yes, working with snapshots is annoying. I am constantly going through a cycle of rm -rf ~/.ivy/cache/org.dflib* / restart the kernel. So fixing this would be great.
Quick check of Ivy docs (and ChatGPT 😎) shows that resolvers can have "changingPattern" and "changingMatcher" attributes, and since JJava configures its own Ivy instance, we should be able to apply them to .*-SNAPSHOT patterns in artifact names.
When working in JJava with classes from a Maven projet under construction, i.e. with a SNAPSHOT version, JJava imports the version from ~/.ivy2 directory without refreshing it.
It is very Very VEry VERY confusing 🤪.
It makes deleted classes non existent and new classes unknown to JJava.
Workaround: manually delete outdated versions of the project in the ~/ivy2/cache directory.
I joined a simple 2 classes Maven project to demonstrate the bug.
jjava-bug-1.tar.gz
The text was updated successfully, but these errors were encountered: