You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Stephen McConnell <mc...@apache.org> on 2004/08/22 17:29:10 UTC
more on gump
I have just replaced all of the avalon/trunk gump project descriptors so
that they now point to svn content as opposed to cvs.
I am expecting some errors related to project id to gump id names
mappings and will sort these out as they come up. All of the new gump
project definitions (138 in total) are using magic to build the
respective targets based on generated definitions - so if something goes
wrong we should be updating information in either magic's gump task or
more probably gump alias declarations in our local index files.
Steve.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: more on gump -- cocoon def
Posted by Stephen McConnell <mc...@apache.org>.
Could someone please update the cocoon-2.1/cocoon gump descriptor and
replace the following line:
<depend project="avalon-framework" ids="impl api" />
with:
<depend project="avalon-framework-api"/>
<depend project="avalon-framework-legacy"/>
<depend project="avalon-framework-impl"/>
Cheers, Steve.
> -----Original Message-----
> From: Stephen McConnell [mailto:mcconnell@apache.org]
> Sent: 22 August 2004 17:29
> To: Avalon Developers List
> Cc: general@gump.apache.org
> Subject: more on gump
>
>
> I have just replaced all of the avalon/trunk gump project descriptors
so
> that they now point to svn content as opposed to cvs.
>
> I am expecting some errors related to project id to gump id names
> mappings and will sort these out as they come up. All of the new gump
> project definitions (138 in total) are using magic to build the
> respective targets based on generated definitions - so if something
goes
> wrong we should be updating information in either magic's gump task or
> more probably gump alias declarations in our local index files.
>
> Steve.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
> For additional commands, e-mail: general-help@gump.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
RE: more on gump
Posted by Stephen McConnell <mc...@apache.org>.
Ummm - I'm a little lost -
... all Avalon projects are failing with the assertion that build.xml
does not exist. That's a little odd because it exists in svn and the
ant basedirs are all correct. Can anyone check if there were any
problems with gump's svn checkout of the Avalon-svn repository content?
Steve.
> -----Original Message-----
> From: Stephen McConnell [mailto:mcconnell@apache.org]
> Sent: 22 August 2004 17:29
> To: Avalon Developers List
> Cc: general@gump.apache.org
> Subject: more on gump
>
>
> I have just replaced all of the avalon/trunk gump project descriptors
so
> that they now point to svn content as opposed to cvs.
>
> I am expecting some errors related to project id to gump id names
> mappings and will sort these out as they come up. All of the new gump
> project definitions (138 in total) are using magic to build the
> respective targets based on generated definitions - so if something
goes
> wrong we should be updating information in either magic's gump task or
> more probably gump alias declarations in our local index files.
>
> Steve.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
> For additional commands, e-mail: general-help@gump.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
RE: more on gump
Posted by Stephen McConnell <mc...@apache.org>.
> -----Original Message-----
> From: Stephen McConnell [mailto:mcconnell@apache.org]
> Sent: 26 August 2004 07:10
> To: 'Avalon Developers List'
> Cc: general@gump.apache.org
> Subject: RE: more on gump
>
>
>
> > -----Original Message-----
> > From: Stephen McConnell [mailto:mcconnell@apache.org]
> > Sent: 24 August 2004 05:08
> > To: 'Avalon Developers List'
> > Cc: general@gump.apache.org
> > Subject: RE: more on gump
> >
> >
> > Current status of the Avalon Gump builds:
> >
> > Successful builds: 98
> > Build failures: 9
> > Prerequisite failures: 30
>
>
> Thinks are getting closer to total success:
>
> Successful builds: 116
> Build failures: 3
> Prerequisite failures: 18
>
> Of the three failures, one is related to the site generation which for
> the moment I simply have not figured out. The second is an issue
> related to the version of JMX (using MX4J libs) - Gump is linked to
> version 2 and Avalon JMX facilities are linked to 1.1 (Cameron is
> digging into this as we speak - i.e. expect synchronization shortly).
Cameron has just committed updates to jmx that should in principal
resolve the current jmx/mx4j builds (and resolve at least 2 of out our
18 prerequisite failures). We should have confirmation from Gump in
around two or three hours.
Cheers, Stephen.
> The third item is the http implementation which requires the addition
of
> the org.mortbay.jaas.jar file by the Gump team (Gump guys .. we need
> your help on this one).
>
> Cheers, Steve.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail: dev-help@avalon.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: more on gump
Posted by Stephen McConnell <mc...@apache.org>.
> -----Original Message-----
> From: Stephen McConnell [mailto:mcconnell@apache.org]
> Sent: 26 August 2004 07:10
> To: 'Avalon Developers List'
> Cc: general@gump.apache.org
> Subject: RE: more on gump
>
>
>
> > -----Original Message-----
> > From: Stephen McConnell [mailto:mcconnell@apache.org]
> > Sent: 24 August 2004 05:08
> > To: 'Avalon Developers List'
> > Cc: general@gump.apache.org
> > Subject: RE: more on gump
> >
> >
> > Current status of the Avalon Gump builds:
> >
> > Successful builds: 98
> > Build failures: 9
> > Prerequisite failures: 30
>
>
> Thinks are getting closer to total success:
>
> Successful builds: 116
> Build failures: 3
> Prerequisite failures: 18
>
> Of the three failures, one is related to the site generation which for
> the moment I simply have not figured out. The second is an issue
> related to the version of JMX (using MX4J libs) - Gump is linked to
> version 2 and Avalon JMX facilities are linked to 1.1 (Cameron is
> digging into this as we speak - i.e. expect synchronization shortly).
Cameron has just committed updates to jmx that should in principal
resolve the current jmx/mx4j builds (and resolve at least 2 of out our
18 prerequisite failures). We should have confirmation from Gump in
around two or three hours.
Cheers, Stephen.
> The third item is the http implementation which requires the addition
of
> the org.mortbay.jaas.jar file by the Gump team (Gump guys .. we need
> your help on this one).
>
> Cheers, Steve.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail: dev-help@avalon.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
RE: more on gump
Posted by Stephen McConnell <mc...@apache.org>.
> -----Original Message-----
> From: Stephen McConnell [mailto:mcconnell@apache.org]
> Sent: 24 August 2004 05:08
> To: 'Avalon Developers List'
> Cc: general@gump.apache.org
> Subject: RE: more on gump
>
>
> Current status of the Avalon Gump builds:
>
> Successful builds: 98
> Build failures: 9
> Prerequisite failures: 30
Thinks are getting closer to total success:
Successful builds: 116
Build failures: 3
Prerequisite failures: 18
Of the three failures, one is related to the site generation which for
the moment I simply have not figured out. The second is an issue
related to the version of JMX (using MX4J libs) - Gump is linked to
version 2 and Avalon JMX facilities are linked to 1.1 (Cameron is
digging into this as we speak - i.e. expect synchronization shortly).
The third item is the http implementation which requires the addition of
the org.mortbay.jaas.jar file by the Gump team (Gump guys .. we need
your help on this one).
Cheers, Steve.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
RE: more on gump
Posted by Stephen McConnell <mc...@apache.org>.
Thanks to some help from Adam we we're getting real close now:
Successful builds: 128
Build failures: 1
Prerequisite failures: 8
The single build failure is related to the avalon-http-examples project
due to a FileNotFoundException:
avalon/http/blocks/avalon-http-servlet-26082004.block. Looking at the
avalon-http-servlet build I can see that the servlet block has been
created and installed - so I'm a little confused (again) but I'll dig
around and see what comes up.
Stephen.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
RE: more on gump
Posted by Stephen McConnell <mc...@apache.org>.
Thanks to some help from Adam we we're getting real close now:
Successful builds: 128
Build failures: 1
Prerequisite failures: 8
The single build failure is related to the avalon-http-examples project
due to a FileNotFoundException:
avalon/http/blocks/avalon-http-servlet-26082004.block. Looking at the
avalon-http-servlet build I can see that the servlet block has been
created and installed - so I'm a little confused (again) but I'll dig
around and see what comes up.
Stephen.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: more on gump
Posted by Stephen McConnell <mc...@apache.org>.
> -----Original Message-----
> From: Adam R. B. Jack [mailto:ajack@apache.org]
> Sent: 24 August 2004 20:14
> To: Avalon Developers List
> Subject: RE: more on gump
>
> > Failures are merlin-cli, jmx-mx4j, and http-impl. The cli failure
> > appears to be related to the build referencing its own published
> > artifact before it is published (probably some tweaking of the build
> > file named).
>
> Do you need to use <work here?
>
> http://gump.apache.org/metadata/project.html#work
>
> BTW: Sometimes Ant (or maybe builds) drop paths from their classpath,
if
> they do not exist at start-up (even if they are populated before being
> used). For that we've used this in the past:
>
> http://gump.apache.org/metadata/project.html#mkdir
>
Actually the problem was related to magic. Basically the build file
contains a filter declaration
<x:filter feature="classpath" platform="windows"
prefix="%MERLIN_HOME%/system"
token="WINDOWS-CLI-CLASSPATH"/>
The above statement results in the creation of a MagicPath object
holding the full transitive dependencies for the project in question.
The default behavior of the path object is to resolve all entries in the
path against the repository. In this case the path entry included the
merlin-cli jar file which does not exist yet. I've just updated Magic
such that filter based acquisition of path objects defaults to
non-resolution of the jar files relative to the repository (because in
effect we only want the path as a string).
Changes should propagate though Gump before morning.
Cheers, Steve.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: more on gump
Posted by "Adam R. B. Jack" <aj...@apache.org>.
> Failures are merlin-cli, jmx-mx4j, and http-impl. The cli failure
> appears to be related to the build referencing its own published
> artifact before it is published (probably some tweaking of the build
> file named).
Do you need to use <work here?
http://gump.apache.org/metadata/project.html#work
BTW: Sometimes Ant (or maybe builds) drop paths from their classpath, if they do not exist at start-up (even if they are populated before being used). For that we've used this in the past:
http://gump.apache.org/metadata/project.html#mkdir
regards
Adam
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: more on gump
Posted by Stephen McConnell <mc...@apache.org>.
> Current status of the Avalon Gump builds:
>
> Successful builds: 98
> Build failures: 9
> Prerequisite failures: 30
Current status:
Successful builds: 114
Build failures: 3
Prerequisite failures: 20
Failures are merlin-cli, jmx-mx4j, and http-impl. The cli failure
appears to be related to the build referencing its own published
artifact before it is published (probably some tweaking of the build
file named). The jmx mx4j failure is a little strange because if
failing with:
[x:javac] /MX4JComponentRegistrationManager.java:43:
package mx4j.adaptor.rmi.jrmp does not exist
[x:javac] import mx4j.adaptor.rmi.jrmp.JRMPAdaptorMBean;
[x:javac] ^
Steve.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: more on gump
Posted by Stephen McConnell <mc...@apache.org>.
> -----Original Message-----
> From: Stephen McConnell [mailto:mcconnell@apache.org]
> Sent: 24 August 2004 05:08
> To: 'Avalon Developers List'
> Cc: general@gump.apache.org
> Subject: RE: more on gump
>
>
> Current status of the Avalon Gump builds:
>
> Successful builds: 98
> Build failures: 9
> Prerequisite failures: 30
Thinks are getting closer to total success:
Successful builds: 116
Build failures: 3
Prerequisite failures: 18
Of the three failures, one is related to the site generation which for
the moment I simply have not figured out. The second is an issue
related to the version of JMX (using MX4J libs) - Gump is linked to
version 2 and Avalon JMX facilities are linked to 1.1 (Cameron is
digging into this as we speak - i.e. expect synchronization shortly).
The third item is the http implementation which requires the addition of
the org.mortbay.jaas.jar file by the Gump team (Gump guys .. we need
your help on this one).
Cheers, Steve.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: more on gump
Posted by Stephen McConnell <mc...@apache.org>.
Current status of the Avalon Gump builds:
Successful builds: 98
Build failures: 9
Prerequisite failures: 30
The build failures are related to two items:
1. getting the jetty jaas libraries into gump
2. a bug in the meta-info generator task (patches by Tim a few
minutes ago)
The prerequisite failures are linked to:
1. internal failures described above.
2. Excalibur build failures.
Should have a clean picture on all of this in a two or three hours.
Steve.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: more on gump
Posted by Stephen McConnell <mc...@apache.org>.
Current status of the Avalon Gump builds:
Successful builds: 98
Build failures: 9
Prerequisite failures: 30
The build failures are related to two items:
1. getting the jetty jaas libraries into gump
2. a bug in the meta-info generator task (patches by Tim a few
minutes ago)
The prerequisite failures are linked to:
1. internal failures described above.
2. Excalibur build failures.
Should have a clean picture on all of this in a two or three hours.
Steve.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
[patch] runtime/index.xml
Posted by Stephen McConnell <mc...@apache.org>.
The following patch corrects the log4j gump alias under the log4j
resource declaration, and secondly, updates the avalon-repository-test
project to declare a null type (required so that the gump task does not
generate an output declaration).
Steve.
Index: index.xml
===================================================================
--- index.xml (revision 36764)
+++ index.xml (working copy)
@@ -33,8 +33,7 @@
<type>jar</type>
</info>
<gump>
- <alias>logging-log4j</alias>
- <id>log4j</id>
+ <alias>logging-log4j-12</alias>
</gump>
</resource>
@@ -497,6 +496,7 @@
<info>
<group>avalon/repository</group>
<name>avalon-repository-test</name>
+ <type>null</type>
</info>
<dependencies>
<include key="avalon-repository-impl" test="false"/>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
[patch] planet/facilities/index.xml
Posted by Stephen McConnell <mc...@dpml.net>.
All facility builds are currently failing due to the presence of the
console/system project declared in the index but non-existant in the svn
repository. The following diff to /planet/facilities/index.xml fixes
that problem.
Index: index.xml
===================================================================
--- index.xml (revision 36699)
+++ index.xml (working copy)
@@ -597,6 +597,7 @@
</plugins>
</project>
+ <!--
<project basedir="console/system">
<info>
<group>avalon/console</group>
@@ -614,6 +615,7 @@
<include key="avalon-meta-tools"/>
</plugins>
</project>
+ -->
<project basedir="console/commands">
<info>
Steve.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: more on gump
Posted by Stephen McConnell <mc...@dpml.net>.
> > Gump is currently running though the Avalon builds mixed results.
> > Basically all of the simple builds are working fine but there are a
> > couple of problems that have emerged:
> >
> > 1. some problems related to inconsistencies between the facilities
> > index and content
Fixed.
> >
> > 2. plugin dependencies are not being considered when generating
the
> > gump descriptors (causing several component builds to fail due
to
> > non-availability of the meta plugin)
Fixed.
> 3. log4j is proving problematic because it produces two separate
> jar files, one containing core log4j and the second containing
the
> lf5 classes - whereas the log4j 1.2.8 distribution is a single
jar.
>
> Synchronizing this with magic's gump descriptor generation is a
> problematic in that magic dependency references to external
> resources are 1-1 and there are no published artifacts against
> which we can link on a 1-1 basis
Maybe fixed.
Steve.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: more on gump
Posted by Stephen McConnell <mc...@dpml.net>.
> -----Original Message-----
> From: Stephen McConnell [mailto:mcconnell@apache.org]
> Sent: 22 August 2004 23:09
> To: 'Avalon Developers List'
> Subject: RE: more on gump
>
>
> Gump is currently running though the Avalon builds mixed results.
> Basically all of the simple builds are working fine but there are a
> couple of problems that have emerged:
>
> 1. some problems related to inconsistencies between the facilities
> index and content
>
> 2. plugin dependencies are not being considered when generating the
> gump descriptors (causing several component builds to fail due to
> non-availability of the meta plugin)
3. log4j is proving problematic because it produces two separate
jar files, one containing core log4j and the second containing the
lf5 classes - whereas the log4j 1.2.8 distribution is a single jar.
Synchronizing this with magic's gump descriptor generation is a
problematic in that magic dependency references to external
resources are 1-1 and there are no published artifacts against
which we can link on a 1-1 basis
Steve.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: more on gump
Posted by Stephen McConnell <mc...@apache.org>.
Gump is currently running though the Avalon builds mixed results.
Basically all of the simple builds are working fine but there are a
couple of problems that have emerged:
1. some problems related to inconsistencies between the facilities
index and content
2. plugin dependencies are not being considered when generating the
gump descriptors (causing several component builds to fail due to
non-availability of the meta plugin)
Aside from the above - things seem to be proceeding nicely. Taking care
of the above two items should not be a problem following which we have
the builds of cornerstone which are themselves dependent on the build of
the Excalibur projects. I'm not too sure just at the moment what the
best approach for the Excalibur content - but I'd like to sort something
out so we can move ahead and get James building again (I've got a magic
based build of james up and running - and passing runtime tests) from
which we can validate the updates to cornerstone.
Cheers, Steve.
> -----Original Message-----
> From: Stephen McConnell [mailto:mcconnell@apache.org]
> Sent: 22 August 2004 17:29
> To: Avalon Developers List
> Cc: general@gump.apache.org
> Subject: more on gump
>
>
> I have just replaced all of the avalon/trunk gump project descriptors
so
> that they now point to svn content as opposed to cvs.
>
> I am expecting some errors related to project id to gump id names
> mappings and will sort these out as they come up. All of the new gump
> project definitions (138 in total) are using magic to build the
> respective targets based on generated definitions - so if something
goes
> wrong we should be updating information in either magic's gump task or
> more probably gump alias declarations in our local index files.
>
> Steve.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail: dev-help@avalon.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org