23 May
2012
23 May
'12
9:43 a.m.
On Tue, May 22, 2012 at 5:58 PM, Vincent Massol <vincent(a)massol.net> wrote:
Hi Caleb,
On May 22, 2012, at 5:00 PM, Caleb James DeLisle wrote:
Hi,
I understand we agreed in http://lists.xwiki.org/pipermail/devs/2012-March/050172.html to
stop
bundling legacy modules by default. What was not so clear is how we should do this.
I want to remove the modules from XE and Manager, and document the method of downloading
them from
maven.xwiki.org and replacing the existing .jar files with them.
It's not enough IMO. Here's a likely scenario:
* Users will download the version without legacy modules.
* Then they'll use the Extension Manager to install extensions from
extensions.xwiki.org
* The extensions will fail
* Users will ditch xwiki since it just doesn't work and the quality is perceived as
not good enough.
We need to solve this before we can stop bundling the legacy modules IMO.
Why:
#1. Not removing API is obviously unsustainable in the long term.
#2. Replacing core .jar files has been judged to be beyond the scope of the extension
manager.
Whether we want to support overriding classes using extensions as a "function
hooking" mechanism is a possible topic for future discussion.
#3. Replacing .jar files in the .war is not an excessively complex task, we ask users to
open the
war file for configuring a database or adding JDBC connectors, cases where there is much
less
technical need to require opening the .war file.
Here's my +1 to remove it ASAP, for 4.1M2 if we can get the tests passing.
-1 till we solve the question above. I'd rather
keep legacy modules than have dissatisfied users.
-1 for the same reason.
Thanks,
Marius
Thanks
-Vincent
Caleb
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs