The root cause it that AMASE registers its own rerun handler at the command id for the AGREE rerun handler resulting in a conflicting handlers being registered at the same id.
AMASE should be modified to use its own rerun handler command id. Further, since it now has its own results view, the enabling and disabling of this should appeal to the AMASE results view rather than the AGREE results view.
Pull request #17 resolves the illegal state exception. However, AMASE does not consistently apply command ids and the safety results view across analyses. Issue #18 has been opened to address this.
This issue was spawned by AGREE issue #81.
The root cause it that AMASE registers its own rerun handler at the command id for the AGREE rerun handler resulting in a conflicting handlers being registered at the same id.
AMASE should be modified to use its own rerun handler command id. Further, since it now has its own results view, the enabling and disabling of this should appeal to the AMASE results view rather than the AGREE results view.