G
Giovanni Azua
hi,
I am close to releasing an OS project (Maven multi-module project) and I
wonder what is best for the downloads section ...
- All delivered jar separately: users have to get the needed dependencies on
their own (is listed in the dependencies report)
- A tarball per project including cumulative dependencies e.g.
sub-module A (tarball including only jar A, documentation, maven
project etc)
sub-module B depends on A (tarball including jar A and B, all the rest
for both)
or
- A tarball per project with non cumulative dependencies e.g.
sub-module A (tarball including only jar A, documentation, maven
project etc)
sub-module B depends on A (tarball including only jar B,
documentation, maven project etc)
- Create bin and src distributions separately per project or just ship all
together?
IMO if I want to get an OS download I don't like to have to think what to
get but rather download the one or two choices not more. However with
multi-module projects it gets a bit hairy.
TIA,
regards,
Giovanni
I am close to releasing an OS project (Maven multi-module project) and I
wonder what is best for the downloads section ...
- All delivered jar separately: users have to get the needed dependencies on
their own (is listed in the dependencies report)
- A tarball per project including cumulative dependencies e.g.
sub-module A (tarball including only jar A, documentation, maven
project etc)
sub-module B depends on A (tarball including jar A and B, all the rest
for both)
or
- A tarball per project with non cumulative dependencies e.g.
sub-module A (tarball including only jar A, documentation, maven
project etc)
sub-module B depends on A (tarball including only jar B,
documentation, maven project etc)
- Create bin and src distributions separately per project or just ship all
together?
IMO if I want to get an OS download I don't like to have to think what to
get but rather download the one or two choices not more. However with
multi-module projects it gets a bit hairy.
TIA,
regards,
Giovanni