I was thinking of a proxy component that is part of the repository manager. It should certainly utilise the indexing, caching and discovery where appropriate.
It should just be pure Java - no http stuff. It's responsibility would be checking if the artifact it is given is out of date or missing locally, and then go and fetch it from the appropriate remote repository/repositories configured. It should use Wagon for this so that the repositories can be file, scp, http, etc. I think it would be included in the main webapp, wrapped by either a webwork action or a servlet filter (or maybe both). I think it is worth going through proximity and maven-proxy since both authors have volunteered to merge the code, and build a feature list from them (and maybe where it is implemented in their code for later reference). We can then say which already exist in MRM (eg, search), which are needed, and which don't make any sense and won't be migrated. How does this sound? - Brett Edwin Punzalan wrote: > > I've been thinking of a good design for the MRM and maven-proxy > integration and got stuck with this issue: > > (1) Should we setup the maven-proxy app and then allow it to use MRM > indexing and caching and other stuffs? > or > (2) can have an MRM app that can accept the same config that maven-proxy > uses ? > > or is there a better way? > > > Comments/suggestions are highly appreciated... > > ^_^ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
