Issue 4794 - adblock engine creating/releasing concurrency

pom.xml

 <?xml version="1.0" encoding="UTF-8"?>
 <project xmlns="http://maven.apache.org/POM/4.0.0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
     <modelVersion>4.0.0</modelVersion>
 
     <groupId>org.adblockplus.libadblockplus.android</groupId>
     <artifactId>parent</artifactId>
     <version>1.0</version>
     <packaging>pom</packaging>
     <name>parent</name>
     
     <properties>
-        <selfVersion>1.0</selfVersion>
+        <selfVersion>1.1</selfVersion>

[anton, 2017/01/13 11:47:55]

this means all maven modules will have 1.1 as module version. this is in
contrast to gradle because gradle is referencing file path but not artifact
name+group+id. We can avoid using same module version for all modules if
required - depends on our agreement. 

[diegocarloslima, 2017/01/25 11:38:19]

Keeping all modules with the same version might be less error prone, but its a
bit weird to update the version of a module that hasn't changed (e.g. updating
the version of libadblockplus-android because of an update in
libadblockplus-android-webviewapp). Also, having different versions for the
module and in the manifest/build.gradle it's kinda of inconsistent. So I'm more
keen to have separate module versions

[anton, 2017/01/25 11:51:58]

Acknowledged. I will make maven and gradle module versions consistent

         <buildTools>22.0.1</buildTools>
     </properties>
 
     <modules>
         <module>libadblockplus-android</module>
         <module>libadblockplus-android-webview</module>
         <module>libadblockplus-android-settings</module>
         <module>libadblockplus-android-webviewapp</module>
     </modules>
     
 </project>