| Issue 9: | Reorganize svn structure | |
| 1 person starred this issue and may be notified of changes. | Back to list |
I think the svn structure is not correct. http://jmesa.googlecode.com/svn/trunk/jmesa/ This should must http://jmesa.googlecode.com/svn/trunk/jmesa/trunk (here the trunk) http://jmesa.googlecode.com/svn/trunk/jmesa/tags (here the last rc must be tagged). svn mv http://jmesa.googlecode.com/svn/trunk/jmesa/ http://jmesa.googlecode.com/svn/trunk/jmesa/trunk. Maybe you have to have tags directory svn mkdir http://jmesa.googlecode.com/svn/trunk/jmesa/tags and copy the last rc to tags svn cp http://jmesa.googlecode.com/svn/trunk/jmesa/trunk http://jmesa.googlecode.com/svn/trunk/jmesa/tags/2.rc2
Apr 9, 2007
#1
extremec...@gmail.com
Apr 9, 2007
Actually we are ok with the current structure. Google already has the tags and branches folders set up in subversion. I didn't notice until I set up Eclipse to point to the svn directory, and then I could see the folders below that. https://jmesa.googlecode.com/svn/ If anything looks a little odd it is because I am checking in both the jmesa code and the jmesa web site (jmesaWeb). This does not allow me to put the jmesa code right under the trunk directory, which is what you were probably expecting. However, this seems to work out fine and I will just consistently put tags and branches in the respective folders that matches what the trunk looks like. For example: /trunk/jmesa/ /trunk/jmesaWeb/ /tags/2_0_0/jmesa/ /tags/2_0_0/jmesaWeb/
Status:
Invalid
Apr 17, 2007
An other idea concerning the structure. What about using maven2 ? With the following structure : root folder :http://jmesa.googlecode.com/svn/trunk/jmesa/. Content : - pom.xml (root pom). - jmesa-component (or an other name like taglib ?) here a pom.xml. - jmesa-webapp here a pom.xml. If you like I can be volunteer to provide patch :-) Just let me know. I'm sure a maven build could be helpfull some people use your great tag lib. -- Olivier
Apr 17, 2007
I would like to keep the current project structure because it works well and is easy to work with. However, if you would like to create a pom.xml for jmesa and/or jmesaWeb I would include them in the distribution! |