Is possible to change the URL path the artifactory is binding on?

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Is possible to change the URL path the artifactory is binding on?

Kostis Anagnostopoulos

Hi,

We are currently switching from codehaus's maven-proxy into artifactory.

We would like to reuse the URL where we had installed maven-proxy, so the
switch would be completely transparent to the client builders (not event
overriding repositories with settings.xml).

So, lets say that the maven0prosy were listening on:
  http://server.com/maven-proxy/repository

In order to make the Artifactory listen on the above URL, we can either:

1) Use apache mod_rewrite (is it OK?), or
2) Fiddle included .war to assign different context (is it possible?)

Is this line of thinking correct?

Any help on the second alternative would be appreciated.



Thank you for your efforts,
  Kostis
--
View this message in context: http://www.nabble.com/Is-possible-to-change-the-URL-path-the-artifactory-is-binding-on--tf3640568.html#a10167105
Sent from the Artifactory-Users mailing list archive at Nabble.com.



Reply | Threaded
Open this post in threaded view
|

Re: Is possible to change the URL path the artifactory is binding on?

Frederic Simon-3
Hi,
Interesting idea...
First playing with the war file name and renaming it maven-proxy.war and changing the jetty.xml declaration if you are using jetty should work. I don't remember any constraints on the context path of artifactory war.
Second, the main issue is with the path after. One of the first feature we added to artifactory compare to maven-proxy is the multi-repositories management in one war. So the name after artifactory is the name of the repository inside artifactory you want to access. And here the default one (aggregate all local and remote repos) is hardcoded "repo" (next version 1.3 should solve this with alias management).
So, there are 2 solutions:
- You use only one local repo named "repository" and it should work. But you can never split deployment repositories.
- Using apache mod_rewrite for transforming "repository" into "repo". So, no need to change the war.

Anyway, in all cases you will not use the feature of multi local repositories which I think is a nice one...

Good luck.

On 4/24/07, ankostis <[hidden email]> wrote:

Hi,

We are currently switching from codehaus's maven-proxy into artifactory.

We would like to reuse the URL where we had installed maven-proxy, so the
switch would be completely transparent to the client builders (not event
overriding repositories with settings.xml).

So, lets say that the maven0prosy were listening on:
  http://server.com/maven-proxy/repository

In order to make the Artifactory listen on the above URL, we can either:

1) Use apache mod_rewrite (is it OK?), or
2) Fiddle included .war to assign different context (is it possible?)

Is this line of thinking correct?

Any help on the second alternative would be appreciated.



Thank you for your efforts,
  Kostis
--
View this message in context: http://www.nabble.com/Is-possible-to-change-the-URL-path-the-artifactory-is-binding-on--tf3640568.html#a10167105
Sent from the Artifactory-Users mailing list archive at Nabble.com.


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users

Reply | Threaded
Open this post in threaded view
|

Re: Is possible to change the URL path the artifactory is binding on?

Kostis Anagnostopoulos
On 4/24/07, Frederic Simon <[hidden email]> wrote:

> Hi,
> Interesting idea...
> First playing with the war file name and renaming it maven-proxy.war and
> changing the jetty.xml declaration if you are using jetty should work. I
> don't remember any constraints on the context path of artifactory war.
> Second, the main issue is with the path after. One of the first feature we
> added to artifactory compare to maven-proxy is the multi-repositories
> management in one war. So the name after artifactory is the name of the
> repository inside artifactory you want to access. And here the default one
> (aggregate all local and remote repos) is hardcoded "repo" (next version 1.3
> should solve this with alias management).
> So, there are 2 solutions:
> - You use only one local repo named "repository" and it should work. But you
> can never split deployment repositories.

But then Artifactory won't be possible to function as a proxy to other
remote repositories, would it?

> - Using apache mod_rewrite for transforming "repository" into "repo". So, no
> need to change the war.
>
> Anyway, in all cases you will not use the feature of multi local
> repositories which I think is a nice one...

I think mod_rewrite, in principal, allows us to have multi-local repos
(and remote proxying).

Am i missing something here?



Admiration for your excellent response time,
  Kostis

