At the very least, I'd like the interface to be the same.
So far I have not found any reason to believe that use of the
org.apache.geronimo.kernel.repository.* interfaces will be a
problem. We just write a facade that impls our repo interfaces and
then delegates to the Maven2 API.
Okay... though I think it should be relatively simple...
I had been chatting with some Atlassian developers about potentially
using the maven2 repo for plugin discover/download for confluence and
jira.
From chatting with some maven2 peeps looks like it might be
relatively simple to get
At the very least, I'd like the interface to be the same. Can you
find and post the maven2 repository interface to this list?
My feeling on this is if it works it works. I don't think we should
turn on downloading by default anytime soon, but I think we should
make it available as an
Cuz, I think that is will be too much work to get in and tested.
We're trying to get this done in the next few days, so it is just
easier to write one that can read the m2 layout.
-dain
On Feb 7, 2006, at 1:39 PM, Jason Dillon wrote:
Why not reuse the Maven2 code to handle repository
I took a quick look. How closely do you think you will be able to
support the current ListableRepository, WriteableRepository, and
Repository interfaces? The console currently makes use of both forms
of the copyToRepository method (inputstream and file) ... but I suspect
we could conform to
I have added a repository that can read a repo using the maven 2
layout. This required a few changes to the Repository interface, so
please take a look at it. The code is the configId branch that David
Jencks and I are working on for the quick 1.1 release (old 1.0.1).
Specifically, Aaron
