I did a run through this.   The installer portion is very clean, I like
it.
The only question I have is related to the build process for the ejb3
portion.

Previously we would switch the jdk to a 1.5 and build the ejb3 modules.
I'm assuming the installer now pulls this stuff in automatically from
the ejb3 profile.

Will our standard procedure be to create the initial jbossas build using
a 1.5 version jdk (so that the ejb3 profile will be created)?



Ruel Loehr
JBoss QA
 
-----------------------------
512-342-7840 ext 2011
Yahoo: ruelloehr
Skype: ruelloehr
AOL: dokoruel

-----Original Message-----
From: Scott M Stark 
Sent: Saturday, May 06, 2006 12:56 PM
To: 'jboss-development@lists.sourceforge.net'; '[EMAIL PROTECTED]'
Subject: Updated JBossASReleaseChecklist

I updated the jbossas release to reflect the fact that the installer has
been broken out as a separate project. We need to go through a couple of
iterations to make sure that this updated process works for qa:

http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossASReleaseChecklist
http://wiki.jboss.org/wiki/Wiki.jsp?page=JEMSInstallerReleaseChecklist

All of the javaee5 preview technology as well as the jbossas dist
contents itself are pulled into the jems-installer project via the
binary repository. I have thrown out some prototype binaries for the
jbossas/4.0.4.GA contents and the jboss/ejb3/ 1.0.0.CR7-jboss4 that are
referenced by the jems-installer/build-thirdparty.xml descriptor. Let's
arrange for a walkthrough of a build by Monday. 



-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to