[
https://issues.apache.org/jira/browse/DMAP-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Werner Keil updated DMAP-169:
-----------------------------
Labels: Java Maven build question tck tck_issues (was: Java Maven build
question tck_issues)
> Apply standard build infrastructure to "reference" client
> ---------------------------------------------------------
>
> Key: DMAP-169
> URL: https://issues.apache.org/jira/browse/DMAP-169
> Project: DeviceMap
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 2.0.0 Java
> Reporter: Werner Keil
> Labels: Java, Maven, build, question, tck, tck_issues
>
> 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?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
