Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider moving @MoshiAdapterFactory into it's own artifact #67

Closed
vanniktech opened this issue Oct 28, 2016 · 1 comment
Closed

Consider moving @MoshiAdapterFactory into it's own artifact #67

vanniktech opened this issue Oct 28, 2016 · 1 comment

Comments

@vanniktech
Copy link

It'd be awesome if @MoshiAdapterFactory would be in it's own artifact so that one does not have to use the following:

provided 'com.ryanharter.auto.value:auto-value-moshi:0.4.1'

to add the annotation to the classpath. The big disadvantage is that all of the other classes are also added to the class path (AutoValue components, possible Guava etc).

@serj-lotutovici
Copy link
Contributor

Butterknife does something similar. There's an annotation artefact, that is shared between the runtime library and the annotation processor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants