I have implemented an alternative approach in Validator that uses an svn:external to pull in the commons-build.
http://www.mail-archive.com/commons-dev%40jakarta.apache.org/msg76982.html http://svn.apache.org/viewcvs.cgi?rev=386450&view=rev I set up a new "shared-build" directory in commons-build and created an svn:external to pull in that directory. Anything that gets dropped in "shared-build" will be automatically pulled into Validator (or any other component that uses it) via the svn:external. This has the benefit of removing commons-build, but not introducing the requirement to be online to build or view the docs properly. Niall On 3/16/06, Niall Pemberton <[EMAIL PROTECTED]> wrote: > On 3/15/06, Stephen Colebourne <[EMAIL PROTECTED]> wrote: > > Progress to remove commons-build seems to be moving along nicley. So far > > at least [lang], [io], [primitives], [collections], [codec], [logging] > > and [betwixt] are done, plus [pool] unpublished. > > > > > > I believe that I may have an even sneakier way to handle the shared menu > > part however. This is a medium term idea... > > > > We could write a piece of javascript that adds the menu items to the > > page dynamically after the page is loaded. The script could be hosted > > online and referenced by http. Thus one change to the javascript would > > affect all websites without regenerating them (as the CSS will do now). > > > > Unfortunately, I don't have the time to investigate or play with this > > right now, but if anyone else wants to feel free! > > > > > > In the meantime, I suggest continuing with the current process to remove > > commons-build as that seems to be working fine so far. > > The problem with this approach is that as well as requiring an online > connection to build components, it also requires a online connection > to view the docs properly. IMO this isn't that much of an improvement > on having to check out commons-build. Plus as someone else mentioned, > it puts additional load on the apache hardware. > > Seems to me that for the few people that build from source we're > removed one issue and added another (need online connection to build) > and for everyone we've added an issue when viewing the docs. I just > don't see how this can be considered improving the situation. > > Also -1 to having the docs depend on javascript. > > Niall > > > Stephen > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
