There's a STRUTS_2_0_X tag that would become Struts 2.0.8. So you could checkout that tag
$ svn co http://svn.apache.org/repos/asf/struts/struts2/branches/STRUTS_2_0_X and make the changes there. Then, create a patch and attach it to the issue. * http://struts.apache.org/helping.html#patches Later, a committer will review the patch and decide whether to apply it to the 2.0.x branch. If appropriate, we would also apply the changes to the main trunk (or "head"), which will become 2.1.0 in due course. Depending on the extent of the changes, we might ask that a Contributors License Agreement be filed with the foundation. * http://apache.org/licenses/index.html#clas HTH, Ted. On 3/23/07, Felipe Rodrigues <[EMAIL PROTECTED]> wrote:
Ok, I still got a quesiton. When working in a issue to version 2.0.8, what tag (or module) from SVN must I checkout and how proceed to commit my changes? Dave Newton-4 wrote: > > --- Felipe Rodrigues <[EMAIL PROTECTED]> > wrote: >> Can I use Eclipse as IDE and SVN client by >> Subclipse? > > Sure. > >> How to build a local version to test? > > http://cwiki.apache.org/WW/building-the-framework-from-source.html > > d.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
