I have attempted to take into account all of the feedback which has been
provided for the tiles graduation proposal and have documented it on the
Wiki. I've attempted to do so in an unbiased fashion and encourage you
to update any sections you feel need to be modified.
At this point, it
http://cwiki.apache.org/confluence/display/S2WIKI/Tiles2+Graduation+Proposal
David H. DeWolf wrote:
I have attempted to take into account all of the feedback which has been
provided for the tiles graduation proposal and have documented it on the
Wiki. I've attempted to do so in an unbiased
I've made some changes and now instead of specifying the number of items
to be displayed in the dropdown, the absolute height can be specified,
so there is no flash, do you think it would be better this way?
musachy
Ted Husted wrote:
Thanks, Musachy. I'm applying it now.
-Ted.
On 11/25/06,
Dear committers,
I would like to propose branching HEAD because of forthcoming locale
resolution strategy. I am still working on s1 with the focus of bringing
S1 to a full set of customizable internationalization capabilities.
Because the locale resolution is more powerful and may behave
In working out the tests, it seemed like
* we should only scan the classes of actions that invoke execute, so
that we don't create aliases for aliases
* we should ignore get methods, since these would not be meant as actions.
I thought there was a list of methods that we didn't execute, like
On 11/25/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Greetings --
Do you guys think it would be useful to provide an Eclipse workspace for
those who would like to easily see what Struts2 is all about?
I believe Maven will build an Eclipse setup using the plugin.
$ mvn eclipse:eclipse
I
My best suggestion would be to tag and roll a 1.3.6 build now, before
getting into a new line of development. Creating a branch would then
be less important.
If we did create a branch, we should give it a name (like i18n). Then,
if we find the changes joyful, the branch can be merged back into
On 11/26/06, Ted Husted [EMAIL PROTECTED] wrote:
My best suggestion would be to tag and roll a 1.3.6 build now, before
getting into a new line of development. Creating a branch would then
be less important.
I think a 1.3.6 release goes in the 'would be nice' column. There
were a few fixes,
try {
proplist.add(new PropertyDescriptor(disabled,
ELTextTag.class,
null, setDisabledExpr));
} catch (IntrospectionException ex) {
}
For some reason, the ELFormTag is referencing ELTextTag to set the
disabled attribute. It looks clearly
On 11/27/06, Paul Benedict [EMAIL PROTECTED] wrote:
try {
proplist.add(new PropertyDescriptor(disabled,
ELTextTag.class,
null, setDisabledExpr));
} catch (IntrospectionException ex) {
}
For some reason, the ELFormTag is referencing
10 matches
Mail list logo