[gentoo-java] J2EE compatability

[Alistair Bush <alistair.bush@gmail.com>]

Ok here it goes.  Im sure that this has been discussed before (even for 
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 Application 
Server source code is made available in support of the open source 
development process. Some numbered or tagged revisions of this source have 
been tested and found to pass the Java™ 2 Platform, Enterprise Edition 
(J2EE™) Compatibility Test Suite, and you can find information on which 
revisions or tags at www.jboss.com. Please note that since only binaries can 
be tested, source code cannot be described as a compatible implementation of 
the J2EE Specification. The different build environment on your machine and 
any changes you may make to this code could render your resulting build 
incompatible. Because of this, writing or deploying applications to builds 
based on this code can lead to lack of portability. You should instead 
consider deploying production applications on the pre-built binaries of the 
JBoss Application Server that are available at www.jboss.com that have been 
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 
compile/patch etc etc jboss (or in fact any J2EE Application Server) and be 
able to certify that it is complient.  If that takes jboss months to do, we 
dont have a shit shoiw.

So I want to talk strategies for gentoo related to J2EE for a couple of 
reasons.

1)  I dont want upstream(s) hating us because they get lots of "Your server 
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 something 
they are not.

The solution(s) to this is(are)....

1)  	a) Any source based build have an einfo message stating that the package 
may not be J2EE complient and that upstream will not support this 
implementation.
	b)  Provide a binary ebuild as the official implementation and attempt to get 
upstream developers (even unofficially) to agree/accept the build 
location/layout/etc (so that there is at least a forum level of support).  
Maybe this package could be located just in the overlay (like a J2EE overlay 
with bin packages for each j2ee implementation)

2) 	Be true gentooians and go source but be prepared to not be 
considered 'enterprise'.  Initial include a warning as above but once we are 
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 jboss 
implementation compiled from source (as you maybe able to tell from the work 
im doing) .  But I also want a jboss implementation that is as true to 
production (and certifiable) ready as possible.  So therefore my preference 
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 
to string sentences together.

Ps.   I would also like to make sure that the source jboss build depends on 
the specific version (or very close relatives) of the thirdparty packages 
within the bin.  What are ppl's feadback on this.

-- 
gentoo-java@gentoo.org mailing list