10:40 a.m.
Tracking down the various dependencies for JB5 Beta3.
http://jira.jboss.com/jira/browse/JBAS-4562
https://svn.jboss.org/repos/jbossas/trunk/build/build-thirdparty.xml
- We have 10 components at snapshot level. They must reach at least a Beta state until
mid-September. Can the respective owners verify they can deliver on time and make sure the
updates are tracked with subtasks in JIRA (JBAS-4562), including any transitive
dependencies
those component may have?
<componentref name="jboss/aop" version="snapshot"/>
<componentref name="jboss/integration" version="snapshot"/>
<componentref name="jboss/jboss-jaspi-api"
version="1.0-SNAPSHOT"/>
<componentref name="jboss/jboss-javaee"
version="5.0.0-SNAPSHOT"/>
<componentref name="jboss/jboss-security-spi"
version="2.0.1-SNAPSHOT"/>
<componentref name="jboss/jbosssx" version="2.0.1-SNAPSHOT"/>
<componentref name="jboss/jbosssx-client"
version="2.0.1-SNAPSHOT"/>
<componentref name="jboss/jbossts" version="snapshot"/>
<componentref name="jboss/messaging" version="snapshot"/>
<componentref name="jboss/microcontainer" version="snapshot"/>
- What other component updates are required? Are those entered in JIRA as well? For the
time
being we have:
Hibernate Annotations 3.3.1 (from 3.2.1)
Hibernate Entity Manager 3.3.2 (from 3.2.1)
What about jgroups 2.5 ? (now at 2.4.1.SP3). Is something else missing? Any objections on
including Hibernate Validator?
- Synch with AS 4.2.x
xdoclet could go to 1.2.3 (from 1.2b3)
remoting to 2.2.1, or 2.2.2 when available (now at 2.2.0.SP4)
- Removals. Are the following *really* needed? Most do not exist at all in 4.2.x.
wutka-dtdparser
backport-concurrent
jbossretro
apache-myfaces
commons-el
easymock
ehcache
sleepycat
spring
jbpm
opensaml
- Inconsistencies
Don't know how we've managed but we have *two* version of dom4j. Interestingly
enough, the
last wins:
<componentref name="dom4j" version="1.6.1-brew"/>
<componentref name="dom4j" version="1.6.1jboss"/>
I'm inclined to keep the brew'ed one (used in 4.2.x, too) or does someone remember
what's
special with the 1.6.1jboss one?
Another inconsistency is that JBM brings in the old JBoss Common 1.2.0.GA in thirdparty,
although we are using the Common 2.x series. Not sure if it has any other implications.
Cheers
/Dimitris
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dimitris Andreadis
JBoss AS, Project Lead
JBoss, a Division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
4:18 a.m.
Dimitris Andreadis wrote:
Tracking down the various dependencies for JB5 Beta3.
http://jira.jboss.com/jira/browse/JBAS-4562
https://svn.jboss.org/repos/jbossas/trunk/build/build-thirdparty.xml
- We have 10 components at snapshot level. They must reach at least a
Beta state until mid-September. Can the respective owners verify they
can deliver on time and make sure the updates are tracked with subtasks
in JIRA (JBAS-4562), including any transitive dependencies those
component may have?
...
<componentref name="jboss/jbossts"
version="snapshot"/>
JBossTS 4.4 won't be in Beta by mid-September. Probably best
to go with 4.2.3.SP5 instead.
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) and David Owens (Ireland)
5:45 a.m.
Jonathan Halliday wrote:
Dimitris Andreadis wrote:
> Tracking down the various dependencies for JB5 Beta3.
> http://jira.jboss.com/jira/browse/JBAS-4562
>
> https://svn.jboss.org/repos/jbossas/trunk/build/build-thirdparty.xml
>
> - We have 10 components at snapshot level. They must reach at least a
> Beta state until mid-September. Can the respective owners verify they
> can deliver on time and make sure the updates are tracked with
> subtasks in JIRA (JBAS-4562), including any transitive dependencies
> those component may have?
>
...
> <componentref name="jboss/jbossts" version="snapshot"/>
JBossTS 4.4 won't be in Beta by mid-September. Probably best to go with
4.2.3.SP5 instead.
Jonathan.
Are we sticking with jbossts14 ?
https://svn.jboss.org/repos/repository.jboss.org/jboss/jbossts14/
The last jbossts version is 4.2.2.GA
https://svn.jboss.org/repos/repository.jboss.org/jboss/jbossts/
4:49 a.m.
Dimitris Andreadis wrote:
Jonathan Halliday wrote:
> Dimitris Andreadis wrote:
>> Tracking down the various dependencies for JB5 Beta3.
>> http://jira.jboss.com/jira/browse/JBAS-4562
>>
>> https://svn.jboss.org/repos/jbossas/trunk/build/build-thirdparty.xml
>>
>> - We have 10 components at snapshot level. They must reach at least a
>> Beta state until mid-September. Can the respective owners verify they
>> can deliver on time and make sure the updates are tracked with
>> subtasks in JIRA (JBAS-4562), including any transitive dependencies
>> those component may have?
>>
> ...
>> <componentref name="jboss/jbossts"
version="snapshot"/>
>
> JBossTS 4.4 won't be in Beta by mid-September. Probably best to go
> with 4.2.3.SP5 instead.
>
> Jonathan.
>
Are we sticking with jbossts14 ?
https://svn.jboss.org/repos/repository.jboss.org/jboss/jbossts14/
The last jbossts version is 4.2.2.GA
https://svn.jboss.org/repos/repository.jboss.org/jboss/jbossts/
'sticking with'? AS 5.0 currently uses jbossts, not jbossts14.
I'll do a build of 4.2.3.SP5 using java 5 in the next few
days. Right now I'm reviewing the changes we have made since
that tag and trying to figure out if a 4.2.3.SP6 may be
worthwhile.
BTW, the TS 4.2.3 branch does not have JTA 1.1 because I was
not allowed to put that into AS 4.2. That means bad things
are going to happen if anyone is actually using the new
TransactionSynchronizationRegistry already. If anyone is
relying on that interface please let me know and we'll have
to look at backporting JTA 1.1 to the TS 4.2.3 branch
without breaking AS 4.2.
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) and David Owens (Ireland)
5:05 a.m.
>> JBossTS 4.4 won't be in Beta by mid-September. Probably
best to go
>> with 4.2.3.SP5 instead.
>>
>> Jonathan.
>>
>
> Are we sticking with jbossts14 ?
>
> https://svn.jboss.org/repos/repository.jboss.org/jboss/jbossts14/
>
> The last jbossts version is 4.2.2.GA
>
> https://svn.jboss.org/repos/repository.jboss.org/jboss/jbossts/
>
'sticking with'? AS 5.0 currently uses jbossts, not jbossts14.
I'll do a build of 4.2.3.SP5 using java 5 in the next few days. Right
now I'm reviewing the changes we have made since that tag and trying to
figure out if a 4.2.3.SP6 may be worthwhile.
So essentially both AS 4.2 and 5.0 will be using the same JBossTS, the latter one compiled
with jdk5.
BTW, the TS 4.2.3 branch does not have JTA 1.1 because I was not
allowed
to put that into AS 4.2. That means bad things are going to happen if
anyone is actually using the new TransactionSynchronizationRegistry
already. If anyone is relying on that interface please let me know and
we'll have to look at backporting JTA 1.1 to the TS 4.2.3 branch without
breaking AS 4.2.
Jonathan.
Isn't a requirement of TCK5 to offer support for JTA 1.1 ?
5:13 a.m.
Dimitris Andreadis wrote:
So essentially both AS 4.2 and 5.0 will be using the same JBossTS,
the
latter one compiled with jdk5.
for AS 4.2.1, AS 5.0.beta3 that's the idea yes.
Isn't a requirement of TCK5 to offer support for JTA 1.1 ?
yep. The proposed solution is not ideal, but nor is holding
AS 5.0.beta3 until TS 4.4 is in beta. I opted for what I
consider the lesser evil.
Jonathan.
5:22 a.m.
Jonathan Halliday wrote:
Dimitris Andreadis wrote:
> So essentially both AS 4.2 and 5.0 will be using the same JBossTS, the
> latter one compiled with jdk5.
for AS 4.2.1, AS 5.0.beta3 that's the idea yes.
> Isn't a requirement of TCK5 to offer support for JTA 1.1 ?
yep. The proposed solution is not ideal, but nor is holding AS 5.0.beta3
until TS 4.4 is in beta. I opted for what I consider the lesser evil.
Jonathan.
That fine. I've created a reminder task here:
http://jira.jboss.com/jira/browse/JBAS-4648
6325
days inactive
6332
days old
jboss-development@lists.jboss.org
7 comments
3 participants
participants (3)
-
Alexey Loubyansky -
Dimitris Andreadis -
Jonathan Halliday