JBehave

Migrate to Git for version control

Details

  • Type: Task Task
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 3.0
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

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

Activity

Hide
Mauro Talevi added a comment -

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 <url>
git checkout <tag-name>
mvn deploy -Preporting,distribution

Show
Mauro Talevi added a comment - 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 <url> git checkout <tag-name> mvn deploy -Preporting,distribution
Hide
Mauro Talevi added a comment -

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.

Show
Mauro Talevi added a comment - 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.
Hide
Mauro Talevi added a comment -

Re-cloned trunk only and only split core, web and site into separate git repos.

Show
Mauro Talevi added a comment - Re-cloned trunk only and only split core, web and site into separate git repos.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: