3:47 p.m.
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.
6:46 a.m.
use jboss maven repository for jboss stuff.
/max
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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
7:01 a.m.
Agreed. Even the Maven developers basically tell users (on irc anyway)
to never rely on direct repository access, and to instead use a
repository manager (ala nexus etc). In which case you should just
federate both jboss and central (plus codehaus...)
On Thu, 2009-06-25 at 13:46 +0200, Max Rydahl Andersen wrote:
use jboss maven repository for jboss stuff.
/max
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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
--
Steve Ebersole <steve(a)hibernate.org>
Hibernate.org
7:05 a.m.
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.
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.
7:14 a.m.
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.
> 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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
--
Steve Ebersole <steve(a)hibernate.org>
Hibernate.org
7:21 a.m.
Yes but central is full of broken JBoss stuff at un normalized
artifact ids. So you're screwed either way.
The only viable solution is to use sonar or artifactory and define the
rules you wish.
On Jun 25, 2009, at 14:05, 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.
> 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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
7:35 a.m.
Yes but central is full of broken JBoss stuff at un normalized
artifact ids. So you're screwed either way.
The only viable solution is to use sonar or artifactory and define the
rules you wish.
On Jun 25, 2009, at 14:05, 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.
> 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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
10:25 a.m.
Emmanuel Bernard wrote:
Yes but central is full of broken JBoss stuff at un normalized
artifact
ids. So you're screwed either way.
The only viable solution is to use sonar or artifactory and define the
rules you wish.
Personally I'm only using Hibernate itself, and no additional JBoss
stuff, so I just want to be able to use Hibernate from central in the
same way I do all my other dependencies.
Max.
10:48 a.m.
Hibernate will never deploy directly to central. At best it was always
going to just be synched across to central. So for Hibernate the JBoss
repo is in fact the authoritative source. That's in direct difference
to the other artifacts with which you deal it sounds like.
On Thu, 2009-06-25 at 16:25 +0100, Max Bowsher wrote:
Emmanuel Bernard wrote:
> Yes but central is full of broken JBoss stuff at un normalized artifact
> ids. So you're screwed either way.
> The only viable solution is to use sonar or artifactory and define the
> rules you wish.
Personally I'm only using Hibernate itself, and no additional JBoss
stuff, so I just want to be able to use Hibernate from central in the
same way I do all my other dependencies.
Max.
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
--
Steve Ebersole <steve(a)hibernate.org>
Hibernate.org
11:07 a.m.
Steve Ebersole wrote:
Hibernate will never deploy directly to central. At best it was
always
going to just be synched across to central. So for Hibernate the JBoss
repo is in fact the authoritative source. That's in direct difference
to the other artifacts with which you deal it sounds like.
It's not really very different at all - no one directly deploys to
central, everyone either deploys to a project/organization repository
for syncing, or puts bundles on an arbitrary website and requests manual
processing via JIRA.
Anyway, should I assume from the direction of this conversation, that
the attempt to organize syncing, which was ongoing, has now been abandoned?
If so, could there be some sort of affirmative comment summarizing what
finally proved to be the metaphorical straw that broke the camel's back
on this?
Thanks,
Max.
11:23 a.m.
I really have no clue. To me it is really a very moot point.
If you are interested, the person in charge of the JBoss maven repo is
Paul Gier; you know him on irc as pgier. Ask him the state of all this
stuff.
On Thu, 2009-06-25 at 17:07 +0100, Max Bowsher wrote:
Steve Ebersole wrote:
> Hibernate will never deploy directly to central. At best it was always
> going to just be synched across to central. So for Hibernate the JBoss
> repo is in fact the authoritative source. That's in direct difference
> to the other artifacts with which you deal it sounds like.
It's not really very different at all - no one directly deploys to
central, everyone either deploys to a project/organization repository
for syncing, or puts bundles on an arbitrary website and requests manual
processing via JIRA.
Anyway, should I assume from the direction of this conversation, that
the attempt to organize syncing, which was ongoing, has now been abandoned?
If so, could there be some sort of affirmative comment summarizing what
finally proved to be the metaphorical straw that broke the camel's back
on this?
Thanks,
Max.
--
Steve Ebersole <steve(a)hibernate.org>
Hibernate.org
5615
days inactive
5616
days old
10 comments
4 participants
participants (4)
-
Emmanuel Bernard -
Max Bowsher -
Max Rydahl Andersen -
Steve Ebersole