Thanks for taking a look.
At first, I tried doing exactly that, just copying the libgdx Array, ObjectMap and Pool over. However, they had too many other dependencies in libgdx to do it cleanly, so I decided to bite the bullet and just make libgdx a dependency.
As for package structure, I agree that it would be better to keep the original one. However, I'm hoping to roll this into libgdx as an extension and figured that I might as well adjust the package structure to make it more suitable to do so.
To be honest I wasn't a huge fan of how things were organized in artemis. They were trying to be extra safe with encapsulation by relying heavily on private and package protected fields/methods. This made rolling a custom Enity and Component managers, for instance, a huge pain. (which what I tried to do first to implement pooling) I wanted to make Artemis more open for extension without having to jump too many hoops.
I submitted an issue to libgdx github wrt this project:
https://github.com/libgdx/libgdx/issues/789I wouldn't mind rolling the package structure back, but that depends on whether libgdx guys are willing to add this as an extension.