On Mon, Sep 13, 2010 at 10:31 AM, Simon Laws <simonsl...@googlemail.com> wrote: > Hi > > > On Fri, Sep 10, 2010 at 4:43 PM, Raymond Feng <enjoyj...@gmail.com> wrote: >> What really matters here is the mechanism. The feature poms we have now are >> just some pre-canned profiles to demonstrate ways of grouping modules >> together (like the various Eclipse packages for people to pick). They are >> choices and there are always specific needs to regroup. If you are not happy >> with the grouping, you can easily add yours. >> Thanks, >> Raymond > > Right, the point here is that we are defining a mechanism that is able > to produce the artifacts that we want to see in the binary Tuscany > distribution.
There's lots of different ways the artifacts can be produced, what difference does it really make how its done, users are just interested in the artifcats not how they're made. If we have aggregated jars they can be made with the shade plugin or assembly plugin or several other ways, maven users could use the pom type features or just depend on the module jars to get the transitive dependencies, all the approaches work, what happens inside the build to produce the artifacts seems minor, this question you have next seems like the important thing - > Another useful question is what should the output > artifacts be. From past discussion we seem to need... > > - full set of Tuscany jars and their dependencies (either naturally > OSGi or converted to OSGi by Tuscany) should the user whish to pick > and choose, or more importantly replace, individual parts of the > runtime > - shaded jars that present core and extensions that can be easily > combined on the classpath to create a working runtime > - suitable OGSi configuration to allow both OSGi runtime and Eclipse > target platform to be configured with Tuscany and dependency Jars. > The things i think we've seen users want is: - clear dependencies - less jars is easier - support for non-maven use Having just a single binary distribution with everything in a single modules directory makes it difficult to do anything but take all 200+ jars at 80+Meg. The shaded and -nodep jars in a separate more structured lib directory make it a bit easier, what alternatives are there so that the distribution isn't so all or nothing? ...ant
