Re: Repository organization for complex project

On 10/14/2010 3:11 PM, David Weintraub wrote:
> What? You want a GOOD Maven manual? Real programmers don't use
> manuals.

Yeah, I know - they don't write them either (except for subversion, of
course). As you might guess, I'm more of a system administrator than a
programmer...

> Fortunately, you don't really have to know too much about Maven if
> you're not a Java developer. The intricacies of the pom.xml file don't
> concern you. Possibly, the only Maven command you really have to know
> is "mvn deploy:deploy-file" which doesn't require a pom.xml file
> <http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html>.
> And, if that command concerns you too much, you can simply revert to
> "curl".
>
> You do have to understand the Maven repository layout which is a
> fairly straight forward hierarchal affair and both Nexus and
> Artifactory cover that pretty well.

Thanks - the piece I need is how to map our project tags and
branch/revision_numbers into the maven repo URLs, hopefully in a way
that wouldn't break it for actual maven use since we do have some java
developers here.

-- 
   Les Mikesell
    lesmikesell_at_gmail.com