Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
2.0.0 Java
-
None
Description
Currently client files and the TCK in 2.0 "reference" are all built with proprietary .sh scripts, being environment-specific and making assumptions about the relative path between checked-out artifacts (e.g. "../../data/2.0" etc.)
Maven works fine for all other Java artifacts in DeviceMap, so why not use Maven here?
Attachments
Issue Links
- relates to
-
DMAP-168 Provide org.apache package structure to "reference" client
- Closed