Closed faktorsmak closed 12 years ago
The short answer is that using a source repo for this is kind of a mis-matched approach, much as you said, Rob. Many folks also used Google Code for a similar free-Maven-repo reason. But I think the level of effort to store the resources is greater than it should be.
Direct access to a repository where you can create folders easily is key. Amazon S3 is a cheap way to do this. Any other FTP or WEBDAV server is also a viable approach. Here's an article on how to do it with S3:
http://www.build-doctor.com/2011/10/10/repository-thats-not-a-repository/
And a code example:
Replicated intentionally to https://github.com/githubtraining/feedback/issues/4
Hey, we are looking to set up a local Maven repository for hosting both open source jars and internally generated jars for our java projects. Somebody on my team found this article about using github to do this: (http://cemerick.com/2010/08/24/hosting-maven-repos-on-github/)
I kind of thought that using a source code repository for built components was bad practice, but I wanted to see if you guys had an opinion over there about this. It's nice that we wouldn't have to worry about hosting a repository (Nexus, Artifactory, Archiva, etc) ourselves. Any thoughts?
Thanks, Rob