Beyond this, you can try programmatically injecting a new SourceModification into the project's build (Off the top of my head, I think it would be something like addSourceModification() under ${pom.build}). However, as I mentioned previously, you may have to re-establish some of the source-based properties which are initially set in the driver.jelly (I think).
Good luck.
-john
P.S. Is there some reason you can't just add rmic to your build process, and re-create the stub/skeletons with each build? I'm no RMI guru...would this cause too much of a performance penalty on the build? -J
Randy Xu wrote:
Jason van Zyl wrote:
Some of our modules have classes that need to be post-processed and rmic'ed. We'd like to not recompile and process those if they didn't change. In ANT, we had a target of 'compile-minimal'. They are named a particularly way so it'd be easy enough to exclude them, as long as I can add an exclusion to sourceModifications in a goal.On Sun, 2005-01-09 at 04:14, Randy Xu wrote:
I just need a goal which will add an exclusion (**/*Bean.java) to sourceModifications. Any idea how to do this?
First off what is the reason for excluding sources from the build?
Strictly platform variances or something else?
-Randy
--------------------------------------------------------------------- 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]
