Separate ButterFaces and PrimeFaces pages to different wars

[ggam]

Having PrimeFaces, ButterFaces and OmniFaces along with BootsFaces on the showcase clutters the classpath and we run the risk of some of those libraries changing some behavior without our knowledge.

I propose to separate the showcase into 3 different wars, deployed on the following context roots:

• /showcase: bootsfaces+omnifaces
• /showcase/primefaces: bsf+of+primefaces
• /showcase/butterfaces: bsf+of+butterfaces

I think we can remain using OmniFaces as it is a must for every new JSF application anyway. It solves some problems and I think we should even recomend to use it.

I think Maven can be instructed to output different artifacts from just one compilation like if it was an EAR.

[stephanrauh]

Another option is to drop support for ButterFaces because of two reasons: we don't have enough developers to really support it, and BootsFaces has recently acquired many components previously offered exclusively by ButterFaces. On the other hand, I'm not sure I really want to do this to Lars Michaelis.

[ggam]

ButterFaces link has been removed on https://github.com/TheCoder4eu/BootsFacesWeb/commit/528061790c8b50aa7294318df6ca689154075a9d

Can the dependency be removed? I'm just seeking for a cleaner classpath. Also, PrimeFaces has just released 6.1. Should we update that?