Sim has contributed a huge effort (in fact I've seen my inbox
overflowing with commits at times), fixing the River website, donating
his own funds to renew the jini.org domain, improving testing and the
build process, not to mention researching ways to get around firewalls,
I respect his opinion and hope that we can demonstrate the benefits of
the modular build structure and get his support. Sim is an asset to the
Apache community.
I don't mean you any disrespect Sim, by not wanting to discuss the
benefits further until I myself have a good understanding and code to
demonstrate. When the time comes we'll all have an opportunity to
analyse and discuss whether the modular build structure should be
adopted, if the community decides not to adopt it for whatever reason, I
will still have had the opportunity to learn much about River's structure.
Cheers,
Peter.
Sim IJskes - QCG wrote:
It is big, but not complex.
Have a look at the png, you can see clear patterns here.
http://people.apache.org/~sijskes/build.png
It's a bit messy in the front (that was me, trying to maintain
compatibility, to stay as less controversial as possible).
But what is the process basically:
- compile (ant supports compiling only changed files)
- building deps (only those that need change)
- building jars (only those that need change)
We can reduce a lot of duplication by bundling those actions in single
targets, and better uptodate checking. A number of macros should suffice.
We can reduce a lot of variable definition, by specifiying them in the
target where they are needed.
Gr. Sim
