Re: Introducing commons-skin
Henri Yandell wrote: Looks good - nice work :) Only bit that leaps out to me as missing are the little arrows to symbolize external links. We may not care. Yes, I have seen that as well. The problem is that the M2 site plugin does not generate a class=externalLink for those links like M1 did. I'll have a look and see if that's difficult to add. Definitely don't care that 'About Lang' is gone; and I'm not bothered that 'Development Process' is gone either. I presume these are standard Maven things that have gone from m1 to m2. M1 and M2 produces slightly different content, that's all. Hen On 12/27/06, Dennis Lundberg [EMAIL PROTECTED] wrote: Hi all Finally I took the time to sit down and create a Maven 2 skin for Jakarta Commons. What I have done is taken maven-classic-skin and combined that with the stylesheet rules that can be found in the site.xml file in commons/trunks-sandbox. Then I played around with the site for commons-lang to try to create a site that resembles what we get when we build the site using Maven 1. A SNAPSHOT of the skin has been uploaded to the Apache M2 SNAPSHOT repository, so you don't need to build it yourself to try it. You may need to tweak some files in your component to be able try out the skin. Instructions for this is on the wiki [1]. They should really be in SVN along with commons-skin, but I figured we should use wiki to get things started. To make it easier for you to review I have staged the commons-lang site that was generated using Maven 2 and commons-skin [2]. Compare it to the original commons-lang site [3] and give me some feedback. [1] http://wiki.apache.org/jakarta-commons/UsingCommonsSkin [2] http://people.apache.org/~dennisl/commons-lang/ [3] http://jakarta.apache.org/commons/lang/ -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Introducing commons-skin
Martin Cooper wrote: On 12/27/06, Henri Yandell [EMAIL PROTECTED] wrote: Looks good - nice work :) Only bit that leaps out to me as missing are the little arrows to symbolize external links. We may not care. Actually, I like those. :-) A couple of things I noticed: * The Docs for 2.2 is missing. Personally, I think it's important to know the version that I'm looking at, so I hope that can be put back. I'll see if that is available in M2, but that is not part of the skin. If it's in there it is an addition to site.xml, which for commons-lang is just something I put together quickly for now. We should however create a parent site.xml for all of commons. This gets inherited, published and versioned along side of our parent pom.xml. But that's an issue for another thread :) * The current page now shows in the menu as black, and looks the same as a menu heading. Previously it was bolded blue, which made it a distinct style from other items and from the headers. Yes, hmm. The current page is no longer a link, like it was in M1, so I was reluctant to change it to a link-like color. It should be doable though, if you feel strongly about it. Perhaps a slightly lighter shade of gray rather than black? Other than that, they look a lot alike. ;-) -- Martin Cooper Definitely don't care that 'About Lang' is gone; and I'm not bothered that 'Development Process' is gone either. I presume these are standard Maven things that have gone from m1 to m2. Hen On 12/27/06, Dennis Lundberg [EMAIL PROTECTED] wrote: Hi all Finally I took the time to sit down and create a Maven 2 skin for Jakarta Commons. What I have done is taken maven-classic-skin and combined that with the stylesheet rules that can be found in the site.xml file in commons/trunks-sandbox. Then I played around with the site for commons-lang to try to create a site that resembles what we get when we build the site using Maven 1. A SNAPSHOT of the skin has been uploaded to the Apache M2 SNAPSHOT repository, so you don't need to build it yourself to try it. You may need to tweak some files in your component to be able try out the skin. Instructions for this is on the wiki [1]. They should really be in SVN along with commons-skin, but I figured we should use wiki to get things started. To make it easier for you to review I have staged the commons-lang site that was generated using Maven 2 and commons-skin [2]. Compare it to the original commons-lang site [3] and give me some feedback. [1] http://wiki.apache.org/jakarta-commons/UsingCommonsSkin [2] http://people.apache.org/~dennisl/commons-lang/ [3] http://jakarta.apache.org/commons/lang/ -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Introducing commons-skin
Phil Steitz wrote: Thanks, Dennis! On 12/27/06, Martin Cooper [EMAIL PROTECTED] wrote: On 12/27/06, Henri Yandell [EMAIL PROTECTED] wrote: Looks good - nice work :) Only bit that leaps out to me as missing are the little arrows to symbolize external links. We may not care. Actually, I like those. :-) A couple of things I noticed: * The Docs for 2.2 is missing. Personally, I think it's important to know the version that I'm looking at, so I hope that can be put back. That should be no problem - that is the content. I think Dennis was just testing the skin. * The current page now shows in the menu as black, and looks the same as a menu heading. Previously it was bolded blue, which made it a distinct style from other items and from the headers. Other than that, they look a lot alike. ;-) The skin looks great to me - I don't have any problems with the arrows or menu bolding. I am, however, seeing a problem that I have seen before on Firefox. Could be a Firefox/Linux abnormality. Using Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.1) Gecko/20061208 Firefox/2.0.0.1, I get this: http://people.apache.org/~psteitz/newLang.jpg I see something similar when I enlarge the font size (CTRL +) 2 times when using Mozilla 2.0.0.1 on Windows. Nothing like it shows up for the M1 site, so I'm guessing the problem is in the way that M2 generates the html+css. Have you seen this on other M2 sites besides in Commons? It doesn't seem to matter how wide the navigation column is either. I tried making it wider but the effect is still there. Thanks again for picking this up. Phil -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r490688 - /jakarta/commons/proper/vfs/tags/vfs-1.0/
Author: imario Date: Thu Dec 28 01:48:05 2006 New Revision: 490688 URL: http://svn.apache.org/viewvc?view=revrev=490688 Log: release Added: jakarta/commons/proper/vfs/tags/vfs-1.0/ - copied from r490687, jakarta/commons/proper/vfs/tags/vfs-1.0-RC/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[RESULT][VOTE][VFS] release commons-vfs 1.0 based on RC10
Hi! Sorry for being late, I am ill, though, it's getting better slowly :-( The vote to release commons-vfs 1.0 has passed. Details: +1 Henry Yandell Niall Pemberton Oliver Heger Jörg Schaible Rahul Akolkar Martin van den Bernt Phil Steitz Mario Ivankovits No other votes. The voting thread can be found here [1] Thanks to everyone who voted and - more generally - to everyone who shared the effort to make this release come true! Next I'll put the website online and move the artifacts to their intended place, I'll post the announcement tomorrow to be sure the artifact has been mirrored. Ciao, Mario [1] http://www.mail-archive.com/commons-dev@jakarta.apache.org/msg88020.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Commons Transaction 1.2
Hi Oliver, Oliver Zeigermann wrote: We have worked our way through three release candidates now and the latest has been out there for quite some time without substantial shortcomings reported: http://people.apache.org/~ozeigermann/tx-1.2rc3/ Do you also have a link for the 1.2 site ? - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[nightly build] id failed.
Failed build logs: http://people.apache.org/~psteitz/commons-nightlies/20061228/id.log - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project commons-jelly-tags-jaxme (in module commons-jelly) 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 commons-jelly-tags-jaxme has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Configuration Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-jaxme : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-jaxme-28122006.jar] identifier set to project name -ERROR- No such project [ws-jaxme] for property. -ERROR- No such project [ws-jaxme] for property. -ERROR- No such project [ws-jaxme] for property. -ERROR- No such project [ws-jaxme] for property. -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme] -ERROR- Unhandled Property: maven.jar.jaxme-js on: Maven on Project:commons-jelly-tags-jaxme -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme] -ERROR- Unhandled Property: maven.jar.jaxme on: Maven on Project:commons-jelly-tags-jaxme -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme] -ERROR- Unhandled Property: maven.jar.jaxme-api on: Maven on Project:commons-jelly-tags-jaxme -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme] -ERROR- Unhandled Property: maven.jar.jaxme-xs on: Maven on Project:commons-jelly-tags-jaxme -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -INFO- Failed with reason configuration failed -ERROR- Bad Dependency. Project: ws-jaxme unknown to *this* workspace -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/rss.xml - Atom: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 1928122006, vmgump.apache.org:vmgump-public:1928122006 Gump E-mail Identifier (unique within run) #39. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project commons-jelly-tags-jaxme (in module commons-jelly) 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 commons-jelly-tags-jaxme has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Configuration Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-jaxme : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-jaxme-28122006.jar] identifier set to project name -ERROR- No such project [ws-jaxme] for property. -ERROR- No such project [ws-jaxme] for property. -ERROR- No such project [ws-jaxme] for property. -ERROR- No such project [ws-jaxme] for property. -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme] -ERROR- Unhandled Property: maven.jar.jaxme-js on: Maven on Project:commons-jelly-tags-jaxme -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme] -ERROR- Unhandled Property: maven.jar.jaxme on: Maven on Project:commons-jelly-tags-jaxme -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme] -ERROR- Unhandled Property: maven.jar.jaxme-api on: Maven on Project:commons-jelly-tags-jaxme -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme] -ERROR- Unhandled Property: maven.jar.jaxme-xs on: Maven on Project:commons-jelly-tags-jaxme -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -INFO- Failed with reason configuration failed -ERROR- Bad Dependency. Project: ws-jaxme unknown to *this* workspace -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/rss.xml - Atom: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 1928122006, vmgump.apache.org:vmgump-public:1928122006 Gump E-mail Identifier (unique within run) #39. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project commons-jelly-tags-jsl-test (in module commons-jelly) 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 commons-jelly-tags-jsl-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 82 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-jsl-test : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on ant exists, no need to add for property maven.jar.ant-optional. -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -WARNING- Overriding Maven properties: [/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties] -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/test-reports The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/gump_work/build_commons-jelly_commons-jelly-tags-jsl-test.html Work Name: build_commons-jelly_commons-jelly-tags-jsl-test (Type: Build) Work ended in a state of : Failed Elapsed: 15 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/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/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/commons-cli-1.0.x/target/commons-cli-28122006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-28122006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-28122006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-28122006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-28122006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-28122006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-28122006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-28122006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-28122006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-28122006.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-28122006.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar - [junit] at org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:64) [junit] at org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:59) [junit] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:263) [junit] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96) [junit] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187) [junit] at org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:66) [junit] at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:113) [junit] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96) [junit] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187) [junit] at org.apache.commons.jelly.tags.jsl.TemplateTag$1.run(TemplateTag.java:161) [junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59) [junit] at org.dom4j.rule.Mode.applyTemplates(Mode.java:80) [junit] at org.dom4j.rule.RuleManager$1.run(RuleManager.java:171) [junit]
[EMAIL PROTECTED]: Project commons-jelly-tags-jsl-test (in module commons-jelly) 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 commons-jelly-tags-jsl-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 82 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-jsl-test : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on ant exists, no need to add for property maven.jar.ant-optional. -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -WARNING- Overriding Maven properties: [/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties] -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/test-reports The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/gump_work/build_commons-jelly_commons-jelly-tags-jsl-test.html Work Name: build_commons-jelly_commons-jelly-tags-jsl-test (Type: Build) Work ended in a state of : Failed Elapsed: 15 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/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/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/commons-cli-1.0.x/target/commons-cli-28122006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-28122006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-28122006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-28122006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-28122006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-28122006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-28122006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-28122006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-28122006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-28122006.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-28122006.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar - [junit] at org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:64) [junit] at org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:59) [junit] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:263) [junit] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96) [junit] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187) [junit] at org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:66) [junit] at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:113) [junit] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96) [junit] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187) [junit] at org.apache.commons.jelly.tags.jsl.TemplateTag$1.run(TemplateTag.java:161) [junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59) [junit] at org.dom4j.rule.Mode.applyTemplates(Mode.java:80) [junit] at org.dom4j.rule.RuleManager$1.run(RuleManager.java:171) [junit]
[EMAIL PROTECTED]: Project commons-jelly-tags-fmt-test (in module commons-jelly) 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 commons-jelly-tags-fmt-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 26 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-fmt-test : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-fmt-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -WARNING- Overriding Maven properties: [/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/build.properties] -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/target/test-reports The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-fmt-test/gump_work/build_commons-jelly_commons-jelly-tags-fmt-test.html Work Name: build_commons-jelly_commons-jelly-tags-fmt-test (Type: Build) Work ended in a state of : Failed Elapsed: 12 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/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/packages/bsh-2.0b4/bsh-commands-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-classpath-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-core-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-bsf-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-reflect-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-util-2.0b4.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-28122006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-28122006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-28122006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/beanshell/target/commons-jelly-tags-beanshell-28122006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-28122006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-28122006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-28122006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-28122006.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-28122006.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/target/commons-jelly-tags-fmt-28122006.jar - [junit] at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) [junit] at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) [junit] at java.net.URLClassLoader.access$100(URLClassLoader.java:56) [junit] at java.net.URLClassLoader$1.run(URLClassLoader.java:195) [junit] at java.security.AccessController.doPrivileged(Native Method) [junit] at java.net.URLClassLoader.findClass(URLClassLoader.java:188) [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:306) [junit] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:251) [junit] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) [junit] at org.apache.commons.jelly.tags.ant.AntTagLibrary.createProject(AntTagLibrary.java:128)
[EMAIL PROTECTED]: Project commons-jelly-tags-fmt-test (in module commons-jelly) 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 commons-jelly-tags-fmt-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 26 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-fmt-test : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-fmt-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -WARNING- Overriding Maven properties: [/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/build.properties] -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/target/test-reports The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-fmt-test/gump_work/build_commons-jelly_commons-jelly-tags-fmt-test.html Work Name: build_commons-jelly_commons-jelly-tags-fmt-test (Type: Build) Work ended in a state of : Failed Elapsed: 12 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/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/packages/bsh-2.0b4/bsh-commands-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-classpath-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-core-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-bsf-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-reflect-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-util-2.0b4.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-28122006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-28122006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-28122006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/beanshell/target/commons-jelly-tags-beanshell-28122006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-28122006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-28122006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-28122006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-28122006.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-28122006.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/target/commons-jelly-tags-fmt-28122006.jar - [junit] at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) [junit] at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) [junit] at java.net.URLClassLoader.access$100(URLClassLoader.java:56) [junit] at java.net.URLClassLoader$1.run(URLClassLoader.java:195) [junit] at java.security.AccessController.doPrivileged(Native Method) [junit] at java.net.URLClassLoader.findClass(URLClassLoader.java:188) [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:306) [junit] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:251) [junit] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) [junit] at org.apache.commons.jelly.tags.ant.AntTagLibrary.createProject(AntTagLibrary.java:128)
Re: [RESULT][VOTE][VFS] release commons-vfs 1.0 based on RC10
On 12/28/06, Mario Ivankovits [EMAIL PROTECTED] wrote: Hi! Sorry for being late, I am ill, though, it's getting better slowly :-( The vote to release commons-vfs 1.0 has passed. Details: +1 Henry Yandell Niall Pemberton Oliver Heger Jörg Schaible Rahul Akolkar Martin van den Bernt Phil Steitz Mario Ivankovits No other votes. The voting thread can be found here [1] Thanks to everyone who voted and - more generally - to everyone who shared the effort to make this release come true! Next I'll put the website online and move the artifacts to their intended place, I'll post the announcement tomorrow to be sure the artifact has been mirrored. On the subject of announcements I was pondering adding this to the documentation: http://people.apache.org/~bayard/j-c-release/announce-email.html For what we currently do it really just means reminding us to explain what Commons Foo is and not assume the reader knows. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Introducing commons-skin
On 12/28/06, Dennis Lundberg [EMAIL PROTECTED] wrote:
Phil Steitz wrote:
Thanks, Dennis!
On 12/27/06, Martin Cooper [EMAIL PROTECTED] wrote:
On 12/27/06, Henri Yandell [EMAIL PROTECTED] wrote:
Looks good - nice work :)
Only bit that leaps out to me as missing are the little arrows to
symbolize external links. We may not care.
Actually, I like those. :-)
A couple of things I noticed:
* The Docs for 2.2 is missing. Personally, I think it's important to
know
the version that I'm looking at, so I hope that can be put back.
That should be no problem - that is the content. I think Dennis was
just
testing the skin.
* The current page now shows in the menu as black, and looks the same as
a
menu heading. Previously it was bolded blue, which made it a distinct
style
from other items and from the headers.
Other than that, they look a lot alike. ;-)
The skin looks great to me - I don't have any problems with the arrows
or
menu bolding. I am, however, seeing a problem that I have seen before
on
Firefox. Could be a Firefox/Linux abnormality. Using Mozilla/5.0 (X11;
U;
Linux i686; en-US; rv:1.8.1.1) Gecko/20061208 Firefox/2.0.0.1, I get
this:
http://people.apache.org/~psteitz/newLang.jpg
I see something similar when I enlarge the font size (CTRL +) 2 times
when using Mozilla 2.0.0.1 on Windows. Nothing like it shows up for the
M1 site, so I'm guessing the problem is in the way that M2 generates the
html+css. Have you seen this on other M2 sites besides in Commons?
Not yet. Struts, Shale, Maven all look fine. I vaguely remember a similar
problem back in m1, where I had to add a margin for the #leftcolumn, like
so:
#leftColumn {
margin: 10px 0 0 5px;
When I hack that in to maven-theme.css , it moves the nav bar over to where
it belongs. I don't know if that is the right way to fix the problem, but I
think the missing margin: element may be the cause of it.
Phil
Re: Introducing commons-skin
On 12/28/06, Dennis Lundberg [EMAIL PROTECTED] wrote: Martin Cooper wrote: On 12/27/06, Henri Yandell [EMAIL PROTECTED] wrote: Looks good - nice work :) Only bit that leaps out to me as missing are the little arrows to symbolize external links. We may not care. Actually, I like those. :-) A couple of things I noticed: * The Docs for 2.2 is missing. Personally, I think it's important to know the version that I'm looking at, so I hope that can be put back. I'll see if that is available in M2, but that is not part of the skin. Right. Sorry, I was just spotting differences between the pages I was looking at, and not really thinking skin versus non-skin. If it's in there it is an addition to site.xml, which for commons-lang is just something I put together quickly for now. We should however create a parent site.xml for all of commons. This gets inherited, published and versioned along side of our parent pom.xml. But that's an issue for another thread :) * The current page now shows in the menu as black, and looks the same as a menu heading. Previously it was bolded blue, which made it a distinct style from other items and from the headers. Yes, hmm. The current page is no longer a link, like it was in M1, so I was reluctant to change it to a link-like color. It should be doable though, if you feel strongly about it. Perhaps a slightly lighter shade of gray rather than black? I'm not sure I would say I feel _strongly_ about it, but I think it would be good for the current page to have a distinct style, whatever that might be. A different colour, an underscore, a background colour - I'm not that fussed. Just not blinking, please. ;-) -- Martin Cooper Other than that, they look a lot alike. ;-) -- Martin Cooper Definitely don't care that 'About Lang' is gone; and I'm not bothered that 'Development Process' is gone either. I presume these are standard Maven things that have gone from m1 to m2. Hen On 12/27/06, Dennis Lundberg [EMAIL PROTECTED] wrote: Hi all Finally I took the time to sit down and create a Maven 2 skin for Jakarta Commons. What I have done is taken maven-classic-skin and combined that with the stylesheet rules that can be found in the site.xml file in commons/trunks-sandbox. Then I played around with the site for commons-lang to try to create a site that resembles what we get when we build the site using Maven 1. A SNAPSHOT of the skin has been uploaded to the Apache M2 SNAPSHOT repository, so you don't need to build it yourself to try it. You may need to tweak some files in your component to be able try out the skin. Instructions for this is on the wiki [1]. They should really be in SVN along with commons-skin, but I figured we should use wiki to get things started. To make it easier for you to review I have staged the commons-lang site that was generated using Maven 2 and commons-skin [2]. Compare it to the original commons-lang site [3] and give me some feedback. [1] http://wiki.apache.org/jakarta-commons/UsingCommonsSkin [2] http://people.apache.org/~dennisl/commons-lang/ [3] http://jakarta.apache.org/commons/lang/ -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RESULT][VOTE][VFS] release commons-vfs 1.0 based on RC10
Hi Henri! http://people.apache.org/~bayard/j-c-release/announce-email.html For what we currently do it really just means reminding us to explain what Commons Foo is and not assume the reader knows. Ok, thanks! Will try my best. Ciao, Mario - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r490774 - /jakarta/commons/sandbox/commons-skin/trunk/src/main/resources/css/maven-theme.css
Author: dennisl
Date: Thu Dec 28 11:34:05 2006
New Revision: 490774
URL: http://svn.apache.org/viewvc?view=revrev=490774
Log:
Make the current page stand out a little less in the menu.
Modified:
jakarta/commons/sandbox/commons-skin/trunk/src/main/resources/css/maven-theme.css
Modified:
jakarta/commons/sandbox/commons-skin/trunk/src/main/resources/css/maven-theme.css
URL:
http://svn.apache.org/viewvc/jakarta/commons/sandbox/commons-skin/trunk/src/main/resources/css/maven-theme.css?view=diffrev=490774r1=490773r2=490774
==
---
jakarta/commons/sandbox/commons-skin/trunk/src/main/resources/css/maven-theme.css
(original)
+++
jakarta/commons/sandbox/commons-skin/trunk/src/main/resources/css/maven-theme.css
Thu Dec 28 11:34:05 2006
@@ -69,6 +69,10 @@
padding-left: 8px;
}
+#navcolumn li strong {
+ color: #369;
+}
+
#breadcrumbs {
background-color: #ccc;
color: #000;
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r490776 - in /jakarta/commons/proper/commons-parent/trunk/src: ./ site/ site/site.xml
Author: dennisl Date: Thu Dec 28 11:40:22 2006 New Revision: 490776 URL: http://svn.apache.org/viewvc?view=revrev=490776 Log: Add a site.xml that can be shared by all commons components that want to generate its site using Maven 2. Added: jakarta/commons/proper/commons-parent/trunk/src/ jakarta/commons/proper/commons-parent/trunk/src/site/ jakarta/commons/proper/commons-parent/trunk/src/site/site.xml (with props) Added: jakarta/commons/proper/commons-parent/trunk/src/site/site.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/commons-parent/trunk/src/site/site.xml?view=autorev=490776 == --- jakarta/commons/proper/commons-parent/trunk/src/site/site.xml (added) +++ jakarta/commons/proper/commons-parent/trunk/src/site/site.xml Thu Dec 28 11:40:22 2006 @@ -0,0 +1,43 @@ +?xml version=1.0 encoding=ISO-8859-1? +project name=Jakarta Commons + bannerLeft +nameThe Jakarta Project/name +srchttp://jakarta.apache.org/images/original-jakarta-logo.gif/src +hrefhttp://jakarta.apache.org//href + /bannerLeft + bannerRight +nameJakarta Commons/name +srchttp://jakarta.apache.org/commons/images/logo.png/src +hrefhttp://jakarta.apache.org/commons//href + /bannerRight + publishDate format=dd position=left / + version position=left / + skin +groupIdorg.apache.commons/groupId +artifactIdcommons-skin/artifactId +version1.0-SNAPSHOT/version + /skin + body +links + item name=Jakarta Commons href=http://jakarta.apache.org/commons/; / +/links +menu ref=reports inherit=bottom / +menu name=Commons inherit=bottom + item name=Home href=http://jakarta.apache.org/commons/; / + item name=Components href=http://jakarta.apache.org/commons/components.html; collapse=true +item name=Full list... href=http://jakarta.apache.org/commons/components.html; / + /item + item name=Sandbox href=http://jakarta.apache.org/commons/sandbox/index.html; collapse=true +item name=Full list... href=http://jakarta.apache.org/commons/sandbox/index.html; / + /item + item name=Dormant href=http://jakarta.apache.org/commons/dormant/index.html; collapse=true +item name=Full list... href=http://jakarta.apache.org/commons/dormant/index.html; / + /item + item name=Volunteering href=http://jakarta.apache.org/commons/volunteering.html; / + item name=Contributing Patches href=http://jakarta.apache.org/commons/patches.html; / + item name=Building Components href=http://jakarta.apache.org/commons/building.html; / + item name=Releasing Components href=http://jakarta.apache.org/commons/releases/index.html; / + item name=Wiki href=http://wiki.apache.org/jakarta-commons/FrontPage; / +/menu + /body +/project Propchange: jakarta/commons/proper/commons-parent/trunk/src/site/site.xml -- svn:eol-style = native - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r490778 - /jakarta/commons/proper/commons-parent/trunk/pom.xml
Author: dennisl Date: Thu Dec 28 11:52:57 2006 New Revision: 490778 URL: http://svn.apache.org/viewvc?view=revrev=490778 Log: Exclude the navigation file for Maven 1 sites, as it interferes with the site generation. Modified: jakarta/commons/proper/commons-parent/trunk/pom.xml Modified: jakarta/commons/proper/commons-parent/trunk/pom.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/commons-parent/trunk/pom.xml?view=diffrev=490778r1=490777r2=490778 == --- jakarta/commons/proper/commons-parent/trunk/pom.xml (original) +++ jakarta/commons/proper/commons-parent/trunk/pom.xml Thu Dec 28 11:52:57 2006 @@ -141,6 +141,22 @@ /plugins /build + reporting +plugins + plugin +groupIdorg.apache.maven.plugins/groupId +artifactIdmaven-site-plugin/artifactId +configuration + !-- Exclude the navigation file for Maven 1 sites, as it interferes + with the site generation. -- + moduleExcludes +xdocnavigation.xml/xdoc + /moduleExcludes +/configuration + /plugin +/plugins + /reporting + profiles profile idrelease/id - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Introducing commons-skin
Martin Cooper wrote: On 12/27/06, Henri Yandell [EMAIL PROTECTED] wrote: Looks good - nice work :) Only bit that leaps out to me as missing are the little arrows to symbolize external links. We may not care. Actually, I like those. :-) There's no built-in support for these arrows. I'm going to ask over in Maven-land if it can be done with a custom Velocity template. A couple of things I noticed: * The Docs for 2.2 is missing. Personally, I think it's important to know the version that I'm looking at, so I hope that can be put back. * The current page now shows in the menu as black, and looks the same as a menu heading. Previously it was bolded blue, which made it a distinct style from other items and from the headers. I managed to fix both of these. A new staged site can be found here: http://people.apache.org/~dennisl/commons-lang2/ This time all the common bits for the site.xml is inherited from commons-parent. New versions of commons-skin and commons-parent has been uploaded to the snapshot repo, if someone want's to try it. Now I'm going to start converting the sites in the sandbox to use commons-skin, unless someone stops me... Other than that, they look a lot alike. ;-) -- Martin Cooper Definitely don't care that 'About Lang' is gone; and I'm not bothered that 'Development Process' is gone either. I presume these are standard Maven things that have gone from m1 to m2. Hen On 12/27/06, Dennis Lundberg [EMAIL PROTECTED] wrote: Hi all Finally I took the time to sit down and create a Maven 2 skin for Jakarta Commons. What I have done is taken maven-classic-skin and combined that with the stylesheet rules that can be found in the site.xml file in commons/trunks-sandbox. Then I played around with the site for commons-lang to try to create a site that resembles what we get when we build the site using Maven 1. A SNAPSHOT of the skin has been uploaded to the Apache M2 SNAPSHOT repository, so you don't need to build it yourself to try it. You may need to tweak some files in your component to be able try out the skin. Instructions for this is on the wiki [1]. They should really be in SVN along with commons-skin, but I figured we should use wiki to get things started. To make it easier for you to review I have staged the commons-lang site that was generated using Maven 2 and commons-skin [2]. Compare it to the original commons-lang site [3] and give me some feedback. [1] http://wiki.apache.org/jakarta-commons/UsingCommonsSkin [2] http://people.apache.org/~dennisl/commons-lang/ [3] http://jakarta.apache.org/commons/lang/ -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Introducing commons-skin
On 12/28/06, Dennis Lundberg [EMAIL PROTECTED] wrote: Martin Cooper wrote: On 12/27/06, Henri Yandell [EMAIL PROTECTED] wrote: Looks good - nice work :) Only bit that leaps out to me as missing are the little arrows to symbolize external links. We may not care. Actually, I like those. :-) There's no built-in support for these arrows. I'm going to ask over in Maven-land if it can be done with a custom Velocity template. A couple of things I noticed: * The Docs for 2.2 is missing. Personally, I think it's important to know the version that I'm looking at, so I hope that can be put back. * The current page now shows in the menu as black, and looks the same as a menu heading. Previously it was bolded blue, which made it a distinct style from other items and from the headers. I managed to fix both of these. A new staged site can be found here: http://people.apache.org/~dennisl/commons-lang2/ Still has the leftcolumn offset problem for me on Firefox/Linux. Phil
Re: Introducing commons-skin
Phil Steitz wrote: On 12/28/06, Dennis Lundberg [EMAIL PROTECTED] wrote: Martin Cooper wrote: On 12/27/06, Henri Yandell [EMAIL PROTECTED] wrote: Looks good - nice work :) Only bit that leaps out to me as missing are the little arrows to symbolize external links. We may not care. Actually, I like those. :-) There's no built-in support for these arrows. I'm going to ask over in Maven-land if it can be done with a custom Velocity template. A couple of things I noticed: * The Docs for 2.2 is missing. Personally, I think it's important to know the version that I'm looking at, so I hope that can be put back. * The current page now shows in the menu as black, and looks the same as a menu heading. Previously it was bolded blue, which made it a distinct style from other items and from the headers. I managed to fix both of these. A new staged site can be found here: http://people.apache.org/~dennisl/commons-lang2/ Still has the leftcolumn offset problem for me on Firefox/Linux. Phil Phil, could you please check the following site and report back if it has the same problem or not: http://people.apache.org/~dennisl/commons-lang3/ The problems I saw earlier don't appear there. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (COLLECTIONS-235) Missing static int ListUtils.indexOf(List,Predicate) method
[ http://issues.apache.org/jira/browse/COLLECTIONS-235?page=all ] Dave Meikle updated COLLECTIONS-235: Attachment: COLLECTIONS-235.patch Here is a patch to add the ListUtils.indexOf method and the related unit test. Missing static int ListUtils.indexOf(List,Predicate) method --- Key: COLLECTIONS-235 URL: http://issues.apache.org/jira/browse/COLLECTIONS-235 Project: Commons Collections Issue Type: New Feature Affects Versions: 3.2 Reporter: Nathan Egge Attachments: COLLECTIONS-235.patch Similar to this method on CollectionUtils: public static Object find(Collection c,Predicate p) there should be the following method on ListUtils: public static int indexOf(List l,Predicate p) which returns the index of the first Object in the List where the Predicate evaluates true. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r490831 - in /jakarta/commons/proper/io/trunk: RELEASE-NOTES.txt src/java/org/apache/commons/io/FileUtils.java
Author: scolebourne
Date: Thu Dec 28 13:32:16 2006
New Revision: 490831
URL: http://svn.apache.org/viewvc?view=revrev=490831
Log:
IO-104 - Add release notes for copyFileToDirectory(File, File, boolean)
Modified:
jakarta/commons/proper/io/trunk/RELEASE-NOTES.txt
jakarta/commons/proper/io/trunk/src/java/org/apache/commons/io/FileUtils.java
Modified: jakarta/commons/proper/io/trunk/RELEASE-NOTES.txt
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/io/trunk/RELEASE-NOTES.txt?view=diffrev=490831r1=490830r2=490831
==
--- jakarta/commons/proper/io/trunk/RELEASE-NOTES.txt (original)
+++ jakarta/commons/proper/io/trunk/RELEASE-NOTES.txt Thu Dec 28 13:32:16 2006
@@ -109,6 +109,9 @@
- FileUtils.checksum, FileUtils.checksumCRC32
- add methods to create a checksum of a file
+- FileUtils.copyFileToDirectory [IO-104]
+ - add variant that optionally retains the file date
+
- FileDeleteStrategy
- FileCleaner[IO-56,IO-70]
- FileDeleteStrategy is a strategy for handling file deletion
Modified:
jakarta/commons/proper/io/trunk/src/java/org/apache/commons/io/FileUtils.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/io/trunk/src/java/org/apache/commons/io/FileUtils.java?view=diffrev=490831r1=490830r2=490831
==
---
jakarta/commons/proper/io/trunk/src/java/org/apache/commons/io/FileUtils.java
(original)
+++
jakarta/commons/proper/io/trunk/src/java/org/apache/commons/io/FileUtils.java
Thu Dec 28 13:32:16 2006
@@ -500,6 +500,7 @@
* @throws IOException if source or destination is invalid
* @throws IOException if an IO error occurs during copying
* @see #copyFile(File, File, boolean)
+ * @since Commons IO 1.3
*/
public static void copyFileToDirectory(File srcFile, File destDir, boolean
preserveFileDate) throws IOException {
if (destDir == null) {
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r490833 - /jakarta/commons/sandbox/commons-skin/trunk/src/main/resources/css/maven-theme.css
Author: dennisl
Date: Thu Dec 28 13:36:52 2006
New Revision: 490833
URL: http://svn.apache.org/viewvc?view=revrev=490833
Log:
Use em instead of px, so that we don't get into trouble if the font size grows.
Modified:
jakarta/commons/sandbox/commons-skin/trunk/src/main/resources/css/maven-theme.css
Modified:
jakarta/commons/sandbox/commons-skin/trunk/src/main/resources/css/maven-theme.css
URL:
http://svn.apache.org/viewvc/jakarta/commons/sandbox/commons-skin/trunk/src/main/resources/css/maven-theme.css?view=diffrev=490833r1=490832r2=490833
==
---
jakarta/commons/sandbox/commons-skin/trunk/src/main/resources/css/maven-theme.css
(original)
+++
jakarta/commons/sandbox/commons-skin/trunk/src/main/resources/css/maven-theme.css
Thu Dec 28 13:36:52 2006
@@ -78,7 +78,7 @@
color: #000;
border-top: 1px solid #aaa;
border-bottom: 1px solid #aaa;
- height: 14px;
+ height: 1.4em;
}
#breadcrumbs div {
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (COLLECTIONS-226) ListOrderedMap additional methods
[ http://issues.apache.org/jira/browse/COLLECTIONS-226?page=all ] Dave Meikle updated COLLECTIONS-226: Attachment: COLLECTIONS-226.patch Patch to add putAll(int index, Map map) method to ListOrderedMap ListOrderedMap additional methods - Key: COLLECTIONS-226 URL: http://issues.apache.org/jira/browse/COLLECTIONS-226 Project: Commons Collections Issue Type: Improvement Components: Map Reporter: Stephen Colebourne Priority: Minor Fix For: 3.3 Attachments: COLLECTIONS-226.patch Some new methods I had a need for on ListOrderedMap: - putAll(int, Map) - set(int, Object key, Object value) - sorting - potentially by making the keyList/valueList/entryList modifiable -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Introducing commons-skin
Phil Steitz wrote: On 12/28/06, Dennis Lundberg [EMAIL PROTECTED] wrote: Martin Cooper wrote: On 12/27/06, Henri Yandell [EMAIL PROTECTED] wrote: Looks good - nice work :) Only bit that leaps out to me as missing are the little arrows to symbolize external links. We may not care. Actually, I like those. :-) There's no built-in support for these arrows. I'm going to ask over in Maven-land if it can be done with a custom Velocity template. A couple of things I noticed: * The Docs for 2.2 is missing. Personally, I think it's important to know the version that I'm looking at, so I hope that can be put back. * The current page now shows in the menu as black, and looks the same as a menu heading. Previously it was bolded blue, which made it a distinct style from other items and from the headers. I managed to fix both of these. A new staged site can be found here: http://people.apache.org/~dennisl/commons-lang2/ Still has the leftcolumn offset problem for me on Firefox/Linux. Phil OK, I think I've found and fixed the problem now. Please double check this one: http://people.apache.org/~dennisl/commons-lang4/ -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (COLLECTIONS-226) ListOrderedMap additional methods
[ http://issues.apache.org/jira/browse/COLLECTIONS-226?page=comments#action_12461260 ] Dave Meikle commented on COLLECTIONS-226: - With regards to set(int, Object key, Object value), does put(int index, Object key, Object value) not already provide this functionality as it replaces the key-value mapping at the location with the passed pair? Cheers, Dave ListOrderedMap additional methods - Key: COLLECTIONS-226 URL: http://issues.apache.org/jira/browse/COLLECTIONS-226 Project: Commons Collections Issue Type: Improvement Components: Map Reporter: Stephen Colebourne Priority: Minor Fix For: 3.3 Attachments: COLLECTIONS-226.patch Some new methods I had a need for on ListOrderedMap: - putAll(int, Map) - set(int, Object key, Object value) - sorting - potentially by making the keyList/valueList/entryList modifiable -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (IO-105) Add a FileUtils.copyDirectoryStructure method
[ http://issues.apache.org/jira/browse/IO-105?page=all ] Stephen Colebourne updated IO-105: -- Fix Version/s: 1.4 Description: For potential source, see: https://svn.codehaus.org/plexus/plexus-utils/trunk/src/main/java/org/codehaus/plexus/util/FileUtils.java (was: For potential source, see: https://svn.codehaus.org/plexus/plexus-utils/trunk/src/main/java/org/codehaus/plexus/util/FileUtils.java) Perhaps you could describe what the method is supposed to do? Add a FileUtils.copyDirectoryStructure method - Key: IO-105 URL: http://issues.apache.org/jira/browse/IO-105 Project: Commons IO Issue Type: Improvement Components: Utilities Reporter: Henri Yandell Fix For: 1.4 For potential source, see: https://svn.codehaus.org/plexus/plexus-utils/trunk/src/main/java/org/codehaus/plexus/util/FileUtils.java -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (IO-103) commons-io cannot be deployed with Maven 2
[ http://issues.apache.org/jira/browse/IO-103?page=all ] Stephen Colebourne resolved IO-103. --- Resolution: Fixed Assignee: Henri Yandell I don't use Maven2, but this change appears to have been committed. commons-io cannot be deployed with Maven 2 -- Key: IO-103 URL: http://issues.apache.org/jira/browse/IO-103 Project: Commons IO Issue Type: Bug Affects Versions: 1.3 Reporter: Jochen Wiedmann Assigned To: Henri Yandell Fix For: 1.3 Attachments: commons-io-resources.patch The commons-io POM contains a resource section, which specifies that the NOTICE.txt and LICENSE.txt files are being added to the jar files META-INF directory. Unfortunately, this triggers MSOURCES-6, a well known bug in the maven-sources-plugin, which attempts to include the base directory into the source jar file. The base directory includes the sources jar itself, which is growing while it is being included into itself, which is growing while it is included into itself, ... In other words, the maven-sources-plugin is creating a jar file endleseely. When deploying the commons-io with mvn -Prc commons-io deploy or mvn -Prelease commons-io deploy then the maven-sources-plugin is invoked by the commons-parent POM. In other words, the commons-io jar file cannot be deployed. The attached patch removes the resources section from the commons-parent POM: This can easily be done, because the commons-parent POM is already addressing this by invoking the antrun plugin. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Introducing commons-skin
Hmmm. http://people.apache.org/~dennisl/commons-lang3/http://people.apache.org/%7Edennisl/commons-lang3/ puts the nav bar in the right place flush left, but shows a big black box between the Jakarta and Lang logos on the top. http://people.apache.org/~dennisl/commons-lang4/http://people.apache.org/%7Edennisl/commons-lang4/ puts the nav bar in the middle, as before. Phil On 12/28/06, Dennis Lundberg [EMAIL PROTECTED] wrote: Phil Steitz wrote: On 12/28/06, Dennis Lundberg [EMAIL PROTECTED] wrote: Martin Cooper wrote: On 12/27/06, Henri Yandell [EMAIL PROTECTED] wrote: Looks good - nice work :) Only bit that leaps out to me as missing are the little arrows to symbolize external links. We may not care. Actually, I like those. :-) There's no built-in support for these arrows. I'm going to ask over in Maven-land if it can be done with a custom Velocity template. A couple of things I noticed: * The Docs for 2.2 is missing. Personally, I think it's important to know the version that I'm looking at, so I hope that can be put back. * The current page now shows in the menu as black, and looks the same as a menu heading. Previously it was bolded blue, which made it a distinct style from other items and from the headers. I managed to fix both of these. A new staged site can be found here: http://people.apache.org/~dennisl/commons-lang2/ Still has the leftcolumn offset problem for me on Firefox/Linux. Phil OK, I think I've found and fixed the problem now. Please double check this one: http://people.apache.org/~dennisl/commons-lang4/ -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (IO-107) FileUtils.openOutputStream
FileUtils.openOutputStream -- Key: IO-107 URL: http://issues.apache.org/jira/browse/IO-107 Project: Commons IO Issue Type: New Feature Components: Utilities Reporter: Stephen Colebourne Assigned To: Stephen Colebourne Fix For: 1.3 Add a new method - FileUtils.openOutputStream. This will centralise the opening of a file in a single place in the source code. The new method will check that the file is not a directory, and will create parent directories if required. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r490858 - in /jakarta/commons/proper/io/trunk: RELEASE-NOTES.txt src/java/org/apache/commons/io/FileUtils.java src/test/org/apache/commons/io/FileUtilsTestCase.java
Author: scolebourne
Date: Thu Dec 28 14:50:07 2006
New Revision: 490858
URL: http://svn.apache.org/viewvc?view=revrev=490858
Log:
IO-107 - Add FileUtils.openOutputStream, creating parent directories if required
Modified:
jakarta/commons/proper/io/trunk/RELEASE-NOTES.txt
jakarta/commons/proper/io/trunk/src/java/org/apache/commons/io/FileUtils.java
jakarta/commons/proper/io/trunk/src/test/org/apache/commons/io/FileUtilsTestCase.java
Modified: jakarta/commons/proper/io/trunk/RELEASE-NOTES.txt
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/io/trunk/RELEASE-NOTES.txt?view=diffrev=490858r1=490857r2=490858
==
--- jakarta/commons/proper/io/trunk/RELEASE-NOTES.txt (original)
+++ jakarta/commons/proper/io/trunk/RELEASE-NOTES.txt Thu Dec 28 14:50:07 2006
@@ -102,6 +102,9 @@
- wildcardMatch - new method that has IOCase as a parameter
- equals - new method that has IOCase as a parameter
+- FileUtils.openOutputStream [IO-107]
+ - new method to open a FileOutputStream, creating parent directories if
required
+
- FileUtils.isFileOlder
- add methods to check if a file is older (i.e. isFileOlder()) - counterparts
to the existing isFileNewer() methods.
Modified:
jakarta/commons/proper/io/trunk/src/java/org/apache/commons/io/FileUtils.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/io/trunk/src/java/org/apache/commons/io/FileUtils.java?view=diffrev=490858r1=490857r2=490858
==
---
jakarta/commons/proper/io/trunk/src/java/org/apache/commons/io/FileUtils.java
(original)
+++
jakarta/commons/proper/io/trunk/src/java/org/apache/commons/io/FileUtils.java
Thu Dec 28 14:50:07 2006
@@ -107,6 +107,39 @@
//---
/**
+ * Opens a [EMAIL PROTECTED] FileOutputStream} for the specified file,
checking and
+ * creating the parent directory if it does not exist.
+ * p
+ * At the end of the method either the stream will be successfully opened,
+ * or an exception will have been thrown.
+ * p
+ * The parent directory will be created if it does not exist.
+ * The file will be created if it does not exist.
+ * An exception is thrown if the file object exists but is a directory.
+ * An exception is thrown if the parent directory cannot be created.
+ *
+ * @param file the file to create, not null
+ * @throws IOException if the file object is a directory
+ * @throws IOException if a parent directory needs creating but that fails
+ */
+public static FileOutputStream openOutputStream(File file) throws
IOException {
+if (file.exists()) {
+if (file.isDirectory()) {
+throw new IOException(File ' + file + ' exists but is a
directory);
+}
+} else {
+File parent = file.getParentFile();
+if (parent.exists() == false) {
+if (parent.mkdirs() == false) {
+throw new IOException(File ' + file + ' could not be
created);
+}
+}
+}
+return new FileOutputStream(file);
+}
+
+//---
+/**
* Returns a human-readable version of the file size, where the input
* represents a specific number of bytes.
*
Modified:
jakarta/commons/proper/io/trunk/src/test/org/apache/commons/io/FileUtilsTestCase.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/io/trunk/src/test/org/apache/commons/io/FileUtilsTestCase.java?view=diffrev=490858r1=490857r2=490858
==
---
jakarta/commons/proper/io/trunk/src/test/org/apache/commons/io/FileUtilsTestCase.java
(original)
+++
jakarta/commons/proper/io/trunk/src/test/org/apache/commons/io/FileUtilsTestCase.java
Thu Dec 28 14:50:07 2006
@@ -102,8 +102,55 @@
FileUtils.deleteDirectory(getTestDirectory());
}
-// byteCountToDisplaySize
+//---
+public void test_openOutputStream_exists() throws Exception {
+File file = new File(getTestDirectory(), test.txt);
+createLineBasedFile(file, new String[] {Hello});
+FileOutputStream out = null;
+try {
+out = FileUtils.openOutputStream(file);
+out.write(0);
+} finally {
+IOUtils.closeQuietly(out);
+}
+assertEquals(true, file.exists());
+}
+
+public void test_openOutputStream_existsButIsDirectory() throws Exception {
+File directory = new File(getTestDirectory(), subdir);
+directory.mkdirs();
+try {
+FileUtils.openOutputStream(directory);
+fail();
+} catch (IOException
Re: [commons-parent] Make deployment URL pluggable
Fool that I am. Of course, I forgot the patch.
On 12/29/06, Jochen Wiedmann [EMAIL PROTECTED] wrote:
Hi,
in light of
http://marc.theaimsgroup.com/?l=jakarta-commons-devm=116560781629523w=2
and following a suggestion by Jörg Schaible, I'd like to propose the
attached patch. It introduces properties
commons.deployment.protocol
commons.deployment.release.url
commons.deployment.rc.url
The former is specifies as scp and may be overwritten, for example,
to be scpexe. The others are used by the release and rc
profiles, respectively. Both are referencing
${commons.deployment.protocol}.
In other words, the proposed patch is upwards compatible with the
current settings, except that it allows to override the deployment
protocol or URL. Both makes sense, IMO. For example, nightly builds
might wish to override the rc URL.
Thoughts? If noone else intervenes, I'll apply the patch.
Jochen
--
My wife Mary and I have been married for forty-seven years and not
once have we had an argument serious enough to consider divorce;
murder, yes, but divorce, never.
(Jack Benny)
--
My wife Mary and I have been married for forty-seven years and not
once have we had an argument serious enough to consider divorce;
murder, yes, but divorce, never.
(Jack Benny)
Index: pom.xml
===
--- pom.xml (Revision 490873)
+++ pom.xml (Arbeitskopie)
@@ -164,7 +164,7 @@
repository
idapache.releases/id
nameApache Release Distribution Repository/name
- urlscp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository/url
+ url${commons.deployment.release.url}/url
/repository
/distributionManagement
build
@@ -203,8 +203,13 @@
repository
idapache.snapshots/id
nameApache Development Snapshot Repository/name
- urlscp://people.apache.org/www/people.apache.org/repo/m2-snapshot-repository/url
+ url${commons.deployment.rc.url}/url
/repository
+snapshotRepository
+ idapache.snapshots/id
+ nameApache Development Snapshot Repository/name
+ url${commons.deployment.rc.url}/url
+/snapshotRepository
/distributionManagement
build
plugins
@@ -245,4 +250,15 @@
maven.compile.target1.3/maven.compile.target
/properties
--
-/project
\ Kein Zeilenvorschub am Ende der Datei
+ properties
+!--
+ Make the deployment protocol and the URL pluggable. This allows to
+ switch to other protocols (like scpexe, which some users prefer over
+ scp) or URL's (if users are working locally on people.apache.org)
+ by overriding these properties.
+--
+commons.deployment.protocolscp/commons.deployment.protocol
+commons.deployment.release.url${commons.deployment.protocol}://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository/commons.deployment.release.url
+commons.deployment.rc.url${commons.deployment.protocol}://people.apache.org/www/people.apache.org/repo/m2-snapshot-repository/commons.deployment.rc.url
+ /properties
+/project
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[commons-parent] Make deployment URL pluggable
Hi,
in light of
http://marc.theaimsgroup.com/?l=jakarta-commons-devm=116560781629523w=2
and following a suggestion by Jörg Schaible, I'd like to propose the
attached patch. It introduces properties
commons.deployment.protocol
commons.deployment.release.url
commons.deployment.rc.url
The former is specifies as scp and may be overwritten, for example,
to be scpexe. The others are used by the release and rc
profiles, respectively. Both are referencing
${commons.deployment.protocol}.
In other words, the proposed patch is upwards compatible with the
current settings, except that it allows to override the deployment
protocol or URL. Both makes sense, IMO. For example, nightly builds
might wish to override the rc URL.
Thoughts? If noone else intervenes, I'll apply the patch.
Jochen
--
My wife Mary and I have been married for forty-seven years and not
once have we had an argument serious enough to consider divorce;
murder, yes, but divorce, never.
(Jack Benny)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (IO-107) FileUtils.openOutputStream
[ http://issues.apache.org/jira/browse/IO-107?page=all ] Stephen Colebourne resolved IO-107. --- Resolution: Fixed FileUtils.openOutputStream -- Key: IO-107 URL: http://issues.apache.org/jira/browse/IO-107 Project: Commons IO Issue Type: New Feature Components: Utilities Reporter: Stephen Colebourne Assigned To: Stephen Colebourne Fix For: 1.3 Add a new method - FileUtils.openOutputStream. This will centralise the opening of a file in a single place in the source code. The new method will check that the file is not a directory, and will create parent directories if required. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (IO-107) FileUtils.openOutputStream
[ http://issues.apache.org/jira/browse/IO-107?page=comments#action_12461270 ] Stephen Colebourne commented on IO-107: --- This call is also being used to add the 'create parent folders' behaviour to other methods in FileUtils. See the release notes for details. FileUtils.openOutputStream -- Key: IO-107 URL: http://issues.apache.org/jira/browse/IO-107 Project: Commons IO Issue Type: New Feature Components: Utilities Reporter: Stephen Colebourne Assigned To: Stephen Colebourne Fix For: 1.3 Add a new method - FileUtils.openOutputStream. This will centralise the opening of a file in a single place in the source code. The new method will check that the file is not a directory, and will create parent directories if required. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (COLLECTIONS-220) Serialization/Deserialization doesn't work well with empty buffers.
[ http://issues.apache.org/jira/browse/COLLECTIONS-220?page=all ]
Dave Meikle updated COLLECTIONS-220:
Attachment: COLLECTIONS-200.patch
Proposed Patch to fix Object Serialization Problem
Serialization/Deserialization doesn't work well with empty buffers.
---
Key: COLLECTIONS-220
URL: http://issues.apache.org/jira/browse/COLLECTIONS-220
Project: Commons Collections
Issue Type: Bug
Components: Buffer
Affects Versions: 3.2
Reporter: Jose Luis Huertas
Priority: Minor
Attachments: COLLECTIONS-200.patch, SerializationTest.java
When I serialize the queue to disk an it has elements, all works ok, but when
I serialize an empty queue I have some problems when I create a new object
using the serialized file.
When I deserialize the queue it has a 'buffer' with size 1 (with null
content), 'tail' and 'head' fields are 0 (they are declared transient). So,
when I try to add a new object to the queue, the sentence:
Object[] tmp = new Object[((buffer.length - 1) * 2) + 1];
Is executed in the add() method to increase the buffer length, but the buffer
remains with the same size! (buffer.length = 1 -- (1 - 1) * 2 + 1 = 1). So,
the object is added and when the tail is going to be incremented, it is reset
to 0!!
private int increment(int index) {
index++;
if (index = buffer.length) {
index = 0;
}
return index;
}
So it is impossible to add new elements after an empty queue has been
serialized / deserialized.
I attach a simple TestCase where this is proved. The example works when you
use XMLEncoder to serialize the buffer but doesn't work if you use
ObjectOutputStream or XStream.
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (IO-99) FileCleaner thread never ends and cause memory leak in AS
[ http://issues.apache.org/jira/browse/IO-99?page=comments#action_12461277 ] Jochen Wiedmann commented on IO-99: --- I have reviewed Stephen's patch and it looks good to me. Only minor note: I'd recommend to make getTrackCount() synchronized. Can we close this issue now and proceed with releasing 1.3? FileCleaner thread never ends and cause memory leak in AS - Key: IO-99 URL: http://issues.apache.org/jira/browse/IO-99 Project: Commons IO Issue Type: Bug Affects Versions: 1.2 Environment: JBOssPortal with commons.fileupload Reporter: Vera Mickaël Priority: Critical Fix For: 1.3 Attachments: IO-99.patch FileCleaner opens a thread and no solution is given to the user to end it. So when an application is undeployed in an Application Server, a thread is still alive. The WebApp can't be undeployed and this results in a classloader leak that will cause an OutOfMemoryError. I think the API should be extended so that a user can end the thread. A better way would be to provide a class that cleans everything for commons IO. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r490867 - in /jakarta/commons/proper/io/trunk: RELEASE-NOTES.txt src/java/org/apache/commons/io/FileUtils.java
Author: scolebourne
Date: Thu Dec 28 15:13:32 2006
New Revision: 490867
URL: http://svn.apache.org/viewvc?view=revrev=490867
Log:
IO-107 - Use FileUtils.openOutputStream, thus creating parent directories if
required
Modified:
jakarta/commons/proper/io/trunk/RELEASE-NOTES.txt
jakarta/commons/proper/io/trunk/src/java/org/apache/commons/io/FileUtils.java
Modified: jakarta/commons/proper/io/trunk/RELEASE-NOTES.txt
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/io/trunk/RELEASE-NOTES.txt?view=diffrev=490867r1=490866r2=490867
==
--- jakarta/commons/proper/io/trunk/RELEASE-NOTES.txt (original)
+++ jakarta/commons/proper/io/trunk/RELEASE-NOTES.txt Thu Dec 28 15:13:32 2006
@@ -104,16 +104,22 @@
- FileUtils.openOutputStream [IO-107]
- new method to open a FileOutputStream, creating parent directories if
required
+- FileUtils.touch
+- FileUtils.copyURLToFile
+- FileUtils.writeStringToFile
+- FileUtils.writeByteArrayToFile
+- FileUtils.writeLines
+ - enhanced to create parent directories if required
- FileUtils.isFileOlder
- - add methods to check if a file is older (i.e. isFileOlder()) - counterparts
+ - new methods to check if a file is older (i.e. isFileOlder()) - counterparts
to the existing isFileNewer() methods.
- FileUtils.checksum, FileUtils.checksumCRC32
- - add methods to create a checksum of a file
+ - new methods to create a checksum of a file
- FileUtils.copyFileToDirectory [IO-104]
- - add variant that optionally retains the file date
+ - new variant that optionally retains the file date
- FileDeleteStrategy
- FileCleaner[IO-56,IO-70]
Modified:
jakarta/commons/proper/io/trunk/src/java/org/apache/commons/io/FileUtils.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/io/trunk/src/java/org/apache/commons/io/FileUtils.java?view=diffrev=490867r1=490866r2=490867
==
---
jakarta/commons/proper/io/trunk/src/java/org/apache/commons/io/FileUtils.java
(original)
+++
jakarta/commons/proper/io/trunk/src/java/org/apache/commons/io/FileUtils.java
Thu Dec 28 15:13:32 2006
@@ -116,6 +116,7 @@
* The parent directory will be created if it does not exist.
* The file will be created if it does not exist.
* An exception is thrown if the file object exists but is a directory.
+ * An exception is thrown if the file exists but cannot be written to.
* An exception is thrown if the parent directory cannot be created.
*
* @param file the file to create, not null
@@ -127,6 +128,9 @@
if (file.isDirectory()) {
throw new IOException(File ' + file + ' exists but is a
directory);
}
+if (file.canWrite() == false) {
+throw new IOException(File ' + file + ' cannot be written
to);
+}
} else {
File parent = file.getParentFile();
if (parent.exists() == false) {
@@ -168,14 +172,15 @@
* closed without modifying it, but updating the file date and time.
* p
* NOTE: As from v1.3, this method throws an IOException if the last
- * modified date of the file cannot be set
+ * modified date of the file cannot be set. Also, as from v1.3 this method
+ * creates parent directories if they do not exist.
*
* @param file the File to touch
* @throws IOException If an I/O problem occurs
*/
public static void touch(File file) throws IOException {
if (!file.exists()) {
-OutputStream out = new FileOutputStream(file);
+OutputStream out = openOutputStream(file);
IOUtils.closeQuietly(out);
}
boolean success = file.setLastModified(System.currentTimeMillis());
@@ -790,34 +795,19 @@
* will be created if they don't already exist. codedestination/code
* will be overwritten if it already exists.
*
- * @param source A codeURL/code to copy bytes from.
- * @param destination A non-directory codeFile/code to write bytes to
- * (possibly overwriting).
- *
- * @throws IOException if
- * ul
- * licodesource/code URL cannot be opened/li
- * licodedestination/code cannot be written to/li
- * lian IO error occurs during copying/li
- * /ul
+ * @param source the codeURL/code to copy bytes from, not null
+ * @param destination the non-directory codeFile/code to write bytes
to
+ * (possibly overwriting), not null
+ * @throws IOException if codesource/code URL cannot be opened
+ * @throws IOException if codedestination/code is a directory
+ * @throws IOException if codedestination/code cannot be written
+ * @throws IOException if codedestination/code needs creating but
can't be
+ * @throws IOException if an IO error occurs during copying
*/
public static void
Re: [io] Non-encoding versions of readFileToString etc
Henri Yandell wrote: We have encoding in io.* in two places, FileUtils and IOUtils. In IOUtils we provide the default variant, in FileUtils we don't. Whatever the arguments for or against this, I prefer consistency if possible. On reviewing the code in more detail, we do have defaults for encoding, and defaults for other parameters as well. There is thus no overriding good reason not to allow these additional defaulting methods. If you want them, go ahead and add them ;-) Stephen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (EMAIL-60) Performance in HtmlEmail#setMsg(String msg)
[ http://issues.apache.org/jira/browse/EMAIL-60?page=all ] Ben Speakmon updated EMAIL-60: -- Attachment: HtmlEmail.patch Here's a better patch that calculates the exact size of the StringBuffer. Also, it turns the constant strings into static constants. Performance in HtmlEmail#setMsg(String msg) --- Key: EMAIL-60 URL: http://issues.apache.org/jira/browse/EMAIL-60 Project: Commons Email Issue Type: Improvement Affects Versions: 1.0 Reporter: Cédrik LIME Priority: Minor Attachments: HtmlEmail.patch The method HtmlEmail.setMsg(String) builds an HTML message from a text message using a StringBuffer. This StringBuffer should be correctly sized according to inputted message, to avoid unnecessary resizing: 138c138 new StringBuffer() --- new StringBuffer(msg.length() + 37) -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [commons-parent] Make deployment URL pluggable
On 12/28/06, Jochen Wiedmann [EMAIL PROTECTED] wrote:
Hi,
in light of
http://marc.theaimsgroup.com/?l=jakarta-commons-devm=116560781629523w=2
and following a suggestion by Jörg Schaible, I'd like to propose the
attached patch. It introduces properties
commons.deployment.protocol
commons.deployment.release.url
commons.deployment.rc.url
The former is specifies as scp and may be overwritten, for example,
to be scpexe. The others are used by the release and rc
profiles, respectively. Both are referencing
${commons.deployment.protocol}.
In other words, the proposed patch is upwards compatible with the
current settings, except that it allows to override the deployment
protocol or URL. Both makes sense, IMO. For example, nightly builds
might wish to override the rc URL.
Thoughts? If noone else intervenes, I'll apply the patch.
snip/
Meant to get back to this (but got distracted). Thanks for following
up with a proposal.
Since that thread, we now have more data points about scpexe://
because I had the same problem with the Shale master pom (see thread
linked in from the comment in issue below for feedback received from
Linux, Windows -- with and without Cygwin -- and Mac users):
http://issues.apache.org/struts/browse/SHALE-369
So, it seems just changing scp:// to scpexe:// is a decent solution
(and simpler). Are you still +0 to that?
-Rahul
Jochen
--
My wife Mary and I have been married for forty-seven years and not
once have we had an argument serious enough to consider divorce;
murder, yes, but divorce, never.
(Jack Benny)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
