At least in theory the next Gump runs (starting with the one from Jan
25 0:00 PST) will be using Maven 1.0.2, unless I've broken something.
At least in theory since we probably won't see any Gump runs until
we get the certificate is expired problem resolved. I think I only
need to do a manual
Hmm,
we seem to be using Maven 1.0.2 now,
http://brutus.apache.org/gump/kaffe/directory-naming/naming-factory/gump_work/build_directory-naming_naming-factory.html
Are those Jelly warnings something to worry about?
Stefan
-
To
On Tue, 25 Jan 2005, Brett Porter [EMAIL PROTECTED] wrote:
That doesn't look very healthy. The build failed too.
I thought that, too.
Maybe I should have done something more than just pointing MAVEN_HOME
to a different location (actually I twisted a symlink)? Something
like removing the Maven
Maybe I should have done something more than just pointing MAVEN_HOME
to a different location (actually I twisted a symlink)? Something
like removing the Maven cache and re-populate it with newer plugin
versions (I'd need to know how to do that, though).
Unless Adam did something funny when
Date: 2005-01-25T02:07:37
Editor: StefanBodewig
Wiki: Gump Wiki
Page: BrutusConfig
URL: http://wiki.apache.org/gump/BrutusConfig
no comment
Change Log:
--
@@ -66,7 +66,7 @@
!-- additional
On Tue, 25 Jan 2005, Brett Porter [EMAIL PROTECTED] wrote:
Maybe I should have done something more than just pointing
MAVEN_HOME to a different location (actually I twisted a symlink)?
Something like removing the Maven cache and re-populate it with
newer plugin versions (I'd need to know how
That's to populate the repository, but the new install has picked that
up just fine.
I think it's likely to be kaffe - let's hold for the JDK 1.5 run.
- Brett
On Tue, 25 Jan 2005 11:08:35 +0100, Stefan Bodewig [EMAIL PROTECTED] wrote:
On Tue, 25 Jan 2005, Brett Porter [EMAIL PROTECTED] wrote:
On Tue, 25 Jan 2005, Stefan Bodewig [EMAIL PROTECTED] wrote:
On Tue, 25 Jan 2005, Brett Porter [EMAIL PROTECTED] wrote:
Maybe I should have done something more than just pointing
MAVEN_HOME to a different location (actually I twisted a symlink)?
Something like removing the Maven cache and
the bit about offline? If this were a problem, it would exhibit as
dependencies not being found.
the bit about bootstrapping?
when jelly and directory (my foray into gump) are stable, sure.
plugins? It should be fine. ~/.maven/cache is just a cache, only the
plugin JARs that exist in
On Tue, 25 Jan 2005, Brett Porter [EMAIL PROTECTED] wrote:
the bit about offline?
Yes. Sorry if my statement was too cryptic.
You should be able to test it by setting your JDK to 1.4, going to
the jelly checkout, and running maven jar.
Works, even with --offline, using the build.properties
Stefan Bodewig wrote:
On Tue, 25 Jan 2005, Stefan Bodewig [EMAIL PROTECTED] wrote:
On Tue, 25 Jan 2005, David Crossley [EMAIL PROTECTED] wrote:
Not sure what caused the sudden fill-up, but it is not me.
It seems as if the kaffe and public Gump workspaces lived on /home -
maybe one of them is
11 matches
Mail list logo