Greetings all,
I recently listened to a talk from Gunnar about the EBR tool. I have some suggestions and would like to contribute when I can.
- It would be nice if the tool automatically set the dependency versions based on the pom.xml of the library that it’s creating the bundle for
- Optionally it would be nice if the tool could create a Blueprint file based on any spring context files found in the library (both to expose beans and to inject them from other bundles)
- Create a plugin for Nexus where if a group ending in “.ebr” is requested and the artifact does not exist, auto-generate the library using the EBR tool. Additionally the generated project should be checked
into a configured source repository.
Converting an existing Spring project to OSGi with lots of dependencies is a real hassle. These three items would be drastically reduce the cost of this kind of migration. It would not be perfect and some of the projects would need
to be touched after they have been auto-generated, but I think it’s a worthwhile goal.
What do you guys think? Too ambitious? Outside the scope of what EBR is supposed to do? What can I help with first (even if it’s not one of the items above)?
Thank you,
Justin Rosenberg
| Software Architect | Corporate Development Team | CRL Global Services
rosenbergj@xxxxxxxxxxx
|
www.crlcorp.com