On Mon, 8 Nov 2004 11:50:43 -0800, Don Brown <[EMAIL PROTECTED]> wrote:
>
>
> I'm not sure what you mean and how refactoring is enhanced by using one
> trunk. I'm just suggesting giving each subproject its own structure, but
> they would all be in the same repository, and could be all checked out at
> one shot by checking out struts/
I'm not saying that it is enhanced - rather, I'm asking the question. ;-)
What I'm getting at is this. Say I'm working on 'faces' and I come
across a class that really should be part of 'core' instead. Can I
still use the regular SVN move mechanism to move the class over,
keeping history, etc., when 'core' and 'faces' have separate trunk /
branches / tags?
boolean martin_happy = (answer.equals("yes")); // ;-)
--
Martin Cooper
> Don
>
> On Sun, 7 Nov 2004 10:03:27 -0800, Martin Cooper <[EMAIL PROTECTED]> wrote:
> > One of the initial reasons for having one trunk / branches / tags
> > group, rather than several, was the desire to be able to refactor
> > across artifacts. If that is still retained with the proposal below,
> > then I'm fine with it. Otherwise, I think we need to consider it a bit
> > more.
> >
> > --
> > Martin Cooper
> >
> >
> >
> >
> > On Fri, 05 Nov 2004 15:26:45 -0800, Don Brown <[EMAIL PROTECTED]> wrote:
> > > In a perfect world...
> > >
> > > svn.apache.org/asf/struts
> > > /core
> > > /trunk
> > > /branches
> > > /tags
> > > /faces
> > > /trunk
> > > /branches
> > > /tags
> > > /bsf
> > > /trunk
> > > /branches
> > > /tags
> > > /flow
> > > /trunk
> > > /branches
> > > /tags
> > >
> > > Therefore, we would then instruct folks that want to work on Struts core
> > > to use http://svn.apache.org/asf/struts/core/trunk
> > >
> > > Don
> > >
> > >
> > >
> > >
> > > Craig McClanahan wrote:
> > >
> > > >On Fri, 5 Nov 2004 08:01:33 -0800, Don Brown <[EMAIL PROTECTED]> wrote:
> > > >
> > > >
> > > >>No, actually, it would be a simple matter of a couple of "svn move"
> > > >>commands. They are quick, and can be easily redone later if we change
> > > >>our minds.
> > > >>
> > > >>
> > > >
> > > >Agree that it's easy to move things around ... but I've got a question
> > > >-- does this still all end up under our single canonical SVN URL
> > > >(https://svn.apache.org/asf/struts)?
> > > >
> > > >If so, I'm fine with it ... once we figure out what to name the top
> > > >level directories of course :-).
> > > >
> > > >
> > > >
> > > >>Don
> > > >>
> > > >>
> > > >
> > > >Craig
> > > >
> > > >
> > > >
> > > >>
> > > >>
> > > >>On Fri, 5 Nov 2004 07:42:44 -0600, Joe Germuska <[EMAIL PROTECTED]>
> > > >>wrote:
> > > >>
> > > >>
> > > >>>At 9:52 PM -0800 11/4/04, Don Brown wrote:
> > > >>>
> > > >>>
> > > >>>>If so, why is struts-faces located in /trunk/ and therefore branched
> > > >>>>and
> > > >>>>tagged along with Struts core? Shouldn't it have its own
> > > >>>>trunk/branches/tags triad for its own release cycles?
> > > >>>>
> > > >>>>
> > > >>>+1
> > > >>>
> > > >>>Just curious, do we need to ask someone in [EMAIL PROTECTED] to
> > > >>>do this? I don't seem to understand where the real SVN repository
> > > >>>actually lives.
> > > >>>
> > > >>>Joe
> > > >>>
> > > >>>--
> > > >>>Joe Germuska
> > > >>>[EMAIL PROTECTED]
> > > >>>http://blog.germuska.com
> > > >>>"In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn
> > > >>>back; I'll know I'm in the wrong place."
> > > >>> - Carlos Santana
> > > >>>
> > > >>>
> > > >>>
> > > >>---------------------------------------------------------------------
> > > >>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]
