[hibernate-dev] Can we have an update on Maven central repository syncing?
steve at hibernate.org
Thu Jun 25 08:14:00 EDT 2009
The JBoss repo is somewhat messy, yes. But so is central (new to you or
not), were they routinely allow artifacts to be moved around...
The JBoss repo was set up incorrectly as the person who manages it
eagerly agrees. Originally the "duplicates" were copied because JBoss
wanted (gasp) reproducibility to their AS builds; and since the maven
team allowed artifacts to be moved around after deployment that was not
really an option relying on stuff from central. But really what should
have been done was to have 2 JBoss repos: 1) for "duplicates" from
central and 2) one for JBoss published artifacts (hibernate et al).
That's actually what I am more interested in seeing happen.
On Thu, 2009-06-25 at 13:05 +0100, Max Bowsher wrote:
> Max Rydahl Andersen wrote:
> > use jboss maven repository for jboss stuff.
> > /max
> As I have said several times on this list, the jboss maven repository is
> sufficiently polluted with non-jboss artifacts with poor naming schemes
> that conflict with central, and artifacts named the same as ones which
> exist in central but which may or may not be the same, that I do not and
> will not trust it.
> And even if that were not the case, it is still convenient to have
> everything available in central.
> > Max Bowsher wrote:
> >> With Hibernate Core 3.3.2 just released, it seems like a relevant time
> >> to ask:
> >> What happened to the ongoing struggle to get jboss artifacts synced to
> >> maven central?
> >> Could we please have an update of what the current status is?
> >> Thanks,
> >> Max.
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
Steve Ebersole <steve at hibernate.org>
More information about the hibernate-dev