P4Web would work. Our exact implementation is to use mirrors to defer load from the Perforce server (large organisation) and improve performance for remote offices. The mirrors stay in sync and simply make the directory available with httpd.
Ivy settings, just use a URL resolver pointed at the root of the ivy repo on the share. Daniel had a good example of that in his email. In terms of publishing, we are not yet sharing publishing to the shared repository. I created a space in our project for jars created by our build system to be published to - but should we decide to, it would be a simple matter of configuring httpd to allow it. On Wed, Jan 26, 2011 at 11:29 AM, Felix Drueke <fdru...@orga-systems.com>wrote: > Thanks for that valuable information. > > Would publishing be possible in your example or is it only meant for > retrieving? > > Felix > > > Holmes, Daniel wrote, on 01/26/2011 05:18 PM: > > We have perforce also, and with p4web, there is a URL path to depot >> contents. I never implemented it, but this was the suggested URL >> resolver I gave to someone who wanted to directly retrieve from >> perforce. (On my team, we just sync for a common Filesystem and use >> Filesystem resolver). So the below should be close but maybe needs >> slight debugging. >> >> Here is a URL from p4 web to a specific jar file in our repository >> >> http://p4web.company.com:4040/@rev1=head@//depot/prod/common_ivy_repo/ma >> in/com.google/collections/1.0/google-collect-1.0.jar >> >> Based on the URL resolver link from the Ivy reference and the settings >> we use for file system recolving for ivy, I think you would need a >> resolver configured like this >> >> <property name="ivy.repo" value=" >> http://p4web.company.com:4040/@rev1=head@//depot/prod/common_ivy_repo/ma >> in"/> >> >> <resolvers> >> <url name="public"> >> <ivy >> pattern="${ivy.repo}/[organisation]/[module]/[revision]/ivy-[module]-[re >> vision].xml" /> >> <ivy >> pattern="${ivy.repo}/[organisation]/[module]/[revision]/ivy-license-[org >> anisation]-[revision].xml" /> >> <artifact >> pattern="${ivy.repo}/[organisation]/[module]/[revision]/[artifact].[ext] >> " /> >> <artifact >> pattern="${ivy.repo}/[organisation]/[module]/[revision]/[artifact]-[revi >> sion].[ext]" /> >> </url> >> </resolvers> >> >> >> Daniel >> >> >> -----Original Message----- >> From: Felix Drueke [mailto:fdru...@orga-systems.com] >> Sent: Wednesday, January 26, 2011 10:14 AM >> To: ivy-user@ant.apache.org >> Subject: Re: ivy resolver for perforce >> >> Hi Jonathan, >> >> thanks for the prompt answer! >> Did you use P4Web as an interface? >> Can you describe that in more detail, e.g. how does your ivysettings >> look like? >> >> Felix >> >> >> Jonathan Williams wrote, on 01/26/2011 04:08 PM: >> >>> Hi Felix, >>> >>> I am running a similar setup at my company where our Ivy repo is >>> >> checked in >> >>> to Perforce. I was unable to find any plugins for Perforce at the time >>> >> (just >> >>> before Xmas this year). Our solution was to provide an HTTP interface >>> >> to the >> >>> root directory of the repo directory structure. Works like a charm. >>> >>> -Jonathan >>> >>> 2011/1/26 Felix Drueke<fdru...@orga-systems.com> >>> >>> Hi, >>>> >>>> I just found the ivy subversion resolver at >>>> http://code.google.com/p/ivysvn/ . >>>> Does a similar resolver exist for perforce already? >>>> Does anyone work on that? >>>> >>>> We're evaluating the use of ivy for our company and we use Perforce >>>> >>> as our >> >>> SCM. >>>> Instead of setting up a Repository manager like Nexus or Artifactory >>>> >>> we're >> >>> thinking about storing all artifacts in perforce. >>>> Are there ways to store them there (and retrieve them from there) >>>> >>> other >> >>> than >>>> via a ivy perforce resolver? >>>> >>>> Thanks for any thoughts and comments! >>>> >>>> Best regards, >>>> Felix >>>> >>>> The information included in this e-mail and any files transmitted >>>> >>> with it >> >>> is strictly confidential and may be privileged or otherwise protected >>>> >>> from >> >>> disclosure. If you are not the intended recipient, please notify the >>>> >>> sender >> >>> immediately by e-mail and delete this e-mail as well as any >>>> >>> attachment from >> >>> your system. If you are not the intended recipient you are not >>>> >>> authorized to >> >>> use and/or copy this message and/or attachment and/or disclose the >>>> >>> contents >> >>> to any other person. >>>> >>>> >>> >> The information included in this e-mail and any files transmitted with >> it is strictly confidential and may be privileged or otherwise protected >> from disclosure. If you are not the intended recipient, please notify >> the sender immediately by e-mail and delete this e-mail as well as any >> attachment from your system. If you are not the intended recipient you >> are not authorized to use and/or copy this message and/or attachment >> and/or disclose the contents to any other person. >> >> > The information included in this e-mail and any files transmitted with it > is strictly confidential and may be privileged or otherwise protected from > disclosure. If you are not the intended recipient, please notify the sender > immediately by e-mail and delete this e-mail as well as any attachment from > your system. If you are not the intended recipient you are not authorized to > use and/or copy this message and/or attachment and/or disclose the contents > to any other person. >
