Re: Checkstyle (was svn commit: r360442 [1/3] )

2006-01-18 Thread Frank W. Zammetti
AARRGGHH!! I haven't been able to get Jalopy to cooperate in the least. A big part of it is that the documentation leaves a great deal to be desired in explaining how to configure it, and naturally the GUI configuration tool, which seems to be the only method talked about anywhere, doesn't s

DO NOT REPLY [Bug 38314] - [shale] clay symbol replacement in CreateComponentCommand

2006-01-18 Thread bugzilla
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

svn commit: r370369 - in /struts/shale/trunk/clay-plugin/src: java/org/apache/shale/clay/Bundle.properties java/org/apache/shale/clay/component/chain/CreateComponentCommand.java test/org/apache/shale/

2006-01-18 Thread gvanmatre
Author: gvanmatre Date: Wed Jan 18 20:36:48 2006 New Revision: 370369 URL: http://svn.apache.org/viewcvs?rev=370369&view=rev Log: Fixed Bug#: 38314 reported by Ryan Wynn. Modified: struts/shale/trunk/clay-plugin/src/java/org/apache/shale/clay/Bundle.properties struts/shale/trunk/clay-pl

svn commit: r370367 - in /struts/shale/trunk/core-library/src: java/org/apache/shale/remoting/ java/org/apache/shale/remoting/impl/ test/org/apache/shale/remoting/ test/org/apache/shale/remoting/impl/

2006-01-18 Thread craigmcc
Author: craigmcc Date: Wed Jan 18 20:24:50 2006 New Revision: 370367 URL: http://svn.apache.org/viewcvs?rev=370367&view=rev Log: Add a helper class (XhtmlHelper) for use by renderers that want to leverage the Shale remoting facilities for accessing remote resources without having to worry about wh

svn commit: r370361 - /struts/shale/trunk/build/project.xml

2006-01-18 Thread wsmoak
Author: wsmoak Date: Wed Jan 18 20:13:22 2006 New Revision: 370361 URL: http://svn.apache.org/viewcvs?rev=370361&view=rev Log: Version 1.8 of the Maven Javadoc Plugin was released. Modified: struts/shale/trunk/build/project.xml Modified: struts/shale/trunk/build/project.xml URL: http://svn.

svn commit: r370357 - /struts/shale/trunk/xdocs/api-stability.xml

2006-01-18 Thread wsmoak
Author: wsmoak Date: Wed Jan 18 19:44:15 2006 New Revision: 370357 URL: http://svn.apache.org/viewcvs?rev=370357&view=rev Log: Fixed URLs. Modified: struts/shale/trunk/xdocs/api-stability.xml Modified: struts/shale/trunk/xdocs/api-stability.xml URL: http://svn.apache.org/viewcvs/struts/shal

DO NOT REPLY [Bug 38295] - [shale] Two web site improvements

2006-01-18 Thread bugzilla
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

svn commit: r370348 - in /struts/shale/trunk/xdocs: building.xml features-test-framework.xml

2006-01-18 Thread wsmoak
Author: wsmoak Date: Wed Jan 18 18:33:19 2006 New Revision: 370348 URL: http://svn.apache.org/viewcvs?rev=370348&view=rev Log: Improve documentation. Bug: 38295 Reported By: Dennis C. Byrne Modified: struts/shale/trunk/xdocs/building.xml struts/shale/trunk/xdocs/features-test-framework.x

DO NOT REPLY [Bug 38314] New: - [shale] clay symbol replacement in CreateComponentCommand

2006-01-18 Thread bugzilla
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

Re: Removing CGLIB enhancement from struts-action

2006-01-18 Thread David Durham
Thoughts? [0] http://issues.apache.org/bugzilla/show_bug.cgi?id=37730 Heh, maybe a custom classloader for struts apps that is aware of struts-config. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional command

Re: Non-discussion emails

2006-01-18 Thread Patrick Lightbody
James, We also agree that side conversations are no good, but that chat can be helpful. To solve this, the WebWork forums have an XMPP chat room attached to them, and each night the transcript of the chat is added to the forums: http://forums.opensymphony.com/thread.jspa?threadID=14656 I can se

