| Issue 24: | Be OSGi compliant | |
| 1 person starred this issue and may be notified of changes. | Back to list |
- Needs a real usecase scenario, but chances are that cglib and the fact that we deal with user domain classes could be a pain - There is an attempt at a clean separation between internal.* and non internal packages, but there may be some leakage
Aug 2, 2009
Project Member
#1
eric.bot...@gmail.com
Labels:
Milestone-Release2.0
|