The definition of EPP is a bit wrong, let me try to rephrase.
EPP embeds EAP which is a 'productized' version of a fork of JBoss AS and a 'productized' version of a fork of GateIn (for EPP5).
By productized I mean:
- Much more intensively tested in QA Lab (Everything that is too time consuming for a project release, such as intensive clustering testing, performance tests, soak testing. But also manual tests)
- Carefully stable, only bug fixes go in EPP, no new feature
- Sanitized, non production-ready feature are removed
(EPP also comes with other aspects such as legal protection, support contracts with SLA, Documentation targetted to the platform... But I stick with code here)
GateIn requires at a bare minimum a servlet container (Tomcat which is also embedded in JBoss AS/EAP). For advanced features and for support it requires JBoss AS (For HA aspect, WSRP...). JBoss Portal requires JBoss AS/EAP.
Note that both projects come with bundled version ie you just download a zip and run the .bat or .sh without having to do any installation process.
EPP 4.3 used EAP 4.3 and a fork of JBoss Portal 2.7
EPP 5 (due in May) will use EAP 5 and a fork of GateIn 3.0
There is no plan to port the JBoss Poral CMS module to GateIn, so for a new approach, I would suggest eXo ECM/WCM or any other alternative.
Hope this helps
The product is called Enterprise Portal Platform.
GateIn is the only association of letters, less than 10 in total and that doesn't have a trademark (And yes it's too late, but yeah we fought for months up to this name, it was definitely not my favorite proposal but the only one our legal team would accept).