Red Hat Bugzilla – Bug 1276077
Include hibernate-osgi when hibernate is released
Last modified: 2015-12-11 11:21:09 EST
+++ This bug was initially created as a clone of Bug #1162402 +++
We would like to align the version of hibernate used in Fuse with that used in EAP however we require hibernate-osgi which is currently not included in the artefacts that EAP releases,
Can you release hibernate-osgi for 4.2.20.Final-redhat-1 and subsequent hibernate releases?
I'm closing this because hibernate-osgi is not released with EAP, so this should not be an EAP BZ.
The hibernate-osgi jars can be found at http://download.devel.redhat.com/brewroot/repos/jb-eap-6.4-rhel-6-build/latest/maven/org/hibernate/hibernate-osgi/ .
Chris O'Brian and John Casey can provide more details about the process for pushing artifacts to maven.repository.redhat.com.
There is precedent for EAP to include some previously excluded modules when they do new builds of a component, so other products can have access to versions of the excluded modules that are compatible with things included in EAP.
Note that this has nothing to do with pushing content to MRRC; it's more a case of considering downstream products and taking on a little extra effort in order to avoid incurring additional compatibility problems later. In many cases, downstream products need access to modules that the EAP team have chosen to patch out of the build process (usually to save a little time).
It also seems reasonable that the Fuse team should be willing to collaborate with EAP in the effort to include the needed modules.
John, I'm confused what you are suggesting. Should this be reopened/recategorized? If so, who is the appropriate person to whom this should be assigned?
First, I was saying that this isn't related to maven.repository.redhat.com at all, which is something that came up in an email thread about this bug.
Second, I was saying that middleware product engineering has long accepted that if EAP builds a project but downstream products need a module that the EAP build patches out (suppresses) - such as hibernate-osgi - it's reasonable to request that they include the module in subsequent builds. This is something I've heard discussed between Paul Gier, Trevor Kirby, and various middleware layered product engineers on multiple occasions.
Given all of that, it seems like filing such a request here would be appropriate.
Is the requestor asking that hibernate-osgi be made available on maven.repository.redhat.com as part of each EAP release?
If EAP builds hibernate-osgi, but doesn't push it as part of their maven repository, it should still be available in MEAD.
David, you are way more familiar with this than I am. I'll assign to you. Please reopen/reassign as appropriate.
(In reply to John Casey from comment #5)
> Is the requestor asking that hibernate-osgi be made available on
> maven.repository.redhat.com as part of each EAP release?
> If EAP builds hibernate-osgi, but doesn't push it as part of their maven
> repository, it should still be available in MEAD.
Yes, we are asking for this additional module to be made available in the public maven repo.
this request is to push hibernate-osgi to the public maven repo, MRRC.
Currently when hibernate is pushed to MRRC the hibernate-osgi jars are not included as they are not required by EAP.
However Fuse is now aligning on the same version of Hibernate as EAP to faciliatate ongoing maintenance and as we require the hibernate-osgi jars I'm requesting that the release process be modified to push hibernate-osgi jars to MRRC for each release.
Having EAP include hibernate-osgi in the repository zip they ship for deployment to MRRC would complicate the process of producing that zip. Sure, it's only a couple of files, but with EAP this would be a truly slippery slope, as so many other products layer on top of it and might need similar concessions. It seems to me to make a lot more sense to have the layered product be responsible for actually shipping that jar to MRRC, regardless of who actually built it.
I've been discussing some other libraries with product engineering that are common between Fuse and EAP and for which there might be some awkward timing issues in getting them up to MRRC. It's starting to look like it might make sense for Fuse to deliver a mini repo.zip for deployment to MRRC when it releases, which would consist of these things that are somewhat awkward to coordinate.
If that idea will work, I'd suggest Fuse include hibernate-osgi in that miniature zip, and we'll call the deployment of hibernate-osgi part of Fuse's release.
Does that make sense?
Just wanted to add that I agree with John's comment that EAP should not include these artifacts in the Maven repository zip. All Hibernate artifacts must be built, however, only the supported set are shipped with a given product. The unshiped/unsupported artifacts are available in the internal repositories. If a product needs these artifacts they can produce a Maven repository which includes them and then upload that to MRRC when the product is released.