Hibernate * releases for JBoss AS 5
by Emmanuel Bernard
I have just released the following:
- Hibernate Annotations 3.3.1.GA
- Hibernate EntityManager 3.3.2.GA
- ejb3-persistence 1.0.1.GA
In addition to that, additional existing dependencies are:
- hibernate 3.2.6.GA
- Hibernate Commons Annotations 3.0.0.GA
All of them in the groupId org.hibernate
I did make an attempt to release correct Maven 2 poms, I would
appreciate a feedback on that.
I've seen some inconsistencies in the release used in ejb3 trunk (the
old ones are used).
Emmanuel
17 years, 7 months
org.jboss.dtf.* package usage
by Jonathan Halliday
Hi All
We are working to open source the Distributed Test Framework
that came from Arjuna along with the transaction service it
was originally built to test, that is now JBossTS.
I'd like to move the test framework code from com.arjuna.*
to org.jboss.dtf.* before it goes public.
Does anyone already use that part of the namespace? Yell now
or I'll consider it duly reserved for DTF project use.
Thanks
Jonathan.
--
------------------------------------------------------------
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111
Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom.
Registered in UK and Wales under Company Registration No.
3798903 Directors: Michael Cunningham (USA), Charlie Peters
(USA), Matt Parsons (USA) and Brendan Lane (Ireland)
17 years, 7 months
Flush failed is back in jgroups
by Adrian Brock
I thought this had been fixed?
I notice the NPE still exists in JBoss Messaging as well.
13:47:12,943 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 127.0.0.1:32774
-------------------------------------------------------
13:47:27,515 WARN [MuxChannel] Flush failed at
127.0.0.1:32774:DefaultPartition-JMS-CTRL
13:47:29,519 WARN [Multiplexer] failed to collect all service ACKs (1)
for [dst: <null>, src: 127.0.0.1:32774 (4 headers), size=0 bytes] after
2000ms, missing ACKs from [127.0.0.1:32774] (received=[]),
local_addr=127.0.0.1:32774
13:47:34,520 WARN [JChannel] Timeout waiting for UNBLOCK event at
127.0.0.1:32774
13:47:34,525 ERROR [ExceptionUtil]
org.jboss.messaging.core.jmx.MessagingPostOfficeService@197e6dc
startService
java.lang.NullPointerException
at
org.jboss.messaging.core.impl.postoffice.GroupMember.start(GroupMember.java:160)
at
org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.start(MessagingPostOffice.java:347)
at
org.jboss.messaging.core.jmx.MessagingPostOfficeService.startService(MessagingPostOfficeService.java:427)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:299)
at
org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 7 months
Re: [jboss-dev] Usage of consistent groupIds/artifactIds
by Pete Muir
On 14 Mar 2008, at 12:41, Dimitris Andreadis wrote:
> Going forward, can we agree on a common set of guidelines what goes
> where? Or else, define consistent groupIds not only for jboss
> projects but for the thirdparty ones, too? Aren't there any maven
> best practises?
Maven2 standarises on
<groupId>org.jboss.seam</groupId>
<artifactId>jboss-seam-mail</artifactId>
<version>2.0.1.GA</version>
<packaging>jar</packaging>
<scope>runtime</scope>
with the common shorthand of: org.jboss.seam:jboss-seam-mail:jar:
2.0.1.GA:runtime
This produces a jar called jboss-seam-mail.jar.
> Can we remove legacy maven stuff that is probably not in use yet?
> (that could be tricky)
Be careful, as other projects (e.g. Seam ;-) are using the repo too.
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete
17 years, 7 months
Update of Microcontainer code
by Adrian Brock
In an effort to get somewhere close to a CR1 release
I'm going to be updating to the latest microcontainer code.
The main change in this release is the new classloaders now
have a proper SPI and metadata
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=130122
but there have also been a few other small api changes
which might trip you up?
e.g. the metatype stuff no longer uses generics
(it was pointless :-)
We haven't done a major integration of the MC code since
JBossAS beta3, so there could be a few unforseen problems.
I'll be doing this later tonight, unless somebody
has a problem with me doing it, e.g. they are currently working on
major change that might conflict (see the list of changes in the
forum thread below).
Unfortunately, I had planned for this to be all stable
releases of the MC projects, but that's not going to be possible
immediately, hopefully later this week?
See
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137132#4137132
for more details.
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 7 months
JBossAS projects - hudson continuous builds
by Rajesh Rajasekaran
Continuous integration builds for all jbossas projects listed below have
been setup in hudson.
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/
All maven artifacts are archived in the build and also gets installed in
the local repository on the QA hudson server.
All these builds also get published to the public hudson server at
http://hudson.jboss.org/
- aop
- classloader
- deployers
- integration
- javaee
- managed
- metadata
- metadata-repository
- microcontainer
- naming
- osgi
- reflection
- reliance
- security (spi, sx, xacml modules)
- test
- vfs
- xb
Thanks
Rajesh
17 years, 7 months
Re: [jboss-dev] Hibernate * releases for JBoss AS 5
by Andrew Lee Rubinger
Emmanuel Bernard wrote:
> On Mar 15, 2008, at 08:40, Andrew Lee Rubinger wrote:
>> Emmanuel Bernard wrote:
>> > I've seen some inconsistencies in the release used in ejb3 trunk (the
>> > old ones are used).
> I was refering to the new place :)
We have a discussion currently taking place to define how we'll
establish a proper build matrix contract between AS Components and their
consumers (ie. EJB3):
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136329
This, when implemented, will ensure everything is of proper version.
S,
ALR
17 years, 7 months
