Le 18/06/2015 16:16, Brandon Bradley a écrit : > Would it be OK to include the gradle wrapper jar as part of the > repo for building? I don't know the exact policy about binary artifacts > in dsc files. Also, what about including JARs not packaging directly > into the package?
There is really no way to keep the wrapper or any other jar. In Debian everything has to be built from the sources, and dependencies must be packaged first. This is quite frustrating for us Java developers used to download artifacts from a Maven repository, but it turns out to be fun too if you see this as a puzzle to be assembled piece by piece. > I'm only building the 'core' subproject which depends on the 'clients' > subproject. Here is a list of runtime dependencies from running > `./gradlew -PscalaVersion=2.9.2 core:dependencies`. If you focus on a subset of Kafka that may be easier. Looking at the dependency tree it looks like the lz4 support may be disabled in favor of snappy. That would leave zkclient as the only dependency left to package. Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5582e1d7.9020...@apache.org
