Installing into your local maven-repository means that maven downloads all dependencies from remote repositories into its local cache.

Furthermore Maven complies your local sourcecode and creates packages in your local maven-repository.

If keeping them up to date is as easy as running a Maven command and uploading a file, I can probably keep them up to date. Getting things in Maven Central requires considerably more effort (Sona Type account, pgp keys, following the Sona Type guide, ideally a CI server that pushes snapshots automatically, i'm sure you guys can come up with other things that should be done for you free of charge because YOU and not the author himself requires it).

Otherwise you can get notification of new releases through the mailing list for each project so you can keep them up to date. Put your money where your mouth is and contribute if you know how to do it and need a specific feature. Actually creating a "freaking POM" is not so strightforward because there are two dependencies which are also not mavenised: Jsonbeans and Minlog.

Further releases of plugins will be made separately. The original goal for the 3.4.0 release was to replace Aether with the exact same code after migration to the Apache Maven project and then proceed with bug fixes to the resolver code as well as other areas of Maven.

Pretty much the same applies to performing a public release. Before I issue a PR you might want to take a look at my quick shot at https://github.com/kriegaex/kryonet/commits/maven.

The Maven release plugin can increment the version number for you, tag your repo and upload the artifacts. Just check out the few changesets I have created in order to see step by step what I did. There are nice how-to tutorials out there, and they look straightforward. Nathan, if you decide to also migrate your repos for Jsonbeans and Minlog from Google Code to Git Hub, give me a sign and I can mavenise those builds too.

We are facing the situation that IDEA's Maven integration is virtually unusable for larger Maven projects (say 50-100 modules).

Some of our problems are:- Opening the project takes about 30 minutes and most of the time involves re-indexing of all files, including JDK classes (by comparison, "mvn eclipse:clean eclipse:eclipse" takes about a minute)- Very often IDEA becomes totally unresponsive and hangs forever when the project is opened- After running a Maven build from the command-line, IDEA indexes all files produced by the build, again causing a loss of time for the developer Although the extremely poor performance makes me wonder whether IDEA's approach of integrating with Maven is fundamentally wrong, I do understand that such criticism isn't very helpful.