[jboss-dev] Re: [Fwd: Re: [JBoss JIRA] Commented: (JBAS-5072) Fix null pointer exception when getting keys, values, or entry's in the ConcurrentHashmap]
Copying to the main dev-list.
Yes, you can change it. But ideally you should test it first.
i.e. checkout the jbossxb 1.0.0SP1 tag
and modfiy the build to use update1
That's what compatiblity means. ;-)
This clearly wasn't done for the brew release
since there's no maven release for that.
Which is another reason why brew is bad.
http://repository.jboss.com/maven2/oswego-concurrent/concurrent/
On Wed, 2007-12-12 at 16:41 -0500, Jay Howell wrote:
Hey Adrian,
I've made a new version of the concurren
lib(https://svn.jboss.org/repos/repository.jboss.org/oswego-concurrent/1....
, and I've changed my build-thirdparty.xml file, but I also need to add
an entry in the jbossxb(component-info.xml) to establish compatibility.
The current version that is current in branch 4.2 for jbossxb is
1.0.0.SP1. My question is, Do I need to make a new version of jbossxb,
or can I check the compatibility changes in for 1.3.4-jboss-update1into
jbossxb 1.0.0SP1? I see that the entry that put the compatibility entry
in for 1.3.4-jboss(1.0.0.GA_CP01-brew) was just added to that version
and a new version(directory) was not added. I can easily either make a
new version(called ???) or I can just change the version that's there.
Thanks, Jay:)
email message attachment (Re: [JBoss JIRA] Commented: (JBAS-5072) Fix
null pointer exception when getting keys, values, or entry's in the
ConcurrentHashmap)
> -------- Forwarded Message --------
> From: Jay Howell <jhowell(a)redhat.com>
> To: Adrian <abrock(a)redhat.com>
> Subject: Re: [JBoss JIRA] Commented: (JBAS-5072) Fix null pointer
> exception when getting keys, values, or entry's in the
> ConcurrentHashmap
> Date: Wed, 12 Dec 2007 15:04:59 -0500
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx