Some of you may have noticed 1.1 build errors last week which were
caused by the relocation of the Apache maven repo from
'cvs.apache.org/repository' to 'people.apache.org/repository'. It's
my understanding from asfinfra that the maven repo will be moved to
yet another location... And also
On Wed, May 24, 2006 at 04:05:40AM -0400, Kevan Miller wrote:
Some of you may have noticed 1.1 build errors last week which were
caused by the relocation of the Apache maven repo from
'cvs.apache.org/repository' to 'people.apache.org/repository'.
I've noticed some strange behavior that
+1 to having a way to download all the dependencies you need with or
in addition to the source. I'm fine if it's effectively a ~/.maven
repository, which we should be able to generate by doing a clean build
on a regular (weekly?) basis. It could also be something checked into
Subversion, but
I added a program I was noodling on into sandbox. Its in
sandbox/releasetools/trunk/src/java/org/apache/geroinimo/releasetools/VersionVerifier.java
Its not complete and very rough but it effectively grinds through the entire G tree and extracts all
dependencies G has on external projects. I
Can we stick the repo in our zone?
-dain
On May 24, 2006, at 7:12 AM, Aaron Mulder wrote:
+1 to having a way to download all the dependencies you need with or
in addition to the source. I'm fine if it's effectively a ~/.maven
repository, which we should be able to generate by doing a clean
On May 24, 2006, at 10:12 AM, Aaron Mulder wrote:
+1 to having a way to download all the dependencies you need with or
in addition to the source. I'm fine if it's effectively a ~/.maven
repository, which we should be able to generate by doing a clean build
on a regular (weekly?) basis. It
Inline
Kevan Miller wrote:
On May 24, 2006, at 10:12 AM, Aaron Mulder wrote:
+1 to having a way to download all the dependencies you need with or
in addition to the source. I'm fine if it's effectively a ~/.maven
repository, which we should be able to generate by doing a clean build
on a
I think it would be in our best interest for the long term using
Maven to host our own repository, which is backed up by svn.
By default the projects will point to the http:// base of our
repository (say http://svn.apache.org/repos/asf/geronimo/repository/
m2 or
It sounds like there are really two issues IIUC. The first is that normal development is impeded
because the sites mirroring Maven content are dynamic and because of circumstances beyond anyone's
control give sporadic results. The second is the ability for a user to rebuild Geronimo n.n after
Does that 428MB include the Geronimo distributioons themselves? I
suspect so -- I use a 60MB .tar.bz2 (repository+source tree) for
Geronimo 1.0 build tests (though I think that builds OpenEJB too so
the size would vary if we use OpenEJB binaries).
Thanks,
Aaron
On 5/24/06, Matt Hogstrom
Your right Aaron...my recollection was that this was a clean repo. After looking at the zip there
was some CTS, other Geronimo artifacts, etc. Here is the current size after doing an rm -rf on
three dirs that are not relevant.
-rw-r--r-- 1 hogstrom users 52499153 May 24 12:50
11 matches
Mail list logo
