-
Notifications
You must be signed in to change notification settings - Fork 395
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
Fixes for provided apk dependency for instrumentation tests #671
Conversation
I think this may be specific to JDK 6. As in the problem is there building with jdk 6 |
@psirosky could u look at this real quick? It is a real issue.. I have a couple projects depending on this change. |
I am happy to merge this. Ideally with some feedback from @psorobka and cut a new release soon.. |
@psorobka Can I get some feedback please? Thanks in advance. |
I'm sorry but I have no idea what is this about. |
There are 2 bugs this solves:
|
-add dummy ZipEntry to apk placeholder. to avoid "0 entries" exception -Changed system dependency to use BaseVersion for snapshot versions. I had issue where the ClasspathModifierLifecycleParticipent used the full snapshot version with timestamp for the placeholder and system dependency. But the GenerateSourcesMojo used the SNAPSHOT version without timestamp, resulting in compilation errors.
@psorobka do you have a better idea of whats it's about? |
@mosabua can you look at this? I promise it is 2 real bugs. |
Let me do that tonight.. |
I will try to release something soon |
Fixes for provided apk dependency for instrumentation tests
Do we have any filed issues that this closes? |
I never created an issue.. just the PR |
-add dummy ZipEntry to apk placeholder. to avoid "0 entries" exception.
-Changed system dependency to use BaseVersion for snapshot versions.
I had issue where the ClasspathModifierLifecycleParticipent used the
full snapshot version with timestamp for the placeholder and system dependency.
But the GenerateSourcesMojo used the SNAPSHOT version without timestamp, resulting in compilation errors. Because actual apk classes.jar wasn't getting added to the classpath.
Note: I experience these problems specifically when there wasn't any artifacts in the local repo. I was doing a verify on an aggregator project, which had both the apk and test projects as modules. So the apk had to come from the previous build, instead of the maven repo. I think this had something to do with the problem. I verified that now it consistently works.