Hi Tim, First of all, thanks for helping us migrating the project to SVN.
Now, regarding the current version of each component, our project have an interesting "feature": the standard sub-project has 2 parallel branches, the 1.1.x (which is the main trunk right now) and 1.0.x. This is necessary because Standard is a implementation of JSTL 1.0 and 1.1 (and probably 1.2 in the future). So, I don't know if SVN can handle it, but the more elegant layout for the project would be externally having a standard-1.0 and standard-1.1 projects (which the normal trunk, releases, tags, etc...), while internally it's indeed just two branches of the same 'standard' project (by externally I mean that they look like 2 separate projects for the end-users; while internally I mean how they are stored in the SVN server). Speaking on Unix-ish, standard-1.0 and standard-1.1 would be symbolic links to standard/trunk and standard/1.0. What do you think? Would such layout be possible? -- Felipe On Tue, 2005-01-11 at 12:10, Tim O'Brien wrote: > svn co https://svn.apache.org/repos/test/jakarta/taglibs/current/ > > Will get you the current trunk of every component in taglib proper (I --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
