Bug#814191: RM: bytecode-compatibility-transformer -- ROM; no longer used

2016-02-08 Thread Emmanuel Bourg
Package: ftp.debian.org
Severity: normal

Hi,

Please remove the bytecode-compatibility-transformer package, it was only used 
by Jenkins
which has been removed recently.

Thank you,

Emmanuel Bourg



Bug#814187: RM: maven-hpi-plugin -- ROM; no longer used

2016-02-08 Thread Emmanuel Bourg
Package: ftp.debian.org
Severity: normal

Hi,

Please remove the maven-hpi-plugin package, it was only used by Jenkins
which has been removed recently.

Thank you,

Emmanuel Bourg



Re: OpenJDK 8...

2016-02-08 Thread Matthias Klose

On 05.02.2016 07:59, Emmanuel Bourg wrote:

...is now the default Java runtime in unstable! I just uploaded
java-common/0.55 to unstable and it switched the default-jre/jdk to
openjdk-8 for all the architectures previously defaulting to openjdk-7.

I expect a few packages to FTBFS after this update (most notably
eclipse) but the main compatibility issues have already been fixed.


https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=openjdk-8-transition;users=debian-java@lists.debian.org

now lists the packages hardcoding openjdk-7.  This need to get fixed to remove 
openjdk-7.




Bug#814144: RM: jenkins-executable-war -- ROM; no longer used

2016-02-08 Thread Emmanuel Bourg
Package: ftp.debian.org
Severity: normal

Hi,

Please remove the jenkins-executable-war package. It was only used by Jenkins
which has been removed recently.

Thank you,

Emmanuel Bourg



Bug#814122: RM: jenkins-task-reactor -- ROM; no longer used

2016-02-08 Thread Emmanuel Bourg
Package: ftp.debian.org
Severity: normal

Hi,

Please remove the jenkins-task-reactor package. It was only used by Jenkins
which has been removed recently.

Thank you,

Emmanuel Bourg



Bug#814123: RM: jenkins-xstream -- ROM; no longer used

2016-02-08 Thread Emmanuel Bourg
Package: ftp.debian.org
Severity: normal

Hi,

Please remove the jenkins-xstream package. It was only used by Jenkins
which has been removed recently.

Thank you,

Emmanuel Bourg



Bug#814117: RM: lucene4 -- ROM; no longer used, replaced by lucene4.10

2016-02-08 Thread Emmanuel Bourg
Package: ftp.debian.org
Severity: normal


Hi,

Please remove the lucene4 package, it has been replaced by lucene4.10 and is no 
longer used.

Thank you,

Emmanuel Bourg



Bug#814120: RM: jenkins-memory-monitor -- ROM; no longer used

2016-02-08 Thread Emmanuel Bourg
Package: ftp.debian.org
Severity: normal

Hi,

Please remove the jenkins-memory-monitor package. It was only used by Jenkins
which has been removed recently.

Thank you,

Emmanuel Bourg



Bug#814118: RM: jenkins-remoting -- ROM; no longer used

2016-02-08 Thread Emmanuel Bourg
Package: ftp.debian.org
Severity: normal


Hi,

Please remove the jenkins-remoting package. It was only used by Jenkins
which has been removed recently.

Thank you,

Emmanuel Bourg



Re: lombok build failes

2016-02-08 Thread Hans-Christoph Steiner


Markus Koschany:
> Am 07.02.2016 um 15:52 schrieb Ioan Eugen Stan:
>> Hello,
>>
>> I'm trying to fix lombok packge so it builds but there are some issues
>> that I don't know how to handle best.
> 
> Hi,
> 
> I need lombok to build lombok-ast but the current lombok package has
> some issues and differs from the upstream version. I intend to start all
> over again with the packaging. I believe there is still something wrong
> with ivyplusplus, so I will start with this one. If you find a solution,
> please send an e-mail to this list. I will keep you updated as well.
> 
> Regards,
> 
> Markus

Turns out that lombok & Co are quite pain to build for Debian, but we
are making progress.  I'm happy to see that someone else has a use for
it, especially considering all the work we've had to put into it.  Also,
upstream has been somewhat responsive, so its worth trying to email
them.  I just emailed the addresses in the git commits.

.hc



Re: lombok build failes

2016-02-08 Thread Markus Koschany
Am 07.02.2016 um 15:52 schrieb Ioan Eugen Stan:
> Hello,
> 
> I'm trying to fix lombok packge so it builds but there are some issues
> that I don't know how to handle best.

