Re: Notes on Reading Gradle Release Notes Since Version 1.5

to 0.3.0 I couldn't find a Debian package for that. .hc 殷啟聰: Hi all, I have added on the wiki page (https://wiki.debian.org/Java/Gradle) some notes after reading the release notes of Gradle so that we can know the dependency changes. Could Komal check it in case I missed anything? Thanks

Notes on Reading Gradle Release Notes Since Version 1.5

Hi all, I have added on the wiki page (https://wiki.debian.org/Java/Gradle) some notes after reading the release notes of Gradle so that we can know the dependency changes. Could Komal check it in case I missed anything? Thanks! Cheers, Kai-Chung -- /* * 殷啟聰 | Kai-Chung Yan * Full-time student

Bug#733148: I Will Help Update Gradle to the Latest Version

I am a would-be GSoC student this year currently working on the integration of Android SDK into Debian and updating Gradle and Groovy is within our to-do list. Hence I will help update Gradle to the latest version during this summer. -- /* * 殷啟聰 | Kai-Chung Yan * Full-time student of Providence

Re: Notes on Reading Gradle Release Notes Since Version 1.5

. Next, I was planning to read the logs of Debian gradle package to find out how the package was built. But as you rightly said packaging of missing dependency is must, I will focus on packaging of PMD as you are focusing on JaCoCo. Komal Sukhani. -- /* * 殷啟聰 | Kai-Chung Yan * Full-time

Re: Notes on Reading Gradle Release Notes Since Version 1.5

Hi, Congratulations on finishing your exams Komal. Currently I am trying to package JaCoCo, which does not exist in Debian but used by Gradle. I think in order to package a fully functional Gradle we should first package all the missing dependencies, ignoring the outdated dependencies for now.

Bug#787707: ITP: bintray-client-java -- Bintray REST Client Java API Bindings

Package: wnpp Severity: wishlist X-Debbugs-CC: pkg-java-maintainers@lists.alioth.debian.org * Package name: bintray-client-java * Version: 0.10 * Upstream: JFrog developers * License: Apache-2.0 * Language: Java * Homepage: https://bintray.com/jfrog/bintray-tools/bintray-client-java * Alioth Git:

Multiple Packages Should Be Added to libspring-java Build-Depends

environment is different to the maintainers'. Cheers, Kai-Chung -- /* * 殷啟聰 | Kai-Chung Yan * Full-time student of Providence University of Taiwan * LinkedIn: https://linkedin.com/in/seamlik * Blog: seamlik.logdown.com */ __ This is the maintainer address of Debian's Java team http

Added Notes on Gradle Outdated/Missing Dependencies

and apologies, Kai-Chung -- /* * 殷啟聰 | Kai-Chung Yan * Full-time student of Providence University of Taiwan * LinkedIn: https://linkedin.com/in/seamlik * Blog: seamlik.logdown.com */ __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java

Re: Missing dependencies of SDK tools

unreleased version. Komal Sukhani On Mon, Jul 27, 2015 at 12:25 PM, 殷啟聰 seamli...@gmail.com wrote: Hi Komal, If upgrading Proguard helps solve the problem that's definitely the best solution, only that I find the latest version is 5.2 and Debian version is 5.0 I wonder there will be much help

Re: [gradle] 05/05: Merge libgradle-core-java and libgradle-plugins-java into gradle

of changes. I'd focus on keeping up to date with upstream since that's usually a challenge by itself. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key . Faith means not wanting to know what is true. -- Nietzsche -- 殷啟聰

Re: [gradle] 05/05: Merge libgradle-core-java and libgradle-plugins-java into gradle

/distribution/Distribution.html + rm debian/gradle-doc/usr/share/doc/gradle/groovydoc/org/gradle/api/initialization/Settings.html get-orig-source: uscan --download-current-version --force-download --repack --compression xz -- 殷啟聰 | Kai-Chung Yan 一生只向真理與妻子低頭 Full-time student

Bug#793911: groovy should not release with stretch

On Tue, 28 Jul 2015 22:38:40 +0200 Moritz Muehlenhoff wrote: > Package: groovy > Severity: serious > > A separate source package groovy2 was uploaded, so reverse dependencies > need to be migrated to that one and groovy removed. > > Cheers, > Moritz > > Hi Moritz and all

Re: [gradle] 02/03: d/control: Add java6-runtime to Depends as an option

binary:Version}), > > libgradle-plugins-java (>= ${binary:Version}), > > ${misc:Depends} > > Hi Kai, > > You probably want java6-runtime-headless instead of java6-runtime here > since gradle is a command line application. > > Emmanuel Bourg > >

