[nightly build] configuration failed.
Failed build logs: http://vmbuild.apache.org/~commons/nightly/logs//20070414/configuration.log - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (CONFIGURATION-263) XMLConfiguration drops attributes if a property value is a list
XMLConfiguration drops attributes if a property value is a list
---
Key: CONFIGURATION-263
URL: https://issues.apache.org/jira/browse/CONFIGURATION-263
Project: Commons Configuration
Issue Type: Bug
Affects Versions: 1.4
Reporter: Oliver Heger
Fix For: 1.5
When the following test is run with the following xml the second assertEquals
statement fails:
XML:
?xml version=1.0 encoding=ISO-8859-1 ?
test
a name=XABC/a
a name=Y1,2,3/a
/test
TEST:
public void testXMLConfig() throws Exception {
File file = new File(/xml/xmlConfigTest.xml);
XMLConfiguration xmlConfig = new XMLConfiguration(file);
xmlConfig.load();
assertEquals(X,xmlConfig.getProperty(a(0)[EMAIL PROTECTED]));
assertEquals(Y,xmlConfig.getProperty(a(1)[EMAIL PROTECTED]));
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (CONFIGURATION-264) SubnodeConfiguration does not see reloads of its parent configuration
SubnodeConfiguration does not see reloads of its parent configuration - Key: CONFIGURATION-264 URL: https://issues.apache.org/jira/browse/CONFIGURATION-264 Project: Commons Configuration Issue Type: Bug Affects Versions: 1.4 Reporter: Oliver Heger Fix For: 1.5 The problem can be reproduced as follows: 1 config = new XMLConfiguration(c:\\conf.xml); 2 config.setReloadingStrategy(new FileChangedReloadingStrategy()); 3 SubnodeConfiguration parentItemConfig = config.configurationAt(parent-item); 4 String ss2 = parentItemConfig.getString(sub-item); 5 //Now, sub-item node value changes to new_value 6 ss2 = parentItemConfig.getString(sub-item); // still returns old_value -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [configuration] 1.4 dependency in PropertyListParser.java
Emmanuel Bourg wrote: My bad sorry, I'll fix this. This might be the opportunity to discuss the JRE requirement for the next releases. What version do we use (1.4 or 5) and when ? I believe it's too early to go directly to Java 5, on the server side JEE 5 is not widely adopted yet (BEA just released WebLogic 10), and on the client side there are still a lot of OS X users that haven't upgraded to Tiger (10.4). I would suggest moving to Java 1.4 for a release in the near future (configuration 1.5 or 1.6) and then jump to Java 5 for the next major release (2.0) involving a deep refactoring of the component. I agree with using Java 5 for version 2.0. About switching to JDK 1.4 I am not sure. I think we should do this switch as late as possible. I.e. as long as no specific 1.4 features are needed for the fixes and features we implement, we should stay with 1.3. I remember a posting on this list shortly before the Configuration 1.3 release, in which the author made clear that he still needs JDK 1.3 support. Even with a version requiring Java 5, I think we should still support the latest pre Java 5 version by fixing the major bugs reported. Thus we will not force people to upgrade, there will still be a great version compatible with Java 1.3/1.4 around, and people with Java 5 will enjoy an even better version. +1 Emmanuel Bourg Oliver snip/ - 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 148 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-14042007.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-14042007.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-14042007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-14042007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-14042007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-14042007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-14042007.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-14042007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-14042007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-14042007.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-14042007.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 148 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-14042007.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-14042007.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-14042007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-14042007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-14042007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-14042007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-14042007.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-14042007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-14042007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-14042007.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-14042007.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]
FileUpload errors
Hello, guys! Thanks for your software, it's pretty good. But I have found an error. For example, on the page http://jakarta.apache.org/commons/fileupload/streaming.html is some outdated code Instead of 'item.openStream(stream)' should be 'item.getInputStream(Stream)'. Thanks for assistance, Kirill A Maksimov - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Some signs of life on log4j 2.0
This has no impact on JCL, but I thought it might be of interest to some here and did not want anyone to feel excluded and am definitely interested in any additional hands. There has been some recent activity on the log4j-dev mailing list that might mark the start of log4j 2.0 development after years of talk (I'm sure that there is still plenty of talk ahead). A couple of weeks ago there was a thread (http://marc.info/? t=11755588553r=1w=2) on the state of log4j 1.3. Out of that came an experiment to see if Chainsaw (dependent on log4j 1.3) could be migrated back to using log4j 1.2 plus a limited amount of backported log4j 1.3 code (http://marc.info/?l=log4j- devm=117623660224909w=2). At this point, Chainsaw can be built with either log4j 1.3 or with the SVN version of log4j 1.2 plus the expression-filter and receivers sandbox projects (which are backports of log4j 1.3 features that can work with log4j 1.2). Out of that came an idea to repackage the log4j 1.3 PatternLayout so that it could be used with log4j 1.2 when users would like to use a feature that had only been in the log4j 1.3 version of PatternLayout. The sandbox project has been set up by copying the corresponding code from log4j 1.3 but no other work has been done yet. The idea laid out in http://permalink.gmane.org/ gmane.comp.jakarta.log4j.devel/11905 (for some reason this message doesn't appear in the other archives) is that after that project has made a log4j 1.2 compatible PatternLayout, it could then be branched off to start defining the log4j 2.0 interfaces around Layouts, LoggingEvents and the like before moving on the bigger and better things. There has been some follow up discussion that got into broader log4j 2.0 issues (latest messages only show up in GMANE archive). If anybody would like to help out on the ground floor of a potential log4j 2.0, please join log4j-dev. If you are already an Apache committer and would like commit rights on the sandbox area to contribute to the precursor experiments, mention it to the list and we will work it out. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Sonfiguration-189
Is Configuration-189 issue resolved in R1.4 of Commons Configuration? This is a proposal to support reloadable configurations in the configuration descriptor parsed by ConfigurationFactory. I suggest two forms, a complete form to fine tune the strategy applied to the configuration: configuration properties fileName=config.properties reloading-strategy class=org.apache.commons.configuration.reloading.FileChangedReloadingStrategy param name=refreshDelay value=3/ /reloading-strategy /properties /configuration and a short form: configuration properties fileName=config.properties reloadable=true/ /configuration This short form will use a FileChangedReloadingStrategy with the default values. This form keeps the descriptor simple for those that don't bother fine tuning the performance of the reloading mechanism. -- Rohit Sharma, Irving, TX 75061 - Ahhh...imagining that irresistible new car smell? Check outnew cars at Yahoo! Autos.