Re: Checkstyle (was svn commit: r360442 [1/3] )

2006-01-18 Thread Frank W. Zammetti
Sure, I'll give it a shot. Should even be able to get to it later tonight :) -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com AIM: fzammetti Yahoo: fzammetti MSN: [EMAIL PROTECTED] On Wed, January 18, 2006 3:04 pm, Ted Husted said: > On 1/18/

Re: Revolutions (was Re: Non-discussion emails)

2006-01-18 Thread Ted Husted
On 1/18/06, Martin Cooper <[EMAIL PROTECTED]> wrote: > I may be mistaken, but AFAIK, Ted is the only person advocating the use of > Confluence. (Well, until you got here, that is. ;) He's certainly the one > who keeps bringing it up. The rest of us are happy enough to stick to the > wiki that the A

Re: Checkstyle (was svn commit: r360442 [1/3] )

2006-01-18 Thread Ted Husted
On 1/18/06, Martin Cooper <[EMAIL PROTECTED]> wrote: > I'd be much more inclined to add the Maven Jalopy plugin to an optional goal. > Then nobody has to install anything (manually). If Jalopy works for everyone, then lets just do that then. Did you want to volunteer to setup a Jalopy configurati

Re: Non-discussion emails

2006-01-18 Thread Greg Reddin
On Jan 18, 2006, at 12:49 PM, faisal abdallah wrote: It is also an un-unsubscribtion mailing list. Has anybody managed to unsubscribe from this mailing list Yes, several times using the information below. - To unsubscribe,

Re: Non-discussion emails

2006-01-18 Thread faisal abdallah
It is also an un-unsubscribtion mailing list. Has anybody managed to unsubscribe from this mailing list Greg Reddin <[EMAIL PROTECTED]> wrote: There are several things I've been thinking about as this discussion has developed. First, it is true with any craft, but especially with technology,

Re: Checkstyle (was svn commit: r360442 [1/3] )

2006-01-18 Thread Frank W. Zammetti
To me, the question comes down to do you want to put the burden of reformatting code (even if it amounts to a click of a button) on committers rather than those submitting patches? I know with JWP, I ask that anyone submitting patches follow the general coding standards the existing code uses, as

Re: Checkstyle (was svn commit: r360442 [1/3] )

2006-01-18 Thread Martin Cooper
On 1/18/06, Ted Husted <[EMAIL PROTECTED]> wrote: > > On 1/18/06, Laurie Harper <[EMAIL PROTECTED]> wrote: > > If the goal is to be able to run a tool to get checkstyle 'conformance' > > wouldn't it be better to tailer checkstyle to a tool anyone could grab, > > rather than tailoring it to what IDE

Re: Non-discussion emails

2006-01-18 Thread Greg Reddin
On Jan 18, 2006, at 12:21 PM, Laurie Harper wrote: Just to point out the obvious: directing wiki/commit/issue logs to separate lists in no way precludes having everything show up on the dev list as well. We could have dev-svn@, dev-wiki@, dev-issues@, etc plus dev-discuss@ and simply subsc

Re: Revolutions (was Re: Non-discussion emails)

2006-01-18 Thread Martin Cooper
On 1/18/06, Patrick Lightbody <[EMAIL PROTECTED]> wrote: > > Sure, that is the standard open source way. It usually works great. > > I'm just confused. I thought that everything had to be blessed, endorsed, > and signed off by the gods/lawyers/infrastructure folks of Apache. If most > of the people

Re: Checkstyle (was svn commit: r360442 [1/3] )

2006-01-18 Thread Ted Husted
On 1/18/06, Laurie Harper <[EMAIL PROTECTED]> wrote: > If the goal is to be able to run a tool to get checkstyle 'conformance' > wouldn't it be better to tailer checkstyle to a tool anyone could grab, > rather than tailoring it to what IDEA can do? Don't get me wrong, I love > IDEA and I'd be quite

Re: Non-discussion emails

