[
http://opensource.atlassian.com/projects/hibernate/browse/EJB-386?page=co...
]
Rob Manning commented on EJB-386:
---------------------------------
It's been a month since this issue was reported (10/01/2008) , and over 2 months since
this version was released (8/20/2008)
According to
http://hibernate.org/6.html, you cannot use Core 3.3.x version without this.
Are you kidding me ? No one who uses
maven for their builds is using JPA with the latest version of Hibernate ? Really ?
It's not like this hasn't been done before
(
http://opensource.atlassian.com/projects/hibernate/browse/EJB-287)
Is Aleksei Valikov still responsible for doing this ? If so, can we at least get him
assigned to this ticket ?
Is it not possible to automatically upload artifacts to the central maven repository as
part of the release build ?
Rob
Deploy 3.4.0 GA to the maven2 central repo
------------------------------------------
Key: EJB-386
URL:
http://opensource.atlassian.com/projects/hibernate/browse/EJB-386
Project: Hibernate Entity Manager
Issue Type: Task
Components: EntityManager
Affects Versions: 3.4.0.GA
Reporter: Steven Cummings
The JPA/Hibernate page [1] lists 3.4.0.GA as the latest version of entitymanager. Please
deploy the artifacts (including source and javadoc jars) to the maven2 central repo.
Thanks.
[1]
http://www.hibernate.org/397.html
--
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