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
I am kind of a fan of Docker but I am wondering whether we need for AMIE since we are using Maven. The only difficulty I encountered in the current setting comes from the fact that Javatools is not integrated in AMIE (and is not automatically installable). Could you please elaborate on the advantages of testing AMIE in a Docker environment?
As you said, my first motivation to create this issue was to be able to test the code easily, and the javatools dependency was my first issue while testing.
I would like to add more advantages :
Debugging (critical), an issue might be linked to a java version, jvm version or even a local operating system issue. Moreover, settings the environment parameter allows a better collaboration; I can work on a linux or windows based computer and be sure that it does not affect the contribution quality.
Build and run latest AMIE anywhere (nice to have), non-java user might want to have the latest version of amie without the hassle to install java lib and tools .
CD/CI flexibility (nice to have) , In issue Configure abstruse ci #62 , I have proposed abstruse CI, which is self-hosted, if it does not work, other ci can use this configuration.
Help for issue Simple GUI for AMIE #60 (nice to have), one common practice is to declare the gui service in a docker file to launch both the gui and amie.
Status :
Installing Dependencies can be tricky (see issues #2 #38 )
Proposal :
Having a dockerfile + command to execute AMIE tests
The text was updated successfully, but these errors were encountered: