Convert project to library project

[NorseDreki]

Do you have plans to convert this project to library project so it can be packaged as JAR or AAR? It would me more handy to use it as standalone library rather than just add source files.

(Great work BTW, really helps me in debugging apps, using with HockeyApp and it works well)

[antoche]

I'm not actively working on this at the moment, so feel free to do it if you like. It does sound more practical indeed.

[NorseDreki]

The whole thing depends on each and every vendor's SDK. That would not be a good idea to include all of them to the project, since it will be bloated (and AFAIK most of people use single error reporter). Any ideas how to handle this?

[antoche]

That might have been the reason I didn't write it as a library in the first
place.

Is there a way to enable/disable compilation of portions of the code in
Java depending on whether the vendor's SDKs are present, sort of like
#ifdef in C?

On Sat, Jul 5, 2014 at 8:01 AM, Alexey Dmitriev notifications@github.com
wrote:

The whole thing depends on each and every vendor's SDK. That would not be
a good idea to include all of them to the project, since it will be bloated
(and AFAIK most of people use single error reporter). Any ideas how to
handle this?

—
Reply to this email directly or view it on GitHub
#1 (comment).

[NorseDreki]

It should be possible to use Gradle build flavors to accomplish this task. Then user would specify vendor's SDK (or either some of them?) to assemble a library file and use that file in his own project.

Now checking this out.

[NorseDreki]

BTW, do you know if it's OK to use vendor's SDK downloaded under private account? For example, Flurry gives you a link to SDK only after registration and logging in. So I'm wondering whether they generate user-specific package? Or, for example, FlurryAnalytics-3.3.3.jar is the same across all users so we can use it in your project?

[antoche]

If you can get the vendor's approval, that might make it simpler for the
library users, but that also means someone has to stay on top of things and
update the included SDKs every time a vendor updates it. It might make it a
bit of a pain.

If there was some central package repository like pypi or npm, things would
probably be simpler.

On Mon, Jul 7, 2014 at 10:13 AM, Alexey Dmitriev notifications@github.com
wrote:

BTW, do you know if it's OK to use vendor's SDK downloaded under private
account? For example, Flurry gives you a link to SDK only after
registration and logging in. So I'm wondering whether they generate
user-specific package? Or, for example, FlurryAnalytics-3.3.3.jar is the
same across all users so we can use it in your project?

—
Reply to this email directly or view it on GitHub
#1 (comment).