AW: [transaction][VOTE] Release 1.0-RC1
+1 Daniel -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Oliver Zeigermann Gesendet: Samstag, 20. November 2004 02:28 An: Jakarta Commons Developers List Betreff: [transaction][VOTE] Release 1.0-RC1 Dear community, I would like to see a 1.0 release candidate. The code is stable, junt tests pass, document exists and the scripts are in good shape. Still we should check that everything looks the way we expect before releasing a final 1.0. I already created the distributions calling 'ant package'. They are ready for inspection here: http://www.apache.org/~ozeigermann/ So, I am +1 for a release. Oliver - 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]
cvs commit: jakarta-commons/transaction project.xml
dflorey 2004/11/21 01:50:18 Modified:transaction project.xml Log: Removed organization name Revision ChangesPath 1.3 +1 -1 jakarta-commons/transaction/project.xml Index: project.xml === RCS file: /home/cvs/jakarta-commons/transaction/project.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- project.xml 19 Nov 2004 23:57:19 - 1.2 +++ project.xml 21 Nov 2004 09:50:18 - 1.3 @@ -90,7 +90,7 @@ nameDaniel Florey/name iddflorey/id email[EMAIL PROTECTED]/email - organizationApache Software Foundation/organization + organization/organization timezone+1/timezone roles roleJava Developer/role - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[GUMP@brutus]: Project commons-latka (in module jakarta-commons) 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-latka has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 10 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-latka : Functional Testing Suite Full details are available at: http://brutus.apache.org/gump/public/jakarta-commons/commons-latka/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-latka.jar] identifier set to project name -DEBUG- Dependency on jaxen exists, no need to add for property jaxen.jar. -INFO- Made directory [/usr/local/gump/public/workspace/jakarta-commons/latka/target/classes] -INFO- Made directory [/usr/local/gump/public/workspace/jakarta-commons/latka/target/test-classes] -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/jakarta-commons/commons-latka/gump_work/build_jakarta-commons_commons-latka.html Work Name: build_jakarta-commons_commons-latka (Type: Build) Work ended in a state of : Failed Elapsed: 6 mins 31 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Djaxen.jar=/usr/local/gump/public/workspace/jaxen/target/jaxen-21112004.jar dist [Working Directory: /usr/local/gump/public/workspace/jakarta-commons/latka] CLASSPATH:
[GUMP@brutus]: Project commons-jelly-tags-ant (in module jelly-tags) 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-ant has an issue affecting its community integration. This issue affects 4 projects, and has been outstanding for 23 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-ant : This is a Jelly interface for Ant. - commons-jelly-tags-fmt : This is a set of Jelly i18n tags. - commons-jelly-tags-jsl : The Jelly Stylesheet Library (JSL) - maven : Project Management Tools Full details are available at: http://brutus.apache.org/gump/public/jelly-tags/commons-jelly-tags-ant/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-ant-21112004.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/jelly-tags/commons-jelly-tags-ant/gump_work/build_jelly-tags_commons-jelly-tags-ant.html Work Name: build_jelly-tags_commons-jelly-tags-ant (Type: Build) Work ended in a state of : Failed Elapsed: 6 secs Command Line: java -Djava.awt.headless=true -Dbuild.clonevm=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dfinal.name=commons-jelly-tags-ant-21112004 jar [Working Directory: /usr/local/gump/public/workspace/jelly-tags/ant] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jelly-tags/ant/target/classes:/usr/local/gump/public/workspace/jelly-tags/ant/target/test-classes:/usr/local/gump/public/workspace/jakarta-commons/jelly/target/commons-jelly-21112004.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-stylebook.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-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/jakarta-commons/collections/build/commons-collections-21112004.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-21112004.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-21112004.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/packages/dom4j-1.4/dom4j-full.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-21112004.jar:/usr/local/gump/public/workspace/jakarta-commons/discovery/dist/commons-discovery.jar:/usr/local/gump/public/workspace/jakarta-servletapi-5/jsr154/dist/lib/servlet-api.jar:/usr/local/gump/public/workspace/jakarta-servletapi-5/jsr152/dist/lib/jsp-api.jar:/usr/local/gump/public/workspace/jakarta-taglibs/dist/standard/lib/standard.jar:/usr/local/gump/public/workspace/jakarta-taglibs/dist/standard/lib/jstl.jar:/usr/local/gump/packages/nekohtml-0.9.3/nekohtmlXni.jar:/usr/local/gump/packages/nekohtml-0.9.3/nekohtml.jar:/usr/local/gump/public/workspace/commons-grant/target/commons-grant-21112004.jar:/usr/local/gump/public/workspace/jelly-tags/util/target/commons-jelly-tags-util-21112004.jar:/usr/local/gump/public/workspace/jelly-tags/junit/target/commons-jelly-tags-junit-21112004.jar - [junit] Testcase: readWriteIn took 0.239 sec [junit] Testcase: startUpReadWrite took 0.15 sec [junit] Testcase: copy took 0.156 sec [junit] Caused an ERROR [junit] file:/home/gump/workspaces2/public/workspace/jelly-tags/ant/target/test-classes/org/apache/commons/jelly/ant/suite.jelly:114:80: util:loadText charsetName [junit] org.apache.commons.jelly.JellyTagException: file:/home/gump/workspaces2/public/workspace/jelly-tags/ant/target/test-classes/org/apache/commons/jelly/ant/suite.jelly:114:80: util:loadText charsetName [junit] at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:680) [junit] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:263) [junit] at
Re: [VOTE] Promote Email to Commons Proper
I prepared a bundle for dumbster on codehaus. It will be synchronize with ibiblio in few hours. Emmanuel - Original Message - From: Henri Yandell [EMAIL PROTECTED] To: Jakarta Commons Developers List [EMAIL PROTECTED] Sent: Friday, November 19, 2004 5:26 AM Subject: Re: [VOTE] Promote Email to Commons Proper Impressively, Jason has now updated the SF site, the Dumbster site and released a new version under the ASL 2.0. All that remains is to get it into Maven, and I figure that one of the [email] guys can happily do that (there are instructions on the Maven site for it). So nothing looks likely to slow down a release, and many kudos to Jason Kitchen for being so responsive to our legal particulars. Hen On Thu, 18 Nov 2004 19:57:09 +, robert burrell donkin [EMAIL PROTECTED] wrote: On 18 Nov 2004, at 11:39, Eric Pugh wrote: Alright.. This thread has somewhat gotton away from me. Since Dumbster is now licensed as ASL (despite the website being out of date), can we move to a conclusion on this thread? If we consider that [email] hasn't materially changed, and therefore a new vote isn't required, then I currently tally: +1 Eric Pugh +1 Matthias Wessendorf +1 Yoav Shapira Robert, you raised the original lgpl issue which I hope is now sorted out. While you didn't specifically put a -1 down, I think it was implied. Would you be willing to change that to something else? i'm now +1 to promotion (and like henri -1 to release until all the loose ends concerning the dumbster license) i would like to see a note added to the web site recommending the latest (ASF licensed) dumbster. i'd also like to see a new version of dumbster (with an ASL license) uploaded to the maven java repository and the project.xml updated to reflect that. - robert - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: jakarta-commons/transaction/xdocs/locks tutorial.xml
Hey, great, this is almost readable now ;) Oliver On 21 Nov 2004 07:52:27 -, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: masonjm 2004/11/20 23:52:27 Modified:transaction/xdocs/locks tutorial.xml Log: Minor grammar and spelling fixes. Revision ChangesPath 1.3 +39 -39jakarta-commons/transaction/xdocs/locks/tutorial.xml Index: tutorial.xml === RCS file: /home/cvs/jakarta-commons/transaction/xdocs/locks/tutorial.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- tutorial.xml 19 Nov 2004 23:58:46 - 1.2 +++ tutorial.xml 21 Nov 2004 07:52:27 - 1.3 @@ -20,12 +20,12 @@ lock/a and specific implementations. There is a a href=../apidocs/org/apache/commons/transaction/locking/GenericLock.htmlgeneric implementation/a of a multi level lock with a subtle, yet simple -compatibility mechanism. This mechanism allows to implement quite a +compatibility mechanism. This mechanism allows for implementing quite a number of different lock types such as a read write lock which is a href=../apidocs/org/apache/commons/transaction/locking/ReadWriteLock.htmlprovided -for covenience/a, although very easy to implement. As already -a href=index.htmlexlained/a in the locking agent can be any Java +for covenience/a. As explained +a href=index.htmlearlier/a the locking agent can be any Java object. Have a look at the simple a href=../apidocs/org/apache/commons/transaction/locking/ReadWriteLock.html#acquireRead(java.lang.Object,%20long) method for acquiring a lock for read access/a as a reference./p @@ -39,7 +39,7 @@ href=../apidocs/org/apache/commons/transaction/locking/LockManager.html#atomicGetOrCreateLock(java.lang.Object)important method/a is for either creating a non existing lock in a specified resource or retrieving it if it was created before. It is important to -make this atomically so there is no chance of acciently creating more +make this atomic so there is no chance of accidently creating more than one lock for a single resource./p pemThe whole trick is to have at most one lock for a resource and have different compatible lock levels @@ -50,23 +50,23 @@ subsection name=Example: Fine grained locks in Jakarta Slide pLets get to the first example which is how Jakarta Slide handles -fine grained locking in its WebDAV layer. Slide can store resources to -all kinds of stores which most likely have locks for consistency as -well. However, there is this generic locking to be very sure there are -no deadlocks, the behavior is similar for all stores and finally to +fine grained locking in its WebDAV layer. Slide can store resources in +all kinds of stores which most likely will implement their own locks for +consistency. However, Slide has generic locking to be certain there are +no deadlocks, and the behavior is similar for all stores to provide locking for stores that do not have locks of their own. All -locks must be set at the very beginning of a request and release at +locks must be set at the very beginning of a request and released at the end of the request in an atomic block to ban the hazard of deadlocks. Slide does this with a simple synchronized block, but to have something to show here we will exercise it with a multi level lock. Such a lock is very simple and is merely -exclusive, it will look like this:/p +exclusive. It will look like this:/p source GenericLock exclusive = new new GenericLock(Mutex, 1, new PrintWriterLogger(new PrintWriter(System.out), Locking, false)); /source p -Now we have a lock called Mutex with the highest lock level of +Now we have a lock called Mutex with a highest lock level of code1/code and a logger that simply writes to stdout. Different lock levels and their compatibility is a special feature of a @@ -80,16 +80,16 @@ This tries to a href=../apidocs/org/apache/commons/transaction/locking/GenericLock.html#acquire(java.lang.Object,%20int,%20boolean,%20boolean,%20long)acquire a lock/a of level one (=exclusive) for the agent -Owner. Parameters three and four tells the lock that it should block +Owner. Parameters three and four tell the lock that it should block the current thread if this lock level can not be acquired and that -this lock is reentrant. Reentrant means that the same agant can -require lock levels otherwise incompatible. Finally, there is a +this lock is reentrant. Reentrant means that the same agent can +require lock levels that would be otherwise incompatible. Finally, there is a timeout which is the maximum time the agent will wait for a lock. If a lock still is unavailable after this time the method will return -false. In our
[GUMP@brutus]: Project commons-latka (in module jakarta-commons) success
To whom it may satisfy... 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-latka *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/jakarta-commons/commons-latka/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-latka.jar] identifier set to project name -DEBUG- Dependency on jaxen exists, no need to add for property jaxen.jar. -INFO- Made directory [/usr/local/gump/public/workspace/jakarta-commons/latka/target/classes] -INFO- Made directory [/usr/local/gump/public/workspace/jakarta-commons/latka/target/test-classes] -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/jakarta-commons/commons-latka/gump_work/build_jakarta-commons_commons-latka.html Work Name: build_jakarta-commons_commons-latka (Type: Build) Work ended in a state of : Success Elapsed: 24 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Djaxen.jar=/usr/local/gump/public/workspace/jaxen/target/jaxen-21112004.jar dist [Working Directory: /usr/local/gump/public/workspace/jakarta-commons/latka] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/latka/target/classes:/usr/local/gump/public/workspace/jakarta-commons/latka/target/test-classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-stylebook.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-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/httpclient/dist/commons-httpclient.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jakarta-commons/codec/dist/commons-codec-21112004.jar:/usr/local/gump/public/workspace/logging-log4j/log4j-21112004.jar:/usr/local/gump/public/workspace/logging-log4j/log4j-chainsaw-21112004.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-21112004.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jakarta-commons/jelly/target/commons-jelly-21112004.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-21112004.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-21112004.jar:/usr/local/gump/public/workspace/jelly-tags/junit/target/commons-jelly-tags-junit-21112004.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-21112004.jar:/usr/local/gump/packages/dom4j-1.4/dom4j-full.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-21112004.jar:/usr/local/gump/public/workspace/jakarta-commons/discovery/dist/commons-discovery.jar:/usr/local/gump/public/workspace/jakarta-servletapi-5/jsr154/dist/lib/servlet-api.jar:/usr/local/gump/public/workspace/jakarta-servletapi-5/jsr152/dist/lib/jsp-api.jar:/usr/local/gump/public/workspace/jakarta-taglibs/dist/standard/lib/standard.jar:/usr/local/gump/public/workspace/jakarta-taglibs/dist/standard/lib/jstl.jar:/usr/local/gump/packages/nekohtml-0.9.3/nekohtmlXni.jar:/usr/local/gump/packages/nekohtml-0.9.3/nekohtml.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-21112004.jar - test: jar: [jar] Building jar: /home/gump/workspaces2/public/workspace/jakarta-commons/latka/target/commons-latka.jar javadoc: [mkdir] Created
cvs commit: jakarta-commons/betwixt/src/java/org/apache/commons/betwixt/strategy NamespacePrefixMapper.java
rdonkin 2004/11/21 13:08:32 Modified:betwixt/src/java/org/apache/commons/betwixt/strategy NamespacePrefixMapper.java Log: Fixed javadocs typo Revision ChangesPath 1.3 +2 -2 jakarta-commons/betwixt/src/java/org/apache/commons/betwixt/strategy/NamespacePrefixMapper.java Index: NamespacePrefixMapper.java === RCS file: /home/cvs/jakarta-commons/betwixt/src/java/org/apache/commons/betwixt/strategy/NamespacePrefixMapper.java,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- NamespacePrefixMapper.java13 Jun 2004 21:32:46 - 1.2 +++ NamespacePrefixMapper.java21 Nov 2004 21:08:32 - 1.3 @@ -28,7 +28,7 @@ * DTDs are not namespace aware and so a fixed prefixed must be chosen * and used consistently. * This class is used to supply consistent, user specified prefixes. - * /p + * /p * @author a href='http://jakarta.apache.org/'Jakarta Commons Team/a * @version $Revision$ */ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-commons/commons-build commons-site.jsl project.xml
rdonkin 2004/11/21 13:26:27
Modified:commons-build commons-site.jsl project.xml
Log:
Removed apachecon references.
Revision ChangesPath
1.14 +1 -1 jakarta-commons/commons-build/commons-site.jsl
Index: commons-site.jsl
===
RCS file: /home/cvs/jakarta-commons/commons-build/commons-site.jsl,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- commons-site.jsl 31 Oct 2004 18:49:04 - 1.13
+++ commons-site.jsl 21 Nov 2004 21:26:27 - 1.14
@@ -161,7 +161,7 @@
}
// window.alert( 'Width = ' + myWidth );
if (myWidth 850) {
-
document['organization-logo'].src='http://ApacheCon.Com/2004/US/logos/logo_only.gif';
+
document['organization-logo'].src='http://jakarta.apache.org/images/original-jakarta-logo.gif';
}
]]// /x:comment
/x:element
1.34 +4 -0 jakarta-commons/commons-build/project.xml
Index: project.xml
===
RCS file: /home/cvs/jakarta-commons/commons-build/project.xml,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -r1.33 -r1.34
--- project.xml 31 Oct 2004 18:49:04 - 1.33
+++ project.xml 21 Nov 2004 21:26:27 - 1.34
@@ -24,8 +24,12 @@
organization
nameThe Apache Software Foundation/name
+urlhttp://jakarta.apache.org/url
+logohttp://jakarta.apache.org/jakarta-logo.gif/logo
+!--
urlhttp://ApacheCon.Com/2004/US//url
logohttp://ApacheCon.Com/2004/US/logos/logo_only.gif/logo
+--
/organization
inceptionYear2001/inceptionYear
logo/images/logo.png/logo
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-commons/betwixt/xdocs faq.xml
rdonkin 2004/11/21 13:28:14 Modified:betwixt/xdocs faq.xml Log: Added note on conversions to the FAQ Revision ChangesPath 1.11 +16 -1 jakarta-commons/betwixt/xdocs/faq.xml Index: faq.xml === RCS file: /home/cvs/jakarta-commons/betwixt/xdocs/faq.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- faq.xml 13 Jun 2004 21:32:49 - 1.10 +++ faq.xml 21 Nov 2004 21:28:14 - 1.11 @@ -102,6 +102,11 @@ a code.betwixt/code file emwithout/em also adding default propertes? /a /li + li +a href=#read-validation + Does Betwixt Validate Values Read? +/a + /li /ol pstrongBuilding Betwixt/strong/p ol @@ -298,8 +303,18 @@ dd Add the codelt;addDefaultsgt;/code and to it add an attribute codeadd-properties=quot;falsequot;/code. +/dd + dt + a name=read-validation +Does Betwixt Validate Values Read? + /a +/dt +dd +Betwixt does not directly validate any property values read. The convertion of the string +in the xml to values suitable for setting on the bean property is delegated to the +ObjectStringConverter. The converter may - or may not - validate values (and throw exceptions +when they fall outside acceptable ranges). /dd - /dl /subsection - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Release Chain 1.0
I believe Chain is now sufficiently complete and stable to warrant an official 1.0 release. There are no outstanding bug reports, and the component is already in use in a number of projects. The plan is to release HEAD as Commons Chain 1.0 on completion of a successful vote. I will be the release manager. --- [ ] +1 I support this release and am willing to help [ ] +0 I support this release but am unable to help [ ] -0 I do not support this release [ ] -1 I do not support this release, and here are my reasons --- Here is my own +1. -- Martin Cooper - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANNOUNCE] Release of Commons HttpClient 3.0 Beta1
The Jakarta Commons team is pleased to announce the first beta release of HttpClient 3.0. Starting with this release the 3.0 API is frozen. We will now focus on creating additional documentation and test cases. All current HttpClient 2.0 users are strongly encouraged to migrate to 3.0. As always we welcome suggestions and bug reports. Thank you, Commons HttpClient Development Team HttpClient 3.0 Web Site: http://jakarta.apache.org/commons/httpclient/3.0/index.html Release Notes: http://www.apache.org/dist/jakarta/commons/httpclient/RELEASE- NOTES.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[io] JDiff and Clirr reports for 1.0 - 1.1 available
I've uploaded JDiff and Clirr reports comparing the current HEAD with Commons IO 1.0. They're available here: http://cvs.apache.org/~martinc/io/ If these look OK (they do to me), and people are happy with the current state of the code, I'd like to go ahead and start the release process for IO 1.1. Any objections, just shout. ;-) -- Martin Cooper - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[GUMP@brutus]: Project commons-latka (in module jakarta-commons) success
To whom it may satisfy... 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-latka *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/jakarta-commons/commons-latka/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-latka.jar] identifier set to project name -DEBUG- Dependency on jaxen exists, no need to add for property jaxen.jar. -INFO- Made directory [/usr/local/gump/public/workspace/jakarta-commons/latka/target/classes] -INFO- Made directory [/usr/local/gump/public/workspace/jakarta-commons/latka/target/test-classes] -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/jakarta-commons/commons-latka/gump_work/build_jakarta-commons_commons-latka.html Work Name: build_jakarta-commons_commons-latka (Type: Build) Work ended in a state of : Success Elapsed: 15 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Djaxen.jar=/usr/local/gump/public/workspace/jaxen/target/jaxen-21112004.jar dist [Working Directory: /usr/local/gump/public/workspace/jakarta-commons/latka] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/latka/target/classes:/usr/local/gump/public/workspace/jakarta-commons/latka/target/test-classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-stylebook.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-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/httpclient/dist/commons-httpclient.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jakarta-commons/codec/dist/commons-codec-21112004.jar:/usr/local/gump/public/workspace/logging-log4j/log4j-21112004.jar:/usr/local/gump/public/workspace/logging-log4j/log4j-chainsaw-21112004.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-21112004.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jakarta-commons/jelly/target/commons-jelly-21112004.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-21112004.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-21112004.jar:/usr/local/gump/public/workspace/jelly-tags/junit/target/commons-jelly-tags-junit-21112004.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-21112004.jar:/usr/local/gump/packages/dom4j-1.4/dom4j-full.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-21112004.jar:/usr/local/gump/public/workspace/jakarta-commons/discovery/dist/commons-discovery.jar:/usr/local/gump/public/workspace/jakarta-servletapi-5/jsr154/dist/lib/servlet-api.jar:/usr/local/gump/public/workspace/jakarta-servletapi-5/jsr152/dist/lib/jsp-api.jar:/usr/local/gump/public/workspace/jakarta-taglibs/dist/standard/lib/standard.jar:/usr/local/gump/public/workspace/jakarta-taglibs/dist/standard/lib/jstl.jar:/usr/local/gump/packages/nekohtml-0.9.3/nekohtmlXni.jar:/usr/local/gump/packages/nekohtml-0.9.3/nekohtml.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-21112004.jar - test: jar: [jar] Building jar: /home/gump/workspaces2/public/workspace/jakarta-commons/latka/target/commons-latka.jar javadoc: [mkdir] Created
[io] Filename prefixes
In order to write the normalize() method properly, I realised that we have to deal with filename prefixes properly. The point being that you can't .. up into a filename prefix. Here's the javadoc for the method I'm writing. Does this cover the cases? /** * Returns the length of the filename prefix, such as codeC://code or code~//code. * p * This method will handle a file in either Unix or Windows format. * The prefix includes the first slash in the full filename. * pre * Windows: * a\b\c.txt -- -- relative * \a\b\c.txt -- \ -- drive relative * C:\a\b\c.txt-- C:\ -- absolute * \\server\a\b\c.txt -- \\server\ -- UNC * * Unix: * a/b/c.txt -- -- relative * /a/b/c.txt -- / -- absolute * ~/a/b/c.txt -- ~/-- current user relative * ~user/a/b/c.txt -- ~user/-- named user relative * /pre * * @param filename the filename to find the prefix in, null returns -1 * @return the length of the prefix, -1 if invalid or null */ Stephen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [io] JDiff and Clirr reports for 1.0 - 1.1 available
Objection! ;-) I believe that a number of the FilenameUtils methods still need work In particular the normalize(), catPath() and resolveFile() methods. Also the path methods need clarifying and reworking now that I've discovered a need to identify the prefix part of the filename (other thread). I wasn't going to check anything in yet, but I will now - new bits commented out. Stephen - Original Message - From: Martin Cooper [EMAIL PROTECTED] I've uploaded JDiff and Clirr reports comparing the current HEAD with Commons IO 1.0. They're available here: http://cvs.apache.org/~martinc/io/ If these look OK (they do to me), and people are happy with the current state of the code, I'd like to go ahead and start the release process for IO 1.1. Any objections, just shout. ;-) -- Martin Cooper - 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]
Re: [io] Filename prefixes
On Mon, 22 Nov 2004 01:03:28 -, Stephen Colebourne [EMAIL PROTECTED] wrote: In order to write the normalize() method properly, I realised that we have to deal with filename prefixes properly. The point being that you can't .. up into a filename prefix. Here's the javadoc for the method I'm writing. Does this cover the cases? Looks good to me. I can't think of any other options, at least for Windows and Unix. -- Martin Cooper /** * Returns the length of the filename prefix, such as codeC://code or code~//code. * p * This method will handle a file in either Unix or Windows format. * The prefix includes the first slash in the full filename. * pre * Windows: * a\b\c.txt -- -- relative * \a\b\c.txt -- \ -- drive relative * C:\a\b\c.txt-- C:\ -- absolute * \\server\a\b\c.txt -- \\server\ -- UNC * * Unix: * a/b/c.txt -- -- relative * /a/b/c.txt -- / -- absolute * ~/a/b/c.txt -- ~/-- current user relative * ~user/a/b/c.txt -- ~user/-- named user relative * /pre * * @param filename the filename to find the prefix in, null returns -1 * @return the length of the prefix, -1 if invalid or null */ Stephen - 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]
cvs commit: jakarta-commons/io/src/java/org/apache/commons/io FilenameUtils.java
scolebourne2004/11/21 17:11:56
Modified:io/src/java/org/apache/commons/io FilenameUtils.java
Log:
Add commented out implementations of prefix handling, Javadoc
Revision ChangesPath
1.26 +218 -17
jakarta-commons/io/src/java/org/apache/commons/io/FilenameUtils.java
Index: FilenameUtils.java
===
RCS file:
/home/cvs/jakarta-commons/io/src/java/org/apache/commons/io/FilenameUtils.java,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- FilenameUtils.java31 Oct 2004 04:17:34 - 1.25
+++ FilenameUtils.java22 Nov 2004 01:11:55 - 1.26
@@ -23,9 +23,10 @@
/**
* Utility class that provides methods to manipulate filenames and filepaths.
* p
- * This class defines three basic components within a filename (example
C:\dev\file.txt):
+ * This class defines four basic components within a filename (example
C:\dev\project\file.txt):
* ul
- * lithe path - C:\dev
+ * lithe prefix - C:\
+ * lithe path - dev\project
* lithe name - file.txt
* lithe extension - txt
* /ul
@@ -90,11 +91,119 @@
*/
private static final char SYSTEM_SEPARATOR = File.separatorChar;
+///**
+// * The separator character that is the opposite of the system
separator.
+// */
+//private static final char OTHER_SEPARATOR;
+//static {
+//if (SYSTEM_SEPARATOR == WINDOWS_SEPARATOR) {
+//OTHER_SEPARATOR = UNIX_SEPARATOR;
+//} else {
+//OTHER_SEPARATOR = WINDOWS_SEPARATOR;
+//}
+//}
+
/**
* Instances should NOT be constructed in standard programming.
*/
public FilenameUtils() { }
+//
//---
+///**
+// * Checks if the character is a separator.
+// *
+// * @param ch the character to check
+// * @return true if it is a separators
+// */
+//private static boolean isSeparator(char ch) {
+//return (ch == UNIX_SEPARATOR) || (ch == WINDOWS_SEPARATOR);
+//}
+//
+//
//---
+///**
+// * Normalizes a path, removing double and single dot path steps.
+// * p
+// * This method normalizes a path to a standard format.
+// * The input may contain separators in either Unix or Windows format.
+// * The output will contain separators in the format of the system.
+// * p
+// * A double slash will be merged to a single slash (thus UNC names are
not handled).
+// * A single dot path segment will be removed with no other effect.
+// * A double dot will cause that path segment and the one before to be
removed.
+// * If the double dot has no parent path segment to work with,
codenull/code
+// * is returned.
+// * pre
+// * /foo// -- /foo/
+// * /foo/./ -- /foo/
+// * /foo/../bar -- /bar
+// * /foo/../bar/ -- /bar/
+// * /foo/../bar/../baz -- /baz
+// * //foo//./bar -- /foo/bar
+// * /../ -- null
+// * ../foo -- null
+// * foo/../../bar-- null
+// * foo/../bar -- bar
+// * /pre
+// *
+// * @param path the path to normalize, null returns null
+// * @return the normalized String, or null if too many ..'s.
+// * @todo prefixes for Windows
+// */
+//public static String normalize(String path) {
+//if (path == null) {
+//return null;
+//}
+//char[] array = path.toCharArray();
+//int size = array.length;
+//// fix separators
+//for (int i = 0; i array.length; i++) {
+//if (array[i] == OTHER_SEPARATOR) {
+//array[i] = SYSTEM_SEPARATOR;
+//}
+//}
+//// adjoining slashes
+//for (int i = 1; i size; i++) {
+//if (array[i] == SYSTEM_SEPARATOR array[i - 1] ==
SYSTEM_SEPARATOR) {
+//System.arraycopy(array, i, array, i - 1, size - i);
+//size--;
+//i--;
+//}
+//}
+//// dot slash
+//for (int i = 2; i size; i++) {
+//if (array[i] == SYSTEM_SEPARATOR array[i - 1] == '.'
+//array[i - 2] == SYSTEM_SEPARATOR) {
+//System.arraycopy(array, i, array, i - 2, size - i);
+//size -=2;
+//i--;
+//}
+//}
+//// double dot slash
+//outer:
+//for (int i = 2; i size; i++) {
+//if (array[i] == SYSTEM_SEPARATOR array[i -
Re: [io] Filename prefixes
Hi, I don't have any comment on the implementation, but I'm not wild on the use of the name filename prefix. Perhaps file origin (as in a graph origin, being the point that coordinates are relative to)? Or file source? Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [io] Filename prefixes
Basically it looks like we'll need: getPrefix() - C:\ getPath() - dev\project getFullPath() - C:\dev\project getName() - file.txt getExtension() - txt (input C:\dev\project\file.txt) Normalize/catPath can then use the other methods to stitch together a result. Naming: catPath() should be renamed to concat() getFullPath()/getPath() - are these logical names? Stephen - Original Message - From: Martin Cooper [EMAIL PROTECTED] On Mon, 22 Nov 2004 01:03:28 -, Stephen Colebourne [EMAIL PROTECTED] wrote: In order to write the normalize() method properly, I realised that we have to deal with filename prefixes properly. The point being that you can't .. up into a filename prefix. Here's the javadoc for the method I'm writing. Does this cover the cases? Looks good to me. I can't think of any other options, at least for Windows and Unix. -- Martin Cooper /** * Returns the length of the filename prefix, such as codeC://code or code~//code. * p * This method will handle a file in either Unix or Windows format. * The prefix includes the first slash in the full filename. * pre * Windows: * a\b\c.txt -- -- relative * \a\b\c.txt -- \ -- drive relative * C:\a\b\c.txt-- C:\ -- absolute * \\server\a\b\c.txt -- \\server\ -- UNC * * Unix: * a/b/c.txt -- -- relative * /a/b/c.txt -- / -- absolute * ~/a/b/c.txt -- ~/-- current user relative * ~user/a/b/c.txt -- ~user/-- named user relative * /pre * * @param filename the filename to find the prefix in, null returns -1 * @return the length of the prefix, -1 if invalid or null */ Stephen - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [io] Filename prefixes
Prefix is the name used internally in the JDK File/FileSystem class. I'm not completely averse to alternatives, but I do quite like the 'prefix'. Mainly, I think thats because we are dealing with filenames here not files. Stephen - Original Message - From: Simon Kitching [EMAIL PROTECTED] I don't have any comment on the implementation, but I'm not wild on the use of the name filename prefix. Perhaps file origin (as in a graph origin, being the point that coordinates are relative to)? Or file source? Regards, Simon - 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]
Re: [io] Filename prefixes
On Mon, 22 Nov 2004 01:17:40 -, Stephen Colebourne [EMAIL PROTECTED] wrote: Basically it looks like we'll need: getPrefix() - C:\ getPath() - dev\project getFullPath() - C:\dev\project getName() - file.txt getExtension() - txt (input C:\dev\project\file.txt) Perhaps one more: getBaseName() - file Normalize/catPath can then use the other methods to stitch together a result. Naming: catPath() should be renamed to concat() That's fine. I think your earlier suggestion was merge(), but I like concat() better. ;-) getFullPath()/getPath() - are these logical names? I think getFullPath() is fine. I'm not so thrilled with getPath(), since I suspect people might expect it to do what getFullPath() does, but I don't have any good suggestions for an alternative name. I'm fine with the use of the term 'prefix', since I've seen it used elsewhere with the same meaning. -- Martin Cooper Stephen - Original Message - From: Martin Cooper [EMAIL PROTECTED] On Mon, 22 Nov 2004 01:03:28 -, Stephen Colebourne [EMAIL PROTECTED] wrote: In order to write the normalize() method properly, I realised that we have to deal with filename prefixes properly. The point being that you can't .. up into a filename prefix. Here's the javadoc for the method I'm writing. Does this cover the cases? Looks good to me. I can't think of any other options, at least for Windows and Unix. -- Martin Cooper /** * Returns the length of the filename prefix, such as codeC://code or code~//code. * p * This method will handle a file in either Unix or Windows format. * The prefix includes the first slash in the full filename. * pre * Windows: * a\b\c.txt -- -- relative * \a\b\c.txt -- \ -- drive relative * C:\a\b\c.txt-- C:\ -- absolute * \\server\a\b\c.txt -- \\server\ -- UNC * * Unix: * a/b/c.txt -- -- relative * /a/b/c.txt -- / -- absolute * ~/a/b/c.txt -- ~/-- current user relative * ~user/a/b/c.txt -- ~user/-- named user relative * /pre * * @param filename the filename to find the prefix in, null returns -1 * @return the length of the prefix, -1 if invalid or null */ Stephen - 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] - 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]
Re: [VOTE] Release Chain 1.0
+1 If the beanutils and digester dependencies are updated, it looks like commons-collections can be removed as a dependency from the project.xml file. David --- Martin Cooper [EMAIL PROTECTED] wrote: I believe Chain is now sufficiently complete and stable to warrant an official 1.0 release. There are no outstanding bug reports, and the component is already in use in a number of projects. The plan is to release HEAD as Commons Chain 1.0 on completion of a successful vote. I will be the release manager. --- [ ] +1 I support this release and am willing to help [ ] +0 I support this release but am unable to help [ ] -0 I do not support this release [ ] -1 I do not support this release, and here are my reasons --- Here is my own +1. -- Martin Cooper - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-commons/commons-build/xdocs volunteering.xml
martinc 2004/11/21 17:49:56 Modified:commons-build project.xml commons-build/xdocs volunteering.xml Log: Nagoya is going away, so use the logical names instead. Revision ChangesPath 1.35 +2 -2 jakarta-commons/commons-build/project.xml Index: project.xml === RCS file: /home/cvs/jakarta-commons/commons-build/project.xml,v retrieving revision 1.34 retrieving revision 1.35 diff -u -r1.34 -r1.35 --- project.xml 21 Nov 2004 21:26:27 - 1.34 +++ project.xml 22 Nov 2004 01:49:56 - 1.35 @@ -58,13 +58,13 @@ nameCommons Dev List/name subscribe[EMAIL PROTECTED]/subscribe unsubscribe[EMAIL PROTECTED]/unsubscribe - archivehttp://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]/archive + archivehttp://mail-archives.apache.org/eyebrowse/[EMAIL PROTECTED]/archive /mailingList mailingList nameCommons User List/name subscribe[EMAIL PROTECTED]/subscribe unsubscribe[EMAIL PROTECTED]/unsubscribe - archivehttp://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]/archive + archivehttp://mail-archives.apache.org/eyebrowse/[EMAIL PROTECTED]/archive /mailingList /mailingLists 1.3 +2 -2 jakarta-commons/commons-build/xdocs/volunteering.xml Index: volunteering.xml === RCS file: /home/cvs/jakarta-commons/commons-build/xdocs/volunteering.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- volunteering.xml 1 Mar 2004 22:31:33 - 1.2 +++ volunteering.xml 22 Nov 2004 01:49:56 - 1.3 @@ -68,7 +68,7 @@ people often get involved initially by scratching your own itch as the saying goes. -* Have you called up the bug reports gt;http://nagoya.apache.org/bugzilla/lt; +* Have you called up the bug reports gt;http://issues.apache.org/bugzilla/lt; for the Commons project, and seen any bugs that you can create a patch for? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-commons/chain project.xml
martinc 2004/11/21 17:55:12 Modified:chainproject.xml Log: Update BeanUtils and Digester versions; remove Collections dependency; update version number to 1.0-dev in anticipation of a 1.0 release soon. Revision ChangesPath 1.10 +3 -8 jakarta-commons/chain/project.xml Index: project.xml === RCS file: /home/cvs/jakarta-commons/chain/project.xml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- project.xml 29 Sep 2004 19:18:54 - 1.9 +++ project.xml 22 Nov 2004 01:55:12 - 1.10 @@ -21,7 +21,7 @@ logo/images/chain-logo-white.png/logo - currentVersion0.2-dev/currentVersion + currentVersion1.0-dev/currentVersion inceptionYear2003/inceptionYear shortDescriptionCommons Chain/shortDescription descriptionAn implmentation of the GoF Chain of Responsibility pattern/description @@ -100,17 +100,12 @@ dependency groupIdcommons-beanutils/groupId artifactIdcommons-beanutils/artifactId - version1.6/version -/dependency -dependency - groupIdcommons-collections/groupId - artifactIdcommons-collections/artifactId - version2.1/version + version1.7.0/version /dependency dependency groupIdcommons-digester/groupId artifactIdcommons-digester/artifactId - version1.5/version + version1.6/version /dependency dependency groupIdcommons-logging/groupId - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-commons/chain build.xml
martinc 2004/11/21 17:59:50
Modified:chainbuild.xml
Log:
Regenerate Ant build file to pick up changes to project.xml.
Revision ChangesPath
1.9 +164 -381 jakarta-commons/chain/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-commons/chain/build.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- build.xml 25 Feb 2004 00:01:07 - 1.8
+++ build.xml 22 Nov 2004 01:59:50 - 1.9
@@ -1,395 +1,178 @@
-!--
- Copyright 2003-2004 The Apache Software Foundation
+?xml version=1.0 encoding=UTF-8?
- Licensed under the Apache License, Version 2.0 (the License);
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
+!--build.xml generated by maven from project.xml version 1.0-dev
+ on date November 21 2004, time 1758--
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an AS IS BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
---
-project name=Chain Of Responsibility Pattern default=compile
basedir=.
-
-
-!--
-Chain of Responsibility component of the Jakarta Commons Subproject
-$Id$
---
-
-
-!-- == Initialize Properties =
--
-
-
- property file=build.properties/!-- Component local
--
- property file=../build.properties/ !-- Commons local
--
- property file=${user.home}/build.properties/ !-- User local
--
-
-
-!-- == External Dependencies =
--
-
-
- !-- The directory containing your binary distribution of JUnit,
- version 3.8.1 or later --
- property name=junit.home value=/usr/local/junit3.8.1/
-
- !-- (OPTIONAL) The directory containing your JavaServer Faces API JAR
file --
- property name=jsf-api.home
value=${user.home}/jwsdp-1.2/jsf/lib/
-
- !-- (OPTIONAL) The directory containing your Portlet API JAR file --
- property name=portlet-api.home
value=../../jakarta-jetspeed-2/portlet-api/
-
- !-- (OPTIONAL) The directory containing your Servlet API JAR file --
- property name=servlet-api.homevalue=lib/
-
-
-!-- == Derived Values
--
-
-
- !-- The pathname of the junit.jar JAR file --
- property name=junit.jar value=${junit.home}/junit.jar/
-
- !-- (OPTIONAL) The pathname of the JavaServer Faces API JAR file --
- property name=jsf-api.jar
value=${jsf-api.home}/jsf-api.jar/
-
- !-- (OPTIONAL) The pathname of the Portlet API JAR file --
- property name=portlet-api.jar
value=${portlet-api.home}/target/portlet-api-0.6.6.jar/
-
- !-- (OPTIONAL) The pathname of the Servlet API JAR file --
- property name=servlet-api.jar
value=${servlet-api.home}/servlet.jar/
-
-
-!-- == Component Declarations
--
-
-
- !-- The name of this component --
- property name=component.name value=chain/
-
- !-- The primary package name of this component --
- property name=component.package value=org.apache.commons.chain/
-
- !-- The title of this component --
- property name=component.title value=Chain Of Responsibility
Pattern/
-
- !-- The current version number of this component --
- property name=component.version value=0.1-dev/
-
- !-- The base directory for compilation targets --
- property name=build.home value=target/
-
- !-- The base directory for component configuration files --
- property name=conf.home value=src/conf/
-
- !-- The base directory for distribution targets --
- property name=dist.home value=dist/
-
- !-- The base directory for component sources --
- property name=source.home value=src/java/
-
- !-- The base directory for unit test sources --
- property name=test.home value=src/test/
-
-
-!-- == Compiler Defaults =
--
-
-
- !-- Should Java compilations set the 'debug' compiler option? --
- property name=compile.debug value=true/
-
- !-- Should Java compilations set the 'deprecation' compiler option? --
- property name=compile.deprecation value=false/
-
- !-- Should Java compilations set the 'optimize' compiler option? --
- property name=compile.optimizevalue=true/
-
-
[VOTE] Promote Resources to Commons Proper
The Resources project has been in the sandbox for quite some time, and is essentially complete and almost ready for a release. Several projects are using it already, and others are ready to pick it up once it is released. Therefore I propose that we promote Resources out of the sandbox and into Commons Proper, in preparation for a 1.0 release in the near future. --- [ ] +1 I support this proposal and am willing to help [ ] +0 I support this proposal but am unable to help [ ] -0 I do not support this proposal [ ] -1 I do not support this propsal, and here are my reasons --- Here is my own +1. -- Martin Cooper - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Promote Resources to Commons Proper
--- [X] +1 I support this proposal and am willing to help [ ] +0 I support this proposal but am unable to help [ ] -0 I do not support this proposal [ ] -1 I do not support this proposal, and here are my reasons --- -- James Mitchell Software Engineer / Open Source Evangelist EdgeTech, Inc. 678.910.8017 AIM: jmitchtx - Original Message - From: Martin Cooper [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, November 21, 2004 9:20 PM Subject: [VOTE] Promote Resources to Commons Proper The Resources project has been in the sandbox for quite some time, and is essentially complete and almost ready for a release. Several projects are using it already, and others are ready to pick it up once it is released. Therefore I propose that we promote Resources out of the sandbox and into Commons Proper, in preparation for a 1.0 release in the near future. --- [ ] +1 I support this proposal and am willing to help [ ] +0 I support this proposal but am unable to help [ ] -0 I do not support this proposal [ ] -1 I do not support this propsal, and here are my reasons --- Here is my own +1. -- Martin Cooper - 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]
Re: [VOTE] Promote Resources to Commons Proper
+1. On Sun, 21 Nov 2004 18:20:33 -0800 (PST), Martin Cooper [EMAIL PROTECTED] wrote: The Resources project has been in the sandbox for quite some time, and is essentially complete and almost ready for a release. Several projects are using it already, and others are ready to pick it up once it is released. Therefore I propose that we promote Resources out of the sandbox and into Commons Proper, in preparation for a 1.0 release in the near future. --- [ ] +1 I support this proposal and am willing to help [ ] +0 I support this proposal but am unable to help [ ] -0 I do not support this proposal [ ] -1 I do not support this propsal, and here are my reasons --- Here is my own +1. -- Martin Cooper - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-commons/jelly/xdocs changes.xml
dion2004/11/21 19:05:08 Modified:jelly/xdocs changes.xml Log: [maven-scm-plugin] prepare release 1.0-RC1 Revision ChangesPath 1.23 +1 -1 jakarta-commons/jelly/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/jakarta-commons/jelly/xdocs/changes.xml,v retrieving revision 1.22 retrieving revision 1.23 diff -u -r1.22 -r1.23 --- changes.xml 27 Oct 2004 21:57:50 - 1.22 +++ changes.xml 22 Nov 2004 03:05:07 - 1.23 @@ -24,7 +24,7 @@ author email=[EMAIL PROTECTED]dIon Gillard/author /properties body -release version=1.0-beta-5-SNAPSHOT date=in CVS +release version=1.0-RC1 date=2004-11-22 action dev=dion type=fix issue=JELLY-148 due-to=Hans GildeHuge memory leak resulting from the use of ThreadLocal./action action dev=dion type=fix issue=JELLY-138Character data is flushed by XMLOuput while XML data isn't./action action dev=dion type=updateMove to beanutils 1.7.0./action - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-commons/jelly project.xml
dion2004/11/21 19:12:56
Modified:jellyproject.xml
Log:
Put back entity that scm:prepare-release removed
Revision ChangesPath
1.154 +99 -61jakarta-commons/jelly/project.xml
Index: project.xml
===
RCS file: /home/cvs/jakarta-commons/jelly/project.xml,v
retrieving revision 1.153
retrieving revision 1.154
diff -u -r1.153 -r1.154
--- project.xml 26 Oct 2004 23:54:37 - 1.153
+++ project.xml 22 Nov 2004 03:12:56 - 1.154
@@ -18,12 +18,12 @@
See the License for the specific language governing permissions and
limitations under the License.
--
+
project
pomVersion3/pomVersion
namecommons-jelly/name
idcommons-jelly/id
- currentVersion1.0-beta-5-SNAPSHOT/currentVersion
-
+ currentVersion1.0-RC1/currentVersion
organization
nameApache Software Foundation/name
urlhttp://jakarta.apache.org/url
@@ -32,7 +32,6 @@
logo/images/logo.jpg/logo
packageorg.apache.commons.*/package
gumpRepositoryIdjakarta/gumpRepositoryId
-
inceptionYear2002/inceptionYear
packageorg.apache.commons.jelly/package
packageGroups
@@ -58,26 +57,17 @@
/packageGroup
/packageGroups
shortDescriptionCommons Jelly/shortDescription
-
- description
-Jelly is a Java and XML based scripting engine.
-Jelly combines the best ideas from JSTL, Velocity, DVSL, Ant and Cocoon
all together in a simple
-yet powerful scripting engine.
- /description
-
+ descriptionJelly is a Java and XML based scripting engine. Jelly
combines the best ideas from JSTL, Velocity, DVSL, Ant and Cocoon all together
in a simple yet powerful scripting engine./description
urlhttp://jakarta.apache.org/commons/jelly//url
issueTrackingUrlhttp://nagoya.apache.org/jira/secure/BrowseProject.jspa?id=10012/issueTrackingUrl
-
siteAddressjakarta.apache.org/siteAddress
siteDirectory/www/jakarta.apache.org/commons/${pom.artifactId.substring(8)}//siteDirectory
distributionDirectory/www/jakarta.apache.org/builds/jakarta-commons/${pom.artifactId.substring(8)}//distributionDirectory
-
repository
connectionscm:cvs:pserver:[EMAIL
PROTECTED]:/home/cvspublic:jakarta-commons/jelly/connection
developerConnectionscm:cvs:ext:[EMAIL
PROTECTED]:/home/cvs:jakarta-commons/jelly/developerConnection
urlhttp://cvs.apache.org/viewcvs/jakarta-commons/${pom.artifactId.substring(8)}//url
/repository
-
mailingLists
mailingList
nameCommons Dev List/name
@@ -92,7 +82,6 @@
archivehttp://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]/archive
/mailingList
/mailingLists
-
versions
version
id1.0-beta-1/id
@@ -104,9 +93,13 @@
name1.0-beta-4/name
tagCOMMONS-JELLY-1_0-beta-4/tag
/version
+version
+ id1.0-RC1/id
+ name1.0-RC1/name
+ tagCOMMONS_JELLY-1_0_RC1/tag
+/version
/versions
- branches/branches
-
+ branches/
developers
developer
nameJames Strachan/name
@@ -158,7 +151,7 @@
developer
namePaul Libbrecht/name
email[EMAIL PROTECTED]/email
-/developer
+/developer
developer
nameRobert Burrell Donkin/name
idrdonkin/id
@@ -167,10 +160,9 @@
developer
nameDaniel F. Savarese/name
iddfs/id
- emaildfs - apache.org/email
+ emaildfs -gt; apache.org/email
/developer
/developers
-
contributors
contributor
nameErik Fransen/name
@@ -207,7 +199,7 @@
contributor
nameOtto von Wachter/name
email[EMAIL PROTECTED]/email
- organization/organization
+ organization/
roles
roleAuthor of the tutorials/role
roleDeveloper/role
@@ -227,14 +219,14 @@
roles
roleDeveloper/role
/roles
-/contributor
+/contributor
contributor
nameJason Horman/name
email[EMAIL PROTECTED]/email
roles
roleDeveloper/role
/roles
-/contributor
+/contributor
contributor
nameTim Anderson/name
email[EMAIL PROTECTED]/email
@@ -242,107 +234,157 @@
roles
roleDeveloper/role
/roles
-/contributor
+/contributor
contributor
nameTheo Niemeijer/name
email[EMAIL PROTECTED]/email
- organization/organization
+ organization/
roles
roleDeveloper/role
/roles
-/contributor
+/contributor
contributor
nameJ. Matthew Pryor/name
email[EMAIL PROTECTED]/email
- organization/organization
+ organization/
roles
roleDeveloper/role
/roles
-
RE: [io] Filename prefixes
Stephen, What happens to getExtension() when there is no . character? Also, what is there are multiple ., are you thinking name.substring( name.lastIndexOf( . ) + 1 )? What does getPrefix() return on Unix? Nothing? Tim -Original Message- From: Stephen Colebourne [mailto:[EMAIL PROTECTED] Sent: Sunday, November 21, 2004 7:18 PM To: Jakarta Commons Developers List Subject: Re: [io] Filename prefixes Basically it looks like we'll need: getPrefix() - C:\ getPath() - dev\project getFullPath() - C:\dev\project getName() - file.txt getExtension() - txt (input C:\dev\project\file.txt) Normalize/catPath can then use the other methods to stitch together a result. Naming: catPath() should be renamed to concat() getFullPath()/getPath() - are these logical names? Stephen - Original Message - From: Martin Cooper [EMAIL PROTECTED] On Mon, 22 Nov 2004 01:03:28 -, Stephen Colebourne [EMAIL PROTECTED] wrote: In order to write the normalize() method properly, I realised that we have to deal with filename prefixes properly. The point being that you can't .. up into a filename prefix. Here's the javadoc for the method I'm writing. Does this cover the cases? Looks good to me. I can't think of any other options, at least for Windows and Unix. -- Martin Cooper /** * Returns the length of the filename prefix, such as codeC://code or code~//code. * p * This method will handle a file in either Unix or Windows format. * The prefix includes the first slash in the full filename. * pre * Windows: * a\b\c.txt -- -- relative * \a\b\c.txt -- \ -- drive relative * C:\a\b\c.txt-- C:\ -- absolute * \\server\a\b\c.txt -- \\server\ -- UNC * * Unix: * a/b/c.txt -- -- relative * /a/b/c.txt -- / -- absolute * ~/a/b/c.txt -- ~/-- current user relative * ~user/a/b/c.txt -- ~user/-- named user relative * /pre * * @param filename the filename to find the prefix in, null returns -1 * @return the length of the prefix, -1 if invalid or null */ Stephen - 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] - 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]
cvs commit: jakarta-commons/jelly project.xml
dion2004/11/21 19:26:01 Modified:jellyproject.xml Log: Fix up entity stuffup via scm:prep Revision ChangesPath 1.155 +21 -53jakarta-commons/jelly/project.xml Index: project.xml === RCS file: /home/cvs/jakarta-commons/jelly/project.xml,v retrieving revision 1.154 retrieving revision 1.155 diff -u -r1.154 -r1.155 --- project.xml 22 Nov 2004 03:12:56 - 1.154 +++ project.xml 22 Nov 2004 03:26:01 - 1.155 @@ -1,3 +1,18 @@ +!-- + Copyright 2002,2004 The Apache Software Foundation. + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +-- ?xml version=1.0 encoding=UTF-8? !DOCTYPE project [ !-- see file for description -- @@ -293,75 +308,28 @@ /contributor /contributors dependencies -!-- - Copyright 2002,2004 The Apache Software Foundation. - - Licensed under the Apache License, Version 2.0 (the License); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an AS IS BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. --- -commonDeps; + !-- the common Maven dependencies for Jelly shared by the core build and all individual taglib builds. Use this file to keep all dependency versions in sync. Does not include CLI (Command Line Interface). -- + commonDeps; -dependency - idcommons-jexl/id - version1.0/version -/dependency -dependency - idxml-apis/id - version1.0.b2/version -/dependency -dependency - idcommons-beanutils/id - version1.7.0/version -/dependency -dependency - idcommons-collections/id - version2.1/version -/dependency -dependency - idcommons-logging/id - version1.0.3/version -/dependency -dependency - iddom4j/id - version1.5/version -/dependency -dependency - idjaxen/id - version1.1-beta-2/version -/dependency -dependency - idxerces/id - version2.2.1/version -/dependency !-- for servlet support -- - dependency idservletapi/id version2.3/version /dependency -!-- for command line interface support -- +!-- for command line interface support -- dependency idcommons-cli/id version1.0/version /dependency -!-- this is brought in by the commons-cli dependency -- +!-- this is brought in by the commons-cli dependency -- dependency idcommons-lang/id version2.0/version @@ -370,15 +338,15 @@ idcommons-discovery/id version20030211.213356/version /dependency -!-- for the jelly startup scripts -- +!-- for the jelly startup scripts -- dependency idforehead/id version1.0-beta-5/version urlhttp://forehead.werken.com//url /dependency -!-- for the jstl interfaces -- +!-- for the jstl interfaces -- dependency groupIdjstl/groupId artifactIdjstl/artifactId - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-commons/jelly project.xml
dion2004/11/21 19:27:47 Modified:jellyproject.xml Log: And now my turn Revision ChangesPath 1.156 +1 -16 jakarta-commons/jelly/project.xml Index: project.xml === RCS file: /home/cvs/jakarta-commons/jelly/project.xml,v retrieving revision 1.155 retrieving revision 1.156 diff -u -r1.155 -r1.156 --- project.xml 22 Nov 2004 03:26:01 - 1.155 +++ project.xml 22 Nov 2004 03:27:47 - 1.156 @@ -1,3 +1,4 @@ +?xml version=1.0 encoding=UTF-8? !-- Copyright 2002,2004 The Apache Software Foundation. @@ -13,26 +14,10 @@ See the License for the specific language governing permissions and limitations under the License. -- -?xml version=1.0 encoding=UTF-8? !DOCTYPE project [ !-- see file for description -- !ENTITY commonDeps SYSTEM file:commonDependencies.ent ] -!-- - Copyright 2002,2004 The Apache Software Foundation. - - Licensed under the Apache License, Version 2.0 (the License); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an AS IS BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. --- project pomVersion3/pomVersion - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jelly] Building 1.0-RC1
I'm in the process of building 1.0-RC1. CVS has been tagged. We really should document this process at some point :-) -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Promote Resources to Commons Proper
+1 David --- Martin Cooper [EMAIL PROTECTED] wrote: The Resources project has been in the sandbox for quite some time, and is essentially complete and almost ready for a release. Several projects are using it already, and others are ready to pick it up once it is released. Therefore I propose that we promote Resources out of the sandbox and into Commons Proper, in preparation for a 1.0 release in the near future. --- [ ] +1 I support this proposal and am willing to help [ ] +0 I support this proposal but am unable to help [ ] -0 I do not support this proposal [ ] -1 I do not support this propsal, and here are my reasons --- Here is my own +1. -- Martin Cooper - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Chain 1.0
Before a 1.0 release, I would like to suggest an alternative Context
interface. Sorry, I realize I'm getting to the game a little late ;) I
think it is inappropriate for Context to extend from Map, because a Context
as defined in the Chain package isn't really a Map. Maps are great, but for
what the Chain package is trying to do they're probably overkill. One
testament to this fact is the incredible difficulty of implementing the
ServletWebContext class. Implementing methods like entrySet(), keySet(),
and values() are a real pain, and the implementations are all O(n)... ouch.
Below is my suggested alternative interface. It's simple by design, to make
it easy to implement.
public interface Context {
public String[] getPropertyNames() throws ContextException;
public Object get(String propertyName) throws ContextException;
public void set(String propertyName, Object propertyValue)
throws ContextException;
}
I also am concerned that the ServletWebContext class exposes too much
information that is specific to the presentation tier. Even if a business
object were to depend only on the Context interface, if a ServletWebContext
was passed in, the business object would be tied to HTTP symantics with
calls such as context.get(sessionScope.myBean.myProperty). I would
recommend a context simliar to the one available to the JST: let request
attributes be a scratchpad and let session and application items be visible
so long as they aren't blocked by a lower level.
For full javadoc on my ideas behind contexts, please see the
net.sf.morph.Context class and the net.sf.morph.context.* package. Also,
take a look at net.sf.morph.context.ServletWebContext. Here's a link to the
Morph homepage where you can access the Morph API:
http://www.crystalcognition.com/sgarlatm/morph
I'm not on SourceForge yet but I applied on Friday so hopefully I'll be
there soon!
Matt
- Original Message -
From: Martin Cooper [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, November 21, 2004 6:01 PM
Subject: [VOTE] Release Chain 1.0
I believe Chain is now sufficiently complete and stable to warrant an
official 1.0 release. There are no outstanding bug reports, and the
component is already in use in a number of projects.
The plan is to release HEAD as Commons Chain 1.0 on completion of a
successful vote. I will be the release manager.
---
[ ] +1 I support this release and am willing to help
[ ] +0 I support this release but am unable to help
[ ] -0 I do not support this release
[ ] -1 I do not support this release, and here are my reasons
---
Here is my own +1.
--
Martin Cooper
-
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]
Re: [jelly] Building 1.0-RC1
On Mon, 22 Nov 2004 14:42:53 +1100, Dion Gillard [EMAIL PROTECTED] wrote: I'm in the process of building 1.0-RC1. CVS has been tagged. We really should document this process at some point :-) Do you mean the general Commons component release process: http://jakarta.apache.org/commons/releases/index.html or something more specific to Jelly? -- Martin Cooper -- http://www.multitask.com.au/people/dion/ - 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]
Re: [VOTE] Release Chain 1.0
I disagree - Context should extend Map. I've used Chain in several
production applications and have enjoyed the methods Map brings to
Context. It makes it easy for the context to be exposed to external
applications that don't need to know any more than Map interfaces, and
therefore are not required to know about Chain at all. A good example
of this would be JXPath or JSTL tags. I have used the methods you
mention in addition to ones like putAll() - very handy for moving from
one context to another.
As for ServletWebContext, I see your point, but I'd argue that
business classes would never see the actual ServletWebContext, but
rather get passed an application-specific context, which may or may
not contain ServletWebContext. For Struts, I'm thinking we'd use an
ActionContext, which would look for objects in the scope hierarchy on
a get() as you suggest, if it detected a WebContext. Otherwise, the
value would come right out of the ActionContext. I could see the
value in bringing that scope logic to WebContext, however.
Don
On Sun, 21 Nov 2004 22:55:51 -0500, Matt Sgarlata
[EMAIL PROTECTED] wrote:
Before a 1.0 release, I would like to suggest an alternative Context
interface. Sorry, I realize I'm getting to the game a little late ;) I
think it is inappropriate for Context to extend from Map, because a Context
as defined in the Chain package isn't really a Map. Maps are great, but for
what the Chain package is trying to do they're probably overkill. One
testament to this fact is the incredible difficulty of implementing the
ServletWebContext class. Implementing methods like entrySet(), keySet(),
and values() are a real pain, and the implementations are all O(n)... ouch.
Below is my suggested alternative interface. It's simple by design, to make
it easy to implement.
public interface Context {
public String[] getPropertyNames() throws ContextException;
public Object get(String propertyName) throws ContextException;
public void set(String propertyName, Object propertyValue)
throws ContextException;
}
I also am concerned that the ServletWebContext class exposes too much
information that is specific to the presentation tier. Even if a business
object were to depend only on the Context interface, if a ServletWebContext
was passed in, the business object would be tied to HTTP symantics with
calls such as context.get(sessionScope.myBean.myProperty). I would
recommend a context simliar to the one available to the JST: let request
attributes be a scratchpad and let session and application items be visible
so long as they aren't blocked by a lower level.
For full javadoc on my ideas behind contexts, please see the
net.sf.morph.Context class and the net.sf.morph.context.* package. Also,
take a look at net.sf.morph.context.ServletWebContext. Here's a link to the
Morph homepage where you can access the Morph API:
http://www.crystalcognition.com/sgarlatm/morph
I'm not on SourceForge yet but I applied on Friday so hopefully I'll be
there soon!
Matt
- Original Message -
From: Martin Cooper [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, November 21, 2004 6:01 PM
Subject: [VOTE] Release Chain 1.0
I believe Chain is now sufficiently complete and stable to warrant an
official 1.0 release. There are no outstanding bug reports, and the
component is already in use in a number of projects.
The plan is to release HEAD as Commons Chain 1.0 on completion of a
successful vote. I will be the release manager.
---
[ ] +1 I support this release and am willing to help
[ ] +0 I support this release but am unable to help
[ ] -0 I do not support this release
[ ] -1 I do not support this release, and here are my reasons
---
Here is my own +1.
--
Martin Cooper
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Chain 1.0
+1 On Sun, 21 Nov 2004 15:01:02 -0800 (PST), Martin Cooper [EMAIL PROTECTED] wrote: I believe Chain is now sufficiently complete and stable to warrant an official 1.0 release. There are no outstanding bug reports, and the component is already in use in a number of projects. The plan is to release HEAD as Commons Chain 1.0 on completion of a successful vote. I will be the release manager. --- [ ] +1 I support this release and am willing to help [ ] +0 I support this release but am unable to help [ ] -0 I do not support this release [ ] -1 I do not support this release, and here are my reasons --- Here is my own +1. -- Martin Cooper - 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]
[jira] Created: (JELLY-166) Intermittent error with weak reference wrapper
Intermittent error with weak reference wrapper -- Key: JELLY-166 URL: http://nagoya.apache.org/jira/browse/JELLY-166 Project: jelly Type: Bug Components: core / taglib.core Versions: 1.0 Reporter: dion gillard The following happens sometimes when running tests: [junit] Testcase: testChoose(org.apache.commons.jelly.tags.junit.CaseTag$1): Caused an ERROR [junit] null:-1:-1: null Attempt to use a script that has been garbage collected. [junit] org.apache.commons.jelly.JellyTagException: null:-1:-1: null Attempt to use a script that has been garbage collected. [junit] at org.apache.commons.jelly.impl.WeakReferenceWrapperScript.script(WeakReferenceWrapperScript.java:62) [junit] at org.apache.commons.jelly.impl.WeakReferenceWrapperScript.run(WeakReferenceWrapperScript.java:74) [junit] at org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://nagoya.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jelly] Building 1.0-RC1
Jelly doesn't have an Ant build file AFAIK, which this documentation assumes. Reading through those documents, Maven's prepare/perform release cycle does every step except for PGP signing which I do manually for distribution releases but is a planned feature (and obviously the sanity checks that things ended up in a certain web server). Some newer stuff may not be setup for Jelly (like being able to use announcement:mail to mail the announcement if you are happy with what was in changes.xml). This document covers the process: http://maven.apache.org/reference/developers/releasing-plugins.html I am currently rewriting the Maven documentation and will make this a bit more general so it can be used for other Maven projects. Cheers, Brett Quoting Martin Cooper [EMAIL PROTECTED]: On Mon, 22 Nov 2004 14:42:53 +1100, Dion Gillard [EMAIL PROTECTED] wrote: I'm in the process of building 1.0-RC1. CVS has been tagged. We really should document this process at some point :-) Do you mean the general Commons component release process: http://jakarta.apache.org/commons/releases/index.html or something more specific to Jelly? -- Martin Cooper -- http://www.multitask.com.au/people/dion/ - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: jakarta-commons/jelly project.xml
Is there any reason not to modify the inheritence to remove the entity? http://maven.apache.org/faq.html#using-entities (I need to update this entry to mention that inheritence can be used as a solution). I think something like this in terms of hierarchy: commons-build/project.xml | +- jelly/shared-dependencies.xml | +- jelly/project.xml +- jelly-tags/project.xml So shared-dependencies.xml would look like: !-- LICENSE GOES HERE -- project extend../commons-build/project.xml/extend dependencies ... /dependencies /project And the other project.xml files would extend that instead of commons-build, and omit the entity. WDYT? Cheers, Brett Quoting [EMAIL PROTECTED] [EMAIL PROTECTED]: dion2004/11/21 19:12:56 Modified:jellyproject.xml Log: Put back entity that scm:prepare-release removed - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: jakarta-commons/jelly project.xml
On Mon, 22 Nov 2004 13:00:47 +0800, Brett Porter [EMAIL PROTECTED] wrote: Is there any reason not to modify the inheritence to remove the entity? Just the history of inheritance not quite working. http://maven.apache.org/faq.html#using-entities (I need to update this entry to mention that inheritence can be used as a solution). I've never understood removing the ability to use a standard XML feature. I understand why it would be discouraged, but removing seems wrong. I think something like this in terms of hierarchy: commons-build/project.xml | +- jelly/shared-dependencies.xml | +- jelly/project.xml +- jelly-tags/project.xml So shared-dependencies.xml would look like: !-- LICENSE GOES HERE -- project extend../commons-build/project.xml/extend dependencies ... /dependencies /project And the other project.xml files would extend that instead of commons-build, and omit the entity. WDYT? Sounds good. I've reverted to using 1.0.1 anyway as 1.1-SNAPSHOT of maven has issues ATM. -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32343] New: - [Validator] Javascript Rendering Extension
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32343. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32343 Summary: [Validator] Javascript Rendering Extension Product: Commons Version: unspecified Platform: All URL: http://www.niallp.pwp.blueyonder.co.uk/validatorjs.html OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Validator AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have developed an extension for Commons Validator that renders the dynamic javascript for Form validation. More details on the listed web site along with a download of the source code and a sample webapp that lets you try it out and shows you the source code. * The main component is the ScriptRenderer class which renders the necessary javascript for form validation to a StringBuffer. * Static javascript methods have more appropriate method signatures and are smaller and simpler. * fields are validated in the order defined in validation.xml (rather than by Validator) * it handles 'indexed' field validation * I've re-written the Date Validation Javascript Validator so its simpler and takes properly into account the difference between the different date patterns. * It can now provide field level validation - for example in the onchange method of a field. There are examples of all this in the sample webapp. The only word of warning - until a couple of weeks ago I knew virtually no javascript! So it would be good if someone experienced could re-view it - the sample webapp shows you the generated javascript. I would like to add this to Commons Validator, but thought I would post it fore re-view first. Niall -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Chain 1.0
This sounds like an enhancement request to me. Are you really
suggesting that Chain should not be released until your specific
enhancement is endorsed and incorporated into the component? I'm
afraid I, for one, can't sign up for that.
Suggestions for enhancements should be made on separate threads. This
thread is for a vote on whether or not to release what we have now.
--
Martin Cooper
On Sun, 21 Nov 2004 22:55:51 -0500, Matt Sgarlata
[EMAIL PROTECTED] wrote:
Before a 1.0 release, I would like to suggest an alternative Context
interface. Sorry, I realize I'm getting to the game a little late ;) I
think it is inappropriate for Context to extend from Map, because a Context
as defined in the Chain package isn't really a Map. Maps are great, but for
what the Chain package is trying to do they're probably overkill. One
testament to this fact is the incredible difficulty of implementing the
ServletWebContext class. Implementing methods like entrySet(), keySet(),
and values() are a real pain, and the implementations are all O(n)... ouch.
Below is my suggested alternative interface. It's simple by design, to make
it easy to implement.
public interface Context {
public String[] getPropertyNames() throws ContextException;
public Object get(String propertyName) throws ContextException;
public void set(String propertyName, Object propertyValue)
throws ContextException;
}
I also am concerned that the ServletWebContext class exposes too much
information that is specific to the presentation tier. Even if a business
object were to depend only on the Context interface, if a ServletWebContext
was passed in, the business object would be tied to HTTP symantics with
calls such as context.get(sessionScope.myBean.myProperty). I would
recommend a context simliar to the one available to the JST: let request
attributes be a scratchpad and let session and application items be visible
so long as they aren't blocked by a lower level.
For full javadoc on my ideas behind contexts, please see the
net.sf.morph.Context class and the net.sf.morph.context.* package. Also,
take a look at net.sf.morph.context.ServletWebContext. Here's a link to the
Morph homepage where you can access the Morph API:
http://www.crystalcognition.com/sgarlatm/morph
I'm not on SourceForge yet but I applied on Friday so hopefully I'll be
there soon!
Matt
- Original Message -
From: Martin Cooper [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, November 21, 2004 6:01 PM
Subject: [VOTE] Release Chain 1.0
I believe Chain is now sufficiently complete and stable to warrant an
official 1.0 release. There are no outstanding bug reports, and the
component is already in use in a number of projects.
The plan is to release HEAD as Commons Chain 1.0 on completion of a
successful vote. I will be the release manager.
---
[ ] +1 I support this release and am willing to help
[ ] +0 I support this release but am unable to help
[ ] -0 I do not support this release
[ ] -1 I do not support this release, and here are my reasons
---
Here is my own +1.
--
Martin Cooper
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
