Yes, just make the change to XWork and assume that CruiseControl will publish it
correctly. We have noticed that Maven isn't automatically pulling down the
latest snapshot, for some reason, so everyone else will probably need to nuke
their cached artifact. (I fail to understand the whole point of a snapshot if
maven won't check for the latest version, but oh well)
Don
tm jee wrote:
What is the standard procedure one need to take when making some modification
in XWork2 code that would affect Struts2?
In Opensymphony, while using ivy, when one made changes to xwork and commit it,
the auto-build setup by Pat will detect the changes and generate a new snapshot
of xwork (checkout form cvs, run test, if failed retry after certain period of
time etc.). One need to commit the relevant changes to WebWork as well. When
another user do a cvs update on WebWork, and run ant ivy will kick in and get
the new xwork jar.
Does it work the same way in Apache? One need to just commit relevant changes in both Xwork and
Struts2 repository. To do testing locally, we want to just nuke local repo xwork-stanpshot and do a
local "mvn install" so the new xwork is in local repo and to "mvn clean test"
on Struts2. Is this the standard way?
Thanks in advance.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
