It sounds like we've hashed most of the issues out, so yes, I think a vote would be good. Care to call one :)? It would be nice to reach a consensus so we can start the import when infrastructure gets everything fixed.
-James On Mon, 2005-01-10 at 13:20 +0100, Stefan LÃtzkendorf wrote: > Yes, thats an Option too. > > Should we have a vote about our decision? > > Stefan > > James Mason wrote: > > > Agreed. It's fairly easy to move stuff around in Subversion, so > > refactoring should be easier. On that note, I'd like to suggest we do > > the initial conversion from CVS to a structure like > > > > /slide > > /branches > > /tags > > /trunk > > > > and then move stuff around after everything is in Subversion. This will > > let us keep our project history from CVS in case someone needs to grab > > anything ancient. > > > > Maybe adding a /slide/archives folder with the pre 2.2 branches and tags > > would be a good idea? > > > > -James > > > > On Thu, 2005-01-06 at 16:53 +0100, Stefan LÃtzkendorf wrote: > > > >>I think we should do it step by step. > >>- first migrate to svn > >>- get this working with ant > >>- and than, if we have time, introduce maven > >>otherwise we will be blocked for some time. > >> > >>Stefan > >> > >> > >>Daniel Florey wrote: > >> > >>>There is a strongly recommended project structure for maven based projects. > >>>Have a look at: > >>>http://maven.apache.org/reference/dirlayout.html > >>>We should try to stay close to this recommendation as we will have less > >>>trouble in use maven later on. > >>>I'll try to help as much as I can, but unfortunately I've not much time at > >>>the moment... > >>> > >>>Cheers, > >>>Daniel > >>> > >>> > >>> > >>>>-----UrsprÃngliche Nachricht----- > >>>>Von: [EMAIL PROTECTED] > >>>>[mailto:[EMAIL PROTECTED] Im > >>>>Auftrag von Stefan LÃtzkendorf > >>>>Gesendet: Donnerstag, 6. Januar 2005 11:57 > >>>>An: Slide Developers Mailing List > >>>>Betreff: Re: SVN Migration > >>>> > >>>>Ok, I try to sum up. > >>>> > >>>>- We split the clients. > >>>>- After svn migration we will update our ant build scripts to resolve > >>>>the dependencies to the clientlib (the testsuite and the server have > >>>>this depenency too). > >>>>- Later on we will (perhaps) create a maven build (requires maven a > >>>>special directory layout??) > >>>> > >>>>Any further things we have to consider? > >>>>At least the date of the migration is to be fixed. > >>>> > >>>>Stefan > >>>> > >>>> > >>>>The adapted layout (I have removed the libs directories from the clients): > >>>> > >>>>/jakarta > >>>> /slide > >>>> /server > >>>> /branches > >>>> /tags > >>>> /trunk > >>>> /src (content of current jararta-slide/src) > >>>> /docs (content of current jararta-slide/docs) > >>>> /lib (content of current jararta-slide/lib) > >>>> (the other directories go to other locations) > >>>> > >>>> /clientlib > >>>> /branches > >>>> /tags > >>>> /trunk (partial content of current > >>>> jararta-slide/webdavclient/clientlib) > >>>> files in current jararta-slide/webdavclient/clientlib > >>>> /src (content of current jararta-slide/webdavclient/src) > >>>> /lib (content of current jararta-slide/webdavclient/lib) > >>>> /ant > >>>> /branches > >>>> /tags > >>>> /trunk (content of current jararta-slide/webdavclient/ant) > >>>> /commandline > >>>> /branches > >>>> /tags > >>>> /trunk (content of current ararta-slide/webdavclient/commandline) > >>>> /connector > >>>> /branches > >>>> /tags > >>>> /trunk (content of current jararta-slide/webdavclient/connector) > >>>> /src > >>>> /example > >>>> /conf (content of current jararta-slide/webdavclient/etc/conf) > >>>> > >>>> /wck > >>>> /branches > >>>> /tags > >>>> /trunk (content of current jararta-slide/wck) > >>>> /projector > >>>> /branches > >>>> /tags > >>>> /trunk (content of current jararta-slide/projector) > >>>> /testsuite > >>>> /branches > >>>> /tags > >>>> /trunk (content of current jararta-slide/testsuite) > >>>> /proposals > >>>> /branches > >>>> /tags > >>>> /trunk (content of current jararta-slide/proposals) > >>>> /indexing > >>>> /jcrri > >>>> /taglib > >>>> /tamino > >>>> /wvcm > >>>> > >>>>-- > >>>>Stefan LÃtzkendorf -- [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]
