Some confusion here. Maven is a binary deployment repository. You're asking about a source repository. You can use code.google.com which supports svn and mercurial for source control, github.com, which supports git, sourceforge.com which supports at least svn. Any of these would do.
But, please do release built jars from time to time and if you put those in a maven-style deployment repository, others will be able to use maven, ant, Ivy, gradle, etc. To build and automatically fetch the right versions in their software builds. Regards, Christian Sent from my iPhone. On Apr 18, 2011, at 8:09, antalk <ant...@intercommit.nl> wrote: > The 'problem' with Maven is that it is a read-only repository. I want users > to be able to create bugfixes and or new features. Otherwise everyone will > be depending on how often we release. > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/New-component-library-tp4310339p4310579.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
