maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anders Hammar <>
Subject Re: Packaging up pre-existing jar and source jar
Date Thu, 17 Jan 2013 09:00:57 GMT
OK, here goes:

Maven is about several different things. One of those is distributing
software (in the form of artifacts). Maven does that through (remote) Maven
repositories. So unless it is just you, you do need a remote repo. And,
even if it is just you in the dev group, it would probably make sense to
have a repo manager anyways.

A remote repo is basically just a file system area with the Maven artifacts
and some metadata. So you could be fine with a file server or a plain web
server. BUT, your life is going to be so much easier if you go with any of
the (free) repo managers available as it will provide a lot of nice extra
features. And they are also quicker to install that you trying to create
your of solution.

Internally on your machine, Maven also uses a local repository. But this is
just sort of a cache that Maven uses and you should NEVER try to use that
in any way not intended. And it is not intended to be used outside of your
local Maven execution. It doesn't even support multiple concurrent local
Maven executions.

In the early days of Maven we all though we didn't need repo managers. We
all connected directly to remote repos like central and did hacky solutions
to have internal (remote) repos. But today we know that a Maven-based dev
environment REQUIRES a repo manager.


On Thu, Jan 17, 2013 at 9:43 AM, Joachim Durchholz <> wrote:

> Am 17.01.2013 08:10, schrieb Anders Hammar:
>> You need to read up on Maven terminology. "deploy" means deploying/copying
>> to a remote repo (outside your machine). What you seem to be aiming at is
>> "install" as installing/copying to your local repo on your machine.
> Been there, done that. Can't say that the docs are easy to navigate - it's
> really hard to see whether you have seen everything relevant, and if you
> want to find the exact definition of some terminology, googling is useless
> because that terminology is used all over the place and nobody links to the
> formal definition.
>  But, you seriously need to look into how Maven is supposed to work.
> Again, been there, done that, had the same problems.
> I'm turning to this mailing list because the docs didn't work for me.
> Don't blame me for not having grokked it all, I haven't had a chance for
> that.
> > Trying
>> to fight the Maven way will just cause you pain and us on the mailing list
>> a lot of trouble trying to patch your work. Start by getting a repo
>> manager
>> and set up a remote repo. You need that!
> Then please tell why I need that. What's going to go wrong without it.
> (A link would be fine.)
>  Ron, if you're listening here, could you please tell Joachim how you
>> wasted
>> years not using a repo manager before you saw the light?
> No religious terminology like "see the light", "don't fight it", or "Maven
> way", please.
> I vastly prefer understanding over believing.
> I also vastly prefer to be in control of the tools, instead of the tools
> being in control of me.
> I'm handing control to tools as I gain confidence in that they'll do what
> I want.
> Unfortunately, Maven doesn't really qualify (yet) because of the trouble
> I'm having with the docs. (I'm not having that kind of trouble with the
> Spring docs, by the way. Just to give feedback and a data point.)
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@maven.**<>
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message