Re: [gradle] 02/03: d/control: Add java6-runtime to Depends as an option

dk instead of default-jdk-headless. Regards, Kai-Chung Yan 2015-10-03 20:50 GMT+08:00 殷啟聰 <seamli...@gmail.com>: > Hi Emmanuel, > > Yeah that was my mistake, too carelessly. Thank you for pointing out! > > Regards, > Kai-Chung Yan > > > Emmanuel Bourg <ebo...@apach

Re: [gradle] 02/03: d/control: Add java6-runtime to Depends as an option

Hi Emmanuel, However, "gradle --gui" will fail if full runtime is not installed. Emmanuel Bourg <ebo...@apache.org> 於 2015年10月6日週二 00:14 寫道： > Le 05/10/2015 18:02, 殷啟聰 a écrit : > > > Gradle has a submodule gradle-ui.jar which enables us to launch a GUI > >

Bug#825617: Should Enable Parallel Builds According to DEB_BUILD_OPTIONS

Package: gradle-debian-helper Version: 1.1 Severity: wishlist Gradle supports parallel building through "--parallel" and "--max-workers". Currently gradle-debian-helper does not honor the parallel options in DEB_BUILD_OPTIONS and I have to write this: ``` ifneq (,$(filter

Bug#811053: *.poms Should Not Be Required to Ensure Trailing Newline

Package: maven-repo-helper Version: 1.8.12 Severity: normal If the $package.poms contains only one line, say: debian/foo.pom --usj-name=foo maven-repo-helper will not install any .pom or symlinks to usr/share/maven-repo. But if I append a newline to the end, it works without any problem. And

Bug#811053: *.poms Should Not Be Required to Ensure Trailing Newline

Thank you for responding so rapidly! I am packaging android-platform-libcore in . Actually I think this is also the reason why src:gradle currently only installs .pom but without symlinks. __ This is the maintainer address

Bug#815137: Release 56.1 Is Available

Source: icu4j Version: 4.2.1.1-3 Severity: wishlist The Android Frameworks for developing Android applications depends on icu4j-56, please update this source package to at least 56. Better to avoid creating another libicu4j-56-java :( Would be better if it is migrated to Git. __ This is the

Permission on Moving icu4j to Git?

Hi Thykier, Tille, Moeller, I would like update icu4j to 59.1. Before that I want to move icu4j to Git, would you allow me to do that? Thanks! Cheers, Kai-Chung Yan -- /* * 殷啟聰 | Kai-Chung Yan * 一生只向真理與妻子低頭 * Undergraduate student in National Taichung University of Education * LinkedIn: <ht

Re: Permission on Moving icu4j to Git?

Hi Emmanuel, I used your script and I am reusing the original icu4j package. The script is great! Regards, Kai-Chung Yan 2016-03-01 16:04 GMT+08:00 Emmanuel Bourg <ebo...@apache.org>: > Le 1/03/2016 07:37, 殷啟聰 a écrit : > >> I would like update icu4j to 59.1. Before that I

Bug#819193: Change BD to libicu4j-4.2-java

Control: block -1 by 819192 __ This is the maintainer address of Debian's Java team . Please use debian-j...@lists.debian.org for discussions and questions.

Bug#819193: Change BD to libicu4j-4.2-java

Source: lucene2 Version: 2.9.4+ds1-4 Severity: wishlist Control: block -1 819192 Owner: Kai-Chung Yan src:icu4j is going to be updated to 57.1 which will break src:lucene2. The current workaround is to change the BD from libicu4j-java to libicu4j-4.2-java. __ This is the

Bug#819193: Change BD to libicu4j-4.2-java

Control: block -1 819192 First icu4j-4.2 must be uploaded. __ This is the maintainer address of Debian's Java team . Please use debian-j...@lists.debian.org for discussions and questions.

Re: Permission on Moving icu4j to Git?

fam-tille.de>: > I'm perfectly fine with moving to Git (was not even aware that I'm involved > any more). Please excuse my brewity - I'm on vacation, Andreas. > > On Tue, Mar 01, 2016 at 07:08:38AM +, Niels Thykier wrote: >> 殷啟聰: >> > Hi Thykier, Tille, Moeller, &g

Re: RFS: jacoco/0.7.7-1 [ITP]

o.build/debian/org.jacoco.build-debian.pom > > Since we only need the org.jacoco.core artifact at the moment, they are > probably superfluous. What do you think? > > Regards, > > Markus > -- /* * 殷啟聰 | Kai-Chung Yan * 一生只向真理與妻子低頭 * Undergraduate student in National Taichung Uni

Bug#855262: Set System Encoding as UTF-8

Package: gradle-debian-helper Version: 1.5.1 Severity: wishlist On Debian Buildd the default encoding on Java is usually not UTF-8, which results in compilation failure on source files containing CJK symbols or even a "©". Currently we need to add `-Dfile.encoding=UTF-8` to

Bug#836391: gradle: recent update of jsch to version 0.1.54 breaks Gradle based projects

We did a binary upload to Debian, but seems that Ubuntu syncs the packages by source and builds them again. I think someone at the Ubuntu side should do a binary upload to e.g. 2.13-4ubuntu1. I filed a bug about this to Launchpad.

Bug#837882: Gradle Fails to Load Its pom.xml

Package: libpolyglot-maven-java Version: 0.8~tobrien+git20120905-3 Severity: important Executing a simple Gradle script that declares the dependency on "pmaven-common.jar": ``` apply plugin: 'java' repositories { maven { url '/usr/share/maven-repo' } } dependencies { compile

Bug#838033: Please Switch to libandroid-json-java from dusty libandroid-json-org-java

Source: closure-compiler Version: 20130227+dfsg1-8 Severity: minor This package build-depends on libandroid-json-org-java which is very old. libandroid-json-java is part of src:android-platform-libcore [1] which is actively maintained and part of the Android SDK packaging force. Please consider

Bug#841491: Inject A Task for Generating Maven POMs

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

Bug#844021: libnative-platform-java 0.11-4 is not compatible with programs built with 0.10*

Control: tags -1 moreinfo Gradle 3.1 is now uploaded, looks like this bug is fixed? __ This is the maintainer address of Debian's Java team . Please use debian-j...@lists.debian.org for discussions and questions.

Bug#845606: The Bytecode Should Not Be Targeting Java 1.2

Package: libasm-java Version: 5.1-1 Severity: important The current package of libasm-java contains classes that targets the ancient Java 1.2 where generics is not supported. When I was building a package for Jack (Java Android Compiler Kit) which uses the generics code in ASM, it yielded the

Bug#811053: *.poms Should Not Be Required to Ensure Trailing Newline

Actually, not all programs think `debian/libandroid-dex-java.poms` has a trailing new line. Inside the text, it is like: `line1\n` While the version without trailing new line would be: `line1` So some program considers this file has one line regardless the trailing new line. And the bug is,

Bug#844021: libnative-platform-java 0.11-4 is not compatible with programs built with 0.10*

Hi Vincent, FYI, there's been a patch [1] in gradle/3.1-1 which disable the buildSrc test during the build. It's this test who causes FTBFS [1]: https://anonscm.debian.org/cgit/pkg-java/gradle.git/tree/debian/patches/disable_buildSrc_tests.patch?h=debian/3.1-1 __ This is the maintainer address

Bug#844336: gradle: fails to upgrade to 3.1-1

Control: tags -1 + moreinfo Hi Salvo, Thank you for reporting the bug! I believe it is fixed in 3.1-2, could you comfirm if it works now? __ This is the maintainer address of Debian's Java team . Please use

Bug#844531: mh_depends: Generate ${maven:Depends} Accorfing to *.poms

Source: maven-repo-helper Version: 1.9.2 Severity: wishlist maven-repo-helper should contain a program `mh_depends` which by examining the POMs in a `.poms` file and generate a ${maven:Depends} or even ${maven:DocDepends}. There are a couple of benefits of using mh_depends instead of

Bug#844021: libnative-platform-java 0.11-4 is not compatible with programs built with 0.10*

Hi Vincent, Thank you for the report. In fact I have patched libnative-platform-java/0.11-4 to work with gradle/2.13, see [1]. Turns out the upstream developer suddenly renamed the class without any transition. I do not make sure this patch works for gradle/2.13 building all packages, but I can

Bug#842721: jayway-jsonpath: FTBFS (Could not resolve all dependencies)

I tried the build and seems it is. The new gradle-debian-helper automatically adds the "maven" plugin to every projects that has a "java" plugin applied, and the "maven" plugin adds a "install" task which seems to depend on the "jar" task. d/rules executes the "install" task, which also executes

Bug#841491: Inject A Task for Generating Maven POMs

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

Bug#842721: jayway-jsonpath: FTBFS (Could not resolve all dependencies)

Control: tags -1 + fixed I believe this bug has been fixed in . But I'm not the maintainer behind this package so I'll leave the rest for its maintainers. I found this bug during a rebuild of

Bug#842721: jayway-jsonpath: FTBFS (Could not resolve all dependencies)

Oops, I posted the wrong link. Here's the right link: __ This is the maintainer address of Debian's Java team

Bug#842808: gant: FTBFS: Cannot add task ':gant:install' as a task with that name already exists

Control: tags -1 + fixed Thank you for the report. I believe this bug is fixed by . __ This is the maintainer address of Debian's Java team

Bug#840317: Please Separate CLI, GUI and Library Packages

Looks like Gradle does not depend on Proguard. But we still benefit from separating the CLI and GUI program, or simply put default-jdk in "Suggests" and default-jdk-headless in "Depends". __ This is the maintainer address of Debian's Java team

Bug#842838: Reassigning #842838

Control: reassign -1 gradle-debian-helper 1.4 Control: tags -1 + fixed I believe this bug is fixed by . __ This is the maintainer address of Debian's Java team

Bug#840317: Please Separate CLI, GUI and Library Packages

Source: proguard Version: 5.3-1 Severity: wishlist Currently src:proguard builds a single pkg:proguard package providing both the GUI, CLI programs, the Gradle plugin and the library. Since Gradle depends on Progaurd's library, even if a package build-depends on default-jdk-headless it still

Bug#847428: Package the Entire "eclipse.jdt.core"

Source: ecj Version: 3.11.0-7 Severity: wishlist Control: block 847427 by -1 Dear maintainers, android-toolchain-jack requires both the existing libecj-java and the "org.eclipse.jdt.compiler.apt" module in "eclipse.jdt.core". As the upstream of src:ecj is exactly "eclipse.jdt.core", so I wish

Bug#846845: A New Option for Prefixing usj-name with Group ID

Package: maven-repo-helper Version: 1.9.2 Severity: wishlist There are Java libraries that are forks of some upstreams or are some internal libraries that are never released to be used by other projects. There are also libraries whose names are too general (e.g.

Bug#844531: mh_depends: Generate ${maven:Depends} Accorfing to *.poms

Control: reassign -1 src:maven-repo-helper maven-repo-helper It's not a source-wise or build-wise problem, so it's better to stay in the binary package section. __ This is the maintainer address of Debian's Java team .

Bug#844531: mh_depends: Generate ${maven:Depends} Accorfing to *.poms

Control: reassign -1 maven-repo-helper 1.9.2 Oops, wrong command. __ This is the maintainer address of Debian's Java team . Please use debian-j...@lists.debian.org for discussions and questions.

Bug#845606: The Bytecode Should Not Be Targeting Java 1.2

FYI, I forwarded the bug to ASM's upstream issue tracker [1]. I propose the follwing patch to fix the bug: ``` diff --git a/debian/rules b/debian/rules index 734f78c..ed59b80 100755 --- a/debian/rules +++ b/debian/rules @@ -6,7 +6,7 @@ VERSION ?= $(shell dpkg-parsechangelog | sed -rne

Bug#845606: The Bytecode Should Not Be Targeting Java 1.2

In version 1.3~b8 that I have been packaging, Jack uses ASM 5.0.4 [1]. The upstream Jack is not affected by this particular problem because the source of Jack includes the source of all external dependencies which are compiled using Ant and javac and are included into `jack.jar` when Jack is

Bug#845606: The Bytecode Should Not Be Targeting Java 1.2

I tried building Jack using the asm-all.jar from jcenter and it failed with the same error. And when I checked the classes in this JAR it gave me "Java 1.2" as well. So looks like the same problem applies to the upstream as well. __ This is the maintainer address of Debian's Java team

Bug#846463: Depends on default-jre-headless and Suggests default-jre?

Package: proguard Version: 5.3.1-1 Severity: wishlist proguard is mostly used as a command line program and used by various build systems such as the Gradle Android Plugin. There's no need to force install the headful JRE together with Proguard. Perhaps putting it to Suggests is a better

Bug#844336: Fixed in 3.1-2

Control: fixed -1 3.1-2 Turns out you can't use controls in the closing emails. __ This is the maintainer address of Debian's Java team . Please use debian-j...@lists.debian.org for discussions and questions.

Bug#844021: libnative-platform-java 0.11-4 is not compatible with programs built with 0.10*

Hi Vincent, Thanks for the patch, I think breaking libgradle-core-java is enough as this is the very package that uses libnative-platform-java. I'm uploading it soon. __ This is the maintainer address of Debian's Java team

Bug#856996: libjacoco-java: Where is the jacoco agent located?

As ebourg said, maven-pgp-plugin isn't necessary for the build process, IMO. Well if it does affect the process, then something's probably not right... I tried updating maven-shade-plugin to the latest version (3.0.0) but gave up since it introduces quite a few new dependencies that are absent in

Bug#856996: libjacoco-java: Where is the jacoco agent located?

Hello Quinson, The current Debian package only provides 2 JARs: `org.jacoco.core.jar` and `org.jacoco.report.jar`. It is an incomplete package at the moment because building the whole project requires a lot more new packages. At the time when I was packaing it, JaCoCo was only used by the Gradle

Bug#862529: uncommons-watchmaker-doc: Rename the documentation package to lib*-java-doc

The reason behind this package name is that it provides the Javadoc for both of the 2 library packages (libuncommons-watchmaker-framework-java & libuncommons-watchmaker-swing-java). If I split their Javadocs, there will be dead hyperlinks (or in fact the class fullname instead of hyperlinks)

Bug#862529: uncommons-watchmaker-doc: Rename the documentation package to lib*-java-doc

@ebourg Could you grant me the upload permission on this package? I am about to rename the package. Thank you! __ This is the maintainer address of Debian's Java team . Please use debian-j...@lists.debian.org for

Accepted jcommander 1.71-1 (source) into unstable

ava-maintainers@lists.alioth.debian.org> Changed-By: Kai-Chung Yan (殷啟聰) <seamli...@gmail.com> Description: libjcommander-java - Java framework for parsing command line parameters libjcommander-java-doc - Java framework for parsing command line parameters (documentation Closes: 886553 Changes:

Accepted jboss-xnio 3.6.2-2 (source) into unstable

ava-maintainers@lists.alioth.debian.org> Changed-By: Kai-Chung Yan (殷啟聰) <seamli...@gmail.com> Description: libjboss-xnio-java - simplified low-level I/O layer for NIO libjboss-xnio-java-doc - Documentation for jboss-xnio Changes: jboss-xnio (3.6.2-2) unstable; urgency=medium . * B

Accepted felix-bundlerepository 2.0.10-3 (source) into unstable

: Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org> Changed-By: Kai-Chung Yan (殷啟聰) <seamli...@gmail.com> Description: libfelix-bundlerepository-java - Felix OSGi bundle repository service libfelix-bundlerepository-java-doc - Documentation for Felix OSGi bundle reposi

Accepted bnd 3.5.0-1 (source) into unstable

hanged-By: Kai-Chung Yan (殷啟聰) <seamli...@gmail.com> Description: bnd- tool to create and diagnose OSGi bundles Closes: 889406 Changes: bnd (3.5.0-1) unstable; urgency=medium . * New upstream release * Drop obsolete patches: * disable-jpm-plugin.patch * gradle-compati

Accepted osgi-compendium 6.0.0-1 (source) into unstable

<pkg-java-maintainers@lists.alioth.debian.org> Changed-By: Kai-Chung Yan (殷啟聰) <seamli...@gmail.com> Description: libosgi-compendium-java - Java OSGi API - Compendium module libosgi-compendium-java-doc - Javadoc for Java OSGi API - Compendium module Closes: 889329 Changes: osgi-compend

Accepted libnative-platform-java 0.14-3 (source) into unstable

Maintainer: Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org> Changed-By: Kai-Chung Yan (殷啟聰) <seamli...@gmail.com> Description: libnative-platform-java - Java bindings for various native APIs libnative-platform-java-doc - testing and specification framework for Java

Accepted maven-bundle-plugin 3.5.0-1 (source) into unstable

ers@lists.alioth.debian.org> Changed-By: Kai-Chung Yan (殷啟聰) <seamli...@gmail.com> Description: libmaven-bundle-plugin-java - Maven plugin to handle artifact OSGi metadata Changes: maven-bundle-plugin (3.5.0-1) unstable; urgency=medium . * New upstream release * Use a simpler get

Bug#879175: androidsdk-tools: Duplicate of android-platform-tools-swt

(I am one maintainer of android-platform-tools-swt) To be honest, both should be removed since Google has abandoned android-platform-tools-swt. That's why it remains unbuildable as of today. signature.asc Description: OpenPGP digital signature __ This is the maintainer address of Debian's

Bug#888741: Does Not Honor defaultTasks

Package: gradle-debian-helper Version: 1.6 Severity: normal One may specify the default tasks to run in a Gradle script, thus avoid messing with the commandline. However gradle-debian-helper makes it impossible to use this feature, for it adds a "jar" task if no task is specified. It could be

Bug#890345: Depending on "default-jre-headless" Should be Sufficient

Package: jflex Version: 1.6.1-2 Severity: wishlist "jflex" seems to me a commandline program, thus depending on "default-jre-headless" should be sufficient. Right now it depends on "default-jre" and "pbuilder" always fetches the whole graphical stack while building "libsmali-java".

Bug#880886: maven-bundle-plugin FTBFS with libmaven-dependency-tree-java

This is getting awkward... Maven Bundle Plugin does not only rely on old Maven Dependency Tree, but also targets Maven 2.x [1]. What's worse, Maven Dependency Tree 2.x also relies on Maven 2.x [2]. I tried building Maven Dependency Tree 2.2 against Maven 3.x and found that it uses removed

Bug#875336: FTBFS with Java 9: _ as identifier

I recently updated the package to 3.5.0 just to find out the current Groovy (2.4.8) does not support Java 9 [1]. Groovy was used by the bootstrapping script. Setting source & target to Java 8 doesn't solve the problem either. [1]: https://github.com/gradle/gradle/issues/2995 signature.asc

Bug#891695: "mh_linkjar" and "mh_installpoms" Do Not Support "--relocate"

Because I was trying to get around with the error of "mh_linkjar" I admit that is a wrong attempt. But never mind, the point is to let all "mh_" sequence support all options in "*.poms" files but ignore whatever is irrelevant to them. signature.asc Description: OpenPGP digital signature

Bug#847428: Package the Entire "eclipse.jdt.core"

Thank you for this! However, the Jack & Jill toolchain is deprecated now and we no longer plan to package it... signature.asc Description: OpenPGP digital signature __ This is the maintainer address of Debian's Java team

Bug#880886: maven-bundle-plugin FTBFS with libmaven-dependency-tree-java

forwarded -1 https://issues.apache.org/jira/browse/FELIX-5795 signature.asc Description: OpenPGP digital signature __ This is the maintainer address of Debian's Java team . Please use debian-j...@lists.debian.org for

Bug#880886: maven-bundle-plugin FTBFS with libmaven-dependency-tree-java

Control:  forwarded -1 https://issues.apache.org/jira/browse/FELIX-5795 signature.asc Description: OpenPGP digital signature __ This is the maintainer address of Debian's Java team . Please use

Bug#875336: FTBFS with Java 9: _ as identifier

I just tried building it and Groovy was fine enough, but now Gradle complains Theoretically, ALL Gradle packages FTBFS since the current version is too old to play with Java 9's fancy version number. signature.asc Description: OpenPGP digital signature __ This is the maintainer address

Bug#880886: maven-bundle-plugin FTBFS with libmaven-dependency-tree-java

I adopted the patch from Fedora and it looks good. The package builds fine now and 154 of its reverse-build-dependencies built successfully. 27 failed: * activemq-activeio * activemq * apache-directory-server * dnssecjava * istack-commons * jackson-datatype-joda * javassist * jayway-jsonpath *

Bug#880886: maven-bundle-plugin FTBFS with libmaven-dependency-tree-java

I removed the javadoc package now and it builds find in Sid. Shall I upload it right now? (I still need the upload permission) signature.asc Description: OpenPGP digital signature __ This is the maintainer address of Debian's Java team

Bug#880886: maven-bundle-plugin FTBFS with libmaven-dependency-tree-java

I propose to bring back Maven Dependency Tree 2.x as a new package that coexists with its latest version. Even in the latest (3.5.0) version, Maven Bundle Plugin still uses those deprecated APIs in Maven Dependency Tree 2.x. These deprecated APIs have been removed from Maven Dependency Tree

Bug#891695: "mh_linkjar" and "mh_installpoms" Do Not Support "--relocate"

Package: maven-repo-helper Version: 1.9.2 Severity: important If I use "jh_maven_repo_helper" and then add a "relocate" option to ".poms", "mh_linkjar" shows the following error: > Invalid option: relocate So I move the "relocate" option to "debian/rules" as ```make override_mh_installpoms:   

Bug#891695: "mh_linkjar" and "mh_installpoms" Do Not Support "--relocate"

I put this in the .poms: > debian/pom.xml --no-parent --usj-name=osgi.cmpn > --relocate=org.osgi:org.osgi.compendium:debian The point is to let all mh_ sequences support all options and simply ignore anything that's irrelevant to themselves. signature.asc Description: OpenPGP digital