Mark Wielaard <[EMAIL PROTECTED]> writes:
> Paul also wrote a little Perl script which allows us to maintain both the
> 2.0 and 2.1 Servlet API. This is very convenient because almost everybody
> still uses the 2.0 API, but we really wanted to write the 2.1 API (and no,
> they are not really backwards compatible...) How do other people handle
> such a situation? We wanted to use cpp, but cpp does not work inside
> comments and we have a lot of things like:
>
> /**
> [...]
> #ifdef VERSION_2_1
> * @deprecated Use [...]
> #endif
> [...]
> */
On the automake side of things you could use AM_CONDITIONALs to do the
same sort of thing. Your java files would be named FileName.java.am
and automake would create FileName.java.in and autoconf would create
FileName.java. I'm not sure this is the _best_ way to go, but it
would probably work. On the other side of things if those packages
were maintained in a separate CVS module, you could have two trees
possibly, though I've never managed such a beast and I don't know how
much trouble it would be. I don't think you can branch on part of a
module, but the CVS info pages would know for sure.
Brian
--
|-------------------------------|Software Engineer
|Brian Jones |[EMAIL PROTECTED]
|[EMAIL PROTECTED] |http://www.nortel.net
|http://www.classpath.org/ |-------------------------------
