Hi dear artifactory users!
I just finished upgrading my artifactory to 2.3.3.1 to 2.6.1 and all went
fine. I couldn't accomplish that just updating the files (jars, libs, war,
etc), I needed to do a clean install and restore a full backup, but it's ok.
Now I have just one problem: All my projects are set up to use artifactory
on http://myserver/maven2, but artifactory runs by default in
http://myserver/artifactory and I couldn't find an easy way to change it
besides rename the artifactory.war file inside /var/lib/artifactory/webapps
to maven2.war (and rename it would break my rpm update, I would need to
rename again in every update).
In jetty it was easy to change, but in tomcat it doesn't seem to be.
I found this link
http://stackoverflow.com/questions/6623586/tomcats-context-path-for-a-webapp-not-workingshowing
someone with a similar problem, no useful answer.
What I did now? I set up a workaround through the apache ProxyPass, like
this:
ProxyPass /maven2 ajp://localhost:8019/artifactory
ProxyPassReverse /maven2 ajp://localhost:8019/artifactory
It seems to work fine, the webapp gets redirected to /artifactory before
login and I could run a maven build, that downloaded some artifacts, and I
could also deploy one artifact. But, as I had only bad experiences in the
past changing the suburi on ProxyPass, I ask you: Is there any other way to
workaround this?
Thanks in advance,
--
BrunoJCM
------------------------------------------------------------------------------
Keep yourself connected to Go Parallel:
VERIFY Test and improve your parallel project with help from experts
and peers. http://goparallel.sourceforge.net
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
