Closed mrattfeldt closed 4 years ago
I started a fresh maven project with the following dependencies:
<dependencies>
<dependency>
<groupId>org.choco-solver</groupId>
<artifactId>choco-solver</artifactId>
<version>4.10.4</version>
</dependency>
</dependencies>
added the bunch of code you pasted, and run the following commands:
$ mvn clean install -DskipTests -U
$ java -cp .:/Users/cprudhom/.m2/repository/org/choco-solver/choco-solver/4.10.4/choco-solver-4.10.4-jar-with-dependencies.jar:./target/untitled-1.0-SNAPSHOT.jar Pareto
-U
means that dependencies should be updated (to avoid, in my case, to rely on my repository),
and got this output:
-----------------------------------
W: 75 G:195 L: 45
Strawberry jam: 0
Bananas: 0
Apples: 5
Honey: 5
...
Could double-check your configuration?
--- EDIT --- Ok, I am able to reproduce the bug after purging dependencies.
I must release once again.. Thank for the bug detection btw.
That's the reason why I posted this :
https://github.com/chocoteam/choco-solver/issues/699#issuecomment-688855606
This ensures you have all fresh dependencies. I also wrote in my PR that I was having issues with compilation issues and I could not test my changes because of them.
Also the compilation issue I had should have been fixed if you removed the geost dependency (the one you told me should be removed)
edit : fixed misuses of words.
That will be part of the next release
Expected behavior
No IllegalAccessError should be generated.
Actual behavior
Possible Solution
Possible a JPMS issue. See also https://github.com/chocoteam/choco-solver/issues/699
Steps to Reproduce (for bugs)
The problem is triggered when running the following model (taken from https://www.cosling.com/choco-solver/pareto).
Context
Environment