Question: PropertiesManager

[Coinhunter]

First, I'd like to say that this is likely more of a problem with gradle than it is owner, but since this is an issue that's likely to crop up for many projects wishing to utilize this lib I thought I'd post it anyway, and perhaps someone else will do some additional digging. So... I'm having problems using owner in a project because it seems not all of the beans get transitively added to the apk that I am building. The setup is of a multi-module type in android studio, because the android and java plugins for gradle don't quite get along, and the owner code resides in a pure java library.

  java.lang.NoClassDefFoundError: java.beans.PropertyEditorManager
        at org.aeonbits.owner.Converters$4.tryConvert(Converters.java:147)
        at org.aeonbits.owner.Converters.doConvert(Converters.java:227)
        at org.aeonbits.owner.Converters.convert(Converters.java:222)
        at org.aeonbits.owner.PropertiesInvocationHandler.resolveProperty(PropertiesInvocationHandler.java:83)
        at org.aeonbits.owner.PropertiesInvocationHandler.invoke(PropertiesInvocationHandler.java:54)
        at $Proxy2.local_server_url(Native Method)
        at se.springworks.api.client.M2HClient.<init>(M2HClient.java:40)
        at se.springworks.apiexample.androidexampleapp.ExampleActivity.onCreate(ExampleActivity.java:18)
        at android.app.Activity.performCreate(Activity.java:5426)
        at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1105)
        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2269)
        at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2363)
        at android.app.ActivityThread.access$900(ActivityThread.java:161)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1265)
        at android.os.Handler.dispatchMessage(Handler.java:102)
        at android.os.Looper.loop(Looper.java:157)
        at android.app.ActivityThread.main(ActivityThread.java:5356)
        at java.lang.reflect.Method.invokeNative(Native Method)
        at java.lang.reflect.Method.invoke(Method.java:515)
        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1265)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1081)
        at dalvik.system.NativeStart.main(Native Method)

The module that contains owner directly is free from this issue. What are your recommendations?

Also created a Stack Overflow q for this type of problem:

http://stackoverflow.com/questions/22988376/missing-runtime-dependencies-with-owner-gradle-for-android

If you feel this is completely removed from what you're trying to do here, don't hesitate to close the issue. : )

[lviggiano]

From my understanding, this happens because Android is missing most of the classes in java.beans package in its runtime environment (see for example java.beans package on JDK5).

Afaik, at the moment this can't be solved unless I reimplement those classes inside OWNER itself, or I find some library working with android that does the same job.

Thanks for opening the question on stackoverflow, I'll monitor that answer and see if someone comes with a suggestion about this.

I can definitely fix OWNER to work on android: a solution to this issue should not be difficult to implement, if there is something already available or if I can find a quick way to port the few java.beans classes used inside OWNER itself and package in an optional dependency (like owner-android-support.jar)

[lviggiano]

I'll try to come out with a quick solution asap, and provide you a fixed jar so you can test it on android/gradle and tell me if this is fixed.

[Coinhunter]

Oh I see, well that explains it. Yeah that would be awesome. 👍 : )

[lviggiano]

Would you be available to help me testing OWNER on android?

After fixing this issue, I can't exclude that some other issue can show up, since - afaik - nobody yet tried to use OWNER on android. So, if I can count on some help (also just for testing) from an android guy, I can for sure make OWNER android-compatible, I think.

[Coinhunter]

First, I should let you know that I'm not an "Android-guy" per se. I've been involved in a couple of projects but it's not my forte.

In this case I'm using it in a pure java library that Android then depends on, so I'll only find issues that are proximate. This might mean that I would miss things that would be issues if used directly in an Android project. I will say this though, I like what I've seen so far and will probably attempt to use it again when I find myself in need of configuration (which is likely to be soon). So no promises, but I'll likely be able to tell you when it breaks, and we do test our code. : )

[lviggiano]

No worries. You have already been very helpful.

Now I'm planning to set up some environment to test android compatibility, and offer full fledged support for android. The problem is always time shortage to do all the things I would like to do.

But this issue should be easy to fix.

[Coinhunter]

Will you let me know when there's a version out that solves this? : )

[lviggiano]

Of course!

Thank you.