I just used a work around for this but I'm not sure if it's a good permanent solution. You can keep your project as an apklib. Maven will actually build the jar in the process of producing the apklib. The problem is it doesn't publish it. You can have this deployed for other projects using the attach-artifact goal of the build-helper-maven-plugin like this:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>build-helper-maven-plugin</artifactId>
<version>1.4</version>
<executions>
<execution>
<id>attach-jar</id>
<phase>package</phase>
<goals>
<goal>attach-artifact</goal>
</goals>
<configuration>
<artifacts>
<artifact>
<file>${project.build.directory}/${project.build.finalName}.jar</file>
<type>jar</type>
</artifact>
</artifacts>
</configuration>
</execution>
</executions>
</plugin>