Cannot resolve @StorIOSQLiteCreator #727
Comments
|
Version with |
|
Well, it's slightly confusing if you are adding unreleased features into your README :) Is it possible to use a snapshot version? |
|
I understand you. It is particularly my fault since I have done PR with README update, but I didn't expect that it will be merged before the new version. Sorry for the confusion. |
|
A snapshot version will be really awesome. If that doesn't happen, we'll be forced to use something else :( |
|
We'll try to do release soon, don't worry :)
…On 6 Dec 2016 4:09 pm, "Saket Narayan" ***@***.***> wrote:
A snapshot version will be really awesome. If that doesn't happen, we'll
be forced to use something else :(
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#727 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA7B3Pn_F6hT7rW3uvwMbGU1wpzRQuBXks5rFV6dgaJpZM4LFXHh>
.
|
|
@Saketme check please 1.12.0! |
|
@nikitin-da I'm seeing this error:
|
|
@Saketme can you please show your class if it is possible? |
|
Daaamn. @geralt-encore looks like because of annotation processing rounds our annotation processor sees class generated by AutoValue, or I'm wrong |
|
Sure, but can I email it to you instead? |
|
@Saketme there is no more need I have been able to reproduce it. |
|
Nono, wait, no specific ignores, we need to find more general solution, I'm
pretty sure we can force it to inherit class level annotations too or
otherwise prevent it from inheriting any of our annotations!
…On Fri, Dec 16, 2016, 14:34 Ilya Zorin ***@***.***> wrote:
@Saketme <https://github.com/Saketme> there is no more need I have been
able to reproduce it.
@artem-zinnatullin <https://github.com/artem-zinnatullin> the problem is,
that AutoValue classes also inherit annotations from the original class
methods. I think that the easiest solutions will be skipping classes which
names start from AutoValue_.
I am deeply sorry because this is completely my fault and lack of proper
testing. I was testing it using just regular abstract java classes assuming
that it will be the same for AutoValue case.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#727 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA7B3P1zn9JaNtAxyCrJ2ruINw6pOc_Uks5rIncpgaJpZM4LFXHh>
.
|
|
Inherit class level annotation is not an option because then we will get two tables and that is not what we really need. After quick googling I haven't found anything related to annotations inheritance in AutoValue. |
|
I believe it's not AutoValue specific, I remember facing pretty similar
behavior but with Reflection lookup for child classes.
…On Fri, Dec 16, 2016, 15:16 Ilya Zorin ***@***.***> wrote:
Inherit class level annotation is not an option because then we will get
two tables and that is not what we really need. After quick googling I
haven't found anything related to annotations inheritance in AutoValue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#727 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA7B3NwymTY9Q9ZpCHGBK8ckvbzfHCZAks5rIoECgaJpZM4LFXHh>
.
|
|
I think it has to be AutoValue specific because I remember that while working on others project annotation processor it didn't come up by default. |
|
Well, ok let's start with specific thing and then try to generalize it
…On Fri, Dec 16, 2016, 15:54 Ilya Zorin ***@***.***> wrote:
I think it has to be AutoValue specific because I remember that while
working on others project annotation processor it didn't come up by default.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#727 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA7B3CJOkdIXT2WA3aMVY0zNV5lQr030ks5rIooBgaJpZM4LFXHh>
.
|
|
@artem-zinnatullin so specific ignore then or you have a better idea? |
|
We can start with specific ignore. Or what about checking parent class
annotations and skip classes that have our annotations on parents?
…On Fri, Dec 16, 2016, 20:26 Ilya Zorin ***@***.***> wrote:
@artem-zinnatullin <https://github.com/artem-zinnatullin> so specific
ignore then or you have a better idea?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#727 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA7B3O5cLB8tFg8eaLKhRyE6lCnk2qvwks5rIsnMgaJpZM4LFXHh>
.
|
|
I also was thinking about it but then I thought that if we want to introduce support for inheritance in future it might be a bad idea. |
|
Well, then child class will also need class level annotation and everything
will be ok!
…On Sat, Dec 17, 2016, 00:30 Ilya Zorin ***@***.***> wrote:
I also was thinking about it but then I thought that if we want to
introduce support for inheritance in future it might be a bad idea.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#727 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA7B3AtzcDkFpxFlOC4YI-1KAwrPJodAks5rIwMNgaJpZM4LFXHh>
.
|
|
@Saketme please verify that the issue is fixed in the latest version. |
|
@geralt-encore I'm sorry, I didn't realize a fix has already been released. I will test the new version and report back. |
|
Closing. Feel free to reopen if you met some problems |
Hello, I'm using the latest version of the library (1.11.0) and I cannot seem to be able to find
@StorIOSQLiteCreator. I've these dependencies in mybuild.gradlefile:Any idea what I'm missing?
The text was updated successfully, but these errors were encountered: