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 coordi
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
> ".substvars" file.
Great! This is something that has been on my TODO list for a long time.
How di
One of the differences between "mh_resolve_dependencies" and "mh_shlibdeps" is
that "mh_shlibdeps" uses Maven Resolver to resolve dependencies, thus being
able to better handle POM elements like variable substitutions, ignores, and
inheritance. Though it can't handle version ranges since Maven R
Hi,
Am 16.02.2018 um 15:47 schrieb 殷啟聰 | Kai-Chung Yan:
> I wrote 2 Debhelper plugins for easing maintenance of packages with Maven
> artifacts. They are in a new package called "maven-repo-helper-extras" [1].
>
> "mh_shlibdeps" works just like "dh_shlibdeps". It examines the Maven
> artifacts
I wrote 2 Debhelper plugins for easing maintenance of packages with Maven
artifacts. They are in a new package called "maven-repo-helper-extras" [1].
"mh_shlibdeps" works just like "dh_shlibdeps". It examines the Maven artifacts
installed by a package and generate "${maven:Depends}" in a
".subs
5 matches
Mail list logo