[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-5101) Please deploy hibernate 3.5.0.Final release to central maven repo
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5101?page=c...
]
Steve Ebersole closed HHH-5101.
-------------------------------
Resolution: Rejected
Right its not really a duplicate of any existing JIRA issue(s). But it has been discussed
numerous times on the hibernate dev list, the jboss dev list and others. The correct
solution which we are waiting on is to have the JBoss repo synch its "authoritative
artifacts" to central.
We will not be doing this as central has some prohibitive requirements including the fact
that *all* dependencies must also be present in central. We rely on quite a few other
JBoss projects and artifacts which are not out there.
Please deploy hibernate 3.5.0.Final release to central maven repo
-----------------------------------------------------------------
Key: HHH-5101
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5101
Project: Hibernate Core
Issue Type: Task
Components: build
Affects Versions: 3.5.0-Final
Environment: All
Reporter: Erik Brakkee
Hibernate version 3.5.0.Final (core and related) is not deployed to the central maven
repo (repo1.maven.org). As a result, projects depending on hibernate will not be able to
get deployed on the central maven repo. This is because the central maven repo must be
selfcontained meaning that any dependence in a project's pom must also be in the
central maven repository.
Solution is to deploy to the central maven repo. Perhaps a longer term solution is to
make the jboss maven repo one of the approved 'forges'.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira