Yes, you can do it. The general approach is to put the source library
someplace convenient to all the projects using it, getting it to build
independenly under Gradle, and then in projects that use it, add a module
and point the module to the directory where the module lives. You can do it
in settings.gradle like this:
include ':libraryName'
project(':libraryName').projectDir=new File('/path/to/library')
On Thu, Sep 18, 2014 at 9:46 AM, Ryan Bis <[email protected]> wrote:
> So when you import a source library, it seems to copy that library's
> contents into the current project.
>
> I have a library that is used with several different projects. This
> library has it's own repo (which is separate from the project's repo).
>
> So, as it seems AS copies the library into the project, what happens when
> that library's repo gets updated? Does this mean I have to copy these
> changes throughout all of my projects? Is there an easier way to set this
> up, so that I don't have to manually edit the library in every project that
> it's in?
>
> Thanks,
> Ryan
>
> --
> You received this message because you are subscribed to the Google Groups
> "adt-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
