On 14 Jan., 07:43, Jake Wharton <
jakewhar...@gmail.com> wrote:
> Yes I had assumed that this was going to come up sooner or later.
> Especially since I made the mistake of allowing this in v3.x.
>
> Currently, the compat lib plugin maven module consists of only the three
> files that need changed. During the generate-sources phase (the one that
> occurs immediately before compilation if you're not a maven user), a plugin
> explodes the binary compat lib .jar's classes into the destination
> directory. Then, when compilation occurs, our three source files overwrite
> the original three that were exploded from the .jar.
>
> I chose to do it this way so that I would only have to perform merges on 3
> files when a new version is released which should make my life a lot easier
> and that process a lot quicker.
>
> Now, that being said, it would be trivial to clone this module into a
> compat-lib-map folder and modify the FragmentActivity's class declaration
> to extend from MapActivity. Do I want to do this and distribute it,
> however, is the question.
>
> Ideally there would be an even more efficient way where duplicating the
> sources wasn't required, it would only copy everything from the normal
> compat-lib plugin and replace the class declaration.
>
> I will have to think on this over the weekend. Maybe we'll get lucky and
> get a proper MapFragment with the next revision of the compat lib (since it
> was alluded to in one of the developer chats) and the whole thing will be
> moot!
>
> ---