Re: Jelly and a new beta release

I'm a strong +1 on this. Should we start working towards a release candidate next? What sort of new features/major issues are there outstanding? - Brett Quoting Dion Gillard <[EMAIL PROTECTED]>: > >From JIRA there is one issue remaining for beta 4 : > > http://issues.apache.org/jira/browse/JE

[jira] Commented: (JELLY-26) xml:file produces very bad output

The following comment has been added to this issue: Author: dion gillard Created: Mon, 30 Aug 2004 10:23 PM Body: Is this issue still occurring? Do you have a small test we can use? - View this comment: http://i

cvs commit: jakarta-commons/jelly/src/java/org/apache/commons/jelly/tags/core UseBeanTag.java

dion2004/08/30 22:16:16 Modified:jelly/src/java/org/apache/commons/jelly/tags/core UseBeanTag.java Log: Update comment Revision ChangesPath 1.17 +5 -5 jakarta-commons/jelly/src/java/org/apache/commons/jelly/tags/core/UseBeanTag.java

[jira] Commented: (JELLY-120) UseBean tag improvement

The following comment has been added to this issue: Author: Hans Gilde Created: Mon, 30 Aug 2004 10:01 PM Body: Thanks. I meant to add this comment to validateBeanProperties. /** If [EMAIL PROTECTED] #isIgnoreUnknownProps()} returns true, make sure that * every non-ignored (

[jira] Closed: (JELLY-98) [patch] forEach items cannot handle comma-separated String

Message: The following issue has been closed. Resolver: dion gillard Date: Mon, 30 Aug 2004 10:00 PM Applied patches with a little documentation update - View the issue: http://issues.apache.org/jira/browse/JELLY-

cvs commit: jakarta-commons/jelly/src/java/org/apache/commons/jelly/tags/core ForEachTag.java

dion2004/08/30 21:58:11 Modified:jelly/src/java/org/apache/commons/jelly/tags/core ForEachTag.java Log: Docs for Jelly-98 Revision ChangesPath 1.26 +6 -3 jakarta-commons/jelly/src/java/org/apache/commons/jelly/tags/core/ForEachTag.ja

cvs commit: jakarta-commons/jelly/xdocs changes.xml

dion2004/08/30 21:56:09 Modified:jelly/xdocs changes.xml Log: Docs for Jelly-98 Revision ChangesPath 1.8 +1 -0 jakarta-commons/jelly/xdocs/changes.xml Index: changes.xml === RCS file:

cvs commit: jakarta-commons/jelly/src/test/org/apache/commons/jelly suite.jelly

dion2004/08/30 21:55:02 Modified:jelly/src/java/org/apache/commons/jelly/expression ExpressionSupport.java jelly/src/test/org/apache/commons/jelly suite.jelly Log: Apply Jelly-98. Allow comma separated strings in forEach Revision Chang

[jira] Updated: (JELLY-98) [patch] forEach items cannot handle comma-separated String

The following issue has been updated: Updater: dion gillard (mailto:[EMAIL PROTECTED]) Date: Mon, 30 Aug 2004 9:55 PM Changes: Version changed to 1.0-beta-4 Version changed from 1.1-beta-1

[jira] Assigned: (JELLY-98) [patch] forEach items cannot handle comma-separated String

Message: The following issue has been re-assigned. Assignee: dion gillard (mailto:[EMAIL PROTECTED]) - View the issue: http://issues.apache.org/jira/browse/JELLY-98 Here is an overview of the issue: -

cvs commit: jakarta-commons/jelly/src/test/org/apache/commons/jelly suite.jelly

dion2004/08/30 21:52:30 Modified:jelly/src/test/org/apache/commons/jelly suite.jelly Log: Detab Revision ChangesPath 1.19 +6 -9 jakarta-commons/jelly/src/test/org/apache/commons/jelly/suite.jelly Index: suite.jelly ===

cvs commit: jakarta-commons/jelly/xdocs changes.xml

dion2004/08/30 21:47:20 Modified:jelly/xdocs changes.xml Log: Doc JELLY-120 Revision ChangesPath 1.7 +1 -0 jakarta-commons/jelly/xdocs/changes.xml Index: changes.xml === RCS file: /hom

Jelly and a new beta release

>From JIRA there is one issue remaining for beta 4 : http://issues.apache.org/jira/browse/JELLY-47 which seems to be a dom4j related issue. I'd like to do a new release of Jelly ASAP and start planning the next beta. If anyone has bugs they'd like fixed for the beta or *urgent* new functionali

[jira] Closed: (JELLY-120) UseBean tag improvement

Message: The following issue has been closed. Resolver: dion gillard Date: Mon, 30 Aug 2004 9:28 PM I made minor changes to the patch: - use Properties instead of Props - remove use of Jelly junit taglib, and put asserts back in the code - added license for new file

cvs commit: jakarta-commons/jelly/src/test/org/apache/commons/jelly/core testUseBeanTag.jelly

dion2004/08/30 21:27:04 Modified:jelly/src/test/org/apache/commons/jelly/core testUseBeanTag.jelly Log: JELLY-120. Allow subclasses to ignore bad properties Revision ChangesPath 1.4 +23 -2 jakarta-commons/jelly/src/test/org/apache/co

cvs commit: jakarta-commons/jelly/src/java/org/apache/commons/jelly/tags/core UseBeanTag.java

dion2004/08/30 21:26:51 Modified:jelly/src/test/org/apache/commons/jelly/core TestUseBeanTag.java jelly/src/test/org/apache/commons/jelly/core/extension CoreExtensionTagLibrary.java jelly/src/java/org/apach

[jira] Updated: (JELLY-120) UseBean tag improvement

The following issue has been updated: Updater: Hans Gilde (mailto:[EMAIL PROTECTED]) Date: Mon, 30 Aug 2004 9:15 PM Comment: Let me know if you think of more test cases. There are none with arrays or collections... Changes: Attachment changed to usebean-validate.zi

[jira] Commented: (JELLY-85) TagScript doesn't clear its cached tags after run()

The following comment has been added to this issue: Author: Hans Gilde Created: Mon, 30 Aug 2004 9:08 PM Body: See JELLY-122 for a partial fix. - View this comment: http://issues.apache.org/jira/browse/JELLY-85?p

cvs commit: jakarta-commons/commons-build/xdocs user-guides.xml

bayard 2004/08/30 21:07:35 Added: commons-build/xdocs user-guides.xml Log: aim is to have a user guides link on the front page that makes it easy to find these documents Revision ChangesPath 1.1 jakarta-commons/commons-build/xdocs/user-guides.xml

Re: [general] logging

On Tue, 31 Aug 2004, Simon Kitching wrote: > On Tue, 2004-08-31 at 13:27, Henri Yandell wrote: > > > I'll happily agree that debugging statements in code is very useful > > (despite the arguments of the IDE debuggers), but I'm unconvinced that > > released stable binaries should contain the debu

Re: [general] logging

On Tue, 31 Aug 2004 14:10:05 +1200, Simon Kitching <[EMAIL PROTECTED]> wrote: > On Tue, 2004-08-31 at 13:27, Henri Yandell wrote: > > On Thu, 26 Aug 2004, Craig McClanahan wrote: > > > > > You are asking two separate but related quesitons here, so they should > > > be addressed separately. > > > >

Re: [general] logging

On Tue, 2004-08-31 at 13:27, Henri Yandell wrote: > On Thu, 26 Aug 2004, Craig McClanahan wrote: > > > You are asking two separate but related quesitons here, so they should > > be addressed separately. > > > > (1) Should libraries depend on *any* logging library? > > > > It seems obvious to me th

[lang] Boundaries of Lang RE: [lang] Tokenizer

On Mon, 30 Aug 2004, Gary Gregory wrote: > > -Original Message- > > From: Stephen Colebourne [mailto:[EMAIL PROTECTED] > > Sent: Saturday, August 28, 2004 05:05 > > To: Jakarta Commons Developers List > > Subject: [lang] Tokenizer > > > > > > I did wonder whether it might be better to cr

Re: [general] logging

On Thu, 26 Aug 2004, Craig McClanahan wrote: > You are asking two separate but related quesitons here, so they should > be addressed separately. > > (1) Should libraries depend on *any* logging library? > > It seems obvious to me that libraries would benefit from having > logging embedded. It's

RE: [lang] Tokenizer

> -Original Message- > From: Stephen Colebourne [mailto:[EMAIL PROTECTED] > Sent: Saturday, August 28, 2004 05:05 > To: Jakarta Commons Developers List > Subject: [lang] Tokenizer > > I took a look at Tokenizer this morning and fixed some issues. Others need > some discussion... > > a) To

Re: [general] logging

On Mon, 2004-08-30 at 21:22, robert burrell donkin wrote: > i am suspect that it would be possible to use byte-code engineering to > wire up alternative implementations. the logging code wouldn't be > stripped but rather a new implementation would be wired in. of course, > the problem with this

DO NOT REPLY [Bug 30946] New: - [email] - being able to specify the port number

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

cvs commit: jakarta-commons/lang/src/java/org/apache/commons/lang SystemUtils.java

ggregory2004/08/30 14:21:18 Modified:lang/src/java/org/apache/commons/lang SystemUtils.java Log: Removed comment: // Windows XP returns 'Windows 2000' just for fun... On my machine (Windows XP Pro SP1) the os.name property is "Windows XP". Revision ChangesPath 1.3

cvs commit: jakarta-commons/lang/src/java/org/apache/commons/lang SystemUtils.java

ggregory2004/08/30 14:19:52 Modified:lang/src/java/org/apache/commons/lang SystemUtils.java Log: Refactor "Windows" into private static final String OS_NAME_WINDOWS_PREFIX = "Windows"; Revision ChangesPath 1.34 +13 -8 jakarta-commons/lang/src/java/org/apache/co

RE: [Sandbox/Email] nightly builds

> Great! Thanks for volunteering your time and machine! +1 -Matze - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Sandbox/Email] nightly builds

No ... I missed the fact that the fixed version had actually been checked in. The "email" package will be in tonight's nightly builds. Great! Thanks for volunteering your time and machine! Joe -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "In fact, when I die, if I d

cvs commit: jakarta-commons/digester RELEASE-NOTES.txt

rdonkin 2004/08/30 01:01:47 Modified:digester Tag: RELEASE_DIGESTER_1_6_0_BRANCH RELEASE-NOTES.txt Log: Improved release notes Revision ChangesPath No revision No revision 1.13.2.2 +3 -2 jakarta-commons

cvs commit: jakarta-commons/digester build.xml project.xml

rdonkin 2004/08/30 00:52:02 Modified:digester Tag: RELEASE_DIGESTER_1_6_0_BRANCH build.xml project.xml Log: Release candidate 2 Revision ChangesPath No revision No revision 1.53.2.5 +2 -2 jakarta-common

Re: [digester] release candidate digester 1.6RC1 now available

On 28 Aug 2004, at 11:18, Simon Kitching wrote: 4. The "commons-digester-1.6.0RC1-src.zip" file contains files with unix line terminators. Isn't the convention that the .tgz files contain unix format (LF) files, and the .zip files contain dos (CRLF)? the way i've always cut releases is that the o

Re: [digester] release candidate digester 1.6RC1 now available

hi simon thanks for taking a look at release candidate and for catching all those things! i think that i've addressed all except 4 (which may need a little bit of talking about which i'll kick off in a separate email). i'm probably going to go ahead and roll another release candidate sometime s