> On Jun 21, 2017, at 8:06 AM, Christofer Dutz
> wrote:
>
> Ok I changed the android stuff to build with Java8 and to use retrolambda to
> produce a java7 version and ensure it’s valid java7 using the animalsniffer
> plugin. So that should be ok.
I noticed that. Thanks!
> The thing with empt
Ok I changed the android stuff to build with Java8 and to use retrolambda to
produce a java7 version and ensure it’s valid java7 using the animalsniffer
plugin. So that should be ok.
The thing with empty jars is that if for example I would be building some
application with maven targeting andro
I ask things without understanding some of the implications/consequences :-)
> On Jun 20, 2017, at 11:03 AM, Christofer Dutz
> wrote:
> ...
> Well I could move the module back outside of the android module. The problem
> with this is, that as far as I understood it, it won’t work in the Java8
Same here, busy being distracted with other stuff.
Dan.
On Tuesday, June 20, 2017 7:20 AM, Susan Cline wrote:
We are here, we are here, we are here … Hi Chris, yes, there are. It’s a bit
of a quiet time now, but we most certainly are.
Cheers,
Susan
> On Jun 19, 2017, at 11:22 PM, Ch
Hi Dale,
Well I could move the module back outside of the android module. The problem
with this is, that as far as I understood it, it won’t work in the Java8
version and it is only used in the android distribution – which must be java7.
The current version will definitely mislead people to try
> On Jun 20, 2017, at 2:22 AM, Christofer Dutz
> wrote:
> ...
> Ok … so to me it sounds like I should simply move the android directory to
> the android platform part of the build - So it’s only built, when building
> the android distribution. Then to remove it from the java7 platform. That
>
We are here, we are here, we are here … Hi Chris, yes, there are. It’s a bit
of a quiet time now, but we most certainly are.
Cheers,
Susan
> On Jun 19, 2017, at 11:22 PM, Christofer Dutz
> wrote:
>
> Chris
>
> PS: By the way … are there any other Edgent developers? It seems quite quiet
>
Hi all,
So, I just pushed the finished andoid platform support.
What I did, was to move the android module from the root into the android
platform. After that I had to refactor the code to be directly compilable with
Java7.
Also, I ensured that as soon as someone wants to build the android plat
Hi Dale,
Ok … so to me it sounds like I should simply move the android directory to the
android platform part of the build - So it’s only built, when building the
android distribution. Then to remove it from the java7 platform. That should be
all from a build point of view. I could duplicate th
> On Jun 19, 2017, at 4:20 PM, Christofer Dutz
> wrote:
> ...
> If you could write down exactly what the difference is between java8/7 and
> android, then I could probably finish that tomorrow.
Android is our j7 platform release with these changes:
- will not support due to no JMX support (
Datum: 19.06.17 21:01 (GMT+01:00)
An: dev@edgent.apache.org
Betreff: Re: Java7 compatability issue in analytics/sensors
Success! Now I need to spend some time understanding the results :-)
questions to follow
$ mvn -t toolchains-local.xml -Djava8.home=$JAVA_HOME clean install site:site
Success! Now I need to spend some time understanding the results :-)
questions to follow
$ mvn -t toolchains-local.xml -Djava8.home=$JAVA_HOME clean install site:site
-Pplatform-java7,platform-android
…
[INFO] Apache Edgent (Java 7): Test: SVT .. SUCCESS [ 57.896 s]
[INFO] --
Hmm… changed the CLI options order to match that in .travis.yml and it’s
working now.
I’ll report once everything has run.
> On Jun 19, 2017, at 12:05 PM, Dale LaBossiere wrote:
>
> Did you commit&push all of your changes?
> I pulled the latest PR-309 stuff. Created my toolchains-local.xml
>
Did you commit&push all of your changes?
I pulled the latest PR-309 stuff. Created my toolchains-local.xml
(copied/edited toolchains-travis.xml)
and then...
> On Jun 19, 2017, at 10:13 AM, Christofer Dutz
> wrote:
>
> mvn –Pplatform-java7,platform-android –Djava8.home={JAVA8_HOME} –t
> toolc
Ok guys … now some MAJOR update :-)
I managed to setup a build that build all modules with Java8, if the profile
“platform-java7” is enabled, also Java7 versions are produced by unpacking the
Java8 versions in some pom-only modules, applying retrolambda there and then
running all unit- and inte
Nice catch!
I created https://issues.apache.org/jira/browse/EDGENT-423
— Dale
> On Jun 18, 2017, at 8:04 AM, Christofer Dutz
> wrote:
>
> While fine tuning my maven migration, I stumbled over a problem in the
> analytics/sensors modules.
> As part of the build I am validating the classes for J
16 matches
Mail list logo
