Re: [gatein-dev] Initial commit on API implementation

On Jul 11, 2011, at 12:56 PM, Boleslaw Dawidowicz wrote: > On Jul 8, 2011, at 5:46 PM, Christophe Laprun wrote: > >> Folks, >> >> I've committed the initial code for the API implementation: https://source.jboss.org/changelog/GateIn?cs=6849 >> I've created a new branch for this work: https://svn.jboss.org/repos/gatein/portal/branches/api >> It currently won't compile because there is no deployed artifact for the prototype API. >> >> Action items: >> - Please comment on code organization on the portal side. > > So if I understand correctly you want to keep gatein-api in github and place implementation in svn component/api-impl. This sounds good too me. We'll need to work release process and productization but thats the same case for Nicks work actually. On our side we are inclined to move to GIT but not without having planned it. For now it is not formally planned. It does not mean we should not use it right now, but at least we should define and agree and basic things before using GIT as a part of our formal version control system. In a second step we should plan and define the migration of existing code base to GIT. In addition there is the distinction between GIT (SCM) and GitHub (project infrastructure built on top of GIT). We should discuss that in a separate mail thread and not pollute this thread.

> >> - Please confirm the artifact and group IDs for the API proper and implementation Maven artifacts. > > org.gatein.portal:gatein-api would be separate > org.gatein.portal:gatein-api-impl would live in portal codebase are those correct ?