I think it's important to clarify the problem that you encountered here so that someone who encounters something similar will be able to get a better understanding of the issue.
To summarize, you created a custom osgi bundle with a new service based on WCMCommand
The error you received:
java.lang.VerifyError: Expecting a stackmap frame at branch target 13 in method
pack.age.name.unbindRepo(Lorg/apache/sling/jcr/api/SlingRepository;)V
Is saying that when Java 7 attempts to validate the signature of your method. It's encountering an error. This only occurs in Java7 as Oracle increased the level of validation that occurs. The error that is occuring is in the method signature:
unbindRepo(SlingRepository repo);
If you look at your java class you'll notice that method doesn't exist. The reason it doesn't exist is that it is created for you when you use the Apache Sling @Reference annotation. So there is a good change that in your code you have the following line.
@Reference
private SlingRepository repo;
Which, when compiling, creates the bind and unbind methods for that attribute. When you created a new method manually for the unbind with no arguments you are circumventing the frameworks process. What impact that has in the long term is hard to determine but is certainly not good practice if you don't know what's required to unbind the object in the first place.
To correct your problem I would confirm that you have a signature for the repo object is as I described, and that your aren't using something like.
@Reference
private Repository repo;
If you continue to have problems with this I would consider approaching the Apache Sling people with this issue as it's a potential problem with Annotation process.
Additionally to answer specifically your question on how to do set -XX:-UseSplitVerifier my answer is you don't. The problem is in the code that you created, you need to fix that, and Oracle is in the process of removing that parameter, so that it may not even work.