devicemap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reza Naghibi <>
Subject Re: Improper "aliasing" of devices
Date Fri, 02 Jan 2015 06:22:29 GMT
Werner, please undo this commit immediately:

You just undid this ticket:

That ticket was a request from an important user, Infomaker Scandinavia AB.

Secondly, I do not see the connection between that change and your claim that "aliasing" in
device data is breaking the client. I am shocked that you are being so persistent with very
little idea of what is going on. Quite literally, you are grasping at straws, only now you
are committing code. This is a serious problem.

I closed DMAP-119 and DMAP-120 because the unit tests fail when you link in device data 1.0.2.
The unit tests were designed around 1.0.1. The above enhancement, DMAP-86, added new devices
to 1.0.2. You then proceeded to test those devices against unit tests written against 1.0.1.
So obviously they are going to fail. This has nothing to do with aliasing.

Werner, this is your final warning. Please undo these changes immediately. Everything you
have done and said tonite leads me to believe you are extremely confused regarding how the
data and API work and what the goal of this project is. After you revert the changes you made
to the data and API, you are not to commit anymore changes to trunk. Am I clear?

No more arguments Werner. This is very serious. Please just do as I say and give it a break
for a few days.

      From: Werner Keil <>
 Sent: Friday, January 2, 2015 12:48 AM
 Subject: Improper "aliasing" of devices

As of data 1.x the attempt of "aliasing" device data by trying to override
a parent device with just a single incomplete line is not working and

It breaks both clients.

If such "simplified" device data modeling was desired, it has to be done
for 2.x, as it breaks compatibility with the 1.x and W3C data model.

After elliminating the wrong/incomplete line for "SGP312" remaining SGP311
is properly recognized.

Based on Data 1.0.1 it seems the 2 new/wrong entries are ignored, in fact
if below issue

Tests run: 1176, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.67 sec
<<< FAILURE! - in org.apache.devicemap.DeviceMapClientTest
testDeviceMapClient[1174](org.apache.devicemap.DeviceMapClientTest)  Time
elapsed: 0 sec  <<< FAILURE!
org.junit.ComparisonFailure: classification failed for 'Mozilla/5.0 (Linux;
Android 4.3; SGP311 Build/10.4.B.0.577) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/38.0.2125.102 Safari/537.36' *expected:<[genericAndroid]> but
at org.junit.Assert.assertEquals(

is addressed using data 1.0.2-SNAPSHOT with the correct test data file for
SGP311, the extra line SGP312 in the test file is safely ignored.

Please if needed add a complete record,

This fixes both and you bluntly and prematurely
brushed away.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message