Question: I tried modifying the vibration pattern with the build hint android.pushVibratePattern = 1000 and did not have any luck.
Thank you all in advance!

Answer: 
As specified by the [`maven-assembly-plugin`](http://maven.apache.org/plugins/maven-assembly-plugin/) documentation:

> 
> If your project wants to package your artifact in an uber-jar, the assembly plugin provides only basic support. For more control, use the **Maven Shade Plugin**.
> 
> 
> 

---

Using the [`maven-shade-plugin`](https://maven.apache.org/plugins/maven-shade-plugin) you can have a fat jar (like using the assembly plugin) and solve similar issues of merging file using [Resources transformers](https://maven.apache.org/plugins/maven-shade-plugin/examples/resource-transformers.html). In your case, the [`AppendingTransformer`](https://maven.apache.org/plugins/maven-shade-plugin/examples/resource-transformers.html#AppendingTransformer) would merge files with the same name but with different content.

> 
> Some jars contain additional resources (such as properties files) that have the same file name. To avoid overwriting, you can opt to merge them by appending their content into one file. 
> 
> 
> 

A simple configuration would look like:

```
<build>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-shade-plugin</artifactId>
            <version>2.4.3</version>
            <executions>
                <execution>
                    <phase>package</phase>
                    <goals>
                        <goal>shade</goal>
                    </goals>
                    <configuration>
                        <transformers>
                            <transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer">
                                <resource>path/to/file/file-name-here</resource>
                            </transformer>
                        </transformers>
                    </configuration>
                </execution>
            </executions>
        </plugin>
    </plugins>
</build>

```

---

**Update**  

You don't need an external assembly descriptor for the shade plugin, you can configure your requirements directly as plugin configuration.  

In your case, to exclude resources from assembled jars, you can use [shade filters](https://maven.apache.org/plugins/maven-shade-plugin/examples/includes-excludes.html).

A simple configuration (to be merged with the one above) would look like:

```
<configuration>
    <filters>
        <filter>
            <artifact>*:*</artifact>
            <excludes>
                <exclude>**/*Resources_*</exclude>
                <exclude>**/*ErrorsText_*</exclude>
            </excludes>
        </filter>
    </filters>
</configuration>

```
Also encountered this issue, my need was to filter out resource files of the same name from dependency modules, solution like below:

```
<plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-shade-plugin</artifactId>
            <version>2.4.3</version>
            <executions>
                <execution>
                    <phase>package</phase>
                    <goals>
                        <goal>shade</goal>
                    </goals>
                    <configuration>
                        <filters>
                            <filter>
                                <artifact>artifact1</artifact>
                                <excludes>
                                    <exclude>application.yml</exclude>
                                    <exclude>logging.yml</exclude>
                                </excludes>
                            </filter>
                            <filter>
                                <artifact>artifact2</artifact>
                                <excludes>
                                    <exclude>application.yml</exclude>
                                    <exclude>logging.yml</exclude>
                                </excludes>
                            </filter>
                            <filter>
                                <artifact>*:*</artifact>
                                <excludes>
                                    <exclude>META-INF/*.SF</exclude>
                                    <exclude>META-INF/*.DSA</exclude>
                                    <exclude>META-INF/*.RSA</exclude>
                                </excludes>
                            </filter>
                        </filters>
                    </configuration>
                </execution>
            </executions>
</plugin>

```

***note*** the lines below is to avoid possible exception:

> 
> Exception in thread "main" java.lang.SecurityException: Invalid signature file digest for Manifest main attributes
> 
> 
> 

```
<filter>
          <artifact>*:*</artifact>
          <excludes>
              <exclude>META-INF/*.SF</exclude>
              <exclude>META-INF/*.DSA</exclude>
              <exclude>META-INF/*.RSA</exclude>
          </excludes>
</filter>

```

In case you want more details, refer to [Selecting Contents for Uber JAR](https://maven.apache.org/plugins/maven-shade-plugin/examples/includes-excludes.html)