You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Edwin Punzalan <ep...@exist.com> on 2006/01/11 09:02:15 UTC
Maven Repository Manager and Maven-Proxy integration
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Repository Manager and Maven-Proxy integration
Posted by Edwin Punzalan <ep...@exist.com>.
I think that's great.
I should now take a look at proximity and create a feature list, which
to maintain/improve and which to discard.
I'll be mailing again for your inputs when I collect them. Thanks.
Brett Porter wrote:
>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: dev-unsubscribe@maven.apache.org
>>For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Repository Manager and Maven-Proxy integration
Posted by Brett Porter <br...@apache.org>.
Definitely a possibility!
Milos Kleint wrote:
> maybe unrelated, but anyway..
>
> the repository manager is designed as server side application? Will xmlrpc
> access be possible for integration with IDEs? or what is designed
> approached for this usecase?
>
> Milos
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Repository Manager and Maven-Proxy integration
Posted by Milos Kleint <mk...@gmail.com>.
maybe unrelated, but anyway..
the repository manager is designed as server side application? Will xmlrpc
access be possible for integration with IDEs? or what is designed
approached for this usecase?
Milos
On 1/12/06, Brett Porter <br...@apache.org> wrote:
>
> 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: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Maven Repository Manager and Maven-Proxy integration
Posted by Brett Porter <br...@apache.org>.
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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org