# Package CDI support as a separate module

**URL:** <https://forum.liquibase.org/t/package-cdi-support-as-a-separate-module/2681>\
**Category:** Liquibase Development\
**Created:** [August 14, 2013, 5:32am UTC](https://forum.liquibase.org/t/package-cdi-support-as-a-separate-module/2681 "2013-08-14T05:32:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![David](https://avatars.discourse-cdn.com/v4/letter/d/aeb1de/32.png) [@David](https://forum.liquibase.org/u/David)\
**Post date:** [August 14, 2013, 5:32am UTC](https://forum.liquibase.org/t/package-cdi-support-as-a-separate-module/2681/1 "2013-08-14T05:32:00Z")

</div>

I’d like to suggest removing the CDI support from liquibase-core and packaging it as a separate module.&nbsp; The CDI code seems to work only with JBoss Weld and is effectively a poison-pill when deployed in an OpenEJB environment.&nbsp; It might be worth packaging all the flavors of integration separately.  
  
I have a fork, with a new liquibase-cdi module, that’s working well for me.&nbsp; I’ll try to keep it up to date.&nbsp; Please consider making this change.&nbsp; As it is, the CDI code is a show-stopper.  
  
djh

---

<div class="post-metadata">

**Author:** ![nvoxland](https://avatars.discourse-cdn.com/v4/letter/n/87869e/32.png) [@nvoxland](https://forum.liquibase.org/u/nvoxland)\
**Post date:** [August 14, 2013, 5:32am UTC](https://forum.liquibase.org/t/package-cdi-support-as-a-separate-module/2681/2 "2013-08-14T05:32:00Z")

</div>

I think that’s a good idea. I added it to 3.1 to pull out.

[https://liquibase.jira.com/browse/CORE-1409](https://liquibase.jira.com/browse/CORE-1409)

Nathan