>> I think this will be difficult if the base is made up of a large number >> of jars and poms. AIUI the exlude list would have to name all the poms >> in the base. If the list of poms in the base ever changes then all the >> exclude lists would have to change as well. >> >> A simple solution would be to create a single jar in the maven repository >> called tuscany-sca-base. This could be made up of the contents of a >> number >> of other maven jars but this relationship wouldn't be exposed via maven. >> > A further thought on this: to make it work, extensions would have to be > built with poms that include tuscany-sca-base and not with poms that > include all the different base components individually. This could be > inconvenient for developers of base components as it would be necessary to > rebuild tuscany-sca-base every time an individual base component changes. > > Simon >
Hi Simon Well it would work ok if the "base" remained as an "pom" type pom which just groups together other modules. The only time this would need rebuilding would be when the set of dependency jars change. Which isn't very often. The question then remains whether you can exclude the dependencies without unnecessarily arduous exclude editing. The other drawback of this is that Ant found problems when depending on this pom type pom in order to build aggregate jars. I can't remember precisely what the problem was off the top of my head. So it needs some experimentation to see what really can be made to work. Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
