If you are interested in open source and privacy friendly android apps you should have a look at this two projects.
The group Privacy Friendly Apps are a collection of Android-Applications, which are optimized based on privacy. This means that only a minimum of permissions is used. There are no unnecessary permissions, e.g. a torch application would ask for a permission to read the contacts.
Simple Mobile Tools: A group of simple, stupid, open source Android apps with customizable widgets, without annoying ads and unnecessary permissions.
They develop camera, file-manager, gallery apps and more. You can find the apps on github/f-droid and play store.
On Infoq.com you can wath a presentation about that:
John Rizzo introduces Twitch’s chat’s architecture, telling how their engineers investigated and worked through the issues in what turned out to be a make-or-break situation for the company.
If you are using maven you may have been flabbergasted by an error like this
[ERROR] Non-resolvable parent POM: Failure to find at.test:test:pom:23 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 9, column 10
I had this error and was wondering why it was occurring? I had the parent artifact in my local repository. It was not missing. Maven did know this, because the log said
[DEBUG] Verifying availability of /home/stefon/.repository/at/test/test/23/test-23.pom from [central (http://repo.maven.apache.org/maven2, releases)]
So if I have the parent POM file in my repository and maven knows about it? Why are we getting an error?
As the file is not available on central, Maven will (correctly in my opinion) fail the build as the build would be non-reproducible.
So, what do we do if it is not possible to publish our parent pom artifact?
there is a CLI option that you can enabled in Maven 3.1.1 that tells Maven “I know what I am doing and don’t make that check this time” i.e. –legacy-local-repository
In other words:
mvn clean install --legacy-local-repository
Just remember: This is a hack and may break at any moment with a new maven version! There is an blog article where you can find other solutions for your problem
Java 8 is released since 2014. If you are working in an enterprise oriented company, chances are you are only now getting experience with usage of Java 8. You may ask yourself what this warning is telling you.
VM warning: ignoring option MaxPermSize=128M; support was removed in 8.0
Why is PermGen gone? An article of infoq.com tells you something of the reasoning behind this change.
If you are working behind a proxy and have to access git repositories on the internet via ssh (e.g. github), then you sooner or later (probably sooner) find out that this will not work out of the box. This is because you need to proxy your ssh connection. This summary on stackoverflow explains how to do this in a short but comprehensible manner.