[jbehave-dev] [jira] Commented: (JBEHAVE-262) Migrate to Git for version control
[ http://jira.codehaus.org/browse/JBEHAVE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216714#action_216714 ] Mauro Talevi commented on JBEHAVE-262: -- Configured POMs for core and web to use git. Maven release prepare works fine and creates tag. The perform stage currently fails because the tag needs to be checked out for the deploy to occur. Workaround is to: git clone git checkout mvn deploy -Preporting,distribution > Migrate to Git for version control > --- > > Key: JBEHAVE-262 > URL: http://jira.codehaus.org/browse/JBEHAVE-262 > Project: JBehave > Issue Type: Task >Reporter: Mauro Talevi >Assignee: Mauro Talevi > Fix For: 3.0 > > > Task to track migration to Git for source control for JBehave 3.x. JBehave > 2.x remains in svn. > Git repo is cloned from svn and can be rebased if any changes in 2.x need to > merged to 3.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Commented: (JBEHAVE-262) Migrate to Git for version control
[ http://jira.codehaus.org/browse/JBEHAVE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216716#action_216716 ] Mauro Talevi commented on JBEHAVE-262: -- Also to be considered whether it makes sense to maintain the whole svn directory structure. Could be easier to create git tags/branches from svn ones (to maintain history) but remove file structure. > Migrate to Git for version control > --- > > Key: JBEHAVE-262 > URL: http://jira.codehaus.org/browse/JBEHAVE-262 > Project: JBehave > Issue Type: Task >Reporter: Mauro Talevi >Assignee: Mauro Talevi > Fix For: 3.0 > > > Task to track migration to Git for source control for JBehave 3.x. JBehave > 2.x remains in svn. > Git repo is cloned from svn and can be rebased if any changes in 2.x need to > merged to 3.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Commented: (JBEHAVE-262) Migrate to Git for version control
[ http://jira.codehaus.org/browse/JBEHAVE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=01#action_01 ] Mauro Talevi commented on JBEHAVE-262: -- Re-cloned trunk only and only split core, web and site into separate git repos. > Migrate to Git for version control > --- > > Key: JBEHAVE-262 > URL: http://jira.codehaus.org/browse/JBEHAVE-262 > Project: JBehave > Issue Type: Task >Reporter: Mauro Talevi >Assignee: Mauro Talevi > Fix For: 3.0 > > > Task to track migration to Git for source control for JBehave 3.x. JBehave > 2.x remains in svn. > Git repo is cloned from svn and can be rebased if any changes in 2.x need to > merged to 3.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
