Hello All,
I was wondering when can we start merging the JAXP 1.3 sources ? Merging the code in branch/review/testing/committing to main trunk
would take time so at least from my side i would like to see this work started as early as possible say from tomorrow. What is the general procedure ? Is there any formality that needs to be completed first ? What is the opinion of
(Xml-commons/Xerces/Xalan) committers ?
I'm assuming that this is something that XML-Commons/Xerces/Xalan wish to do?
I've CCd [EMAIL PROTECTED] as well, as I'd like Noel's opinion, but my feeling is that *if* the Xerces/Xalan and/or XML-Commons community want this code to be imported (and it sounds like they do - but I'd like to see that formalised), then the community side is already there.
If that's the case, then I don't think we need to go through the full incubation process (Noel - thoughts appreciated!) - we only need a code grant from Sun (we can't take something into our repository until we are sure we have appropriate legal rights to do so) + someone needs to fill out the incubation docs to show that everything is AOK. I'm happy to help out with the latter part.
Code grant details can be found at :
http://www.apache.org/licenses/#grants
As the sources would be put in a branch so it won't affect normal development but it would be good if we can restrict
large chunk of changes to the main trunk and fix only critical changes. It would help merging the changes back to main
trunk. What do others think ?
Thanks, Neeraj
Neeraj Bajaj wrote:
Ramesh Mandava wrote:
J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same sources should run on other JVMs as well.
- Both Elliotte's and Clay's questions below are important. If someone familiar with the code could comment on: For either the main trunk, or a temporary working branch for integration:
-- What JVM's will this code compile on? Version/Vendors?
-- What JVM's will this code run on? Version/Vendors?
J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources on Sun JVM. But as there is no Sun JVM specific codem these sources should work on other JVMs without modification ( we have to try it out though :-) ).
Right. This hasn't been tried but i don't see any reason why it shouldn't work on any other JVM as there isn't any Sun JVM specific code.
In other mail i have suggested that active Xerces/Xalan committers can try this before committin on main truck as the plan is to put the code
on branch first. I proposed JAXP 1.3 APIs to be committed on xml-commons main trunk but i am totally fine with creating a branch first to test
the compatibility with other JVM.
Neeraj
We need to *clearly* document which versions this stuff works on, and should conditionally compile or something if it won't compile on at least 1.3
Right now we face compilation problems in couple of file with J2SE 1.3, but these should be worked around though. We can atleast have a switch to achieve the requirement of compiling on J2SE 1.3.
(since we still have a lot of older JDK version users here).
My knee-jerk reaction is also to hope that it will compile & run on both recent Sun and IBM JVMs at least before we put this on the main trunk: we should really try to be JVM-vendor agnostic.
I agree.
Regards -Ramesh
(anyone still working on kaffe? 8-)
--- Clay Leeds <[EMAIL PROTECTED]> wrote:
On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
Are these APIs and implementation thereof independent of Java 1.5? i.e. can they be compiled and used in a Java 1.2/1.3/1.4
environment?
If not, could they be backported to work in such environments?
-- Elliotte Rusty Harold [EMAIL PROTECTED]
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/ ref%3Dnosim
Forgive me if this is covered under Mr. Harold's question, but:
Would this also be portable to IBM Java 1.30 (and any other non-Sun implementation of Java...)?
Web Maestro Clay
p.s. I'm not trying to look a gift-horse in the mouth--Thank you
Sun! Love your logo!
--
Clay Leeds - <[EMAIL PROTECTED]>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
===== - Shane
<eof .sig="http://apachecon.com/ November in Vegas, baby!" />
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
