I codenamed it "devicemap-java-classifier", but used the then common OSGi alike artifactId.
"devicemap-java-api", "devicemap-java-client" or even either of those without the "java" seems OK. If the W3C Simple DDR functionality could be 100% available within that artifact, there may not be need for a second/alternate API in the future, as of now, it doesn't seem to provide any of that, so "devicemap-simpleddr" (or with a "-java" if we want to do that consistently?[?]) also has perfect justification. The only reason why it isn't automatically built is the lack of a proper Maven-compliant JAR, see prior message. Werner On Tue, Jul 8, 2014 at 6:13 PM, Reza <[email protected]> wrote: > Right now the java api is called "devicemap-java" and its in the > "org.apache.devicemap" package. Not sure if this is a good name because the > "java" is redundant since the artifact is in a java repo manager. I was > thinking of calling it "devicemap-api" or "devicemap-client" or maybe > "devicemap-java-api"??? Thoughts? > > Not a big deal if we change it later since we are still 1.0, but would > like to get things straight before the 1st release. > > The data repo is "devicemap-data" and I think thats a well suited artifact > id.
