I'd say yes, except that using svn.apache.org as a repo URL is
notoriously problematic due to the configuration of httpd there.
Best bet is to create a repo in svn, then auto-export that tree on to
our zone, and then configure a vanilla httpd there to serve it up, so
that users don't get build failures trying to resolve stuff from http://svn.apache.org/
...
I had planned on creating a little experiment to show this, but then I
got sick.
--jason
On Aug 7, 2008, at 8:13 PM, Donald Woods wrote:
We have danced around the problem of not being able to build
Samples, Plugins or GEP from a clean m2 repo without building the
Server's repository subdir for long enough. I believe it is time to
create the following location in SVN -
geronimo/repo
Which would hold our private patched artifacts of other projects
(like Tomcat, Pluto, ...), just like the OpenEJB team has done for
some of their private depends.
I don't see this as a major hit to the svn infrastructure, given the
jars (10 for 2.2.) will only be downloaded when starting with a
clean m2 repo or when we publish any updated depends.
Unless someone comes up with a better solution by Friday morning,
I'll create the new repo branch and populate it with the latest
2.1.2 and 2.2 patched artifacts tomorrow.
-Donald
