To follow up on this:
We have two snippet variables for XWork setup:
"com.opensymphony.xwork2.", which is now pointing to the new location, so pages using this should be ok now. "xwork2/", which is unfortunately the url most pages seem to use, simply is a pointer to the WX trunk http://svn.opensymphony.com/svn/xwork/trunk/, and pages using this do address the code directly from there. On the http://cwiki.apache.org/confluence/display/WW/Validation page, there were e.g. urls like xwork2/src/java/com/opensymphony/xwork2/validator/ValidatorFactory.java which is bad with the new XWork code structure. To see if it's working, I replaced those references on the validation page with the "com.opensymphony.xwork2." variable, which works as expected -> com.opensymphony.xwork2.validator/ValidatorFactory.java It's not only easier to write, but also independent from the actual source structure to use this variable. So I think the way to go would be eliminate the use of the "xwork2" variable by the export/grep procedure Musachy mentioned and replace it with the "com.opensymphony.xwork2." variable like described above.

Dave Newton schrieb:
Musachy Barroso wrote:
Force an export, or export from the confluence admin page. and then
grep the pages for svn.opensymphony. We could also change the xwork
variable to make it point to a branch/tag before the changes.

Rene said we can just re-base the snippet plugin (I don't think I have access rights to do that anyway).

Dave

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


--
René Gielen
IT-Neering.net
Saarstrasse 100, 52062 Aachen, Germany
Tel: +49-(0)241-4010770
Fax: +49-(0)241-4010771
http://twitter.com/rgielen

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to