OK I mixed a bit the number after a last miute refactoring of the mail... On Fri, Feb 6, 2015 at 11:09 AM, Thomas Mortagne <[email protected]> wrote: > Hi devs, > > There is many ways to make an extension a flavor and we need to chose one. > > Here are a few I have in mind: > > 1) Extension of type FLAVOR (compared to XAR and JAR types for example) > 2) A Boolean indicating if an extension is a flavor
> 2) A tag "Flavor" (or some of the name to be decided later) > 3) A unique category "Flavor" (or some of the name to be decided later) It's of course 3) A tag "Flavor" (or some other name to be decided later) 4) A unique category "Flavor" (or some other name to be decided later) > > I don't like 1) because a flavor does have anything special and I > don't see the point of reimplementing a new extension type handler > just to make an extension a flavor. > > I'm really not a fan for 2) either since it would makes this part of > the core of extension API which I really don't like since flavor are > XWiki runtime specific while you can use the xwiki-commons part of > Extension Manager for many use cases that don't have anything to do > with XWiki right now. > > So I'm hesitating between 3) and 4). When I started thinking about it > I was more into 3) since we already have tags in XWiki Repository but > since I saw that in both Android and IOS each application is in a > unique category I'm tempted to change my mind and give my +1 to 3). I'm sure you understood it's 4) here :) > Plus exposing categories is a nice new feature anyway. > > -- > Thomas Mortagne -- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
