Nicolas, I've already started some work on rejiging the repository/proxy backend.
http://svn.apache.org/repos/asf/archiva/sandbox/new-repository-api/src/main/java/org/apache/archiva/repository/Repository.java Look ma! No java.io.File :) Ill post about this later to the list but there is plenty todo if you want to lend a hand. James On Thu, 2008-07-17 at 07:15 +0200, nicolas de loof wrote: > I also would like to have support for managed repositories on remote > filesystems, not just based on the java.io.File API. I myself have to store > my corporate repos on a file server and access them via SMB from my archiva > server. > > Maybe commons-vfs could help ? > > Nicolas > > 2008/7/17 Maria Odea Ching <[EMAIL PROTECTED]>: > > > On Wed, Jul 16, 2008 at 9:53 AM, James William Dumay <[EMAIL PROTECTED]> > > wrote: > > > > > Hey guys, > > > With 1.1 almost out the door I'm already thinking about what we may want > > > to-do for 1.2. > > > > > > The last release cycle was pretty long - but we introduced a lot of > > > features and improvements (bugs, too, I'm sure.. :P ) but I think the > > > general consensus is that we want to shorten our release cycle. > > > > > > I'm proposing that we choose a small amount of feature/improvement > > > issues for 1.2 and bump the rest to 1.3. Id personally prefer this to be > > > more of a "engine room" release focusing on parts of Archiva that are > > > not so user visible. > > > > > > While being less glamorous, this will allow us to clean up after the big > > > feature work in 1.2. > > > > > > Here are a few features/improvements I would like to see in the next > > > release: > > > * MRM-749 - Support m2eclipse index format > > > * MRM-832 - Investigate future security framework options (Spike? Actual > > > work could probably be scheduled for 1.3) > > > * MRM-541 - convenient way to take proxies offline > > > * MRM-684 - clients timeout due to archiva blocking on downloading large > > > files > > > > > > > Looks good to me.. > > > > > > > > > > Anyone got anymore? :) > > > > > > > I would also like to add the interpolation issues in Archiva, namely: > > * MRM-615 - When scanning, Archiva doesn't resolve properties/variables of > > POMs in managed repositories > > * MRM-686 - 'Unable to find project model' when artifactId contains > > property > > placeholders e.g. ${project.parent.artifactId} > > * MRM-620 - pom.xml that inherit version from parent show up in reports as > > "has an invalid project model" > > > > Thanks for starting this thread James! :) > > > > > > > Thanks > > > James > > > > > > > > > -Deng > >
