[EMAIL PROTECTED]: Project jakarta-poi (in module jakarta-poi) 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 jakarta-poi has an issue affecting its community integration. This issue affects 2 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - jakarta-poi : POI - jakarta-slide : Content Management System based on WebDAV technology Full details are available at: http://vmgump.apache.org/gump/public/jakarta-poi/jakarta-poi/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Output [poi-3.0-alpha2-04122006.jar] identifier set to output basename: [poi-3.0-alpha2] -DEBUG- Output [poi-scratchpad-3.0-alpha2-04122006.jar] identifier set to output basename: [poi-scratchpad-3.0-alpha2] -DEBUG- Output [poi-contrib-3.0-alpha2-04122006.jar] identifier set to output basename: [poi-contrib-3.0-alpha2] -INFO- Failed with reason build failed -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-poi/jakarta-poi/gump_work/build_jakarta-poi_jakarta-poi.html Work Name: build_jakarta-poi_jakarta-poi (Type: Build) Work ended in a state of : Failed Elapsed: 1 sec Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -DDSTAMP=04122006 -f build.xml gump [Working Directory: /usr/local/gump/public/workspace/jakarta-poi] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-poi/build/classes:/usr/local/gump/public/workspace/jakarta-poi/build/contrib-classes:/usr/local/gump/public/workspace/jakarta-poi/build/scratchpad-classes:/usr/local/gump/public/workspace/jakarta-poi/build/test-classes:/usr/local/gump/public/workspace/jakarta-poi/build/scratchpad-test-classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-04122006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-04122006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-04122006.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-04122006.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-04122006.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar - Buildfile: build.xml check-jars: fetch-jars: [get] Getting: http://www.ibiblio.org/maven/commons-logging/jars/commons-logging-1.1.jar [get] To: /x1/gump/public/workspace/jakarta-poi/lib/commons-logging-1.1.jar [get] Error opening connection java.io.FileNotFoundException: http://mirrors.ibiblio.org/pub/mirrors/maven/r/commons-logging/commons-logging/1.1/commons-logging-1.1.jar [get] Error opening connection java.io.FileNotFoundException: http://mirrors.ibiblio.org/pub/mirrors/maven/r/commons-logging/commons-logging/1.1/commons-logging-1.1.jar [get] Error opening connection java.io.FileNotFoundException: http://mirrors.ibiblio.org/pub/mirrors/maven/r/commons-logging/commons-logging/1.1/commons-logging-1.1.jar [get] Can't get http://www.ibiblio.org/maven/commons-logging/jars/commons-logging-1.1.jar to /x1/gump/public/workspace/jakarta-poi/lib/commons-logging-1.1.jar BUILD FAILED /x1/gump/public/workspace/jakarta-poi/build.xml:251: Can't get http://www.ibiblio.org/maven/commons-logging/jars/commons-logging-1.1.jar to /x1/gump/public/workspace/jakarta-poi/lib/commons-logging-1.1.jar Total time: 1 second - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/jakarta-poi/jakarta-poi/rss.xml - Atom: http://vmgump.apache.org/gump/public/jakarta-poi/jakarta-poi/atom.xml
[EMAIL PROTECTED]: Project jakarta-poi (in module jakarta-poi) 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 jakarta-poi has an issue affecting its community integration. This issue affects 2 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - jakarta-poi : POI - jakarta-slide : Content Management System based on WebDAV technology Full details are available at: http://vmgump.apache.org/gump/public/jakarta-poi/jakarta-poi/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Output [poi-3.0-alpha2-04122006.jar] identifier set to output basename: [poi-3.0-alpha2] -DEBUG- Output [poi-scratchpad-3.0-alpha2-04122006.jar] identifier set to output basename: [poi-scratchpad-3.0-alpha2] -DEBUG- Output [poi-contrib-3.0-alpha2-04122006.jar] identifier set to output basename: [poi-contrib-3.0-alpha2] -INFO- Failed with reason build failed -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-poi/jakarta-poi/gump_work/build_jakarta-poi_jakarta-poi.html Work Name: build_jakarta-poi_jakarta-poi (Type: Build) Work ended in a state of : Failed Elapsed: 1 sec Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -DDSTAMP=04122006 -f build.xml gump [Working Directory: /usr/local/gump/public/workspace/jakarta-poi] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-poi/build/classes:/usr/local/gump/public/workspace/jakarta-poi/build/contrib-classes:/usr/local/gump/public/workspace/jakarta-poi/build/scratchpad-classes:/usr/local/gump/public/workspace/jakarta-poi/build/test-classes:/usr/local/gump/public/workspace/jakarta-poi/build/scratchpad-test-classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-04122006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-04122006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-04122006.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-04122006.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-04122006.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar - Buildfile: build.xml check-jars: fetch-jars: [get] Getting: http://www.ibiblio.org/maven/commons-logging/jars/commons-logging-1.1.jar [get] To: /x1/gump/public/workspace/jakarta-poi/lib/commons-logging-1.1.jar [get] Error opening connection java.io.FileNotFoundException: http://mirrors.ibiblio.org/pub/mirrors/maven/r/commons-logging/commons-logging/1.1/commons-logging-1.1.jar [get] Error opening connection java.io.FileNotFoundException: http://mirrors.ibiblio.org/pub/mirrors/maven/r/commons-logging/commons-logging/1.1/commons-logging-1.1.jar [get] Error opening connection java.io.FileNotFoundException: http://mirrors.ibiblio.org/pub/mirrors/maven/r/commons-logging/commons-logging/1.1/commons-logging-1.1.jar [get] Can't get http://www.ibiblio.org/maven/commons-logging/jars/commons-logging-1.1.jar to /x1/gump/public/workspace/jakarta-poi/lib/commons-logging-1.1.jar BUILD FAILED /x1/gump/public/workspace/jakarta-poi/build.xml:251: Can't get http://www.ibiblio.org/maven/commons-logging/jars/commons-logging-1.1.jar to /x1/gump/public/workspace/jakarta-poi/lib/commons-logging-1.1.jar Total time: 1 second - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/jakarta-poi/jakarta-poi/rss.xml - Atom: http://vmgump.apache.org/gump/public/jakarta-poi/jakarta-poi/atom.xml
Re: [VOTE] Another alpha release?
On Fri, 1 Dec 2006, Rainer Klute wrote: However, a beta should be only a step on the way to a full release. This is something we really need to have. There are probably many users out there who don't trust in any beta or alpha releases - not to speak about a nighly build. They just grab the latest full release and use that. How many years have passed since we release it? We really need one! I think the question should be: * should we do a release now, freeze, work to a release now, release with some HSLF apis that are about to change, without excel comment support etc, then do another release in the new year once we have that code? or * alpha/beta now, beta when we've got the HSLF api tweaks + excel comment support in the new year, then freeze and release then? My main reason for suggesting an alpha was the HSLF api tweaks. If we're happy with doing a release where we're planning to change some (admitedly scratchpad) APIs just after, then I don't see why we can't then move to a speedy release. As for the freeze, once we've done this release (be it alpha or beta), we can do an SVN branch for the release candidate (if we decide we want one now). That can be frozen, and all bug fixes applied to it and trunk (new work only to trunk). The final release can be from there. I think that whatever happens, we should do a release in a few days time (be it alpha or beta, based on voting). Between now and then, we should decide if we want this to flow straight into a release candidate process (for a -final in late December / early January), with another -final once we have comments support etc, or if we want to hold off the -final until we have that code in. I'm not too bothered either way, but then I tend to use nightlies in production :) Do other people want to weigh in? Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] Mailing List:http://jakarta.apache.org/site/mail2.html#poi The Apache Jakarta POI Project: http://jakarta.apache.org/poi/
Re[2]: [VOTE] Another alpha release?
+1a. Does the full release mean that HSLF will be moved out of the scratchpad area? Yegor NB * should we do a release now, freeze, work to a release now, release with NB some HSLF apis that are about to change, without excel comment support NB etc, then do another release in the new year once we have that code? NB or NB * alpha/beta now, beta when we've got the HSLF api tweaks + excel comment NB support in the new year, then freeze and release then? NB My main reason for suggesting an alpha was the HSLF api tweaks. If we're NB happy with doing a release where we're planning to change some (admitedly NB scratchpad) APIs just after, then I don't see why we can't then move to a NB speedy release. NB As for the freeze, once we've done this release (be it alpha or beta), we NB can do an SVN branch for the release candidate (if we decide we want one NB now). That can be frozen, and all bug fixes applied to it and trunk (new NB work only to trunk). The final release can be from there. NB I think that whatever happens, we should do a release in a few days time NB (be it alpha or beta, based on voting). Between now and then, we should NB decide if we want this to flow straight into a release candidate process NB (for a -final in late December / early January), with another -final once NB we have comments support etc, or if we want to hold off the -final until NB we have that code in. NB I'm not too bothered either way, but then I tend to use nightlies in NB production :) Do other people want to weigh in? NB Nick NB - NB To unsubscribe, e-mail: [EMAIL PROTECTED] NB Mailing List:http://jakarta.apache.org/site/mail2.html#poi NB The Apache Jakarta POI Project: http://jakarta.apache.org/poi/ - To unsubscribe, e-mail: [EMAIL PROTECTED] Mailing List:http://jakarta.apache.org/site/mail2.html#poi The Apache Jakarta POI Project: http://jakarta.apache.org/poi/
Re[2]: [VOTE] Another alpha release?
On Mon, 4 Dec 2006, Yegor Kozlov wrote: Does the full release mean that HSLF will be moved out of the scratchpad area? No, that'd need another vote. I think we have some way to go before that'd be approved (based on past discussion), in terms of functionality, documentation, examples etc Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] Mailing List:http://jakarta.apache.org/site/mail2.html#poi The Apache Jakarta POI Project: http://jakarta.apache.org/poi/
Re: [VOTE] Another alpha release?
Fine code freeze for 5 minutes. Create a branch. Tag releases from said branch. -Andy Rainer Klute wrote: Andrew C. Oliver schrieb: -1 to any kind of code freeze that lasts more than the time it takes to create a branch. I can accept any -1 that eventually leads to creating a release. However, through the last years (!) that hasn't been possible. So please don't just -1 my proposal, but make a better one. Best regards Rainer Klute Rainer Klute IT-Consulting GmbH Dipl.-Inform. Rainer Klute E-Mail: [EMAIL PROTECTED] Körner Grund 24 Telefon: +49 172 2324824 D-44143 Dortmund Telefax: +49 231 5349423 OpenPGP fingerprint: E4E4386515EE0BED5C162FBB5343461584B5A42E - To unsubscribe, e-mail: [EMAIL PROTECTED] Mailing List:http://jakarta.apache.org/site/mail2.html#poi The Apache Jakarta POI Project: http://jakarta.apache.org/poi/
