Can I license my project under GPL when I use Apache-licensed libraries?

Question

First off, I know that I officially have to ask questions concerning licenses on the Open Source community but I've seen enough questions about it here and posts there get as much views in a day as you'd get here in about 3 minutes.

That said, I have done quite some research already and I think I know the answer to my question but I want to be sure I get this right. I've spent too much time on my project over the last few years to screw it all up with a wrong license.

I'm currently working on an Android application which I want to release as open source at a later moment. I want everyone to be able to contribute to the project but I also want forks of the project to be open source. That's why I initially chose GPLv2 as my license, but I've been reading that it's very restrictive in its 'openness'. At the moment I'm only using Apache v2.0-licensed libraries in my project and as far as I was able to find, the Apache v2.0 license is compatible with GPLv2.

TL;DR
Am I allowed to license and distribute my Android project under GPLv2 when it consists of Apache v2.0-licensed libraries and the code I've written myself? Or is there a better alternative for my wishes?

Answer 1

The Apache Foundation has a document about GPL compatibility.

Choice quotes:

Apache 2 software can therefore be included in GPLv3 projects, because the GPLv3 license accepts our software into GPLv3 works. However, GPLv3 software cannot be included in Apache projects.

Despite our best efforts, the FSF has never considered the Apache License to be compatible with GPL version 2

So it seems you should be fine with including Apache code in GPLv3 projects (not such much with GPLv2).

For the practical aspects of how to include non-GPL code into GPL projects also see this advice from the Software Freedom Law Center.