Good morning,
I thought I was done with my conversion to maven. I’m really close I think. I just have this unit tests that use JavaMemoryAdaptor that are failing when I build from the command line. They run successfully inside Eclipse. When I run in Eclipse I see that EOAdaptor gets the framework bundle for JavaMemoryAdaptor: In Eclipse this bundle is an NSFluffyBunnyProjectBundle to the path to the JavaMemoryAdaptor project directory in Eclipse. When running from the command line it is an NSLegacyBundle with a path to the jar file for JavaMemoryAdaptor in the .m2 repository. Now, if you inspect the info dictionary of each bundle I see that the fluffy bunny is simpler and contains an entry with the key EOAdaptorClassName. The legacy bundle does not have an entry for the key EOAdaptorClassName. This causes an exception when EOF tries to get the adaptor. The exact error is: Unable to get the name of the class to instantiate for the adaptor framework JavaMemoryAdaptor. The possible causes for this error are: the adaptor framework is not installed on your system, the adaptor framework is not linked into your application, or the info dictionary for this adaptor is corrupted. Does anybody have any ideas or understanding of where this EOAdaptorClassName is defined and how is it supposed to end up in the info dictionary? I can see that ~/.m2/repository/wonder/eoadaptors/JavaMemoryAdaptor/7.5-SNAPSHOT/JavaMemoryAdaptor-7.5-SANPSHOT.jar has a Resources/Info.plist but it is missing the EOAdaptorClassName in it. Does anybody have any pointers for this problem? I suspect that if I can get EOAdaptorClassName to be there in the Resources/Info.plist then things will start working again. I see that wonder/Frameworks/EOAdaptors/JavaMemoryAdaptor/build.properties has this property: eoAdaptorClassName=er.memory.adaptor.ERMemoryAdaptor Is this the key that is supposed to be present in the Info.plist? But here the case is different, e.g. eoAdaptorClassName vs EOAdaptorClassName. Thank you Ricardo Parada
