Let's go straight to the meat: we just opened our Early Access Preview (EAP) for Maven support! If you're packaging .jar and .war and have a pom.xml to go with them, you can now add these to your MyGet feeds (or should we start calling them repositories).
To enable Maven support on your account, simply click here. This will enable the feature toggle on your account and give you access to the Maven features described in our documentation.
Which features are available in this EAP?
We currently support almost all features we have available for other package managers: uploading your own packages (via the web UI as well as via
mvn or Gradle) and adding packages from upstream repositories like Maven Central. Packages can then be consumed in IntelliJ IDEA or Eclipse, using Maven or Gradle. It's possible to proxy upstream repositories into your MyGet feed. You can manage permissions and users, inspect package licenses and vulnerabilities, ...
A Maven repository on MyGet can also be used as a staging area: packages and snapshots can be published on MyGet, and once they are stable, pushed upstream to another repository out there - similar to what is possible for NuGet and NPM.
We're looking into supporting build services as well (theoretically you can already create a build.bat and invoke `mvn deploy` from it), but we'd love your feedback on what the perfect convention-based build for Maven/Gradle would look like.
I want to join the preview!
If you are interested in joining the private preview and eager to provide some early feedback, click here to enable Maven support for your account. Our getting started documentation is available as well.
We're really excited about introducing Maven support on MyGet! You can now use MyGet to securely host and collaborate on NuGet, symbols and sources, Chocolatey, PowerShell, NPM, Bower, Maven and VSIX packages.