Re: #define JK_VERSION in j-t-c (doesn't exist)

[Andy Armstrong]

One small point comes to light now you've released this: version.h is
quite a common thing to have on your include path; certainly under MS
operating systems there tends to be a version.h already on the include
path which may cause confusion. Any reason not to call it jk_version.h?

jean-frederic clere wrote:
> 
> Andy Armstrong wrote:
> >
> > jean-frederic clere wrote:
> > >
> > > Hi,
> > >
> > > I have prepared a patch for configure.in to generate JK_EXPOSED_VERSION and
> > > JK_VERSION.
> > > The result is a file named common/version.h:
> > > +++
> > > #define JK_EXPOSED_VERSION "mod_jk/1.2.0-dev"
> > > #define JK_VERSION (((1) << 16) + ((2) << 8) +
> > > (0))
> > > +++
> > > Any comments? - Otherwise I will commit it tomorrow -

-- 
Andy Armstrong, Tagish