> >> Would it be ok to build three different jar files based on whether > >> the target was 1.3, 1.4, or 1.5? Packaging the different jar files > >> into one could be a post-build exercise. > >> Or a specific build target that combined the three jar files. > >> > >> How is the source code structured today? > > > > That could work I guess. For the most part, a given module > is in only > > one language version, but there are a fewt scattered exceptions to > > this. > > Probably we only will need special 1.4 and 1.5 code areas for one > > module in particular. > > For sure, you need the implementation of second class objects > for the 1.4-specific classes and interfaces.
Yup. > And for 1.5, it's the entire annotation processor. Well, all the javax.persistence stuff is 1.5, so all the annotation processing etc. lives safely in 1.5-land. It's just the core OpenJPA modules (which are useable in 1.3) that need special handling for 1.4- and 1.5-specific classes. -Patrick _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
smime.p7s
Description: S/MIME cryptographic signature
