| Age | Commit message (Collapse) | Author |
|---|
|
This reverts commit 9f6a119c8aa276432ece4fe2118bd8a3c9b1067e.
|
|
Change-Id: I3ffafdab27cc4aca256c3a5806b630795b75d5c8
|
|
|
|
Bug: http://code.google.com/p/android/issues/detail?id=18497
Change-Id: I152416022524d2860cb16b46c4812c5be6bdcbad
|
|
Merge commit '747cb3b515e1b01f6b61ec911b693d88d480eaaf'
* commit '747cb3b515e1b01f6b61ec911b693d88d480eaaf':
Make aidl annotate onTransact with @Override
|
|
BUG: 1902262
|
|
|
|
|
|
AIDL generates unnecessary "import" statements. These cause warnings
within Eclipse when the default Eclipse warnings settings are used.
This is inconvenient since the generated .java files are not
editable. Some pesky organisations have a zero-warnings policy
too, so there's no option but to fiddle with the Eclipse settings.
This patch ensures that all usages of class names within the
generated code are fully-qualified. In practice, they were nearly
all fully-qualified already. And this patch also removes the
generation of the import statements, since they are redundant
if we're using fully-qualified names everywhere.
This should fix issue 43 in the Google Code Android issues tracker.
http://code.google.com/p/android/issues/detail?id=43
I would appreciate if somebody who knows exactly how 'aidl'
works could confirm that there's no reason 'import' statements
would have been necessary except for the bits I've fixed. (I think
unqualified names were used much more frequently in early versions
of aidl, which might explain why import statements are generated
so eagerly).
|
|
|
|
|
|
Fixes build with gcc 4.3.2
Signed-off-by: Alexey Zaytsev <alexey.zaytsev@gmail.com>
|
|
|
