Bug#895886: testng: jcommander classes not found

2018-04-17 Thread olivier sallou
Le mar. 17 avr. 2018 à 14:19, 殷啟聰 | Kai-Chung Yan a écrit : > Yeah, I misunderstood you too. > > Strange, if `htsjdk` does not configure `jcommander` in `maven.rules`, > `1.x` should have been replaced by `debian` on the fly. Maybe > `gradle-debian-helper` ignores test

Bug#895886: testng: jcommander classes not found

2018-04-17 Thread 殷啟聰 | Kai-Chung Yan
Yeah, I misunderstood you too. Strange, if `htsjdk` does not configure `jcommander` in `maven.rules`, `1.x` should have been replaced by `debian` on the fly. Maybe `gradle-debian-helper` ignores test classpath? signature.asc Description: OpenPGP digital signature

Bug#895886: testng: jcommander classes not found

2018-04-17 Thread olivier sallou
Le mar. 17 avr. 2018 à 14:06, 殷啟聰 | Kai-Chung Yan a écrit : > By `debian/maven.rules` I mean [1]. It's at line 3. This file configures > Gradle as well. > oh ok, you meant in testng, not in our package... I locally updated pom to make it work, but means that testng needs to

Bug#895886: testng: jcommander classes not found

2018-04-17 Thread 殷啟聰 | Kai-Chung Yan
By `debian/maven.rules` I mean [1]. It's at line 3. This file configures Gradle as well. Gradle understands the relocations, but it won't add it to the build classpath, that's why it fails. [1]: https://sources.debian.org/src/testng/6.9.12-2/debian/maven.rules signature.asc Description:

Bug#895886: testng: jcommander classes not found

2018-04-17 Thread olivier sallou
Le mar. 17 avr. 2018 à 13:37, 殷啟聰 | Kai-Chung Yan a écrit : > Control: tags -1 confirmed > > I relocated `jcommander` from version `1.x` to `debian`, but unfortunately > Gradle does not recognize Maven artifact relocations. > > To fix this, simply remove the line about

Bug#895886: testng: jcommander classes not found

2018-04-17 Thread 殷啟聰 | Kai-Chung Yan
Control: tags -1 |confirmed I relocated `jcommander` from version `1.x` to `debian`, but unfortunately Gradle does not recognize Maven artifact relocations. To fix this, simply remove the line about `jcommander` in `debian/maven.rules`. Hmm, now I have no idea why it used `1.x` in the first

Bug#895886: testng: jcommander classes not found

2018-04-17 Thread olivier sallou
Package: testng Version: 6.9.12-2 Severity: important Dear Maintainer, while trying to use testng to update package htsjdk (using gradle), I face errors about jcommander not being found when running tests Task :compileTestJava actions class loader hash: 1526b3b109d06b230b32697697c7e0ca Passing