And throwing support for JDK 1.4, there are still some parts about that in poms
Kind regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Kapituła Javarsovia http://javarsovia.pl
-
To unsubscribe, e-mail: dev-unsubscr..
Hi,
I also like the idea to extract the View from the Core to external
plugins - jsp, velocity, freemarker. Then the Core can be merged with
Xwork and play the role of an universal Controller. Right now, when
you're using REST plugin, JSP is included in your project anyway.
Kind regards
--
Łuka
(Sorry, this was in my drafts from a couple of days ago.)
2011/2/1 Jordi Fernández Wrote:
> How can we cooridinate efforts effectively?
Maybe via JIRA tickets, with some over-arching tickets that we can add
dependencies to as we refine the tasks? Is that too complicated?
My hit lists:
* S2.0 wi
Since the discussion is pretty quiet, I'll toss out a few more questions. (I
don't have any good answers, since I'm pretty new here :)
1) Not huge uptake due to plethora of options--can't reduce the number of
options, but can make S2 more appealing.
Agreed. Options are good :)
I'm not intimat
I agree. This is a discussion needed to determine short-, medium and
long term goals. If we agree priorities can be more effective at the
time we spend. Right now my colleague Albert and I are still working
on improving and expanding the capabilities of the REST plugin to easy
the creation of hyper
On Tue, Feb 1, 2011 at 11:36 AM, John Lindal wrote:
> Why do you consider its position precarious? Stability is good in the corp
> world :)
>
Precarious in that:
1) Not huge uptake due to plethora of options--can't reduce the number of
options, but can make S2 more appealing.
2) Some plugins ar
It sounds like a good discussion to have.
Why do you consider its position precarious? Stability is good in the corp
world :)
John
On 2/1/11 8:32 AM, "Dave Newton" wrote:
I don't recall the original reason for the shading anymore.
Part of it was wrapped up in a discussion about removing XW
I don't recall the original reason for the shading anymore.
Part of it was wrapped up in a discussion about removing XW functionality
that dupes Commons stuff, which never really got started on.
There are some corners that really need some dusting--I think S2 is in kind
of a precarious position r
The reason I don't think io needs to be shaded is because io was never
actually shaded. Lang was being shaded into io, which can't possibly be right.
>
> -
> org.apache.commons.lang
> +org.a
John,
I didn't follow the asm's matter, but as I said a couple of days ago
[1] struts-core already depends on commons-io library (actually is a
fileupload's dependency), so there cannot be a struts application
without common-io library along its path.
[1] https://issues.apache.org/jira/browse/WW-3
In regards to this ticket:
https://issues.apache.org/jira/browse/XW-388
Nothing in the entire Struts2 code base references either
org.apache.commons.io.xwork or org.objectweb.asm.xwork. I assume these
relocations were intended to be for internal use only? If so, we could
significantly redu
11 matches
Mail list logo
