Dave Barnett
|
We use a tool for performing builds that behaves similar to GNU Make with "VPATH" logic enabled.
One issue we have with the current version of JMake (1.3.3) is that it does not support our "sparse work area" model.
What I mean by "sparse work area" is that we have a baseline built every week that has all of the code in it. When the developers work, they don't require all of the code in their local area, simply the code they're updating. Our build tool uses a pre-computed dependency tree to know what is out-of-date between the local area and the baseline and then re-builds in the developers' local area only that which was impacted by their changes.
I have been able to modify JMake version 1.3.3 [really is probably 1.3.4, since it supports JDK6 and 1.3.3 didn't, but I digress] to support our build model.
I'd like to feed those changes back to the project, so that they might be used by others, if they wish to implement a similar arrangement.
There are some potential issues that I see with my changes:
1. Checking for duplicate source files (i.e. 2 classes both claiming to be foo.bar.Class found from different areas)
2. The use of "CLASSPATH" -- from ClassPath.getCompilerUserClassPath -- to find our "old" class files
3. Others of which I am unaware.
I'll happily provide the changes, but I don't want to break JMake for everyone else, nor do I wish to have everyone else breaking JMake for us....
What do you suggest is the best way forward?
Thanks,
Dave
|
