Shouldn't the artifact id (and also JAR names) rather be org.apache.olingo.*? Thought I saw that on other Apache artifacts too if artifact name is not only project name (Felix, Servicemix)
Andreas -----Original Message----- From: V.A, Chandan [mailto:[email protected]] Sent: Tuesday, September 24, 2013 8:33 AM To: [email protected] Subject: RE: Jira Issues for Documentation +1 for me. @Stephan, You would be doing this for all our modules. Thanks, Kind Regards Chandan VA -----Original Message----- From: Bolz, Michael [mailto:[email protected]] Sent: Monday, September 23, 2013 8:03 PM To: [email protected] Subject: Re: Jira Issues for Documentation Hi, >From me a "+1" for changing the "artifact id". Perhaps we should do this before we start progress on refactoring folder/project structure "https://issues.apache.org/jira/browse/OLINGO-23";. That way we prevent unnecessary merge conflicts. Kind regards, Michael On 23.09.13 15:13, "Klevenz, Stephan" <[email protected]> wrote: >Hi, > >I have opened a new issue which should be fixed before release: > >https://issues.apache.org/jira/browse/OLINGO-22 > > >I think we have to change again groupId and artifactId. Unfortunately this >will affect all documentation and samples which exists already. After >change this needs to be reworked as well. > >-- Stephan > > >On 23.09.13 09:02, "Huesken, Jens" <[email protected]> wrote: > >>Hi, >>I've processed the Jira Issues for initial documentation of the OData >>Library and the JPA Processor. >>https://issues.apache.org/jira/browse/OLINGO-4 >>https://issues.apache.org/jira/browse/OLINGO-5 >>https://issues.apache.org/jira/browse/OLINGO-6<https://issues.apache.org/ >>j >>ira/browse/OLINGO-7> >>https://issues.apache.org/jira/browse/OLINGO-7 >> >>Changes are available on staging and can be reviewed via the following >>link: >>http://olingo.staging.apache.org/documentation.html >> >>I would appreciate feedback before publishing. >> >>Thanks, >>Jens. >> >> >> >
