1. Search all POMs inside the Maven repository of a binary package. 2. Read their coordinates (group:artifact:version:packaging). 3. Use Maven Resolver (formerly Eclipse Aether) to resolve the direct dependencies. 4. Write substvars.
The weak point is at the second step, where I read their coordinates only by reading the XML myself, thus will fail to handle stuff like property substitution. I don't know if Maven's own POM parser [1] can handle these situations, and unfortunately Maven Resolver doesn't read POM for you until you have a coordinate at hand. [1]: https://maven.apache.org/ref/current/apidocs/org/apache/maven/model/io/xpp3/MavenXpp3Reader.html Emmanuel Bourg 於 2018年02月20日 星期二 07:48 上午 寫道: > Le 16/02/2018 à 15:47, 殷啟聰 | Kai-Chung Yan a écrit : > >> "mh_shlibdeps" works just like "dh_shlibdeps". It examines the Maven >> artifacts installed by a package and generate "${maven:Depends}" in a >> "<package>.substvars" file. > Great! This is something that has been on my TODO list for a long time. > How did you implement it? > > Emmanuel Bourg >
signature.asc
Description: OpenPGP digital signature
