-
Notifications
You must be signed in to change notification settings - Fork 18
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
Version regexp match fails on artifacts with numbers #40
Comments
Bravo. Loading from pom file makes sense. Feel free to create a PR and we'll review it and eventually merge it. Don't forget to implement a unit test as this is testable easily |
@stardust85 thanks for response :) I will try to make my solution more general and make PR with new artifact class. Btw. thanks for this lib. Nexus REST api docs are so messed up, I would spend weeks figuring all of this. I failed on using requests to send POM + Jar in same request and I had to fallback to pycurl - because of not implemented |
Thanks for letting us know you like it and what is your use case :). I created it to make it easier to upload RPM packages to nexus, but it is generally usable of course :) Btw, when I worked on a Java project, I used gradle to upload to nexus. It also works well. And of course supports both jar and pom files. |
@stardust85 unfortunately this case is not simple CI style - |
This regex seems more robust:
I plugged in a semantic-versioning-aware regex in the middle. |
just realized that work is on branch not touched for a while, maybe someone will use it :D https://github.com/alkuzad/repositorytools/tree/pom-artifact |
It's rare but can happen, for example:
https://mvnrepository.com/artifact/org.neo4j/neo4j-cypher-compiler-2.1/2.1.2
Has jar named
neo4j-cypher-compiler-2.1-2.1.2.jar
.I wanted to made PR for that but I couldn't find any naming convention that could specify what is correct jar naming. So I made subclass
LocalArtifactWithPomDetection
which loads this data from pom file, if exists (almost every time, there is one)The text was updated successfully, but these errors were encountered: