I'm thinking of rsync'ing the "local-remote" repository to the machine running
Nexus.
Then I'd do the deploy via HTTP (localhost) which would avoid the wire.
So, I'd preserve the auth.
Keeping the copy of the "local-remote" repository around on the Nexus machine
would improve the next build's rsync.
-Max
On 08/28/2012 11:52 PM, Anders Hammar wrote:
If you want to bypass the Repo manager (normally what happens if you
don't deploy through HTTP) you will also bypass authentication,
authorization, and other good stuff that a repo manager helps you
with. Don't do that!
/Anders
On Wed, Aug 29, 2012 at 6:17 AM, Max Spring <[email protected]> wrote:
I do use Nexus for the group repositories.
Using Nexus also locally defeats the purpose.
The deploy to a file://... repo gives me the performance I'm looking for.
Nexus Pro's staging feature would give me what I want, but I'd still have to
transport via HTTP.
-Max
On 08/28/2012 09:05 PM, Manfred Moser wrote:
On Tue, August 28, 2012 4:26 pm, Max Spring wrote:
To speed up my large Maven build I'm thinking of using a "local-remote"
repository sitting on the local file system.
1) build would start with a wiped local-remote repository
2) build's deploys into the local-remote repository
3) if build finished successfully, artifacts in the local-remote
repository get deployed into the real remote group repository.
(The benefits would be that nothing gets deployed until the build
succeeds
and the build result is available sooner.)
Are there tools which would help with 3) ?
I've looked into the Nexus Command Line Tools [1], but they don't do what
I want.
Alternatively I could write my own using the Maven API, I suppose.
Why not just use a local deployment of Nexus?
manfred
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
