Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IllegalArgumentException in AdrToolsImporter while parsing DecisionStatus #108

Closed
mcbeelen opened this issue Oct 16, 2018 · 5 comments
Closed

Comments

@mcbeelen
Copy link
Contributor

mcbeelen commented Oct 16, 2018

We have an application, which generates the diagrams, populates the documentation and parses the ADRs. When I run locally everything works fine, but when it runs on our build-server or at a co-workers computer. the application fails due to a IllegalArgumentException.

Caused by: java.lang.IllegalArgumentException: No enum constant com.structurizr.documentation.DecisionStatus.
 	at java.lang.Enum.valueOf(Enum.java:238)
 	at com.structurizr.documentation.DecisionStatus.valueOf(DecisionStatus.java:6)
 	at com.structurizr.documentation.AdrToolsImporter.extractStatus(AdrToolsImporter.java:142)
        at com.structurizr.documentation.AdrToolsImporter.importArchitectureDecisionRecords(AdrToolsImporte/.java:83)

Based upon the stacktrace I concluded that actual name of the DecisionStatus does not get returned from the statusRegex matcher.group(1). I assume it return an emptyString.

The most apparent difference is that I use a Mac and the build-server and my co-worker run Windows as the OS. I will try to troubleshoot this some further.

Using: Structurizr 1.0.0-RC7

@simonbrowndotje
Copy link
Contributor

I imagine it's related to this -> 491753f

@simonbrowndotje
Copy link
Contributor

v1.0.0 is just releasing to Maven Central, so hopefully upgrading will fix your problem.

@mcbeelen
Copy link
Contributor Author

I will check with v1.0.0, but I got the impression that 491753f already was in 1.0.0-RC7

@simonbrowndotje
Copy link
Contributor

I don't think so -> 1.0.0-RC7...master

@mcbeelen
Copy link
Contributor Author

@simonbrowndotje : You are right.
The problem does not occur anymore after the upgrade to 1.0.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants