Hi Guys, Do you think we could make the standard location for the installed packages on the gump.covalent.net machine? Here my thought: there are a couple packages like jython that are required for turbine2 and bsf (though it's not currently listed as a option) but jython is a doozy to build because it requires JavaCC to build. So as part of an interim solution could we try to eliminate the nested projects that are actually distinct but are either not easy to build or have no cvs access.
So this would apply to jisp (shared by cocoon2 and stratum), jython (shared by bsf and turbine2). This would allow people to scale back their gump builds for personal use without getting bitten like I did when I removed the cocoon2 descriptor and then losing jisp visibility. If we can make the gump.covalent.net net the standard place for installed packages then we can automate the transfer of the installed packages to the other gump boxes so that they are the same. Could we also put all the installed packages in a single file and reference that file in the profile so they don't have to be duplicated across profiles? So to summarize: -> Break out all nested projects that are distinct entities and either make real descriptors for them (i did this with freemarker, webmacro, jgenerator), or make them installed packages so they can be shared across projects. -> Place all the installed packages in a single place and make an update mechanism so that we can easily update as the nest project descriptors are split out. -> Have a single 'installed packages' descriptor that can be referenced in profiles so that we don't have to duplicate installed package definition across profiles (which I had to do when i made the turbine-universe.xml profile) I can definitely help or do the first two but I am really quite useless (intentionally :-)) with xslt. Thoughts? -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
