[EMAIL PROTECTED]: Project chaperon (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project chaperon has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - chaperon : Chaperon is a project that helps to convert structured text ... Full details are available at: http://vmgump.apache.org/gump/public/cocoon/chaperon/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [chaperon-20040205.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/chaperon-20040205.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/chaperon/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/chaperon/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #3. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project chaperon (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project chaperon has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - chaperon : Chaperon is a project that helps to convert structured text ... Full details are available at: http://vmgump.apache.org/gump/public/cocoon/chaperon/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [chaperon-20040205.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/chaperon-20040205.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/chaperon/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/chaperon/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #3. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project knopflerfish-log (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project knopflerfish-log has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - knopflerfish-log : Knopflerfish Log Full details are available at: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-log/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [knopflerfish-log_all-1.0.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/core/knopflerfish-log_all-1.0.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/core -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-log/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-log/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #4. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project knopflerfish-log (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project knopflerfish-log has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - knopflerfish-log : Knopflerfish Log Full details are available at: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-log/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [knopflerfish-log_all-1.0.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/core/knopflerfish-log_all-1.0.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/core -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-log/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-log/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #4. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project xreporter-expression (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xreporter-expression has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - xreporter-expression : An expression language interpreter. Full details are available at: http://vmgump.apache.org/gump/public/cocoon/xreporter-expression/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [xreporter-expression-20040701.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/xreporter-expression-20040701.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/xreporter-expression/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/xreporter-expression/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #5. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project xreporter-expression (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xreporter-expression has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - xreporter-expression : An expression language interpreter. Full details are available at: http://vmgump.apache.org/gump/public/cocoon/xreporter-expression/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [xreporter-expression-20040701.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/xreporter-expression-20040701.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/xreporter-expression/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/xreporter-expression/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #5. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project daisy-util (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project daisy-util has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - daisy-util : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/daisy-util/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [daisy-util-1.4.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/daisy-util-1.4.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/daisy-util/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/daisy-util/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #6. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project daisy-util (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project daisy-util has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - daisy-util : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/daisy-util/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [daisy-util-1.4.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/daisy-util-1.4.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/daisy-util/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/daisy-util/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #6. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jdtcore (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project jdtcore has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jdtcore : Java Development Tools from the Eclipse IDE Project Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jdtcore/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jdtcore-3.1.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jdtcore-3.1.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jdtcore/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jdtcore/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #7. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jdtcore (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project jdtcore has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jdtcore : Java Development Tools from the Eclipse IDE Project Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jdtcore/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jdtcore-3.1.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jdtcore-3.1.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jdtcore/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jdtcore/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #7. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project deli (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project deli has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - deli : Delivery context library Full details are available at: http://vmgump.apache.org/gump/public/cocoon/deli/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [deli-x050330.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/deli-x050330.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/deli/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/deli/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #8. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project deli (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project deli has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - deli : Delivery context library Full details are available at: http://vmgump.apache.org/gump/public/cocoon/deli/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [deli-x050330.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/deli-x050330.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/deli/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/deli/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #8. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project cowarp (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cowarp has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - cowarp : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/cowarp/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [cowarp-0.5-dev-20051002.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/cowarp-0.5-dev-20051002.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/cowarp/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/cowarp/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #9. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project cowarp (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cowarp has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - cowarp : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/cowarp/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [cowarp-0.5-dev-20051002.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/cowarp-0.5-dev-20051002.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/cowarp/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/cowarp/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #9. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project itext (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project itext has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - itext : iText is a library that allows you to generate PDF files on ... Full details are available at: http://vmgump.apache.org/gump/public/cocoon/itext/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [itext-1.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/itext-1.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/itext/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/itext/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #10. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project itext (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project itext has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - itext : iText is a library that allows you to generate PDF files on ... Full details are available at: http://vmgump.apache.org/gump/public/cocoon/itext/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [itext-1.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/itext-1.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/itext/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/itext/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #10. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jackrabbit (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project jackrabbit has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jackrabbit : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jackrabbit/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jackrabbit-1.0-dev-r292737.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jackrabbit-1.0-dev-r292737.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jackrabbit/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jackrabbit/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #11. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jackrabbit (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project jackrabbit has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jackrabbit : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jackrabbit/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jackrabbit-1.0-dev-r292737.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jackrabbit-1.0-dev-r292737.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jackrabbit/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jackrabbit/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #11. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jcr (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project jcr has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jcr : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jcr/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jcr-1.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jcr-1.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jcr/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jcr/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #12. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jcr (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project jcr has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jcr : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jcr/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jcr-1.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jcr-1.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jcr/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jcr/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #12. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project garbage (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project garbage has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - garbage : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/garbage/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [apache-garbage-0.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/apache-garbage-0.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/garbage/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/garbage/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #13. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project garbage (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project garbage has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - garbage : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/garbage/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [apache-garbage-0.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/apache-garbage-0.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/garbage/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/garbage/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #13. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project joost (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project joost has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - joost : Streaming Transformation for XML (STX) library Full details are available at: http://vmgump.apache.org/gump/public/cocoon/joost/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [joost-20040330.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/joost-20040330.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/joost/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/joost/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #14. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project joost (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project joost has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - joost : Streaming Transformation for XML (STX) library Full details are available at: http://vmgump.apache.org/gump/public/cocoon/joost/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [joost-20040330.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/joost-20040330.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/joost/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/joost/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #14. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jing (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project jing has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jing : Jing performs XML Validation using RelaxNG schemas Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jing/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jing-20030619.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jing-20030619.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jing/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jing/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #15. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jing (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project jing has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jing : Jing performs XML Validation using RelaxNG schemas Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jing/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jing-20030619.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jing-20030619.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jing/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jing/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #15. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
Dojo too fat?
Hi, Please see the report below. Comments? Best Regards, Antonio Gallardo. Document Size - http://cocoon.zones.apache.org/demos/21branch/samples/blocks/forms/form1 Documents (1 file) 18 kb http://cocoon.zones.apache.org/demos/21branch/samples/blocks/forms/form1 18 kb Images (6 files)4 kb http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/forms/img/cal.gif 950 bytes http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/forms/img/help.gif 868 bytes http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/forms/img/delete.gif 842 bytes http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/forms/img/move_down.gif 842 bytes http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/forms/img/move_up.gif 842 bytes http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/forms/img/close.gif 51 bytes Style Sheets (4 files) 11 kb http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/forms/htmlarea/htmlarea.css 4 kb http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/forms/css/forms-calendar.css 2 kb http://cocoon.zones.apache.org/demos/21branch/styles/main.css 2 kb http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/forms/css/forms.css 2 kb Scripts (13 files) 317 kb http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/dojo/dojo.js 145 kb http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/forms/htmlarea/htmlarea.js 67 kb http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/forms/mattkruse-lib/CalendarPopup.js 34 kb http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/forms/mattkruse-lib/date.js 12 kb http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/forms/mattkruse-lib/selectbox.js 11 kb http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/forms/js/forms-lib.js 11 kb http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/forms/mattkruse-lib/PopupWindow.js 11 kb http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/forms/mattkruse-lib/OptionTransfer.js 8 kb http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/forms/mattkruse-lib/AnchorPosition.js 5 kb http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/forms/htmlarea/popupwin.js 4 kb http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/forms/htmlarea/lang/en.js 3 kb http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/ajax/cocoon.js 3 kb http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/forms/htmlarea/dialog.js 2 kb Total 350 kb
[EMAIL PROTECTED]: Project knopflerfish-framework (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project knopflerfish-framework has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - knopflerfish-framework : Knopflerfish Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-framework/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [knopflerfish-framework-1.3.3.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/core/knopflerfish-framework-1.3.3.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/core -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-framework/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-framework/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #18. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project knopflerfish-framework (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project knopflerfish-framework has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - knopflerfish-framework : Knopflerfish Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-framework/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [knopflerfish-framework-1.3.3.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/core/knopflerfish-framework-1.3.3.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/core -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-framework/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-framework/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #18. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project nekodtd (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project nekodtd has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - nekodtd : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/nekodtd/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [nekodtd-0.1.11.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/nekodtd-0.1.11.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/nekodtd/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/nekodtd/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #19. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project nekodtd (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project nekodtd has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - nekodtd : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/nekodtd/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [nekodtd-0.1.11.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/nekodtd-0.1.11.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/nekodtd/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/nekodtd/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #19. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jdbi (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project jdbi has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jdbi : Provides convenient access to relational databases using Lis... Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jdbi/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jdbi-1.3.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jdbi-1.3.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jdbi/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jdbi/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #20. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jdbi (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project jdbi has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jdbi : Provides convenient access to relational databases using Lis... Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jdbi/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jdbi-1.3.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jdbi-1.3.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jdbi/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jdbi/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #20. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jackrabbit-commons (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project jackrabbit-commons has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jackrabbit-commons : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jackrabbit-commons/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jackrabbit-commons-1.0-dev-r292737.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jackrabbit-commons-1.0-dev-r292737.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jackrabbit-commons/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jackrabbit-commons/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #21. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jackrabbit-commons (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project jackrabbit-commons has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jackrabbit-commons : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jackrabbit-commons/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jackrabbit-commons-1.0-dev-r292737.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jackrabbit-commons-1.0-dev-r292737.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jackrabbit-commons/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jackrabbit-commons/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #21. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project daisy-htmlcleaner (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project daisy-htmlcleaner has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - daisy-htmlcleaner : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/daisy-htmlcleaner/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [daisy-htmlcleaner-1.4.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/daisy-htmlcleaner-1.4.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/daisy-htmlcleaner/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/daisy-htmlcleaner/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #25. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project daisy-htmlcleaner (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project daisy-htmlcleaner has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - daisy-htmlcleaner : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/daisy-htmlcleaner/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [daisy-htmlcleaner-1.4.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/daisy-htmlcleaner-1.4.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/daisy-htmlcleaner/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/daisy-htmlcleaner/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2504042006, vmgump.apache.org:vmgump-public:2504042006 Gump E-mail Identifier (unique within run) #25. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
Re: Dojo too fat?
Antonio Gallardo said the following on 04-04-2006 09:45: Hi, Please see the report below. Comments? http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/dojo/dojo.js 145 kb I've checked, this must be a slimmed version since the full version (aka kitchen sink) is 225 kb. I understand the worries, but I don't see an alternative. Other toolkits/frameworks were already rejected and growing our own is not a good idea. Bye, Helma
Re: Dojo too fat?
hepabolu wrote:
Antonio Gallardo said the following on 04-04-2006 09:45:
Hi,
Please see the report below. Comments?
http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/dojo/dojo.js
145 kb
I've checked, this must be a slimmed version since the full version (aka
kitchen sink) is 225 kb.
I understand the worries, but I don't see an alternative. Other
toolkits/frameworks were already rejected and growing our own is not a
good idea.
Bye, Helma
If configured correctly, resources only need to be loaded to the client once and
then the cached one is taken.
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
___
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Re: Dojo too fat?
Antonio Gallardo wrote: Please see the report below. Comments? snip/ http://cocoon.zones.apache.org/demos/21branch/_cocoon/resources/dojo/dojo.js 145 kb Dojo is a highly modular toolkit, which can load new JS scripts on demand (using Ajax requests). However, loading individually each and every module leads to an important overhead in page load time. To solve this, Dojo provides a compressor [1] that assembles a set of modules (JS files) in an single dojo.js file and compresses it (removes whitespace and comments, shortens identifiers). Browsers will then cache this dojo.js file, so that only the first use is costly. The work of the compressor is driven by a profile where you describe what modules you want to integrate in that single file. For Cocoon, I used the widget profile which includes the base infrastructure and a number of widgets (see blocks/ajax/dojo/build.xml). The actual profile to be used in a production system should normally be adapted to the actual modules your application uses to achieve maximum performance. We cannot guess within Cocoon what this module set will be, but what we can do is define a profile containing only the Dojo features that are effectively used by what we provide (i.e. the widgets in the forms and ajax blocks). That may allow to have a smaller default dojo.js, while still leaving room for people to build their own version of dojo.jar with their own profile. BTW, Dojo's is very successful, and some CDNs are providing it [2], thus allowing applications to load the full dojo.js from a central location. One single cached JS files served by distributed servers for many unrelated web sites! [1] http://dojotoolkit.org/docs/compressor_system.html [2] http://blog.dojotoolkit.org/2006/01/30/dojo-iamalpha-and-cdns -- Sylvain Wallez http://bluxte.net Apache Software Foundation Member
Re: A new CLI (was Re: [RT] The environment abstraction, part II)
El lun, 03-04-2006 a las 12:34 +0100, Upayavira escribió: Thorsten Scherler wrote: El lun, 03-04-2006 a las 09:00 +0100, Upayavira escribió: David Crossley wrote: Upayavira wrote: Sylvain Wallez wrote: Carsten Ziegeler wrote: Sylvain Wallez wrote: Hmm... the current CLI uses Cocoon's links view to crawl the website. So although the new crawler can be based on servlets, it will assume these servlets to answer to a ?cocoon-view=links :-) Hmm, I think we don't need the links view in this case anymore. A simple HTML crawler should be enough as it will follow all links on the page. The view would only make sense in the case where you don't output html where the usual crawler tools would not work. In the case of Forrest, you're probably right. Now the links view also allows to follow links in pipelines producing something that's not HTML, such as PDF, SVG, WML, etc. We have to decide if we want to loose this feature. I am not sure if we use this in Forrest. If not then we probably should be. In my view, the whole idea of crawling (i.e. gathering links from pages) is suboptimal anyway. For example, some sites don't directly link to all pages (e.g. they are accessed via javascript, or whatever) so you get pages missed. Were I to code a new CLI, whilst I would support crawling I would mainly configure the CLI to get the list of pages to visit by calling one or more URLs. Those URLs would specify the pages to generate. Thus, Forrest would transform its site.xml file into this list of pages, and drive the CLI via that. This is what we do do. We have a property start-uri=linkmap.html http://forrest.zones.apache.org/ft/build/cocoon-docs/linkmap.html (we actually use corresponding xml of course). We define a few extra URIs in the Cocoon cli.xconf There are issues of course. Sometimes we want to include directories of files that are not referenced in site.xml navigation. For my sites i just use a DirectoryGenerator to build an index page which feeds the crawler. Sometime that technique is not sufficent. We also gather links from text files (e.g. CSS) using Chaperon. This works nicely but introduces some overhead. This more or less confirms my suggested approach - allow crawling at the 'end-point' HTML, but more importantly, use a page/URL to identify the pages to be crawled. The interesting thing from what you say is that this page could itself be nothing more than HTML. Well, yes and not really, since e.g. Chaperon is text based and no markup. You need a lex-writer to generate links for the crawler. Yes. You misunderstand me I think. Yes, sorry I did misunderstood you. Even if you use Chaperon etc to parse markup, there'd be no difficulty expressing the links that you found as an HTML page - one intended to be consumed by the CLI, not to be publically viewed. Well in the case of css you want them as well publically viewed but I got your point. ;) In fact, if it were written to disc, forrest would probably delete it afterwards. Forrest actually is *not* aimed for html only support and one can think of the situation that you want your site to be only txt (kind of a book). Here you need to crawler the lex-rewriter outcome and follow the links. Hopefully I've shown that I had understood that already :-) yeah ;) The current limitation of forrest regarding the crawler are IMO not caused by the crawler design but rather by our (as in forrest) usage of it. Yep, fair enough. But if the CLI is going to survive the shift that is happening in Cocoon trunk, something big needs to be done by someone. It cannot survive in its current form as the code it uses is changing almost beyond recognition. Heh, perhaps the Cocoon CLI should just be a Maven plugin. ...or forrest plugin. ;) This would makes it possible that cocoon, lenya and forrest committer can help. Kind of http://svn.apache.org/viewcvs.cgi/lenya/sandbox/doco/ ;) salu2 -- thorsten Together we stand, divided we fall! Hey you (Pink Floyd)
Re: Dojo too fat?
Reinhard Poetz wrote: If configured correctly, resources only need to be loaded to the client once and then the cached one is taken. I think we should provide this correct configuration so users can just make use of it. Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: A new CLI (was Re: [RT] The environment abstraction, part II)
Thorsten Scherler wrote: El lun, 03-04-2006 a las 12:34 +0100, Upayavira escribió: Thorsten Scherler wrote: El lun, 03-04-2006 a las 09:00 +0100, Upayavira escribió: David Crossley wrote: Upayavira wrote: Sylvain Wallez wrote: Carsten Ziegeler wrote: Sylvain Wallez wrote: Hmm... the current CLI uses Cocoon's links view to crawl the website. So although the new crawler can be based on servlets, it will assume these servlets to answer to a ?cocoon-view=links :-) Hmm, I think we don't need the links view in this case anymore. A simple HTML crawler should be enough as it will follow all links on the page. The view would only make sense in the case where you don't output html where the usual crawler tools would not work. In the case of Forrest, you're probably right. Now the links view also allows to follow links in pipelines producing something that's not HTML, such as PDF, SVG, WML, etc. We have to decide if we want to loose this feature. I am not sure if we use this in Forrest. If not then we probably should be. In my view, the whole idea of crawling (i.e. gathering links from pages) is suboptimal anyway. For example, some sites don't directly link to all pages (e.g. they are accessed via javascript, or whatever) so you get pages missed. Were I to code a new CLI, whilst I would support crawling I would mainly configure the CLI to get the list of pages to visit by calling one or more URLs. Those URLs would specify the pages to generate. Thus, Forrest would transform its site.xml file into this list of pages, and drive the CLI via that. This is what we do do. We have a property start-uri=linkmap.html http://forrest.zones.apache.org/ft/build/cocoon-docs/linkmap.html (we actually use corresponding xml of course). We define a few extra URIs in the Cocoon cli.xconf There are issues of course. Sometimes we want to include directories of files that are not referenced in site.xml navigation. For my sites i just use a DirectoryGenerator to build an index page which feeds the crawler. Sometime that technique is not sufficent. We also gather links from text files (e.g. CSS) using Chaperon. This works nicely but introduces some overhead. This more or less confirms my suggested approach - allow crawling at the 'end-point' HTML, but more importantly, use a page/URL to identify the pages to be crawled. The interesting thing from what you say is that this page could itself be nothing more than HTML. Well, yes and not really, since e.g. Chaperon is text based and no markup. You need a lex-writer to generate links for the crawler. Yes. You misunderstand me I think. Yes, sorry I did misunderstood you. Even if you use Chaperon etc to parse markup, there'd be no difficulty expressing the links that you found as an HTML page - one intended to be consumed by the CLI, not to be publically viewed. Well in the case of css you want them as well publically viewed but I got your point. ;) In fact, if it were written to disc, forrest would probably delete it afterwards. Forrest actually is *not* aimed for html only support and one can think of the situation that you want your site to be only txt (kind of a book). Here you need to crawler the lex-rewriter outcome and follow the links. Hopefully I've shown that I had understood that already :-) yeah ;) The current limitation of forrest regarding the crawler are IMO not caused by the crawler design but rather by our (as in forrest) usage of it. Yep, fair enough. But if the CLI is going to survive the shift that is happening in Cocoon trunk, something big needs to be done by someone. It cannot survive in its current form as the code it uses is changing almost beyond recognition. Heh, perhaps the Cocoon CLI should just be a Maven plugin. ...or forrest plugin. ;) This would makes it possible that cocoon, lenya and forrest committer can help. Kind of http://svn.apache.org/viewcvs.cgi/lenya/sandbox/doco/ ;) Well, in the end, it is he who implements that decides. Upayavira
The all embarassing presentation email :-)
Hello everybody all and thanks to all of you for voting me as a committer. I'm so excited to become part of the ASF, expecially within the cocoon project who driven my web developing experience in the last 6 years. I wanted to let you know something about myself as per the Cocoon tradition: I assume you all know how embarassing it is to talk about oneself, so I'll just get on with some random notes. :) I'm 27 and I live in Rome, Italy. I started programming when i was about 7 with C64. It happened for a simple and completely random situation : i received a C64 and a game, inside the C64 box there were two manuals, a short one to run the game, and a big one teaching basic programming. I tried the small one, but since the game wasn't working i tried to read the big one and simply type what was written there, but it took time (and a lot of LOGO programming) to discovered why 10 print ciao 20 goto 10 caused a lot of ciao on my screen :) I decided not to attend university and started working as a freelance. Perl first and PHP/mysql then were the leading technologies back in 1997. For another incredibly random situation, I arrived in Milan in march 2000 to work for Bibop Research, which some of you might remember, where I had the incredible opportunity to work with Gianugo Rabellino, Ricardo Rocha and meet people like Stefano Mazzocchi and many other very skilled guys. I left Bibop a few months later, but this experience pushed me into Cocoon. I currently own a small company, and we work mainly with Cocoon. In the last couple of years we've been collaborating a lot with Pronetics (and from now on with Sourcesense) on intranet applications heavily based on cocoon-forms (a corporate banking and an administration system for a university, a total of about 300 cocoon forms, being the leading projects), binding directly on backend beans, so actually my main area of interest is cocoon forms and more specifically it's interaction with beans and backend persistence (with a strong focus on Hibernate lately). But I'll not limit my work to this field, I look forward to help out consolidating, improving and expanding this great framework, and I'm thrilled to be part of this incredible community. Thanks again to everyone who voted me: I consider being over here a great accomplishment. Simone -- Simone Gianni
[jira] Commented: (COCOON-1819) No support for creation of Bookmarks from JavaFlow
[ http://issues.apache.org/jira/browse/COCOON-1819?page=comments#action_12373077 ] Simone Gianni commented on COCOON-1819: --- Harlan, did you tried the patches? which one worked for you? No support for creation of Bookmarks from JavaFlow -- Key: COCOON-1819 URL: http://issues.apache.org/jira/browse/COCOON-1819 Project: Cocoon Type: Improvement Components: Blocks: Java Flow Reporter: Harlan Iverson Attachments: javaflow-bookmarks-1.diff, javaflow-bookmarks-2.diff, javaflow-bookmarks-sample.diff There is no JavaFlow equivalent of createWebContinuation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: The all embarassing presentation email :-)
10 print Welcome on board Simone! 20 goto 10 run 10 Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on board Simone! Welcome on b^C -- Jean-Baptiste Quenot aka John Banana Qwerty http://caraldi.com/jbq/
Re: What's going on with gump?
On 03.04.2006 17:32, Carsten Ziegeler wrote: I think they are doing this somehow by using an own local repository which always delivers the correct version. They put the results of building the trunks of our dependencies into this local repository. Jörg
[jira] Closed: (COCOON-1809) [PATCH] Forms page styling: Added event handling for group of type choice
[ http://issues.apache.org/jira/browse/COCOON-1809?page=all ] Jean-Baptiste Quenot closed COCOON-1809: Fix Version: 2.2-dev (Current SVN) 2.1.9-dev (current SVN) Resolution: Fixed Committed, thanks! [PATCH] Forms page styling: Added event handling for group of type choice - Key: COCOON-1809 URL: http://issues.apache.org/jira/browse/COCOON-1809 Project: Cocoon Type: Improvement Components: Blocks: Forms Versions: 2.2-dev (Current SVN), 2.1.9-dev (current SVN) Reporter: Rob Berens Assignee: Jean-Baptiste Quenot Priority: Minor Fix For: 2.2-dev (Current SVN), 2.1.9-dev (current SVN) Attachments: 20060403-cocoon-forms-1809, forms-page-styling.txt, forms-page-styling.xsl In forms-page-styling.xsl also a group of the type chois must implement event handling i.e. for the choice elements it must be possible to have an attribute formsOnShow containing some javascript to be executed. The attached patch makes this possible. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: The all embarassing presentation email :-)
Simone Gianni wrote: I'm 27 and I live in Rome, Italy. darn, meet-up opportunity missed ! I was there last weekend :) Jorg
cvs.a.o dependency reduction
fyi, I've removed daisy-util, daisy-htmlcleaner and xreporter-expression from cvs.a.o as they are now on ibiblio. Note that the groupid has changed and that daisy-util is now transitively depended on through daisy-htmlcleaner. The whole process ([1], [2] and [3]) took about 10 days, which isn't that bad I guess. I'll request more of our dependent libs to be uploaded sometime this week. Feel free to help out, instructions on how to create the bundle archive are at [4]. Regards Jorg [1] http://jira.codehaus.org/browse/MAVENUPLOAD-793 [2] http://jira.codehaus.org/browse/MAVENUPLOAD-794 [3] http://jira.codehaus.org/browse/MAVENUPLOAD-795 [4] http://maven.apache.org/guides/mini/guide-ibiblio-upload.html
