You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Huesken, Jens" <je...@sap.com> on 2013/09/23 09:02:18 UTC
Jira Issues for Documentation
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/jira/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.
Re: Jira Issues for Documentation
Posted by "Bolz, Michael" <mi...@sap.com>.
Hi,
IMHO it is common practice to have a group id like "org.apache.olingo" to
group all artifacts which then only have names like "odata2.api" and
"odata2.core".
I would prefer to not have the full qualified name redundant in group and
artifact id.
For me it seems wrong and to long ;o)
Kind regards,
Michael
On 24.09.13 11:25, "Schlosser, Andreas" <an...@sap.com> wrote:
>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:chandan.v.a@sap.com]
>Sent: Tuesday, September 24, 2013 8:33 AM
>To: dev@olingo.incubator.apache.org
>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:michael.bolz@sap.com]
>Sent: Monday, September 23, 2013 8:03 PM
>To: dev@olingo.incubator.apache.org
>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" <st...@sap.com> 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" <je...@sap.com> 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.
>>>
>>>
>>>
>>
>
RE: Jira Issues for Documentation
Posted by "Schlosser, Andreas" <an...@sap.com>.
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:chandan.v.a@sap.com]
Sent: Tuesday, September 24, 2013 8:33 AM
To: dev@olingo.incubator.apache.org
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:michael.bolz@sap.com]
Sent: Monday, September 23, 2013 8:03 PM
To: dev@olingo.incubator.apache.org
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" <st...@sap.com> 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" <je...@sap.com> 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.
>>
>>
>>
>
RE: Jira Issues for Documentation
Posted by "V.A, Chandan" <ch...@sap.com>.
+1 for me.
@Stephan,
You would be doing this for all our modules.
Thanks,
Kind Regards
Chandan VA
-----Original Message-----
From: Bolz, Michael [mailto:michael.bolz@sap.com]
Sent: Monday, September 23, 2013 8:03 PM
To: dev@olingo.incubator.apache.org
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" <st...@sap.com> 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" <je...@sap.com> 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.
>>
>>
>>
>
Re: Jira Issues for Documentation
Posted by "Bolz, Michael" <mi...@sap.com>.
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" <st...@sap.com> 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" <je...@sap.com> 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.
>>
>>
>>
>
Re: Jira Issues for Documentation
Posted by "Klevenz, Stephan" <st...@sap.com>.
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" <je...@sap.com> 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.
>
>
>