Jason van Zyl wrote:
> On Thu, 2002-09-19 at 09:41, Rafal Krzewski wrote:
> You may want to look at the jakarta-ojb repository then. I added the
> codeswitcher plugin which is a preprocessor and it's used in the OJB
> Maven build to select certain options in the sources for JDK 1.2, 1,3
> and 1.4. There are some logging and JDBC 3.0 options that are turned on
> or off.
>
> For the codeswitcher plugin you basically define which switches you want
> turned on/off and the sources will be processed accordingly.
This looks *much* closer to what I'd like to use. Two things to note:
1) I cant help the feeling that you did it the wrong way around in OJB.
I think that ${pom.sourceDirectory} should be src/java like usual,
and the "maven.compile.src.set" fileset should be overriden to contain
${maven.build.dir}/src (or something like that). Wouldn't that be
more intuitive?
2) It would be much nicer if the codeswitcher tag took an source fileset
and destination dir parameters. This way it could compare timestamps
and process only the files that actually changed (or are missing). That
would be certainly faster than copying the whole stuff over and munching
on each and every file.
I assume that both of these can be explained by the fact that it was a
quick hack to get the job done (which it sure does).
I'll be happy to provide patches. :)
I have one more question. I'm using maven-b5. I have a checked out copy
of maven and I've downloaded all dependencies so I'm able to build it.
(Which was *not* fun, because I'm behind a 33k phone line, and I pay
$1.25 per hour. This makes me spend about 10% of my income on bandwith!)
Is that OK to drop a recompiled plugin into my b5 plugins/ directory?
Or should I just switch to running HEAD?
R.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
