Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Maven deploy support incomplete?
-
Hello everyone,
we use ProGet as our internal NuGet server and have been very happy with it so far. Since we recently also started up a few small Java projects in the team we decided to give ProGet's Maven support a try.
Unfortunately, we've been running into quite a few issues with pushing artifacts to ProGet using "mvn deploy":
If the build process produces multiple files, e.g., the main JAR, a JavaDoc JAR and checksum files ProGet will only keep the last file to be pushed. In our case this caused ProGet to return a checksum file when the main JAR was requested.
When pushing snapshot builds ProGet seems to expect the JAR file to be named like *-SNAPSHOT.jar rather than the automatically generated *-SNAPSHOT-timestamp.jar.
Are these scenarios simply unsupported by ProGet so far or are we running into some kind of bug or configuration issue?
Regards
BastianProduct: ProGet
Version: 3.8.1
-
Our Maven support is still relatively new, and being a .NET shop we don't have a lot of internal experience with Maven, so there are currently a few gaps in our implementation. It looks like you found one.
That said, we would very much like to improve the Maven experience in ProGet. We have a basic Maven test environment here, but we're lacking some real-world test cases for it.
If you're able, could you contact us directly at support at inedo.com and supply either an example of how you're using mvn deploy, or a Fiddler trace of the failed push to ProGet?
If you can help us out a little here, we should be able to get this fixed a lot more quickly.
-
That sounds great! I'll mail you some testcases for reproducing the issues we ran into shortly.