Mailing-List: contact commits-help@devicemap.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@devicemap.apache.org
Date: Sat, 17 Dec 2016 16:25:59 +0000 (UTC)
From: "Werner Keil (JIRA)" <jira@apache.org>
To: commits@devicemap.apache.org
Message-ID: <JIRA.12998263.1471542621000.546268.1481991959382@Atlassian.JIRA>
In-Reply-To: <JIRA.12998263.1471542621000@Atlassian.JIRA>
References: <JIRA.12998263.1471542621000@Atlassian.JIRA> <JIRA.12998263.1471542621796@arcas>
Subject: [jira] [Resolved] (DMAP-195) Remote JAR
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 17 Dec 2016 16:26:02 -0000


     [ https://issues.apache.org/jira/browse/DMAP-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Werner Keil resolved DMAP-195.
------------------------------
    Resolution: Won't Fix

> Remote JAR
> ----------
>
>                 Key: DMAP-195
>                 URL: https://issues.apache.org/jira/browse/DMAP-195
>             Project: DeviceMap
>          Issue Type: Task
>          Components: Java Client, Java Examples
>            Reporter: Werner Keil
>            Assignee: Werner Keil
>              Labels: loader, maven, remote
>
> Right now, DeviceMap client can read from a remote URL or a local JAR, but not a remote JAR. In order to read e.g. from a Maven repository (directly from the client because devicemap-data and devicemap-data-sources are exactly the same) or similar location, not just the local classpath.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)