On 28/01/15 2:43 AM, "Miguel Landaeta" wrote:
>> Hi everyone. As part of the JRuby 1.7 package update I'd like to
>>request
>> a sponsor to upload the jnr-constants package at:
>>
>
>I can take care of this.
>
>BTW, Emmanuel prepared a script to migrate debian-java packages from
>svn to git rep
Le 27/01/2015 18:02, Jan Niehusmann a écrit :
> As far as I can tell, it's not really java 6 code, but only some
> @Override annotations on methods implementing interfaces - which is OK
> with java 6 but forbidden with java 5. So I _guess_ the byte code would
> be compatible with java 5. Didn't ve
On 01/27/2015 05:35 PM, Thorsten Glaser wrote:
> On Tue, 27 Jan 2015, Jan Niehusmann wrote:
>
>> Yes, sure - I missed that, because I tried the builds in clean chroots,
>> where only one JDK was installed.
>
> Right, of course.
>
But debian java policy states "Packages must be built with de
On Tue, Jan 27, 2015 at 05:31:11PM +0100, Emmanuel Bourg wrote:
> Le 27/01/2015 17:11, Jan Niehusmann a écrit :
>
> > Yes, that would prevent failing builds, as well. But it will also exclude
> > gcj architectures, as on these, this dependency is not available.
>
> Indeed, but gcj doesn't run Jav
On Tue, 27 Jan 2015, Jan Niehusmann wrote:
> Yes, sure - I missed that, because I tried the builds in clean chroots,
> where only one JDK was installed.
Right, of course.
> > > But debian java policy states "Packages must be built with default-jdk".
> Well at least on some of the gcj architectu
Le 27/01/2015 16:43, Miguel Landaeta a écrit :
> BTW, Emmanuel prepared a script to migrate debian-java packages from
> svn to git repos some time ago.
Here it is:
http://anonscm.debian.org/cgit/pkg-java/pkg-java-svn2git.git/
Emmanuel Bourg
--
To UNSUBSCRIBE, email to debian-java-requ...@lis
Le 27/01/2015 17:11, Jan Niehusmann a écrit :
> Yes, that would prevent failing builds, as well. But it will also exclude
> gcj architectures, as on these, this dependency is not available.
Indeed, but gcj doesn't run Java 6 code, so that's normal.
> In fact, that's the current state:
> https:/
Thorsten, Emmanuel, thanks for your answers!
On Tue, Jan 27, 2015 at 04:14:04PM +0100, Thorsten Glaser wrote:
> On Tue, 27 Jan 2015, Jan Niehusmann wrote:
>
> > Depending on openjdk-6-jdk or openjdk-7-jdk would probably fix that
>
> No, as you can install several JDKs.
Yes, sure - I missed that
On Tue, Jan 27, 2015 at 2:41 AM, Potter, Tim (Cloud Services) wrote:
>
> Hi everyone. As part of the JRuby 1.7 package update I'd like to request
> a sponsor to upload the jnr-constants package at:
>
I can take care of this.
BTW, Emmanuel prepared a script to migrate debian-java packages from
s
On Tue, 27 Jan 2015, Emmanuel Bourg wrote:
> If your package isn't 'arch: all' you can depend on default-jdk (>= 2:1.6).
Ah right, good idea.
And even if it is, he can do that, even though it won’t hit
the buildds. Should, even.
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-531
Le 27/01/2015 15:25, Jan Niehusmann a écrit :
> Are there better alternatives?
If your package isn't 'arch: all' you can depend on default-jdk (>= 2:1.6).
Emmanuel Bourg
--
To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas.
On Tue, 27 Jan 2015, Jan Niehusmann wrote:
> I'm trying to make a java package build on all debian architectures. As
> the source code needs java 6 to compile, it fails on some architectures
> when just depending on default-jdk. These are kfreebsd-* and sparc, where
> default-jdk installs gcj inst
Hi,
I'm trying to make a java package build on all debian architectures. As
the source code needs java 6 to compile, it fails on some architectures
when just depending on default-jdk. These are kfreebsd-* and sparc, where
default-jdk installs gcj instead of openjdk.
Depending on openjdk-6-jdk or
Le 27/01/2015 13:01, Stian Soiland-Reyes a écrit :
> Thanks for the help. Agreed that as long as Maven plugins are up to
> date it should generally work with Maven 2.x. One of the things that
> is not upgraded I believe is the Maven reactor (which figures out the
> build order) - and we have had tr
Thanks for the help. Agreed that as long as Maven plugins are up to
date it should generally work with Maven 2.x. One of the things that
is not upgraded I believe is the Maven reactor (which figures out the
build order) - and we have had trouble with this in the past in
earlier Maven versions. (NPE
Le 27/01/2015 12:34, Stian Soiland-Reyes a écrit :
> Is there a debian/maven* rule I can add to edit/remove the
> element at build time?
Hi Stian, there is no such rule but this can be easily patched. Most of
the time Maven 2 is good enough to build the Debian packages. Even if
the core Maven us
Hi - I've been trying to use mh_make to package a Maven project for Debian.
To start light-weight I have begun with just the Maven Parent pom of
our project.
https://github.com/stain/incubator-taverna-maven-parent/tree/debian
after some struggles with the plugins mh_make generated me a nice set
17 matches
Mail list logo
