Hi Jeff,
Jeff McAffer wrote:
There currently is no support for "known repositories". At least not
that I know of. :-) At various times we talked about priming the repo
list etc in installed configurations but that would likely have been
with "loaded" repos.
Is discovery expensive? For exam
There currently is no support for "known repositories". At least not
that I know of. :-) At various times we talked about priming the repo
list etc in installed configurations but that would likely have been
with "loaded" repos.
Is discovery expensive? For example, if someone clicked an "A
I have created a couple of plugins that use maven2 in order to publish the
jar files in the repository.
I would like to be able to reference these budles in a similar manner as one
would reference remote jars.
However so far I have not found a good way to reference remote bundles (file
path/url)
Hi Jeff,
Jeff McAffer wrote:
Unless it has changed since I messed with it, that
FileServerApplication was some hacky attempt at putting an HTTP server
on front of some repos. It may be an ok starting point but i'd not
put too much weight on it. Perhaps we should just have one thing that
exp
Unless it has changed since I messed with it, that FileServerApplication
was some hacky attempt at putting an HTTP server on front of some
repos. It may be an ok starting point but i'd not put too much weight
on it. Perhaps we should just have one thing that exposes a set of
repos through HTT
Hi Markus,
Markus Alexander Kuppe wrote:
Scott Lewis wrote:
but it would be desirable to have a UI with less detail, that only
shows meta-data and artifact repos rather than all services...and
doesn't show all the details of the service properties as the ECF
discovery view does.
Hi,
do we
Scott Lewis wrote:
but it would be desirable to have a UI with less detail, that only shows
meta-data and artifact repos rather than all services...and doesn't show
all the details of the service properties as the ECF discovery view does.
Hi,
do we really need a separate UI or could we achie
