Velocity in OSGi
On this page:
Symptoms — What Goes Wrong
When developing with Velocity in OSGi, you see some errors in the logs:
Velocity likes to use reflection to load a few classes. This means anything that generates your OSGi imports automatically will not pick up these classes. This includes the case when you let the Atlassian Plugin Framework generate your OSGi manifest for you.
This may not actually hurt your application, probably because after trying the context classloader, Velocity will try the classloader that originally loaded it, and hence find the libraries. Nevertheless, you may see the above errors in the logs.
To fix this, you will need to manually import the packages these classes are in. If using the Maven Bundle Plugin, add this line to the