snip....
>
> Yes that what the current compact distribution does, its in 1.x right now
> as there's few extensions going in 2.x but there should be no problems with
> doing it there too.
>
> ...ant
>
> I looked at the compact distro in 1.x and the distro projects in 2.x and
this is what I found:
Key
Plain text = common between the two
[] = different between the two
* = my opinion
A set of maven modules which define dependencies for features
[in /modules or /distribution]
* I prefer /distribution as the feature modules are not providing any new
function
Samples depend on only the feature modules that they require
An "all" distribution that ships all features
[separate distributions that ship individual features]
* I don't mind having them if people want to support them.
* I suggest though in this first instance (M1) we just ship the "all"
distro and we can see how we get on with that. This is still build from the
separate feature modules.
[separate tuscany jars vs feature jars]
* I don't particularly like the feature jars as it's another step to go
wrong. In particular it uses the shade(?) plugin and you have to configure
transformers.
[Launcher vs manually specified classpath comes into this]
* Manual classpath is easier with feature jars. Can we use a
different approach to support the manual classpath? Manifest jars for each
feature?
[structured libraries directory]
* I like this. It gives some sense of order to the distro lib directory.
Some other distro thoughts came to mind as I went through:
1/ Can we do something about 3rd party licenses? E.g. automate the command
line tools we have that check distro jars are represented in the LICENSE
file so that this happens automatically when distro is built. Also
it would be nice to have a tool that checks that module NOTICE/LICENSE files
match the requirements of the source that they hold. This last is manual at
the moment.
2/ We need to follow through on the reason Raymond started this thread
originally and ensure that samples are tested in the ways that a user will
run then when the distribution is built.
3/ As per 2/ but for webapp samples. Can we re-use some of the work that was
done for webapps in 1.x itest?
I'm happy to help with any of these.
Simon
