[hibernate-issues] [Hibernate-JIRA] Commented: (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...
]
Erik Brakkee commented on HHH-5101:
-----------------------------------
The current situation is preventing me from deploying a project to maven central. However,
I can work around it by separating my project in the production code, which only depends
on JPA 2.0 APIs (that are in the repo already), and in a separate project for only the
tests (which use hibernate, or eclipse link which is also not in the repo).
The issue is that I only use hibernate for testing with JPA 2.0; production code only
depends on JPA 2.0 APIs. Also, eclipse link has the same problem that it is not yet in the
central repo. But at least there is a workaround at the moment.
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