Prime Community Forum

We have been getting requests from the community to move to GitHub and would like to do a poll to get your valuable feedback.

It ONLY makes sense if Primefaces changes the way they accept patches (via pull requests in git). If the policy that code can only be developed by Prime technology (not just committed, but actually developed) is not changed, it makes no sense to move to github.

Voted with +1. It will be easier for you to deploy SNAPSHOTs automatically.

We considered the moving to GitHub for PF Extensions too and decided to do this in the near future as soon as time will allow it. The problem is that we use some Maven plugins for SVN and don't have experience in moving code from SVN to GitHub. Do you know how to migrate the code from SVN to GitHub in an easy way?

Please also consider releases in Maven central repo. I know, I can be annoying, but here is the link again https://docs.sonatype.org/display/Repos ... sage+Guide Thanks.

@Ronald, yes we are changing the policy and accepting patches, that's why we are considering moving to github so the platform makes it easier for users.

@Oleg, I'm not a Git expert so we'll learn as well. Hopefully soon 3.4.1 will be in maven central as well after git migration.

Cagatay, if you go to the google.code where project is hosted, go to the "Administrator" tab and then "Source", you will see "Switch to: Git". We are tried it for a test and it was working. Not clear how to release with trunk and branches, but I think it's not a problem at all because maven-release-plugin does this job automatically.

Git is really good. For example, every commit for PrimeFaces Cookbook is automatically deployed by Jenkins https://buildhive.cloudbees.com/view/Da ... 4showcase/

I have successfully migrated test project to github using svn2git.

https://help.github.com/articles/import ... subversion
https://github.com/nirvdrum/svn2git

Useful links, Nilesh. Thanks.

Oleg wrote:Useful links, Nilesh. Thanks.

Welcome!

Didn't know that google code has git as well.

Main blocker is moving issues to github so switching to git and staying at google code seems logical.

Hi Cagatay,

Issue migration is also possible using:

https://github.com/arthur-debert/google ... s-migrator