Our dev shop at work had very little in the way of Continuous Integration (CI) infrastructure. I’ve been praising the benefits of the CI gospel since I arrived here, but paradigm shifts are never easy.
Since my development is isolated from The Corp’s standard procedures, I began using as much CI best practices as possible. I wanted to start with something that would be simple for other, non-CI developers to adopt, so I started with jar file management. After reviewing a few options, it seemed like Archiva would fit the trick.
After a few weeks of using this on my own, it did not take long for other developers to see the benefit of using Archiva, and I was more than willing to give them access and help. I had my own user, and I gave them a username/password combo that they shared amongst all of their developers.
Every so often these usernames’ passwords would expire, and it was a very annoying process to reset them. After much time googling the issue, I was able to find the documentation that would prevent me from having to reset the passwords on a regular basis:
Just add the following entries to your <ARCHIVA_HOME>/apps/archiva/WEB-INF/classes/org/apache/maven/archiva/security.properties
Hopefully this will help to remove me as the bottle neck for any Archiva related issues.