o generate a .war file for my Struts 2 project that would
> load correctly in my Tomcat 6 server.
>
> Bruce
>
> --
> View this message in context:
> http://www.nabble.com/xWork-2.1.3-available-yet-that-fixes-problem-with-Struts-2.1.6--tp22027436p22036485.html
> Sent from the
y Struts 2 project that would
load correctly in my Tomcat 6 server.
Bruce
--
View this message in context:
http://www.nabble.com/xWork-2.1.3-available-yet-that-fixes-problem-with-Struts-2.1.6--tp22027436p22036485.html
Sent from the Struts - User mailing list archive at
On Sunday 15 February 2009 18:34:05 phillips1021 wrote:
> Dave and Wes - Thank you both for the replies.
>
> We can exclude the xWork 2.1.2 jar dependency from Struts 2.1.6 in our
> pom.xml file for our projects as Wes suggests. However, it doesn't appear
> that xWork 2.1.3 jar is available in the
phony
xwork
2.1.3
compile
Bruce
--
View this message in context:
http://www.nabble.com/xWork-2.1.3-available-yet-that-fixes-problem-with-Struts-2.1.6--tp22027436p22029251.html
Sent from the Struts - User mailing list archive at Nabbl
On Sunday 15 February 2009 18:02:17 Dave Newton wrote:
> phillips1021 wrote:
> > Since we use Maven to manage our dependencies our projects using Struts
> > 2.1.6 automatically receive xWork-2.1.2.
>
> Does declaring your own dependency for XWork (not xWork) 2.1.3 work, or
> does it just retrieve
phillips1021 wrote:
Since we use Maven to manage our dependencies our projects using Struts
2.1.6 automatically receive xWork-2.1.2.
Does declaring your own dependency for XWork (not xWork) 2.1.3 work, or
does it just retrieve both?
Does anyone know when xWork-2.1.3 will be available and w
and when Struts 2.1.6's
pom will be updated to use it?
We have halted our upgrade to Struts 2.1.6 because of this issue.
Bruce
--
View this message in context:
http://www.nabble.com/xWork-2.1.3-available-yet-that-fixes-problem-with-Struts-2.1.6--tp22027436p22027436.html
Sent from the S
7 matches
Mail list logo
