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

Execution of JApiCmp failed: Optional.get() with 0.7.1 and 0.7.2 #130

Closed
ccz99 opened this issue Mar 29, 2016 · 1 comment
Closed

Execution of JApiCmp failed: Optional.get() with 0.7.1 and 0.7.2 #130

ccz99 opened this issue Mar 29, 2016 · 1 comment

Comments

@ccz99
Copy link

ccz99 commented Mar 29, 2016

I hit the below exception with 0.7.1 and 0.7.2. But there is no issue with 0.7.0. So a regression should be introduced here.

Execution of JApiCmp failed: Optional.get() cannot be called on an absent value
java.lang.IllegalStateException: Optional.get() cannot be called on an absent value
at com.google.common.base.Absent.get(Absent.java:47)
at japicmp.model.JApiException.isCheckedException(JApiException.java:25)
at japicmp.model.JApiException.(JApiException.java:18)
at japicmp.model.JApiBehavior.computeExceptionChanges(JApiBehavior.java:66)
at japicmp.model.JApiBehavior.(JApiBehavior.java:53)
at japicmp.model.JApiMethod.(JApiMethod.java:17)
at japicmp.model.JApiClass.sortMethodsIntoLists(JApiClass.java:329)
at japicmp.model.JApiClass.computeMethodChanges(JApiClass.java:304)
at japicmp.model.JApiClass.(JApiClass.java:51)
at japicmp.cmp.ClassesComparator.sortIntoLists(ClassesComparator.java:50)
at japicmp.cmp.ClassesComparator.compare(ClassesComparator.java:30)
at japicmp.cmp.JarArchiveComparator.compareClassLists(JarArchiveComparator.java:183)
at japicmp.cmp.JarArchiveComparator.createAndCompareClassLists(JarArchiveComparator.java:161)
at japicmp.cmp.JarArchiveComparator.compare(JarArchiveComparator.java:72)
at japicmp.cli.JApiCli$Compare.run(JApiCli.java:74)
at japicmp.JApiCmp.main(JApiCmp.java:16)

@siom79
Copy link
Owner

siom79 commented Mar 29, 2016

Since 0.7.1 exceptions are loaded from the classpath. If this fails, you currently see the above error message. Improved this on the develop branch.

@siom79 siom79 closed this as completed Mar 29, 2016
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