2006-01-18 Thread Laurie Harper
Just to point out the obvious: directing wiki/commit/issue logs to separate lists in no way precludes having everything show up on the dev list as well. We could have dev-svn@, dev-wiki@, dev-issues@, etc plus dev-discuss@ and simply subscribe dev@ to each of those to obtain an aggregate. The

Re: J'J'JIRA (was Non-discussion emails)

2006-01-18 Thread Ted Husted
Yes, Matthew, you're right, my choce of words is unfortunate. We discussed the idea of Contigix submitting a Repsonse to the RFP, but the discussions broke down when we realized that there would not be a good match. Since you've opened the door, I'll post the last exchange I have on the thread. If

Re: Checkstyle (was svn commit: r360442 [1/3] )

2006-01-18 Thread Laurie Harper
If the goal is to be able to run a tool to get checkstyle 'conformance' wouldn't it be better to tailer checkstyle to a tool anyone could grab, rather than tailoring it to what IDEA can do? Don't get me wrong, I love IDEA and I'd be quite happy to be able to use it for this, but not everyone ha

Re: J'J'JIRA (was Non-discussion emails)

2006-01-18 Thread Matthew Porter
> Unfortunately, Contegix did not respond to the > Request for Proposal, > and another host has been recommended to the board. Ted, there seems to be a communication issue here. While we were happy to receive the RFP, the date we received it gave us a nearly no time to respond - less than 2 bus

Re: Revolutions (was Re: Non-discussion emails)

2006-01-18 Thread Ted Husted
On 1/18/06, Patrick Lightbody <[EMAIL PROTECTED]> wrote: > Sure, that is the standard open source way. It usually works great. > > I'm just confused. I thought that everything had to be blessed, endorsed, and > signed off > by the gods/lawyers/infrastructure folks of Apache. If most of the people

Re: Revolutions (was Re: Non-discussion emails)

2006-01-18 Thread Patrick Lightbody
Sure, that is the standard open source way. It usually works great. I'm just confused. I thought that everything had to be blessed, endorsed, and signed off by the gods/lawyers/infrastructure folks of Apache. If most of the people working on Struts Action prefer Confluence and JIRA, is there any

DO NOT REPLY [Bug 36054] - [struts-faces] Example 2 application does not get deployed properly.

2006-01-18 Thread bugzilla
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

Re: message style (was: Non-discussion emails)

2006-01-18 Thread Joe Germuska
At 9:10 AM -0600 1/18/06, <[EMAIL PROTECTED]> wrote: I'd just like to point out that this message, being a simple one-liner without any context quoted back, is more appropriate to a forum than to a mailinglist, where the context is more likely to get separated from the reply. I fear that, if thi

Re: svn commit: r369992 - in /struts/shale/trunk/tiger: nbproject/private/ src/java/org/apache/shale/tiger/faces/ src/test/org/apache/shale/tiger/config/ src/test/org/apache/shale/tiger/faces/

2006-01-18 Thread Gary VanMatre
>-- Original message -- >From: Craig McClanahan <[EMAIL PROTECTED]> > > On 1/17/06, Gary VanMatre wrote: > > > > >On 1/17/06, Gary VanMatre wrote: > > >> > > >> This seems like a handly utility. Clay has something similar, > > PropUtils, > > >> that uses the ConvertU

message style (was: Non-discussion emails)

2006-01-18 Thread George.Dinwiddie
I'd just like to point out that this message, being a simple one-liner without any context quoted back, is more appropriate to a forum than to a mailinglist, where the context is more likely to get separated from the reply. I fear that, if this style grows due to access via a forum, this mailing l

Re: Non-discussion emails

2006-01-18 Thread Greg Reddin
There are several things I've been thinking about as this discussion has developed. First, it is true with any craft, but especially with technology, that we must always be willing to change when better ways come along. Otherwise we stagnate and fade away. So if I would be more producti

Revolutions (was Re: Non-discussion emails)

2006-01-18 Thread Ted Husted
On 1/17/06, Patrick Lightbody <[EMAIL PROTECTED]> wrote: > * Jive Forums certainly can filter the email, and I may turn that on, but > then I've bypassed > the team rather than working with them. I don't like that approach at all. I think most of the "old-school" committers would have gone ahead