We could tell people to create such descriptors for their applications if they're not recognized in the EM UI (as a transitional and migration solution) or we could provide these descriptors in updated versions of these apps, or both. > > All this said, I don't think we need to support any of this: > * the user knows what apps he has installed on his wiki > * thus in the EM UI he can pick a version greater than the one he has > installed locally and install it over the existing pages. A new revision > of the pages will be created. The only issue is if the user has modified > application pages and the way to solve it is by manually merging the > changes after having installed the new version. >
Indeed automagic "non-EM-installed plug-in discovery" might indeed be quite complex AI-like nice-to-have task not worth the effort. However following use case must be taken into account 1. Install XWiki without extension manager 2. Install several extensions (both *.jar and *.xar based) 3. Migrate to XWiki powered with extension manager 4. Try re-installing/updating already installed extensions 5*. The use case might be made more complex by dealing with different extensions versions (e.g. originally installed extension is far older than the current one available in EM, page deletions/renames in xars and updated dependency versions in jars should be taken into account) If there are conflicts expected with this use case - it would be nice to at least provide the migration guidelines - because they eventually those advices will occur here, on users[at]xwiki.org -- View this message in context: http://xwiki.475771.n2.nabble.com/Announcement-XWiki-Enterprise-and-XWiki-Enterprise-Manager-3-3-Milestone-2-Released-tp7027420p7028145.html Sent from the XWiki- Users mailing list archive at Nabble.com. _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
