On Mar 17, 2008, at 12:14, Max Bowsher wrote:
Steve Ebersole wrote:
> JBoss as a whole is working with the Maven team (Jason) about
> setting up synching of all the projects we write to the JBoss repo
(
http://repository.jboss.org/maven2/
> ) automatically. Personally, it is not worth my time, imo, to have
> to go through this "upload" rigamarole for every release since we
> already have upload access to the JBoss repo...
Provided I'm not stepping on anyone's toes by doing so, I'd like to
help out with the aforesaid rigmarole until more permanent syncing
arrangments can be put into place.
Sure go ahead, but I don't quite understand the need for duplication.
As far as the jboss repository is concerned...
It contains numerous artifacts with the same ids as things in
central - I *hope* these are just duplicates, not subtley different
variations. It also in a number of cases contains the same artifact
under multiple different group/artifactIds. Altogether, I just don't
trust it enough to list it in my POMs.
Unfortunately,
repo1.maven.org is equally not trustable for Hibernate
today.
http://repo1.maven.org/maven/org.hibernate/
is quite messy and declare wrong dependencies (I know it's the case
for annotations and co).
As far as I can see for HAN, HEM, HV, Commons Annotations, the past is
equally screwed and messy for
repo1.maven.org/maven and
repository.jboss.org/maven2.
If you have improvement ideas for POMs in
http://repository.jboss.org/maven2/org/hibernate/
starting from:
HAN 3.3.1.GA
HEM 3.3.2.GA
HCA 3.3.0.GA
please open a JIRA issue, I'll make it better for the next releases.
My main problem is that I use ivy for my dependency management, so I
can't really test the exclusive maven chain.
Therefore, I think there's a distinct advantage to getting things
into central.
I'd go ahead and file an upload request for hibernate-annotations,
but there's the question I mentioned earlier in this thread of the
javax.persistence:persistence-api:1.0 vs. org.hibernate:ejb3-
persistence:1.0.1.GA duality to resolve.
Max.