SpriMoon / alloy4eclipse

Automatically exported from code.google.com/p/alloy4eclipse
0 stars 0 forks source link

Uses the version of SAT4J that ships with Eclipse instead of the one that ships with A4 #87

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Since Sat4j is not shipping with Eclipse since release 3.4, and the solvers are 
improved regularly, it should be better to rely directly on the version of 
Sat4j that ships with Eclipse instead of the one included in A4.

I did a first trial by adding a dependency to org.sat4j.core to the launch 
plugin and by replacing the alloy4.jar file by the one in attachment.

It works if the solver is run locally. It does not work when the solver is run 
on another thread, since we add directly the alloy4.jar in the classpath in the 
class ExecutableCommand.

That feature should prove an improvement for A4E users relying on Sat4j. 
However, it might be a problem for debugging purposes since we would be out of 
sync with official A4 releases.

Original issue reported on code.google.com by daniel.l...@gmail.com on 14 Nov 2010 at 9:30

Attachments:

GoogleCodeExporter commented 9 years ago
First trial in r884.

Original comment by vasseur....@gmail.com on 4 Apr 2011 at 12:32

GoogleCodeExporter commented 9 years ago
This is the case in the current xtext feature.

Original comment by daniel.l...@gmail.com on 15 Apr 2011 at 8:17