-
Notifications
You must be signed in to change notification settings - Fork 4
Working on POM in SNAPSHOT mode fails to work properly due to .ivy2 cache #55
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
Comments
It might be related to #23 |
Yes, working with snapshots is annoying. I am constantly going through a cycle of 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 |
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: