Russell Gold <[EMAIL PROTECTED]> writes:
>I suppose my biggest concern is in the lag in getting jars into the
>repository. When I need to build using a new jar that is not at
>iBiblio, I have to make other arrangements as a temporary measure - and
>then tell my co-workers to do the same thing. if I could simply point
>to the sourceforge project which is the ultimate host, I wouldn't need
>to do that. And I could use the exact same mechanism for internal
>projects. The distribution is available already, so why should I have
>to take an extra step to argue for the inclusion of a new jar evertime
>it is released - or even when a pre-release version is available?
I have
maven.repo.local=${user.home}/javalibs/intermeta
maven.repo.remote=http://maven.intermeta.de
in my ~/build.properties since ages. The whole ibiblio stuff is
primary politics and ideology and I try to keep away from this as much
as possible.
Whenever I have to rebuild a jakarta project, I switch these lines to
maven.repo.local=${user.home}/javalibs/ibiblio
(note the missing maven.repo.remote line)
and rebuild. Most of the time I have to hand-correct some dependencies
(such as the missing sun jars).
I very much prefer to be in charge of my build process and get
reproduceable results. And we have about 25 jars in our repository
which are not public or open-source.
Maven gets crippled by hardcoding ideology like ibiblio.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
