hello,
shale has a lot of new features:
View Controller: Backing bean for JSP with predefined events
Validations: Client- and service-side validations
JNDI: JSP access to properties in web.xml
Dialog Manager: Web wizards (workflows) driven by XML configuration files
Application Manager: An
On 6/15/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: craigmcc
Date: Thu Jun 15 00:24:49 2006
New Revision: 414495
URL: http://svn.apache.org/viewvc?rev=414495view=rev
Log:
Include the binary JAR files for Shale in the assembly. FIXME - why
does the dependencySets element work in
On Thu, June 15, 2006 6:35 am, Ted Husted wrote:
In the meantime, that would give Frank time to work on those patches.
So you don't want to wait for GA now? That's fine with me... I'm not sure
I can take care of all the complaints by July, but I should be able to get
rid of enough of them to
I was working on a bug for a project using struts 1.2.9 involving
internationalization and one of our subclasses of LookupDispatchAction.
The bug initially seemed to be straightforward because we were getting
exceptions with a familiar stacktrace that read something like,
missing resource in
On 6/15/06, John Sanda [EMAIL PROTECTED] wrote:
I was working on a bug for a project using struts 1.2.9 involving
internationalization and one of our subclasses of LookupDispatchAction.
The bug initially seemed to be straightforward because we were getting
exceptions with a familiar stacktrace
On 6/15/06, Frank W. Zammetti [EMAIL PROTECTED] wrote:
On Thu, June 15, 2006 6:35 am, Ted Husted wrote:
In the meantime, that would give Frank time to work on those patches.
So you don't want to wait for GA now? That's fine with me... I'm not sure
I can take care of all the complaints by
Niall Pemberton wrote:
On 6/15/06, John Sanda [EMAIL PROTECTED] wrote:
I was working on a bug for a project using struts 1.2.9 involving
internationalization and one of our subclasses of LookupDispatchAction.
The bug initially seemed to be straightforward because we were getting
exceptions
Ok, cool Niall... I guess we maybe need to decide what the wait point
really is here... do we want to wait for GA before I generate these
patches, or just the next release? At first I thought Ted was saying
let's wait for GA, but then it sounded like maybe just wait for 1.3.5
(which may or may
The problem is patches. People will tend to write patches against
whatever version they are using. If we make a lot of changes right
after a popular release, then a lot of the patches people submit back
won't work. The ideal time for broad refactorings is at the beginning
of a minor series (pre
Ok, my head is spinning :)
I like simple, so, I'll say the same thing I remember saying months ago...
just ping me when the time is right to deal with Checkstyle complaints,
and so long as I still have some free time then, I'll do it.
You have someone willing to do the work, I'll let you worry
You might at least want to start those discussions about the
checkstyle settings, so that we can develop a strategy about how they
would be fixed the next time there is a window of opportunity.
When I did a a time study in February, curing the the current errors
with the current settings would
[moved to dev list]
On 6/15/06, Gary VanMatre [EMAIL PROTECTED] wrote:
My second attempt was to add the cargo.jvmarg to the /shale-apps pom.xml:
What did you do after that? If you didn't 'mvn install -N' that pom,
it may not have taken effect. (It's supposed to look for ../pom.xml
for the
On 6/15/06, stephan opitz [EMAIL PROTECTED] wrote:
hello,
shale has a lot of new features:
View Controller: Backing bean for JSP with predefined events
Validations: Client- and service-side validations
JNDI: JSP access to properties in web.xml
Dialog Manager: Web wizards (workflows) driven by
From: Craig McClanahan [EMAIL PROTECTED]
On 6/15/06, stephan opitz wrote:
hello,
shale has a lot of new features:
View Controller: Backing bean for JSP with predefined events
Validations: Client- and service-side validations
JNDI: JSP access to properties in web.xml
Thanks to incredible support from Wendy, James, Gary, et. al., it looks like
we've got a viable organization of the repository for Shale in the
mvn_reorg branch. There's work to be done yet on the generated website,
but the basic architecture seems sound. But there is one more thing I'd
like to
Ted Husted wrote:
You might at least want to start those discussions about the
checkstyle settings, so that we can develop a strategy about how they
would be fixed the next time there is a window of opportunity.
Fair enough...
I saw two issues that seem to account for a large number of the
On 6/15/06, Craig McClanahan [EMAIL PROTECTED] wrote:
An interesting question is how we make it possible to do step 4 (build the
sample apps from source) without doing step 2 (build the framework from
source). I presume that means we'd need to publish the shale-parent and
shale-apps-parent
On 6/15/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 6/15/06, Craig McClanahan [EMAIL PROTECTED] wrote:
An interesting question is how we make it possible to do step 4 (build
the
sample apps from source) without doing step 2 (build the framework from
source). I presume that means we'd need
On 6/15/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 6/15/06, Craig McClanahan [EMAIL PROTECTED] wrote:
I deployed the framework JARs (and shale-parent POM) ... but it's still
missing the shale-apps-parent POM. Can I deploy just that without
deploying
the applications themseves? That would
On 6/15/06, Craig McClanahan [EMAIL PROTECTED] wrote:
That did it. Thanks.
Except for the file permissions... when you have a minute, can you log
in and fix them?
And if anyone knows how to convince it to set the group writeable bit
when you scp files up, I'd love to know.
(Yes, my umask
20 matches
Mail list logo