Hi,

I need lombok to build lombok-ast but the current lombok package has
some issues and differs from the upstream version. I intend to start all
over again with the packaging. I believe there is still something wrong
with ivyplusplus, so I will start with this one. If you find a solution,
please send an e-mail to this list. I will keep you updated as well.

Regards,

Markus




signature.asc
Description: OpenPGP digital signature


Re: lombok build failes

2016-02-08 Thread Andreas Tille
Hans-Christoph Steiner wrote:
> Glad to have another person joining in the lombok struggles!  apo and I
> have been working on the lombok suite, but it is not quite complete yet.
> I think apo is still struggling with ivyplusplus, which is the upstream
> build system for lombok.

Ioan and me were working at the Debian Med sprint a bit on ivyplusplus
which was spotted as blocker for lombok by Ioan.  It seemed to us that
you commited some changes in end of December that were helpful to build
ivyplusplus properly.  I basically added a missing watch file and Ioan
contributed a symlink to ant dir.  This builded nicely and thus I
uploaded it to unstable.

If there are further problems with ivyplusplus please discuss this here
and keep me in CC since I'm not subscribed to this list.

Kind regards

  Andreas.

-- 
http://fam-tille.de



Re: lombok build failes

2016-02-08 Thread Hans-Christoph Steiner

Hey Ioan,

Glad to have another person joining in the lombok struggles!  apo and I
have been working on the lombok suite, but it is not quite complete yet.
 I think apo is still struggling with ivyplusplus, which is the upstream
build system for lombok.

.hc

Ioan Eugen Stan:
> Hello,
> 
> I'm trying to fix lombok packge so it builds but there are some issues
> that I don't know how to handle best.
> 
> ...
> [ivy:compile] warning: [options] To suppress warnings about obsolete
> options, use -Xlint:-options.
> [compile:javac] Compiling 18 source files to
> /build/lombok-1.16.6/build/lombok-utils
> [ivy:compile]
> /build/lombok-1.16.6/src/utils/lombok/javac/Javac.java:330: error:
> JCNoType is not abstract and does not override abstract method getTag()
> in Type
> [ivy:compile]   private static class JCNoType extends Type implements
> NoType {
> [ivy:compile]  ^
> [ivy:compile]
> /build/lombok-1.16.6/src/utils/lombok/javac/Javac.java:332: error:
> constructor Type in class Type cannot be applied to given types;
> [ivy:compile]   super(tag, null);
> [ivy:compile]   ^
> [ivy:compile]   required: TypeSymbol
> [ivy:compile]   found: int,
> [ivy:compile]   reason: actual and formal argument lists differ in length
> [ivy:compile]
> /build/lombok-1.16.6/src/utils/lombok/javac/Javac.java:337: error:
> cannot find symbol
> [ivy:compile]   if (tag == ((Integer)
> CTC_VOID.value).intValue()) return TypeKind.VOID;
> [ivy:compile]   ^
> [ivy:compile]   symbol:   variable tag
> [ivy:compile]   location: class JCNoType
> [ivy:compile]
> /build/lombok-1.16.6/src/utils/lombok/javac/Javac.java:338: error:
> cannot find symbol
> [ivy:compile]   if (tag == ((Integer)
> CTC_NONE.value).intValue()) return TypeKind.NONE;
> [ivy:compile]   ^
> [ivy:compile]   symbol:   variable tag
> [ivy:compile]   location: class JCNoType
> [ivy:compile]
> /build/lombok-1.16.6/src/utils/lombok/javac/Javac.java:339: error:
> cannot find symbol
> [ivy:compile]   throw new AssertionError("Unexpected
> tag: " + tag);
> [ivy:compile]
>   ^
> [ivy:compile]   symbol:   variable tag
> [ivy:compile]   location: class JCNoType
> [ivy:compile] 5 errors
> 
> BUILD FAILED
> /build/lombok-1.16.6/build.xml:186: Compile failed; see the compiler
> error output for details.
> 
> Total time: 2 seconds
> debian/rules:15: recipe for target 'override_dh_auto_build' failed
> ...
> 
> 
> So it fails becuse the signature of Type class (from tools.jar) has
> changed from jdk6 to jdk8.
> 
> Of course lombok packages it's own version of the Type class in
> lib/build/net.java.openjdk.custom-javac6.jar so it can build but it's
> not helpfull for Debian since we can't really include that binary.
> 
> Any solutions on how to solve this?
> 
> Thanks,
> 
>