Hi, I suggest to do as Florian has proposed. I will do another ZIP with packaging org.apache.olingo + Apache header. All the rest can be community work.
WDYT? Stephan On 24.07.13 07:43, "V.A, Chandan" <[email protected]> wrote: >Hi all, >We need to refactor not just the package name but also the artifact id in >case of JPA processor library. > >@Stephan, >You had initially proposed changes to artifact id in case of JPA >processor library to align with OData Lib. Do we need to do that now in >GITHUB first or do it after initial commit. > > >Thanks, >Kind Regards >Chandan VA > >-----Original Message----- >From: Bolz, Michael [mailto:[email protected]] >Sent: Tuesday, July 23, 2013 11:39 PM >To: [email protected] >Subject: Re: initial code contribution > >Hi Florian, > >Wouldn't it be better to do it after the initial commit? >So we have this part of history which could help to link to the (a little >messy) history on GitHub. > >Or we do the changes on GitHub on then do the initial commit. I think this >could be a good solution. > >By the way I have attached a small script for package renaming to the JIRA >issue. > >Kind regards, >Michael > > > >On 23.07.13 18:14, "Florian Müller" <[email protected]> wrote: > >>Hi Stephan, >> >>Before we check the code into the Apache Git, we should make a few >>general changes to it. >>We should have at least the Apache header in each source file. It would >>also be good to change package names to something like >>"org.apache.olingo...". >> >> >>Florian >> >> >>> >
