Hi, It is expected behaviour. A release is actually like storing the state of your code for a precise event (often represented with a version).
Maybe what you (also?) want is the release:branch goal. Cheers Le 29 janv. 2013 18:35, "Jeff" <predato...@gmail.com> a écrit : > I've got my first GIT project to release using the maven release plugin, > but it didn't create a branch like I would have expected, it simply > "tagged" the current branch (master in my case) with the release version. > > Is this expected or am I missing something in my job config to make this > happen? > > Thanks!! > > -- > Jeff Vincent > predato...@gmail.com > See my LinkedIn profile at: > http://www.linkedin.com/in/rjeffreyvincent > I ♥ DropBox <http://db.tt/9O6LfBX> !! >
