Bug#1093582: libautomaton-java: inconsistent JAR and POM placement

[Andrius Merkys]

Package: libautomaton-java
Version: 1.12-4+dfsg-1
Severity: important

Hello,

Recently, a bunch of packages build-depending on libautomaton-java 
started to FTBFS (see #1093346 for example). The reason seems to be an 
inconsistent placement of JAR and POM files:

$ tree /usr/share/maven-repo/dk/brics/
/usr/share/maven-repo/dk/brics/
└── automaton
     ├── 1.12-4
     │   └── automaton-1.12-4.jar -> 
../../../../../java/automaton-1.12-4+dfsg.jar
     ├── automaton
     │   ├── 1.11-8
     │   │   └── automaton-1.11-8.pom
     │   └── debian
     │       └── automaton-debian.pom
     └── debian
         └── automaton-debian.jar -> 
../../../../../java/automaton-1.12-4+dfsg.jar

This most likely has been broken due to automaton changing its 
groupId:artifactId. I see automaton carries an upstream- and Debian 
mantainer-provided POMs. Maybe the Debian-provided POM could be dropped 
in favor of the upstream-provided one?

Andrius