Please post questions about using Struts to the Struts Users list only.
The Struts Dev list is for discussing the development and enhancement of
Struts itself.
http://struts.apache.org/mail.html
L.
Radha Krishna wrote:
Hi,
i am working on indexed,nested properties. i have following
Do we have to put the license header on .ftl files? Some of the
examples on the doc will look weird as the header is way bigger than
the actual code:
http://cwiki.apache.org/confluence/display/WW/ajax+theme
musachy
--
Hey you! Would you help me to carry the stone? Pink Floyd
We can create a build without moving to a release. I'd really like to
tap the keg on 2.1.x.
Another issue we should address is our reliance on Rainer and me as
release managers. It's simply not acceptable for either project to
grind to a halt because a single volunteer is on vacation.
If the
On 10/1/07, Ted Husted [EMAIL PROTECTED] wrote:
We can create a build without moving to a release. I'd really like to
tap the keg on 2.1.x.
There was some talk of using the Maven Release Plugin for Struts 2.1,
did that get worked out?
Keep in mind that the release plugin will not let you
2007/10/1, Wendy Smoak [EMAIL PROTECTED]:
On 10/1/07, Ted Husted [EMAIL PROTECTED] wrote:
We can create a build without moving to a release. I'd really like to
tap the keg on 2.1.x.
There was some talk of using the Maven Release Plugin for Struts 2.1,
did that get worked out?
I think
2007/10/1, Musachy Barroso [EMAIL PROTECTED]:
Do we have to put the license header on .ftl files?
From a legal POV, I suppose (and afraid) that it is necessary, since FTL
files are creative works. See:
http://www.apache.org/legal/src-headers.html#faq-exceptions
Some of the
examples on the
Is it only a question of appearance of the code itself, or do you experience
rendering problems too? In the first case, why don't you leave only the
interesting part of the code in the wiki pages?
No rendering problem, it just looks ugly. I just wanted to make sure
we had to before using just
I'm happy with a hybrid mix of XML and annotations; however something
feels very
wrong about using the package-info.java file for holding the XWork
package level
annotations, so I'm trying to think of alternatives.
I can understand the difficultly in using a new language concept that
has
+1 GA
On 9/24/07, James Holmes [EMAIL PROTECTED] wrote:
The Struts 2.0.11 test build is now available.
Release notes:
* http://struts.apache.org/2.x/docs/release-notes-2011.html
Distribution:
* http://people.apache.org/builds/struts/2.0.11/
Maven 2 staging repository:
*
+1 GA
cheers,
Rainer
The Struts 2.0.11 test build is now available.
Release notes:
* http://struts.apache.org/2.x/docs/release-notes-2011.html
Distribution:
* http://people.apache.org/builds/struts/2.0.11/
Maven 2 staging repository:
*
Don is busy with some important refactorings and enhancements for XWork 2.1.
But I think that until these already commited changes are fully tested and
stabilized, no xwork 2.1 release will happen.
There are some other open xwork issues, that need to be addressed prior to
a release.
cheers,
I'm pretty much done, actually. The only other major thing I was
considering, but probably won't get to, was removing commons-logging.
I'll try to spend some time to help close out 2.1 issues.
Don
On 10/2/07, Rainer Hermanns [EMAIL PROTECTED] wrote:
Don is busy with some important
12 matches
Mail list logo
