Thanks so much Quintin, I don't expect to have any more questions!
Have a good weekend everyone, and thanks for the help.
Rob
--------------------------------------------------
From: "Quintin Beukes" <[email protected]>
Sent: Friday, October 16, 2009 1:03 PM
To: "Maven Users List" <[email protected]>
Subject: Re: Hosting a local repo w/out a Repo Manager?
Here is the nexus book. It explains where to get it, how to install it
and how to use it. Took me about 10 minutes from where I finished
downloading it for the first time, till where it was setup and
configured with scheduled tasks and hosted for the whole network,
integrated into the system init, the works.
The book: http://www.sonatype.com/books/nexus-book/reference/
And re. your question of having Maven use ONLY nexus, no matter the
repository, here it is:
http://www.sonatype.com/books/nexus-book/reference/maven-sect-single-group.html
This way the manager will have it's repositories setup, and maven will
query the manager with the group/artifact id and version, and the
manager will look in it's own indexes for the artifact, no matter from
which repository it actually came or how it got into your manager's
repository.
Quintin Beukes
On Fri, Oct 16, 2009 at 9:59 PM, Quintin Beukes <[email protected]>
wrote:
In the nexus book they use that as an example.
You basically do it when you configure the <mirrors> element in your
settings.xml. By matching the mirror against everything, then maven
will query your Nexus no matter what the repository's URL is.
Quintin Beukes
On Fri, Oct 16, 2009 at 9:55 PM, Rob Slifka <[email protected]> wrote:
Alright, alright! :)
I'll have a look at Nexus and go from there.
Is there a way to tell Maven "Only look at the Nexus repo, fail
otherwise" ?
Perhaps it will become clear after using Nexus.
Rob
On Fri, Oct 16, 2009 at 12:08 PM, Quintin Beukes
<[email protected]>wrote:
> I'd like to think of a repo manager as "part of using maven 2".
This is a very good way of seeing it. If you don't see it as yet
another complexity added into the build process, but accepting it as
part of Maven in the first place, then you remove this "extra
complexity". I completely understand your goal of wanting to keep
things simple, and do this myself all the time as well, but some
things are of such great benefits that the complexity is completely
outweighed. Maven is one of them, and the repo manager is a part of
"Maven" (the idea, not just the software).
Q
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
