Add test that shows failure of current exports handling

[jcoveney]

No description provided.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please let us know the company's name.

[jcoveney]

Would love to know how to tie this email to stripe's corporate one :) Or since this isn't my corporate email, should I sign one regardless?

[johnynek]

did you not add stripe's email to this account, or do you have two accounts?

[johnynek]

nice. :)

[jcoveney]

I guess I need to add stripe's email to this account

[jcoveney]

BTW, I pushed a fix to this. I tried a couple bigger refactors, but the issue is that... this is really what it seems we want. We don't do anything more fancy with this information, we just don't want to include the ijars -- everything else is there.

I think we should consider a more principled refactor of this, but this fixes the bug... anything bigger imo is trickier than it seems, and I just want to unblock the scrooge work for now

[johnynek]

I think the defensive thing is to move this above line 198. We don't have a test that fails now, but macros should need scala-reflect at compile time (maybe not runtime). It may be that somehow we are putting scala reflect on every classpath elsewhere.