As a part of 5: backport-concurrent and jbossretro-rt are both needed in
1. The client dir 2. server/all/lib Correct? -----Original Message----- From: Adrian Brock Sent: Friday, March 17, 2006 7:03 AM To: jboss-development Cc: QA Subject: Re: JBossRetro, JBossWS and JDK1.4 I missed one 1a) Tag and release JBossRetro On Fri, 2006-03-17 at 12:59 +0000, Adrian Brock wrote: > Let's move this discussion here so we make sure everybody > is "on the same page". > > I want to get this done before 4.0.4CR2 > so the community has a chance to test it, > rather than dumping it on them in a final release. > > http://jira.jboss.com/jira/browse/JBBUILD-188 > > We need to come up with a roadmap to define who is doing what. > > The tasks that need are: > > 1) Tag concurrent in our cvs repository > The only change since I imported it (tag=BUC_2_1) > is to add an ant script to build and run tests. > I'd suggest something like JBoss_BUC_2_1 > > 2) Get a Javassist release with the > lastest annotation fixes. > This is only necessary when purge=true > but purge=true is very desirable for memory reasons. > > 3) Update buildmagic to provide the retro and retrocheck > tasks to all projects (if they desire it) > > 4) Use it in JBossWS in jboss-head > > 5) Backport to JBoss4 the > * JBossRetro runtime classes > * JBossWS binaries > * javassist > * backport-concurrent-util > > 6) Test it in JBoss4 with JDK1.4 -- xxxxxxxxxxxxxxxxxxxxxxxx Adrian Brock Chief Scientist JBoss Inc. xxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
