Hi Martijn,
So we could do a hybrid solution? Create a distribution that includes all archived releases, and ships google loader (or create our own wicket loader) that can run in either local or internet mode?
I don't know if the google loader accepts changed base urls - if yes, that could be used.
I'd rather keep it out of extensions. I imagine this project have a much higher release rate than the rest of the projects since it depends on ~5 external libraries that have different release schedules. So that would make it a better candidate for stuff I think.
That could be split IMHO - the internet-mode could be placed in core/extensions. Projects needing to have local libraries have to add the current stuff-lib containing the libraries.
Another problem that has already been discussed: what to do with componenents requiring different libraries/library versions. Should there be some policy so a developer is warned when mixing those components on one page?
--- Jan.
