There are two aspects to this question:
1) In fact, in my discussions with Maven developers, they seem to fully
intended that users not rely on the central repo despite any
short-comings you mention.
2) The JBoss folks (who will actually take care of this synching) are
being asked to jump through hoops in order to get this synching in
place. They are in the process of jumping through said hoops.
It is unfortunate that JBoss initially decided to create only a single
repository where they mix/combine artifacts that we push there plus
dependent artifacts on which we depend. They were thinking only as an
end consumer (app server). It would have been better imho for them to
set up 2 separate repos (one for us to publish artifacts and another for
dependent artifacts) plus a proxy unifying them for AS builds. And in
fact that is the plan moving forward. But in the meantime you will need
to choose between making use of the JBoss repo and someone manually
requesting uploads to central.
And as for your points:
1) The JBoss repo is in no way special in this regard. I currently have
had to set up "extra manual configuration" for codehaus, altassian, and
some other repos. This is neither difficult nor unusual.
2) As you mentioned, this is in fact a dumb linear search. But luckily
it is a consistently dumb linear search :) It will always follow the
order in which the repos are specified in your settings.xml. No issue
Principal Software Engineer
JBoss, a division of Red Hat
On Mon, 2008-08-18 at 13:48 +0100, Max Bowsher wrote:
Max Rydahl Andersen wrote:
> On Mon, 18 Aug 2008 12:36:23 +0200, Max Bowsher wrote:
>> Steve Ebersole wrote:
>> Very nice!
>> Will new arrangements for syncing artifacts to Maven2 central now be
>> going active, or it is still up to interested third parties to file
>> requests for a manual copy of specific artifact versions in codehaus
> What is wrong with using the official jboss maven repo ? :)
Two things come to mind immediately:
(1) Why should I require extra manual configuration for Hibernate when I
don't for a multitude of other Java dependencies? The other side of this
is that Maven is less than graceful in dealing with multiple
repositories, with artifact searching being a dumb linear search across
each configured URL.
(2) Maven2 lacks any mechanism for managing same-named artifacts in
different repositories. For that reason, in the interests of being
vaguely confident in my build reproducability, I try to avoid
third-party repositories, or at least only use those that are strictly
limited to offering only their own organisation's artifacts. The jboss
repo seems to be some weird hybrid between a mirror of central, an
upstream distribution point for jboss projects, and a bunch of
duplicated/additional artifacts under non-standard names.
hibernate-dev mailing list