Closed Bug 885087 Opened 6 years ago Closed 6 years ago

Generated file mobile/android/base/braille/com/googlecode/eyesfree/braille/selfbraille/ISelfBrailleService.java left in $(SRCDIR)

Categories

(Firefox for Android :: General, defect)

All
Android
defect
Not set

Tracking

()

RESOLVED FIXED

People

(Reporter: nalexander, Unassigned)

References

Details

The committed patch for Bug 876475 includes the following files:

ISelfBrailleService.aidl
WriteData.aidl
WriteData.java

$(AIDL) generates ISelfBrailleService.java (and presumably WriteData.java).  We should not be checking generated .java files into the tree; we should not even be generating them into $(SRCDIR); and if we absolutely must, we should be listing them in /.hgignore.
The file generated in $(SRCDIR) was checked into the tree in bug 885298. (I agree it's not ideal but it was the least bad solution).
Status: NEW → RESOLVED
Closed: 6 years ago
Depends on: 885298
Resolution: --- → FIXED
(In reply to Kartikaya Gupta (email:kats@mozilla.com) from comment #1)
> The file generated in $(SRCDIR) was checked into the tree in bug 885298. (I
> agree it's not ideal but it was the least bad solution).

kats, I'm aware that this is part of 885298, and I'm not going to re-open immediately, but I am going to ask for an explanation of a) why this is "least bad" for one file and b) why the two generated files are treated differently.

If that's linking to a comment of 885298, so be it.
The initial landing checked in the three files you listed in comment 0. However, WriteData.aidl was only a support file, needed for ISelfBrailleService.aidl to be successfully processed by the aidl tool. The WriteData.java that was checked in is very different from the .aidl and shouldn't be considered a "generated file". [1]

With bug 885298 in the tree the "generated" ISelfBrailleService.java file is checked in, and no more aidl generation is happening. So at least the two .java files are being treated consistently. As for why this was the least bad solution, it is because the alternatives were either (a) bumping up the min SDK requirement to r21 or (b) disabling warning-as-errors. At least, that's my understanding of the problem from the IRC discussion [2].

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=876475#c24
[2] http://irclog.gr/#show/irc.mozilla.org/mobile/292822
You need to log in before you can comment on or make changes to this bug.