Jboss-serialization is now dependent on trove.jar. I used that to solve circular dependencies, and it was way
better to use TIntObjectHashMap and TObjectIntHashMap. And jboss-serialization is included into /client/jboss-all.jar. So, what should I do before GA? Basically I have three
options: I – Remove jboss-serialization.jar from /jboss-all.
Since JMS is using it, I don’t know if this is a good idea, but I’m
considering this option. II – add trove.jar into jboss-all. Sincie it’s a
third-party, I don’t know if we want to do that. III – Keep as is now |
- [JBoss-dev] jboss-serialization dependent on trove.jar Clebert Suconic
- RE: [JBoss-dev] jboss-serialization dependent on trov... Clebert Suconic