Hi Peter:
I’m not sure if supporting MAF is critical to River’s success, but even so I am
in favour of removing the examples from the JTSK build. Anyone else have an
opinion?
I’m curious though, why it’s the browser specifically that doesn’t build - what
did you find?
Cheers,
Greg.
On F
Maf 2.1.0 supports java 8 compact profile 2.
If I remove the browser example from qa-refactor it builds on this profile.
Greg, if your including the browser in the river examples project, I can delete
it?
If so, we can support iphone and android.
Regards,
Peter.
Hi Mike,
Which build & platform?
Regards,
Peter.
- Original message -
> Following along in https://river.apache.org/building-river.html, I
>
> $ cd $RIVER_HOME
> $ ant
>
> ...
>
> jsk-dl.jar:
> [java] Exception in thread "main"
> java.lang.ArrayIndexOutOfBoundsException
Hi Mike:
What you’re running into is the fact that part of River’s build system
(classdep, in fact) uses the ASM library, and that library changed
significantly between Java 7 and Java 8. The net result is that the 2.2.2
release does not build under JDK8.
If you have a JDK7 installation ar
Following along in https://river.apache.org/building-river.html, I
$ cd $RIVER_HOME
$ ant
...
jsk-dl.jar:
[java] Exception in thread "main"
java.lang.ArrayIndexOutOfBoundsException: 5735
[java] at org.objectweb.asm.ClassReader.readClass(Unknown Source)
[java] at org.obj
On 13/02/15 15:26, Patricia Shanahan wrote:
Have you looked at the "River-examples project" thread? The objective is
to create a better "getting started" experience
LOL - just started trawling through it. I did kick Jini around a decade
and a half ago, so didn't need to go through the "gettin
Regardless of whether we actually reorganize the code base, I think
something like this would be useful high level documentation for giving
an idea of how things fit together.
Have you looked at the "River-examples project" thread? The objective is
to create a better "getting started" experien
As part of shaking the rust from my aging memory, and with my minds-eye
looking towards a more modular code experience for Jini/River, I drew up
a small diagram of how things look to me/how I think the codebase could
be chopped up into smaller sub-projects (with dependencies).
https://drive.go
As part of shaking the rust from my aging memory, and with my minds-eye
looking towards a more modular code experience for Jini/River, I drew up
a small diagram of how things look to me/how I think the codebase could
be chopped up into smaller sub-projects (with dependencies).
https://drive.go
