[continuum] BUILD FAILURE: Cocoon - Apache Cocoon [build root] - Build Def:
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=106128&projectId=51 Build statistics: State: Failed Previous State: Failed Started at: Sat 2 Aug 2008 10:40:39 -0700 Finished at: Sat 2 Aug 2008 10:53:04 -0700 Total time: 12m 24s Build Trigger: Schedule Build Number: 310 Exit code: 1 Building machine hostname: vmbuild.apache.org Operating system : Linux(unknown) Java Home version : java version "1.4.2_15" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_15-b02) Java HotSpot(TM) Client VM (build 1.4.2_15-b02, mixed mode) Builder version : Maven version: 2.0.8 Java version: 1.4.2_15 OS name: "linux" version: "2.6.20-16-server" arch: "i386" Family: "unix" SCM Changes: Changed: felixk @ Sat 2 Aug 2008 09:57:07 -0700 Comment: Improve build performance, remove not needed and no longer existing repositories. Files changed: /cocoon/trunk/tools/sitemaptags2daisy/pom.xml ( 682014 ) Dependencies Changes: No dependencies changed Build Defintion: POM filename: pom.xml Goals: clean install Arguments: --batch-mode -P allblocks,it Build Fresh: false Always Build: false Default Build Definition: true Schedule: DEFAULT_SCHEDULE Profile Name: Java 1.4, Large Memory Description: Test Summary: Tests: 373 Failures: 0 Total time: 138.21498
Some questions about site document generation
Hi First I need to say that I'm not that familiar with the doc generation - just in case some questions are OT or just rubbish. - Nightly-docs vs. dev-docs: [1] has a note saying "There is a second job which builds the docs once a day too. In addition to the first one it adds a couple of reports (Findbugs, SVN reports, etc.). See http://cocoon.zones.apache.org/dev-docs/"; Is this really working? Comparing i.e. the summary of a page would say something else [2][3]. Are the dev-docs really run once a day? - Monitoring nightly-/dev-docs generation Does it exists? I've never seen such a mail on a list (dev/private/user) or hasn't it failed ever? - sitemaptags2daisy This scripts is used to update daisy with annotations made in java classes. As I've found multiple page not updated I also doubt that this script is run on a regularly base when generating nigthly-/dev-docs. Does the docs generation also run this script? Why is it a script and not a maven plugin (historical reasons/technical reasons/...)? - Site 'responsible' [4] still has a banner for ApacheCon Europe 08 (April 2008). Do we have people feeling responsible about keeping the site (at least [4], I'm not talking about technical documentation of C2.x)) up to date? Regards Felix [1] http://cocoon.apache.org/1418_1_1.html [2] http://cocoon.zones.apache.org/nightly-docs/2.2/core-modules/core/2.2/890_1_1.html [3] http://cocoon.zones.apache.org/dev-docs/2.2/core-modules/core/2.2/890_1_1.html [4] http://cocoon.apache.org/
[continuum] BUILD FAILURE: Cocoon - Apache Cocoon [build root] - Build Def:
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=105998&projectId=51 Build statistics: State: Failed Previous State: Error Started at: Sat 2 Aug 2008 03:30:01 -0700 Finished at: Sat 2 Aug 2008 03:39:51 -0700 Total time: 9m 50s Build Trigger: Schedule Build Number: 310 Exit code: 1 Building machine hostname: vmbuild.apache.org Operating system : Linux(unknown) Java Home version : java version "1.4.2_15" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_15-b02) Java HotSpot(TM) Client VM (build 1.4.2_15-b02, mixed mode) Builder version : Maven version: 2.0.8 Java version: 1.4.2_15 OS name: "linux" version: "2.6.20-16-server" arch: "i386" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Defintion: POM filename: pom.xml Goals: clean install Arguments: --batch-mode -P allblocks,it Build Fresh: false Always Build: false Default Build Definition: true Schedule: DEFAULT_SCHEDULE Profile Name: Java 1.4, Large Memory Description: Test Summary: Tests: 373 Failures: 0 Total time: 134.11697
Re: Cocoon-jms-sample requires Java >= 1.5
Peter Hunsberger pisze: But when switching the version why don't switch to 1.6 (I think it's on MacOSX now also available). Otherwise we have to switch again in 1 year or so (see http://java.sun.com/products/archive/eol.policy.html). EOL for 1.5 is October 2009. WDYT? There might be people who can't run 1.6 yet. In particular we know some people are still stuck on old versions of Websphere and similar. We've had this discussion before and I'm on the side that we can't support legacy code forever. However, I do feel that a jump to 1.6 might be a bit premature. We just had this discussion internally over the last couple of weeks and we found several 1.6 incompatibilities forcing us to stay on 1.5 for the moment. If we do have a need to move to 1.6 in the future it shouldn't be that much of an issue to change at that point? Technically, switching to new Java version is not that hard, things that you need to do are: 1. Change required Java version in our parent pom. 2. Change profile in Continuum so it uses Java 1.5 3. Upgrade Java used on cocoon.zones.apache.org. 4ยท Announce this fact to our users. In the past, it proven to be more social issue that some people were blocking decision about changing required Java version. At this moment, I don't see any kind of that effect (it looks like every one agrees on the need of change) so I don't think we need to exploit this situation for switching to Java 1.6 immediately. I agree with Peter's arguments that there should be no hurry. On the other hand, I agree with Felix that we'll need to switch to 1.6 in a year but provided there are no people blocking this decision and we have more frequent releases of Cocoon Core I prefer gradual steps. If there is anyone who wants to add something to this discussion I think it's a perfect time to speak out now. Otherwise, I would like to call a vote next week so we can make a formal decision. -- Grzegorz Kossakowski
[continuum] BUILD ERROR: Cocoon - Apache Cocoon [build root] - Build Def:
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=105773&projectId=51 Build statistics: State: Error Previous State: Failed Started at: Sat 2 Aug 2008 00:15:31 -0700 Finished at: Sat 2 Aug 2008 00:16:47 -0700 Total time: 1m 15s Build Trigger: Schedule Build Number: 0 Exit code: 0 Building machine hostname: vmbuild.apache.org Operating system : Linux(unknown) Java Home version : java version "1.4.2_15" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_15-b02) Java HotSpot(TM) Client VM (build 1.4.2_15-b02, mixed mode) Builder version : Maven version: 2.0.8 Java version: 1.4.2_15 OS name: "linux" version: "2.6.20-16-server" arch: "i386" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Defintion: POM filename: pom.xml Goals: clean install Arguments: --batch-mode -P allblocks,it Build Fresh: false Always Build: false Default Build Definition: true Schedule: DEFAULT_SCHEDULE Profile Name: Java 1.4, Large Memory Description: Test Summary: Tests: 0 Failures: 0 Total time: 0.0 Build Error: Provider message: The svn command failed. Command output: --- svn: PROPFIND request failed on '/repos/asf/cocoon/trunk' svn: PROPFIND of '/repos/asf/cocoon/trunk': could not connect to server (http://svn.apache.org) ---