>
> Good luck.
>
>
> On 4/24/07, ankostis <[hidden email]> wrote:
> >
> > Hi,
> >
> > We are currently switching from codehaus's maven-proxy into artifactory.
> >
> > We would like to reuse the URL where we had installed maven-proxy, so the
> > switch would be completely transparent to the client builders (not event
> > overriding repositories with settings.xml).
> >
> > So, lets say that the maven0prosy were listening on:
> >   http://server.com/maven-proxy/repository
> >
> > In order to make the Artifactory listen on the above URL, we can either:
> >
> > 1) Use apache mod_rewrite (is it OK?), or
> > 2) Fiddle included .war to assign different context (is it possible?)
> >
> > Is this line of thinking correct?
> >
> > Any help on the second alternative would be appreciated.
> >
> >
> >
> > Thank you for your efforts,
> >   Kostis
> > --
> > View this message in context:
> http://www.nabble.com/Is-possible-to-change-the-URL-path-the-artifactory-is-binding-on--tf3640568.html#a10167105
> > Sent from the Artifactory-Users mailing list archive at Nabble.com.
> >
> >
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/
> > _______________________________________________
> > Artifactory-users mailing list
> > [hidden email]
> >
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
> >
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Artifactory-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
>


Reply | Threaded
Open this post in threaded view
|

Re: Is possible to change the URL path the artifactory is binding on?

Frederic Simon-3


On 4/24/07, Kostis Anagnostopoulos <[hidden email]> wrote:
On 4/24/07, Frederic Simon <[hidden email]> wrote:

> Hi,
> Interesting idea...
> First playing with the war file name and renaming it maven-proxy.war and
> changing the jetty.xml declaration if you are using jetty should work. I
> don't remember any constraints on the context path of artifactory war.
> Second, the main issue is with the path after. One of the first feature we
> added to artifactory compare to maven-proxy is the multi-repositories
> management in one war. So the name after artifactory is the name of the
> repository inside artifactory you want to access. And here the default one
> (aggregate all local and remote repos) is hardcoded "repo" (next version 1.3
> should solve this with alias management).
> So, there are 2 solutions:
> - You use only one local repo named "repository" and it should work. But you
> can never split deployment repositories.

But then Artifactory won't be possible to function as a proxy to other
remote repositories, would it?

No, it will work. By default after looking into the local repo artifactory try to look in all remote repo from the same URL.

> - Using apache mod_rewrite for transforming "repository" into "repo". So, no
> need to change the war.
>
> Anyway, in all cases you will not use the feature of multi local
> repositories which I think is a nice one...

I think mod_rewrite, in principal, allows us to have multi-local repos
(and remote proxying).

Yes, mod_rewrite will let artifactory configuration intact and clean, and so enables you to tune your local repositories for read (maven download) and write (maven deploy).

Am i missing something here?



Admiration for your excellent response time,
  Kostis

>
> Good luck.
>
>
> On 4/24/07, ankostis <[hidden email]> wrote:
> >
> > Hi,
> >
> > We are currently switching from codehaus's maven-proxy into artifactory.
> >
> > We would like to reuse the URL where we had installed maven-proxy, so the
> > switch would be completely transparent to the client builders (not event
> > overriding repositories with settings.xml).
> >
> > So, lets say that the maven0prosy were listening on:
> >   http://server.com/maven-proxy/repository
> >
> > In order to make the Artifactory listen on the above URL, we can either:

> >
> > 1) Use apache mod_rewrite (is it OK?), or
> > 2) Fiddle included .war to assign different context (is it possible?)
> >
> > Is this line of thinking correct?
> >
> > Any help on the second alternative would be appreciated.
> >
> >
> >
> > Thank you for your efforts,
> >   Kostis
> > --
> > View this message in context:
> http://www.nabble.com/Is-possible-to-change-the-URL-path-the-artifactory-is-binding-on--tf3640568.html#a10167105
> > Sent from the Artifactory-Users mailing list archive at Nabble.com.
> >
> >
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/
> > _______________________________________________
> > Artifactory-users mailing list
> > [hidden email]
> >
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
> >
>

>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Artifactory-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
>

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users