-
Notifications
You must be signed in to change notification settings - Fork 46
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
Ability to specify the artifact to compare to in a generic way a the top level POM #23
Comments
…nt and simpler setup of old and new versions in case of checking just the current artifact #25 Don't perform analysis on projects with non-file artifacts - like the ones with pom packaging. Additionally don't WARN on missing config files, if not configured to right out fail on their absence.
I've added This is going to be present in |
That's very cool, thanks! |
hmm I've tried it and I can't make it work. I have:
I see in eb7d36d that this should work but it doesn't and when I run revapi, it says it's comparing to version 6.4.8 (it should be 8.0 since that's the value of Any idea? Thanks |
Have you built the maven plugin from source? I see you are using revapi-maven-plugin-0.4.3 in you snippet above, but this will be available only in 0.4.4 that I haven't released yet... |
oh my bad... I was using version 0.4.2 and upgraded to 0.4.3, without realizing that the change was in 0.4.4, sorry for the false alarm. Eagerly waiting for 0.4.4 to be released then :) |
This should be present in |
It's almost possible with:
However this will fail for example if the packaging is of type "maven-archetype" (this packaging produces jar files). Right now this forces to override the config in each module having a packaging type that doesn't result in an artifact extension named after the packaging name.
The text was updated successfully, but these errors were encountered: