On Thu, Jan 15, 2009 at 11:43 AM, ant elder <[email protected]> wrote:
> As an fyi to where this is up to there is a compact distribution at [1] now > which does what was described in this thread. So I'd now like to try to see > if we can come up with a single Tuscany distribution that everyone could be > happy with as it would make things much simpler if there is one main > distribution. > > One thing i think is an improvement is instead of having all the jars in a > single lib folder to have the lib folder include sub directories for the > various extensions as that makes it much more obvious what jars are required > for what function, and it makes much easier to remove jars if you don't want > some function. For example: > > lib/ > tuscany core modules and their dependencies like asm and cglib > lib/webservices > tuscany webservices modules and their dependencies like axis2 > lib/bpel > tuscany bpel modules and their dependencies ode > lib/standalone > tuscany standalone runtime modules and dependencies like jetty > lib/jdk5 > the dependency jars needed when using JDK5 not JDK6, like stax, jaxb etc > lib/...folders for all the other extensions > > So instead of having lots of distributions which you can download > individually to build up a custom install you have a single distribution > that you can remove stuff from to make a custom install. > > Any comments on that approach? > > ...ant > Hi Ant Can we have an all distribution and the individual ones that build up to create the all distribution? From Raymond's original post is would be useful to have samples depend on just the individual parts that they need so that when you create an eclipse project you don't get every module in Tuscany as a dependency. Re. the grouping of libs. I like the sound of that if we can make it work for all environments. Have you code code that does this? Can we try that in 2.x and see if it's possible? Simon
