You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Max Bowsher (JIRA)" <ji...@codehaus.org> on 2008/10/15 20:17:19 UTC

[jira] Created: (MAVENUPLOAD-2240) Partial sync of Hibernate Core 3.3.x

Partial sync of Hibernate Core 3.3.x
------------------------------------

                 Key: MAVENUPLOAD-2240
                 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2240
             Project: Maven Upload Requests
          Issue Type: Bug
            Reporter: Max Bowsher


Due to MAVENUPLOAD-2215 the "hibernate-core" artifact for 3.3.x was synced from the jboss repo. That upload request fails to note that as of 3.3, the "Hibernate Core" product is now split over multiple jar files, only one of which is now present in the central repository, in somewhat confusing fashion.

Please sync the following artifactIds, (all within groupId=org.hibernate):

hibernate-c3p0
hibernate-ehcache
hibernate-jbosscache
hibernate-jbosscache2
hibernate-jmx
hibernate-oscache
hibernate-proxool
hibernate-swarmcache
hibernate-cglib-repack

Apart from hibernate-cglib-repack, which has version 2.1_3, the others all have 3.3.* versions, only.
Taken together, the above bring the central repository in line with the classes which ship in the Hibernate Core tarball distribution (where they are present as an uberjar).

Note that the hibernate-jbosscache and hibernate-jbosscache2 reference versions of jbosscache which are not present in the central repository. Please include them or not as you see fit, based on whether you believe the overall referential integrity of the central repo, or the consistent presence of all the artifacts making up the "Hibernate Core" release is more important.




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Closed: (MAVENUPLOAD-2240) Partial sync of Hibernate Core 3.3.x

Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MAVENUPLOAD-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carlos Sanchez closed MAVENUPLOAD-2240.
---------------------------------------

      Assignee: Carlos Sanchez
    Resolution: Fixed

synced all versions of thos artifacts and 1.4.1.ga of jboss cache

> Partial sync of Hibernate Core 3.3.x
> ------------------------------------
>
>                 Key: MAVENUPLOAD-2240
>                 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2240
>             Project: Maven Upload Requests
>          Issue Type: Bug
>            Reporter: Max Bowsher
>            Assignee: Carlos Sanchez
>
> Due to MAVENUPLOAD-2215 the "hibernate-core" artifact for 3.3.x was synced from the jboss repo. That upload request fails to note that as of 3.3, the "Hibernate Core" product is now split over multiple jar files, only one of which is now present in the central repository, in somewhat confusing fashion.
> Please sync the following artifactIds, (all within groupId=org.hibernate):
> hibernate-c3p0
> hibernate-ehcache
> hibernate-jbosscache
> hibernate-jbosscache2
> hibernate-jmx
> hibernate-oscache
> hibernate-proxool
> hibernate-swarmcache
> hibernate-cglib-repack
> Apart from hibernate-cglib-repack, which has version 2.1_3, the others all have 3.3.* versions, only.
> Taken together, the above bring the central repository in line with the classes which ship in the Hibernate Core tarball distribution (where they are present as an uberjar).
> Note that the hibernate-jbosscache and hibernate-jbosscache2 reference versions of jbosscache which are not present in the central repository. Please include them or not as you see fit, based on whether you believe the overall referential integrity of the central repo, or the consistent presence of all the artifacts making up the "Hibernate Core" release is more important.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira