You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it looks like the maven builds (both, self-built as well as on the public repository) do not include the EOAdaptorClassName key correctly. JavaMemoryAdaptor even includes an invalid Info.plist, as the customInfoPListContent is not set in Frameworks/EOAdaptors/JavaMemoryAdaptor/build.properties, which leaves a spurious ${customInfoPListContent} element in the generated Info.plist.
This only affects the maven builds, the ant builds seem fine. I do not (yet?) know enough of the build process to decide, if this is actually an issue with the wonder POMs or with the maven-wolifecycle-plugin from the wolips/woproject repo (although I'll gladly submit a pull request, if I find the core issue). Even if that's the case, the currently deployed JARs seem to be at least problematic, as the adaptors are not recognized as such due to the erroneous Resources/Info.plist.
As a workaround I added this for example to the JavaMemoryAdaptor/build.properties, but this of course does not fix the real issue:
Hello everyone,
it looks like the maven builds (both, self-built as well as on the public repository) do not include the EOAdaptorClassName key correctly. JavaMemoryAdaptor even includes an invalid Info.plist, as the customInfoPListContent is not set in Frameworks/EOAdaptors/JavaMemoryAdaptor/build.properties, which leaves a spurious ${customInfoPListContent} element in the generated Info.plist.
This only affects the maven builds, the ant builds seem fine. I do not (yet?) know enough of the build process to decide, if this is actually an issue with the wonder POMs or with the maven-wolifecycle-plugin from the wolips/woproject repo (although I'll gladly submit a pull request, if I find the core issue). Even if that's the case, the currently deployed JARs seem to be at least problematic, as the adaptors are not recognized as such due to the erroneous Resources/Info.plist.
As a workaround I added this for example to the JavaMemoryAdaptor/build.properties, but this of course does not fix the real issue:
The current on-line JARs are easily verifyable:
Greetings
The text was updated successfully, but these errors were encountered: