Open mcovarr opened 7 years ago
@mcovarr has this changed in the last 9 months? It's labeled as AWS but doesn't sound specific to AWS.
Right, it's not specific to AWS. I tried this yesterday hoping it was like that other ticket and had magically been fixed, but now it dies without a stack trace so it's actually a little worse. 😦
As a user running workflows and setting up configs, I want Cromwell to (fail nicely?) when I reference a pluggable backend class that's not on the classpath, so that I can (still run my workflow? get a nice error message?).
@geoffjentry
When Cromwell is pointed to a config referencing a pluggable backend class that's not on the classpath, this is the result: