From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Ghjwk-0007hM-Be for garchives@archives.gentoo.org; Wed, 08 Nov 2006 09:42:14 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.8) with SMTP id kA89fUfg014407; Wed, 8 Nov 2006 09:41:30 GMT Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.192]) by robin.gentoo.org (8.13.8/8.13.8) with ESMTP id kA89fTvp017580 for ; Wed, 8 Nov 2006 09:41:29 GMT Received: by nz-out-0102.google.com with SMTP id 9so1906347nzo for ; Wed, 08 Nov 2006 01:41:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=RDPUvy/MXdlt6TQB/Sf6xxDP3jjG22Qxywjggmzw/7xeJDAs5sp1QgJi/c/JTuLwgbwNTjF9lTMGY1WT3/Vk87cENOoGHPuDFr15oEXlRZYNkcoZIUjiETPI6IW9dtxocuKyjoqm3W9iyeekXbbrgIdMCRu65bR65DUFTvjdmgg= Received: by 10.65.235.7 with SMTP id m7mr9517504qbr.1162978888583; Wed, 08 Nov 2006 01:41:28 -0800 (PST) Received: from ?10.1.1.4? ( [203.109.237.126]) by mx.google.com with ESMTP id c6sm10331607qbc.2006.11.08.01.41.27; Wed, 08 Nov 2006 01:41:28 -0800 (PST) From: Alistair Bush To: gentoo-java@lists.gentoo.org Subject: [gentoo-java] J2EE compatability Date: Wed, 8 Nov 2006 22:40:45 +1300 User-Agent: KMail/1.9.1 References: <306bf010611060813i295b361cjb6dba9f4227aedfd@mail.gmail.com> <45510E6E.6090602@fastmail.fm> <455119B5.4040700@startnet.cz> In-Reply-To: <455119B5.4040700@startnet.cz> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-java@gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Message-Id: <200611082240.46376.alistair.bush@gmail.com> X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id kA89fTvp017580 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by robin.gentoo.org id kA89fUgA014407 X-Archives-Salt: 92cb28cf-0313-4465-bc46-f61ff11c3420 X-Archives-Hash: 40e4b15f9f804f834d5d1884ff3e8deb Ok here it goes. Im sure that this has been discussed before (even for=20 packages other than jboss but....) but im bringing it up again. [Quote jboss-4.0.4.GA-src/build/docs/readme_j2ee.html] ADDITIONAL NOTICE FROM SUN MICROSYSTEMS: This version of the JBoss Applic= ation=20 Server source code is made available in support of the open source=20 development process. Some numbered or tagged revisions of this source hav= e=20 been tested and found to pass the Java=E2=84=A2 2 Platform, Enterprise Ed= ition=20 (J2EE=E2=84=A2) Compatibility Test Suite, and you can find information on= which=20 revisions or tags at www.jboss.com. Please note that since only binaries = can=20 be tested, source code cannot be described as a compatible implementation= of=20 the J2EE Specification. The different build environment on your machine a= nd=20 any changes you may make to this code could render your resulting build=20 incompatible. Because of this, writing or deploying applications to build= s=20 based on this code can lead to lack of portability. You should instead=20 consider deploying production applications on the pre-built binaries of t= he=20 JBoss Application Server that are available at www.jboss.com that have be= en=20 tested and certified to meet the J2EE compatibility requirements. [/Quote] Now as everyone can see no matter what we do we will never be able to=20 compile/patch etc etc jboss (or in fact any J2EE Application Server) and = be=20 able to certify that it is complient. If that takes jboss months to do, = we=20 dont have a shit shoiw. So I want to talk strategies for gentoo related to J2EE for a couple of=20 reasons. 1) I dont want upstream(s) hating us because they get lots of "Your serv= er=20 isn't workning on Gentoo" or "Something worked on gentoo but not on ...." 2) I don't want users to be deluded into thinking they are getting somet= hing=20 they are not. The solution(s) to this is(are).... 1) a) Any source based build have an einfo message stating that the pac= kage=20 may not be J2EE complient and that upstream will not support this=20 implementation. b) Provide a binary ebuild as the official implementation and attempt t= o get=20 upstream developers (even unofficially) to agree/accept the build=20 location/layout/etc (so that there is at least a forum level of support).= =20 Maybe this package could be located just in the overlay (like a J2EE over= lay=20 with bin packages for each j2ee implementation) 2) Be true gentooians and go source but be prepared to not be=20 considered 'enterprise'. Initial include a warning as above but once we = are=20 a happy with the stability of jboss remove the warning. Now im aware of why_we_build_from_source and my preference IS to have a j= boss=20 implementation compiled from source (as you maybe able to tell from the w= ork=20 im doing) . But I also want a jboss implementation that is as true to=20 production (and certifiable) ready as possible. So therefore my preferen= ce=20 has to be option 1. What are ppl's ideas, feedback etc etc on this. Ps. Im writing this just after a game of hockey (field) so hopefully im = able=20 to string sentences together. Ps. I would also like to make sure that the source jboss build depends = on=20 the specific version (or very close relatives) of the thirdparty packages= =20 within the bin. What are ppl's feadback on this. --=20 gentoo-java@gentoo.org mailing list