the way I've envisioned it: - There is no dedicated EE API (none that I could find that is EE only, except for perhaps session scoped)t - There is SE specific API and the current API could be considered "core" Take the current API module and create two submodules, one for core and one for SE. SE depends on core. EE still refers to core as the same existing coordinates (create new coordinates for the parent). ------------------------------------------------------------------------ *From:* cdi-dev-bounces(a)lists.jboss.org <cdi-dev-bounces(a)lists.jboss.org&gt; on behalf of Antoine Sabot-Durand <antoine(a)sabot-durand.net&gt; *Sent:* Wednesday, October 12, 2016 5:18 AM *To:* cdi-dev *Subject:* [cdi-dev] Spliting SE package in an independent jar to avoid including CDI SE features in Java EE, we already talk about creating a specific SE jar. Any thought on this approach? Antoine ------------------------------------------------------------------------ NOTICE: This e-mail message and any attachments may contain confidential, proprietary, and/or privileged information which should be treated accordingly. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this message, and destroy all physical and electronic copies. Thank you. _______________________________________________ cdi-dev mailing list cdi-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/cdi-dev Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.