Hi Ben, I think i have not defined a snapshot repo in this alpha1 WAR... just central (repo1.maven.org) and 3 local ones.
And yes, SNAPSHOT repositories are handled too. Of course, do not forget it IS alpha1 :) ~t~ On 5/25/06, ben short <[EMAIL PROTECTED]> wrote:
Hi, Had a quick play and it looks good. I wonder if this is what the maven repository-manager was ment to be like. I couldnt download the maven-jar-plugin 2.1-SNAPSHOT though, but i think i remember seeing a post about that. If it possible to setup more repositories, so i can have a snapshot one managed by it too? Ben On 5/25/06, Tamás Cservenák <[EMAIL PROTECTED]> wrote: > Hi all, > > i'd like to announce the Proximity maven proxy release: > > Proximity 1.0.0 alpha1 is out! > > Look for it on site (sorry for bad uplink, this is my ADSL): > https://is-micro.myip.hu/projects/ismicro-commons/proximity > > Features in short: > > - *2-in-1* - With Proximity you can *host your own private repo while > proxying other repositories* and have all the benefits of local (read > FAST) repository access. > - *Access control* - Proximity is well suited for *corporate > deployments*, since it has extensible and configurable AccessManager. > Proximity has various AccessManager and AccessDecisionVoter implementations > out-of-the-box. Some examples: IP based access restriction, HTTPS access > only with client certificate verification and access management based on it. > Access control may be configured on Proximity level and on repository level > independently. > - *HTTP, HTTPS and HTTP Proxy support* - On it's front, Proximity is > unaware is it serving artifacts over plain HTTP or HTTPS (it is container > setup, eg. Tomcat). On it's back Proximity Remote Peer is powered with > latest *Jakarta Commons HttpClient* thus has all the capabilities that > Commons HttpClient has. HttpClient configuration is fully exposed through > Spring context, allowing easy reconfiguration (like http proxy setup). > Furthermore, by employing custom front-ends (the Servlet controller class) > and appropriate AccessControl class Proximity is ready to fit any specific > needs for authorization (authentication is left to container!). > - *Locally reusable proxy storage* - The local storage of defined > repositories are *complete on-demand-mirrors of real remote > repositories*, thus usable for republishing (eg. using simple HTTP > server. But you will share only the currently downloaded artifacts then). > - *Aggregating, but in a smart way* - It is able to host multiple > repositorties, and depending on config, they may or may not be proxied > remote repositories. Proximity may be used to serve private artifacts (those > not uploadable to central due to their licence) as well on local network > only. Still, Proximity tracks and *organizes downloaded artifacts > separatly*, following the origin of the artifact and not mixing them > together. > - *Piping* - Thanx to smart aggregation, Proximity is able to form a > pipe of it's instances, thus for example on corporate network you may have > one central Proximity on a machine with allowed fast outbound traffic, and > multiple instances on local subnetworks where no direct outbound traffic is > possible. Proximity will all way down to last instance in pipe follow and > *keep artifacts in separate storage*, following their originating > repository. Moreover, you will have to publish in house artifacts only in > one place. > - *Fresh as needed* - Proximity can be persistent or not, as > configured. Moreover, Proximity recognizes the following kinds of items: > Maven Snapshots, Maven2 POMs, Maven2 metadata and the rest is "just" > artifact. All of these kinds have independent timeout configuration. Thus, > *every of these item kinds can be: never updated once downloaded, > always updated on request or timeouted*. These are independent > settings (per kind). > - *Fast searches* - With time, your Proximity storage will grow. > Proximity uses *Apache Lucene* as it's indexer to provide fast > searches on repositories. > - *Reusable software* - Proximity Core is *transport and J2EE > technology unaware*, this webapp you see is just a front-end for > Proximity implemented using Springframework, Velocity and *two > controller class*. > - *Extensible* - Proximity Core is *extensible* and usable in many > different ways and containers. The author have used it in Spring framework > container (this webapp actually) and in Codehaus Plexus container (together > with embedded Maven2), SAS and/or Danube. > > > The alpha1 is downloadable as a self-sufficient WAR and has been tested on > Apache Tomcat 5.5.17. Just grab a Tomcat and drop WAR on it! > > > Have fun! > cstamas > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
