-
Notifications
You must be signed in to change notification settings - Fork 15
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
SNAPSHOT releases should be optional #26
Comments
@MahatmaFatalError agreed, let me take a look on this. |
Thanks for fixing. Is there a plan for the 2.0.0 release? Maybe SNAPSHOT? |
@MahatmaFatalError plan is there but I dont have an exact date yet, most probably it will happen in the upcoming 2 weeks or so. In the meantime you can give it a try with the snapshot version. In case you are looking for a CLI, you can do a build yourself from master. |
I build master locally via
BTW, why is |
@MahatmaFatalError Making either of those 2 options optional was on the table already, didn't have the time to do so until now. I just pushed a new commit. Please try that and let me know if it works. |
I tried with the lastest commit and omitting the snapshot repo uri and got:
However, I think this issue is not related to the new code changes but rather on our infrastructure where the jar containing the swagger is packed in a mtar file. |
@MahatmaFatalError the implementation had a bug. Please check out the latest commit and let me know how it goes. :-) |
We don't have any snapshot releases on our nexus.
That leads to this exception (with the maven plugin):
It tries to get
maven-metadata.xml
within a version subfolder, however, there is none. There is only one in the top directory.So the LatestSnapshotNameResolver should not stop the entire process.
swagger-brake/swagger-brake/src/main/java/io/redskap/swagger/brake/maven/maven2/LatestSnapshotNameResolver.java
Line 14 in 9836b8e
The text was updated successfully, but these errors were encountered: