New jboss-as build 7.1.1-12
by Marek Goldmann
A new jboss-as package was built for Rawhide:
https://koji.fedoraproject.org/koji/buildinfo?buildID=369774
This build includes some cleanups in symlinks. Starting from now on
standalone.xml configuration will be the default one (earlier we used
standalone-web.xml file). This change enables by default more services
(like webservices).
Changelog:
- Fixing many missing symlinks
- Make standalone.xml the default configuration instead standalone-web.xml
- Add an easy way to override the default bind address for systemd service
--Marek
11 years, 5 months
CXF stack upgrade
by Marek Goldmann
Hi,
I'm in the process of upgrading the CXF stack in the Fedora
repositories. The most important is the upgrade to latest CXF version:
from 2.4.9 to 2.7.0.
The jbossws-* packages will be updated too:
jbossws-cxf: 4.0.2.GA => 4.1.0.Final
jbossws-api: 1.0.1.GA => 1.0.1.Final
jbossws-spi: 2.0.3.GA => 2.1.0.Final
This is a preparation for the jboss-as package update to add support for
webservices.
All mentioned packages will land in Rawhide only, at least for now. I
plan to backport it to Fedora 18. No plans for Fedora 17.
--Marek
11 years, 5 months
Hibernate 4 support is available in JBoss AS in Fedora Rawhide (jboss-as-7.1.1-10)
by Marek Goldmann
Hi All,
I have some great news to share with you. We managed finally to bake
Hibernate 4 support into JBoss AS in Fedora. This wouldn't be possible
without Gil Cattaneo's support. He was that guy who packaged Hibernate 4:
https://bugzilla.redhat.com/show_bug.cgi?id=852330
And here is the build:
https://koji.fedoraproject.org/koji/taskinfo?taskID=4671784
## Where it is available?
Support for Hibernate 4 is immediately available *for Rawhide* for now.
We need spend some time on porting and testing the Maven resolver before
we can push hibernate (4) package to Fedora 17 or 18 branches.
## Things to note
"hibernate" is now the default hibernate package, hibernate3 is now a
compat package for it.
https://fedoraproject.org/w/index.php?title=User:Akurtakov/JavaPackagingD...
There are few important things to note.
We have now 2 Hibernate versions in Fedora: 3.6.10.Final and 4.1.7.Final.
When using mvn-rpmbuild Maven resolver will look for the version
requested in pom.xml, if we have such one, then the correct library will
be returned. But this is a very rare case.
What happens when we don't have the selected version? A default one will
be returned (4.1.7.Final in this case).
How to resolve Hibernate 3 jars then?
1. Use the correct package version (3.6.10)
2. Use the correct upstream version (3.6.10.Final)
3. Use virtual version (3)
The most "safe" thing to do is to request version "3" in your pom. Maven
will return the latest installed library from hibernate3 package.
If you're unsure which version was resolved, add
"-Dmaven.local.debug=true" to your command.
Enjoy!
--Marek
11 years, 5 months