Le 21/10/2016 à 12:08, 殷啟聰 a écrit :
> I adjusted the indentation to 4 spaces and sorted the imports.
Thanks, looks better now :)
> A large number of packages builds multiple binary packages, where the
> maintainer need to specify which JARs should be installed to which
> binary packages. For
I adjusted the indentation to 4 spaces and sorted the imports. Looks
like Atom's sort-lines plugin ignores upper/lower cases by default.
A large number of packages builds multiple binary packages, where the
maintainer need to specify which JARs should be installed to which
binary packages. For
This is an excellent idea, thank you for the patch! Maybe the plugin
could even generate the debian/.poms file if it doesn't exist so it
can be picked up by maven-repo-helper at the install phase.
The code looks good to me, modulo some style mismatches (2 spaces indent
vs 4 spaces and imports
Package: gradle-debian-helper
Version: 1.3
Severity: wishlist
By default a Gradle project does not contain any Maven POMs which are
important metadata for a Java package in Debian. So far I have been
writing custom tasks [1] for my packages in order to let Gradle
generate the POMs, as I don't
4 matches
Mail list logo
