[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Repository organization for complex project

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Thu, 14 Oct 2010 13:42:55 -0500

On 10/14/2010 8:24 AM, David Weintraub wrote:
> On Thu, Oct 14, 2010 at 3:39 AM, Stephen Connolly
> <stephen.alan.connolly_at_gmail.com> wrote:
>> Our C/C++ guys just use curl to POST the binaries to Nexus over
>> http... we also POST the .pom file and the .md5 and .sha1 files...
>> that is because one of their build toolchain envs cannot have Java on
>> it... Nexus will rebuild the metadata.xml files for you, so all you
>> really need is to post the .pom and the e.g. .so and the .pom.md5,
>> .pom.sha1, .so.md5 and .so.sha1 files and you're done.
> I would think that you'd need whatever protocol Maven uses to actually
> put files on the repository. I guess the Maven protocol is simpler
> than I thought and simply uses webdav authentication and the mvn
> file::deploy simply calculates the URL for you.
> That's good to know. That means you can replace all of Maven with some
> fairly simple shell scripts using curl. Then in a non-Java project,
> all the Maven repositories do is provide a nice interface for
> searching and administration of a HTTP based repository.

Is there a maven-for-dummies reference somewhere that would make a good
starting point for how the repository is supposed to work? I tend to
get lost easily with java-like things that have a bazillion separate
config files all over the place. Also, is mirroring/redundancy built
into the design?

   Les Mikesell
Received on 2010-10-14 20:43:38 CEST

This is an archived mail posted to the Subversion Users mailing list.