|Re: Changing the classpath of an exported product [message #519942 is a reply to message #519925]
||Wed, 10 March 2010 15:00
| Paul Webster
Registered: July 2009
You could include an extra plugin that contains only config files, and |
exports them so they can be seen.
It could be a Configuration feature (and enjoy all the benefits of p2,
update sites, being upgradable, and installable).
Or you could just make a simple bundle with the configuration files and
put it in the dropins folder.
Would that work? That would make them all OSGi, support versioning and
Other than that, in theory you could add your config directory to the
boot class path, that might make them available:
|Re: Changing the classpath of an exported product [message #520478 is a reply to message #519942]
||Fri, 12 March 2010 14:37
| Roel De Nijs
Registered: March 2010
I tried 2 of your suggestions:
1/ appending to the boot class path: works just fine. when you start the application and print the system property you can see that the configuration directory is appended to the boot class path. And the config file is found by Spring, so Spring is happy (and I'm happy too)
2/ I tried to use the dropins folder, but that didn't work. I just created a plugin project containing my config file, I exported this plugin (as deployable plugin), added it to the dropins folder, started the application but it is just ignored and so Spring was not happy at all.
I tried to install the WTP project in my eclipse for plugin developers and that worked without any problem. I tried to do the same with our exported product (export the product, move our feature and plugins to the dropin folder), but that won't work (Application "..." could not be found in the registry).
Nonetheless I'm glad it works with the boot class path.
Many thanks for your time and effort!
Powered by FUDForum
. Page generated in 0.02609 seconds