30 Aug
2016
30 Aug
'16
10:16 a.m.
On 29 Aug 2016, at 14:16, Guillaume Delhumeau
<guillaume.delhumeau(a)xwiki.com> wrote:
OK so let me introduce my third (3) proposal properly.
You mean (4) (since mine was the (3) one ;)).
3.1 - Only one WAR, containing only what we consider
as core extensions.
There is nothing to exclude, we manually select the modules that are
indispensable so that oldcore and DW can run.
3.2 - For the Jetty/HSQLDB packaging, we use my plugin that pre-installs
the extensions needed by the default flavor.
3.3 - Drop support for "ui-all" xars. Knowing that in a near future, we
will let the user chose a flavor, we won't propose "ui-all" xars for all
of
them along with a proper WAR to run them.
I don’t know how many users use that but that’s probably low indeed.
My only problem with this is that I think this is how users who are offline can install
XWiki easily, no?
I think we do need to offer a way to install XWiki offline. It doesn’t have to be through
the ui-all XAR though. What do you suggest?
That should cover our use-cases.
Note that when multiple flavors will be released, we won't have a
Jetty/HSQLDB packaging for each one.
IMO, the XWiki Core Dev Team will only propose one real flavor (the replacement of XE - I
call it “Knowledge Base” but I don’t remember if we’ve finished our brainstorming on this
topic, probably not) so it shouldn’t be an issue.
Since Jetty/HSQLDB is for trial we shouldn’t have a package for the base flavor (which IMO
is only for OEM and thus don’t require a Jetty/HSQLDB packaging).
Thanks
-Vincent
[snip]