Greg Reddin ha scritto:
On 12/29/06, Stone, Sam <[EMAIL PROTECTED]> wrote:
Is this the appropriate mailing list for questions about the Tiles 2
sandbox project?
For now yes. Tiles will soon have its own top-level project and when
that
happens you can ask questions there. But it will lik
Stone, Sam ha scritto:
Am getting "ServletException while including page" (see EX. 1 below).
How can I get more specific information?
My insert looks as follows:
...
org.apache.tiles.taglib.ContainerTagSupport TRAS0014I: The following
exception was logged org.apache.tiles.TilesException: Ser
Stone, Sam ha scritto:
Using the API from Sep 2006 I was able to access externally an attribute
from a tiles definition as follows:
String sTilesDefName = (String) request.getAttribute("tile_name");
TilesContext tilesContext = new
ServletTilesContext(session.getServletContext(), request, respons
On 12/30/06, Ted Husted <[EMAIL PROTECTED]> wrote:
OK, I'll get ready to roll another release then.
I've updated the release notes with the latest changes, and I'm
preparing to tag and roll Struts 2.0.2 against XWork 2.0 RC 1.
-Ted.
On 12/31/06, Ted Husted <[EMAIL PROTECTED]> wrote:
On 12/30/06, Ted Husted <[EMAIL PROTECTED]> wrote:
> OK, I'll get ready to roll another release then.
I've updated the release notes with the latest changes, and I'm
preparing to tag and roll Struts 2.0.2 against XWork 2.0 RC 1.
Just FYI, the
I looked again at a clean checkout and found the reference. The
assembly POM in my usual working copy was missing the XWork stanza.
I'm not sure when I did that or why.
The other thing is why do we get the
Embedded error:
C:\projects\Apache\struts2-clean\assembly\..\target\site isn't a
directory
On 12/31/06, Ted Husted <[EMAIL PROTECTED]> wrote:
I looked again at a clean checkout and found the reference. The
assembly POM in my usual working copy was missing the XWork stanza.
I'm not sure when I did that or why.
The other thing is why do we get the
Embedded error:
C:\projects\Apache\str
I can't even find the XWork reference in the POM assembly. :)
Why don't you go ahead and fix the parent POM, and then we'll tag it.
-Ted.
On 12/31/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 12/31/06, Ted Husted <[EMAIL PROTECTED]> wrote:
> On 12/30/06, Ted Husted <[EMAIL PROTECTED]> wrote:
I was leaving "site" out. Thanks!
-Ted.
On 12/31/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 12/31/06, Ted Husted <[EMAIL PROTECTED]> wrote:
> I looked again at a clean checkout and found the reference. The
> assembly POM in my usual working copy was missing the XWork stanza.
> I'm not sure w
Antonio
Did you ever get to put the eclipse formatter on the wiki?
thanks
musachy
Antonio Petrelli wrote:
Ted Husted ha scritto:
* http://struts.apache.org/releases.html#Coding
In practice, we would like the code to pass our Checkstyle
configuration.
* http://svn.apache.org/viewvc/struts/
On 12/31/06, Ted Husted <[EMAIL PROTECTED]> wrote:
I was leaving "site" out. Thanks!
I'm having trouble with 'mvn install -Pall' (svn trunk, with the
version set at 2.0.2.)
The struts-all build is failing because it can't find
'struts2-config-browser-plugin'. To make it work, I dropped into
Yes, we decided that a combined struts-all.jar wasn't useful.
From clean checkout against a clean repository, I had to install the
plugins first, and then run the usual assembly commands, same as you.
I added a note to the wiki page.
-Ted.
On 12/31/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
For now, I'll just delete it from the library before I sign it, to
avoid confusion. Then, we can take it out all together for Struts
2.0.3.
-Ted.
On 12/31/06, Ted Husted <[EMAIL PROTECTED]> wrote:
Yes, we decided that a combined struts-all.jar wasn't useful.
From clean checkout against a clean
That's the wonderful or terrible thing about successful OSS projects,
you are kidding yourself if you think even 5% of the users are even
on a mailing list, much less that they will read every post.
--
James Mitchell
678.910.8017
On Dec 29, 2006, at 8:09 AM, Ian Roughley wrote:
If we go
WW-1583 was closed, but I don't see the change on svn head.
regards
musachy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Doh, I applied against the wrong ComboBox.js. Should be fixed in head.
Don
Musachy Barroso wrote:
WW-1583 was closed, but I don't see the change on svn head.
regards
musachy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For ad
I was mentioning the other day that we should probably remove
"datepicker" and "timepicker" from struts-tags.tld and the two links in
showcase, given that they are not fully functional yet (these are not
the dropdowns, they are new). Is it ok to keep them for the build even
if they are not work
This reminds me - what about moving all the ajax tags to a plugin for
2.0.3? I think the ajax tags are in the most flux and generate the most
questions on the email list. By moving them to a plugin, we could be
closer to a GA release in core yet give the tags somewhere to breath. I
added sup
The test builds are signed and uploaded
* http://people.apache.org/builds/struts/2.0.2/
but I wasn't able to get the deploy steps (7,10) to work
* http://struts.apache.org/2.x/docs/creating-and-signing-a-distribution.html
There's a problem withy my private key on p.a.o, and so I have to
enter
Don Brown wrote:
This reminds me - what about moving all the ajax tags to a plugin for
2.0.3?
Now I'm confused :), weren't you working on this already?
musachy
I think the ajax tags are in the most flux and generate the most
questions on the email list. By moving them to a plugin, we could
There are still several broken examples and tags., which I listed on
the Showcase index page, in the hope that they still might be fixed
for Struts 2.0.3
Since Struts 2.0.2 uses XWork RC 1 as a dependency, it's doomed to
beta, and we will have to do another build or two regardless.
-Ted.
On 12/
On 12/31/06, Musachy Barroso <[EMAIL PROTECTED]> wrote:
Don Brown wrote:
> This reminds me - what about moving all the ajax tags to a plugin for
> 2.0.3?
Now I'm confused :), weren't you working on this already?
Yes, but we were also talking about branching and doing that in Struts 2.1.0.
-Ted
Oh that's true. Enough for this year. Happy new year every one!
musachy
Ted Husted wrote:
On 12/31/06, Musachy Barroso <[EMAIL PROTECTED]> wrote:
Don Brown wrote:
> This reminds me - what about moving all the ajax tags to a plugin for
> 2.0.3?
Now I'm confused :), weren't you working on this a
The basic idea is to get rid of the "ajax" theme, and create a
dojo-specific tag library. Therefore, we'd keep certain ajax features
like client-side validation in the main tags, but move dojo-specific
tags like div, date picker, anchor, etc out into their own tag library.
IMO, basing a tag l
As it stands, XWork is a "stealth" project using a beta/rc release system.
Working with XWork from Struts is problematic because
* There are no visible mailing lists that track project status
* There are no forums in which to discuss XWork 2 specific issues,
including the release roadmap and th
+1
On 12/31/06, Don Brown <[EMAIL PROTECTED]> wrote:
The basic idea is to get rid of the "ajax" theme, and create a
dojo-specific tag library. Therefore, we'd keep certain ajax features
like client-side validation in the main tags, but move dojo-specific
tags like div, date picker, anchor, etc
At one point wasn't there talk of bring xwork into the apache fold. Is
that still an option or is that off the table? It seems to me that
since xwork is such a critical piece of struts2 that it should be part
of apache and not opensymphony. Then xwork would be forced to follow
the apache pro
That should work just fine. What kind of error do you get? What happens when
you do:
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=55942&messageID=111476#111476
--
Ted,
Making XWork a more "public" project is not a problem - we just hadn't done so
up until now due to no need.
As for the names of the releases (RC, beta, 2.0.1.1.1.1, whatever you
want...)... that is really easy to fix: just ask Rainer or whoever is doing the
release :) OpenSymphony doesn't
+1
I think in general the concept of "themes" for the AJAX stuff was a mistake.
Instead, let's do stuff like:
And make those tags part of an external plugin. That way we don't make
migration from WebWork impossible, but we also fix a mistake we made with
WebWork by trying to stuff too much f
Ted,
Your suggestions all sound very reasonable. Rainer and I would be happy to help
set this up (I can do the forums/infrastructure, and I'm sure Rainer can help
by giving releases more compatible version numbers in the future).
---
As a first follow up, happy new year to everyone.
As Pat mentioned, the infrastructure at OpenSymphony does not have the
rules and bounds Apache has.
I have no problem to release milestones, dot releases or the like, but I
want to achieve that certain issues are fixed and targets were reached for
32 matches
Mail list logo
