I have needed them to use the StrutsTestCase as a parent class and not
that it was so bad, but my application doesn't have any dependencies on
Spring and I had to go add them to unit test my application. It seems
rather silly to pull in dependencies for a class or two. I would assume
we could just grab the code we need from Spring and repackage it into
Struts2 core and break that dependency completely. Then we wouldn't have
to worry about it at all.
-bp
Al Sutton wrote:
I think they only dependencies in core are used for testing.
Of the S2 apps I've written I've never used spring and not needed to
copy any spring- jars into the webapp.
Al.
----- Original Message ----- From: "Brian Pontarelli"
<[EMAIL PROTECTED]>
To: "Struts Developers List" <dev@struts.apache.org>
Sent: Tuesday, January 15, 2008 11:54 PM
Subject: Re: Spring dependancies
I'm more in favor of removing any dependencies to Spring within
struts2-core altogether. All dependencies on Spring should be moved
to the Spring plugin.
-bp
Al Sutton wrote:
I've posted a patch in JIRA to update the dependency.
I think maven based deps are the best way to handle this, and we
could try to convince the maven guys into doing some kind of
"sping-xxx-2.0" repository link which pointed to the latest 2.0.x
release :)
Al.
----- Original Message ----- From: "Brian Pontarelli"
<[EMAIL PROTECTED]>
To: "Struts Developers List" <dev@struts.apache.org>
Sent: Tuesday, January 15, 2008 4:44 PM
Subject: Re: Spring dependancies
Al Sutton wrote:
Are we going to bump the spring dependencies to 2.0.8 (or possibly
go for the 2.5 series) for S2.1?
Al.
P.S. (yup, still working on the test problem, just wondering if
it's a problem in spring-mock).
I got bit by this dependency today and I'm wondering if it makes
sense to find the exact deps and just copy them into the core
codebase to remove any dependencies on Spring. I can do this today
or tomorrow if that sounds good to everyone.
-bp
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
