Re: [xwiki-devs] Approach for extensions with multiple dependencies ?

Hi all, Developping the mail archive, I realize that this app (that will consist of extension .xar + component .jar) will have many dependencies on other extensions. To cite only some, there will be : mktree, tabs, livetable export to excel, ratings, ... When possible I try to make these dependencies optional : if you want the related feature, install the extension and check the option (for ex. livetable export to excel). But some dependencies will be mandatory anyway. To prepare things correctly in advance, what is the best approach in this case ? Do I only need to list the dependencies, and prevent users that to install my app, they need to install the other extensions as prerequisites ? Can it be managed automatically by the extension manager during install of my app (it would install the others before) ?

Or should I package all these inside my own app for sake of simplicity ? (but it's ugly) Thanks, Jeremie -- View this message in context: http://xwiki.475771.n2.nabble.com/Approach-for-extensions-with-multiple-dep… Sent from the XWiki- Dev mailing list archive at Nabble.com. _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs