-
Notifications
You must be signed in to change notification settings - Fork 741
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
mvn test fails to start on HEAD #415
Comments
Not sure what's going on, but "mvn test" does work for me, so I'm inclined to believe there's some local maven repo corruption on your side, maybe Maven version problem on Windows, or something like that. It's been a while since this error is reported. Is this still a problem? |
Which branch and tag works for you? What's your build environment? Why would you think this is windows specific or related to maven repository corruption? Is there a history of such problems on this project? |
Just pulled from upstream and tried again. Still a problem. Almost exactly the same exception too. I'm happy to debug, but is there any chance you could offer ANY insight into why I'd be getting a classpath exception in a maven project? That's usually sign of something unusual in code generation or non-compile scoped dependencies. Since there's a bridge method generator plugin I'm inclined to wonder if it's related. |
Perhaps you could share your own maven version for reference so I can try duplicating that? |
I have no reasons to suspect this to be a Windows specific issue, and there's no history of such problems on this project. I guess I just wanted this problem to go away, and I'm sorry if that annoyed you. It's just that the problem is really odd. The entire jgit is one jar AFAICT, so there cannot be a kind of version mismatch problem within different jars of the same library. The version of jgit used does contain So the only thing I can think of is that somehow surefire is not setting up the classpath correctly, and that happens outside the code in this library. My suggestion is to enable the debug switch on Maven to observe the classpath it's setting up, and to |
Yeah... That's why I'm up to now... |
By the way my environment:
|
Sorry I got grumpy, 6mo was a long wait. I don't blame you for wanting it to go away! Me too! Looks like your guess was good. Forcing a rebuild shows some weird warnings (why not errors, maven, seriously?) about stapler. I deleted that entry from the maven cache and things are at least running. How in the HECK did you guess that? I've never seen a corrupt JAR in the maven cache before... Not that I fully understand their SHA1 sum mechanism, but apparently it aint good enough. That'll be a problem for another day. I was on the wrong track completely with bridge methods. I tried getting Eclipse to help debug this a bit, but the m2e integration doesn't support that plugin. Red herring, my mistake. For now, thank you so much sticking with me, and for the excellent guess. I'll wonder more about maven cache corruption in the future, with classpath errors. |
If I checkout
192e21a9fcacf4dffc975156bcf5e8ff7bf297b1
(HEAD right now), and runmvn test
I see aClassNotFoundException
. It cannot even report success or failure of individual tests.I believe this is related to #388 which upgraded jgit, but maybe not all of the unit tests. Specifically
LifecycleTest
referencesUsernamePasswordCredentialsProvider
which is no longer in the newer versions of jgit.I'll be honest, as I tried to fix this I kept getting some unexpected classpath errors related to jgit (first this one, then one about
GitAPIException
, etc), and much as I know my way around a super complex build, I didn't feel like learning about the maven plugin for bridge method generation, and everything else it might take me to sort this out. Is there something basic I missed for setting up a working development environment for this project? I feel like I must have missed something simple formvn test
not to work.The surefire log shows:
Maven version:
The text was updated successfully, but these errors were encountered: