On Wed, Aug 31, 2016 at 12:28 PM, Guillaume Delhumeau <[email protected]> wrote:
2016-08-30 10:16 GMT+02:00 Vincent Massol <[email protected]>:
On 29 Aug 2016, at 14:16, Guillaume Delhumeau < [email protected]> 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?
In that case we can follow your proposal, having an "extensions" directory in the WAR which are automatically installed when XWiki is started. Inside this directory, we should also bundle XARs extensions so that "ui-all" xar become useless and we can drop it.
This is http://jira.xwiki.org/browse/XE-1420 but as Vincent said in the issue it only make sense for a flavor that would provide its own WAR (what XE currently does but we are supposed to stop that at some point and only provide a flavor). When you only have a minimal WAR for which you choose a Flavor at startup it does not really make much sense.
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] _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Guillaume Delhumeau ([email protected]) Research & Development Engineer at XWiki SAS Committer on the XWiki.org project _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne