On Tue, 15 Jul 2014 23:20:32 +0100, Adam Spragg wrote:
Well, thanks for all the help, but now I'm stuck on step the 9th, trying to
compile SignApk.java. And I think I'm just going to give up.
I'm getting compile errors of the form:
SignApk.java:20: error: cannot find symbol
import
On Wed, 16 Jul 2014, Emmanuel Bourg wrote:
Le 16/07/2014 00:07, Rene Engelhard a écrit :
This is nonsense. Not yet - not as long we want/need gcj (on some archs).
Fair enough. But we already have a lot of packages incompatible with gcj
in Jessie.
Ugh. If you have time, can you work on
On Wednesday 16 Jul 2014 08:28:33 gregor herrmann wrote:
On Tue, 15 Jul 2014 23:20:32 +0100, Adam Spragg wrote:
Well, thanks for all the help, but now I'm stuck on step the 9th, trying
to compile SignApk.java. And I think I'm just going to give up.
I'm getting compile errors of the form:
On 15/07/2014 23:55, Matthias Klose wrote:
Am 15.07.2014 23:08, schrieb Emmanuel Bourg:
This was expected but now it's effective, Java 9 no longer supports
source/target level 1.5:
http://mail.openjdk.java.net/pipermail/jdk9-dev/2014-July/000972.html
So if you update a package and see these
Le 15/07/2014 17:27, Matthias Klose a écrit :
Even before you did start, I was telling you on irc that I'll keep the
openjdk-8
package as one package, and not splitting it up into different source packages
depending on the hotspot version specific for that architecture. You did
continue
Le 16/07/2014 09:41, Adam Spragg a écrit :
ABI-incompatible changes without bumping the major version number? And people
*use* software from upstreams who work in this way?
Unfortunately the BouncyCastle project is known for badly breaking the
compatibility between releases, and this is an
On Wed, Jul 16, 2014 at 01:24:52AM +0200, Emmanuel Bourg wrote:
Le 16/07/2014 00:07, Rene Engelhard a écrit :
This is nonsense. Not yet - not as long we want/need gcj (on some archs).
Fair enough. But we already have a lot of packages incompatible with gcj
in Jessie.
Bad, but other
Le 16/07/2014 11:24, Rene Engelhard a écrit :
Bad, but other packages broken is not a reason to break more.
*any* Java application which is built on/for kfreebsd-* (which has native
stuff) or _all (where it's available on kfreebsd-*, too)
I understand that would be ideal but that's
On Tue, Jul 15, 2014 at 09:39:33PM -0700, tony mancill wrote:
On 07/15/2014 11:30 AM, Bill Allombert wrote:
On Tue, Jul 15, 2014 at 04:57:18PM +0200, Emmanuel Bourg wrote:
Le 15/07/2014 16:22, Bill Allombert a écrit :
Could you please write the definition for each of them, and determine
Source: basex
Version: 7.8.2-1
Severity: important
User: debian-java@lists.debian.org
Usertags: openjdk-8-transition
Hi,
During a rebuild of all Java packages in sid with OpenJDK 8,
this package failed to build with the following error:
[INFO]
Package: proguard
Version: 4.11-1
Severity: important
User: debian-java@lists.debian.org
Usertags: openjdk-8-transition
proguard is unable to process the bytecode produced by Java 8. This
breaks the build of the mobile-atlas-creator package with OpenJDK 8:
Source: gluegen2
Version: 2.1.5-2
Severity: important
User: debian-java@lists.debian.org
Usertags: openjdk-8-transition
Hi,
During a rebuild of all Java packages in sid with OpenJDK 8,
this package failed to build with the following error:
java.build:
[echo] - - - compiling all
Hi all,
I updated the mvel package to fix a build failure with Java 8 and I'm
looking for a sponsor to upload it.
Here is the changelog:
* Fixed a compilation error with Java 8
* Fixed the OptimizerFactory class and the unit tests to work with the
system version of ASM
* Added
On Wednesday 16 Jul 2014 09:23:57 Emmanuel Bourg wrote:
Bugs-nuts insane. Fricking Java, man.
This has nothing to do with Java. Upstream should have provided a proper
build script, try asking them. With Maven, Ant, or Gradle you dot not
have to care about the dependencies and the javac
On Wed, Jul 16, 2014 at 01:49:06AM +0200, Emmanuel Bourg wrote:
Le 14/07/2014 03:53, Miguel Landaeta a écrit :
openjfx is FTBFS due to a missing dependency on antlr3.
Thank you for spotting this issue Miguel. I think I got caught by a
dependency caching mechanism in Gradle, I had another
On Wed, Jul 16, 2014 at 07:23:13PM +0200, Emmanuel Bourg wrote:
Hi all,
I updated the mvel package to fix a build failure with Java 8 and I'm
looking for a sponsor to upload it.
I'll take care of it.
--
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9
On Wed, Jul 16, 2014 at 09:50:46AM +0200, Sylvestre Ledru wrote:
I think that is unfair statement against Emmanuel (especially when
adding d-d d-r to the cc list).
Totally agree with Sylvestre on this.
I also have sponsored many packages for Emmanuel in the Java team.
Frankly, I don't get
Hi,
I intend to package imeji[1] in Debian Science team. Unfortunately I'm
not that skilled with Java packaging. For maven based packages I found
MavenBuilder[2] but this page looks quite outdated refering to
debhelper (= 5), cdbs, openjdk-6-jdk
which lloks somehow ancient. I wonder if
Le 16/07/2014 22:34, Andreas Tille a écrit :
Any hint would be really welcome.
Hi Andreas,
When dealing with a Maven project you just have to checkout the code
and run mh_make. If all goes well this will create the packaging files
and match the dependencies with the Debian packages.
I took a
19 matches
Mail list logo
