Hi team,
I pray that you're all well.
I'm working on an enhancement to bnd to put file locking around the reading/writing of the launcher properties file. For proper testing, I need to be able to have another process to lock the file, so I've written a class that fires up a remote JVM and allows you to send commands to the JVM to lock/unlock files.
I'd like to use the class in tests in more than one project (in aQute.lib and in biz.aQute.launcher), so it would be nice if I could put it somewhere. However, given that the class is really only useful for testing, I don't want to put it somewhere where it will unnecessarily clutter bnd's application code.
Where is the best place in the bnd workspace to put a test utility class like this?
Blessings,
Fr Jeremy