On 07/11/2011 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.
> - Please confirm the artifact and group IDs for the API proper and implementation
Maven artifacts.
org.gatein.portal:gatein-api
org.gatein.portal:gatein-api-impl
Seems fine.
> - Please confirm API versioning scheme.
I'm personally fine with going with 1.0.0 (instead of 3.2.0) for the API as we aim to
keep separate lifecycle for this component long term.
Julien, Thomas any issue with those on your side?
Seems fine, will need to be
properly documented though. But that sounds
good as EPP/PLF/GTN don't have the same version schemes, at least they
can talk about the same version scheme of API.
Thomas
Bolek
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev