Den 27.09.2019 10:15, skrev mer...@debian.org:
jline v2.14.6 is in Debian as libjline2-java, wouldn't this work?
FYI
I did a test of using jline 2.14.6 when running scala 2.12.0-M1 repl,
and it failed with NoSuchMethodError. Downloading and compiling jline
2.14.1, on the other hand, did wo
Hi Andrius,
Den 27.09.2019 10:15, skrev mer...@debian.org:
I have managed to get around Scala FTBFS problem [1] for now, will
continue looking into your script.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941211
Are you trying to compile scala 2.11.12 from the source debian package
Hi
I forgot to mention that the script is located at
https://bitbucket.org/tfinneid/scala-build-process/src/default/build-2.12.0-M1.sh
It runs partially on Debian unstable now, with some errors I will look at:
1- The scala library depenencies are currently hardcoded, so it doesnt
find the cor
Den 26.09.2019 21:29, skrev Thomas Finneid:
I am currently working on making the script work in debian unstable,
using system installed packages for jdk, scala 2.11.12, ant, jline etc.
I will probably have something workign by the end of the evening.
Hi again,
I have updated the scala
On 26.09.2019 16:54, mer...@debian.org wrote:
I have cloned your repo and started playing around. AFAIK, your build
script requires jars built from earlier version of Scala (akka-actor.jar
and friends). Thus I've tried building Scala and ran into a FTBFS [1]. I
will have to figure it out before
Hi
After much work (and previous discussions on this list and with the
Scala team) I have finally created a shell script that builds Scala
2.12.0-M1, instead of the circular dependency of Scala and Sbt.
I am currently refreshing my limited knowledge of creating a debian
package and finetunin
, mer...@debian.org wrote:
Hi Frédéric and Thomas,
Sorry for the delay. I must admit I wasn't aware the dogfooding problem
is so difficult to avoid.
On 2019-08-17 07:53, Thomas Finneid wrote:
The good news is that after talking with some of the maintainers of
Sbt and Scala, they would be very inte
Den 14.08.2019 11:54, skrev Frédéric Bonnard:
But for sbt, as far as I remember, you cannot just javac * and scalac *
(as for the other simple sbt- packages : see d/rules of
sbt-launcher-interface, sbt-serialization etc), because pieces of the
source code is generated during the build process an
Hi
I am just getting to know things, so just a quick question. in reference
to the scla / sbt upgrade discussion threads.
I read through th e Debian policy and specifically about the contrib
archive
(https://www.debian.org/doc/debian-policy/ch-archive.html#the-contrib-archive-area)
does th
On 15.02.2019 18:49, Markus Koschany wrote:
Frederic did the bootstrap part wrong. Unfortunately nobody corrected
him in time before he tried to use the prebuilt upstream binaries for
bootstrapping sbt. Just ignore the current rules file. We have to come
up with something better.
Ok, I can t
On 14.02.2019 18:19, Markus Koschany wrote:
Experimental is merely a playground for developers who think their
packages are not ready for unstable yet. What you usually do is to
bootstrap the package and build all those parts that are essential to
get a functional compiler/build tool. Then you
On 14.02.2019 11:55, Markus Koschany wrote:>
> What you can do of course is to patch sbt or scala. We use so-called
> quilt patches. For instance take a look at sbt. In debian/patches you
> can see several Debian specific patches that change the default Maven
> repository for example.
Thats what
On 14.02.2019 11:43, Markus Koschany wrote:> [btw are you subscribed to
the list? Then I don't need to CC you]
Sorry, it seemed I had subscribed to the wrong java list, but should be
fixed now.
>> No matter how one looks at it, Debian needs to make a strategy change
>> regarding OpenJdk relea
On 12.02.2019 23:48, Markus Koschany wrote:
Personally I would like to keep OpenJDK 8 as well but you also have to
keep the following points in mind:
All these ar good reasons. The issue here is that Jdk8 -> jdk11 is a
special case. Oracle decided to just change the entire release scheme to
On 07.02.2019 15:29, Thorsten Glaser wrote:
If there’s no such path, you’d need more intermediate versions and
upload them, one after another. Into experimental would most likely
be the best, with the understanding that these are intended for
bootstrapping, not for use by users, although they
On 12.02.2019 22:56, Markus Koschany wrote:
Hi,
Am 12.02.19 um 22:45 schrieb Thomas Finneid:
[...]
Is there a jdk6 version available in Debian? I think I have read
something about removing jdk-8 from debian, is that correct?
Also, if I understand the Debian/Java Policy correctly, all jvm
Hi
I have been looking into language and jdk version requirements for the
different version of sbt and scala, for compiling and running. I have
experienced problems if they did not compile or run on their target jdk
versions.
So far I have concluded that sbt 0.13.17 requires jdk-6 to compile
Sorry for all the confusing questions, but getting to know a new build
process, especially such an advanced one as Debians, is quite
confusing to begin with.
On 08.02.2019 02:29, Thorsten Glaser wrote:
On Thu, 7 Feb 2019, Thomas Finneid wrote:
One thought, both the scala team and the
On 07.02.2019 15:29, Thorsten Glaser wrote:
On Thu, 7 Feb 2019, Thomas Finneid wrote:
downloads and installs the required scala and sbt version inside the project
This is absolutely not going to happen in Debian.
I might have been a litte unclear by my wording, when I said scala/sbt
Hi
Having dug a little deeper into building scala 2.12.8, I have found two
issues that needs some explaining.
Scala and sbt environemnts are a bit different from the ordinary java or
C environments.
I know there already exists scala and sbt packages in debian, but as far
as I understand th
On 05.02.2019 16:40, Thorsten Glaser wrote:
Then, yes, an upgrade to 2.12 should be done. Using the new --release
option in javac 11, it can be built looking as if it were using JDK 8,
but JRE 8 is not really available any more either (I believe the idea
was to ship buster without src:openjdk-
Apologies for the iPhone typo: last paragraph about sbt, I never meant to type
“ant 1.x” but rather “sbt 1.x”
Thomas
Sendt fra min iPhone
> 5. feb. 2019 kl. 15:08 skrev Thomas Finneid :
>
> Hi
>
> What I mean is that the scala projects own build process built and tested
scala and sbt and upgrade scala to
2.12.
Hope this explained it better.
Regards
Thomas
Sendt fra min iPhone
> 5. feb. 2019 kl. 13:37 skrev Thorsten Glaser :
>
>> On Mon, 4 Feb 2019, Thomas Finneid wrote:
>>
>> NB1: Scala 2.11 is built for java 6, and has only rudiment
Hi
I am a scala developer, of sorts, and want to help ease the installation
of the development environment for scala developers in debina/ubuntu.
I noticed that the scala package only contains scala 2.11, and the jdk
is on version 8 and 11(?!). So I was wondering if I could start by
helping
24 matches
Mail list logo
