Move annotations into runtime, decouple compiler from annotations.

[JakeWharton]

For various reasons, we need to kill the annotations artifact and move it into the runtime. The compiler will not be able to reference the annotation types directly.

This is annoying, but doable. Annotation information is available via AnnotationMirror instances from which AnnotationValue instances can be pulled. auto/common has some helpers here, and we'll have to write some of our own as well.

Tests for the compiler will move into the runtime's tests which will allow them to reference Android types and runtime types without issue.

[JakeWharton]

Dagger also does this, but it predates auto/common.

[JakeWharton]

Thinking we want:

public AnnotationMirror findAnnotation(ExecutableElement element, String annotationFqcn);
public Map<String, Object> annotationProperties(AnnotationMirror annotation);

[JakeWharton]

This has no public-facing impact, so I'm going to punt from v8 as it's complicated and I don't want to block release.

[tasomaniac]

When are you planning to release v8?

[JakeWharton]

No plans at this time.

On Mon, Nov 9, 2015, 9:05 AM Said Tahsin Dane [email protected]
wrote:

When are you planning to release v8?

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

[lhunath]

Is anything holding back the release of the current snapshot version of v8?

[JakeWharton]

Yes

On Wed, Feb 3, 2016 at 11:11 AM Maarten Billemont [email protected]
wrote:

Is anything holding back the release of the current snapshot version of v8?

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

[lhunath]

Anything the community can do to remove roadblocks?

[fengdai]

For various reasons

What are the reasons?