Issue 9: Reorganize svn structure
Status:  Invalid
Owner: ----
Closed:  Apr 2007
Apr 9, 2007
#1 extremec...@gmail.com
Thats a really good idea! When I started the project I was new to Subversion and have
not thought about the structure once I release a version. Now that I understand
Subversion more I completely agree with your first example of how to re-structure
things and will do so for the upcoming production release.
Apr 9, 2007
#2 extremec...@gmail.com
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
#3 oliver.lamy@gmail.com
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
#4 extremec...@gmail.com
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!