Hi all,
I would like to reanimate this discussion. I have been trying to find
information about having an Repository which is not under Apache control as
part of an Apache project but I could not find any useful information about
this.
In my personal opinion we should not use the GitHub reposit
Christian Amend created OLINGO-1033:
---
Summary: V4: @odata.type annotation incorrect for primitive types
Key: OLINGO-1033
URL: https://issues.apache.org/jira/browse/OLINGO-1033
Project: Olingo
On 14/10/2016 10:35, Amend, Christian wrote:
Hi all,
I would like to reanimate this discussion. I have been trying to find
information about having an Repository which is not under Apache control as
part of an Apache project but I could not find any useful information about
this.
In my person
Santosh kumar created OLINGO-1034:
-
Summary: Provide Call backs for CRUD operations
Key: OLINGO-1034
URL: https://issues.apache.org/jira/browse/OLINGO-1034
Project: Olingo
Issue Type: New Fea
[
https://issues.apache.org/jira/browse/OLINGO-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15574817#comment-15574817
]
Santosh kumar commented on OLINGO-1034:
---
Linked to this issue, since, both of them
[
https://issues.apache.org/jira/browse/OLINGO-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15574817#comment-15574817
]
Santosh kumar edited comment on OLINGO-1034 at 10/14/16 9:38 AM:
--
[
https://issues.apache.org/jira/browse/OLINGO-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15574995#comment-15574995
]
Kavindu Dodanduwa commented on OLINGO-834:
--
This is regarding URI parsing. Prior
GitHub repo is created to capture the early enthusiasm of community
contributors without much restrictions of ICLA and ASF and also to gauge the
interest of the participant to drive the feature to the somewhat of a mature
state. If Olingo starts adapting all the extensions which are not directly
Please correct me if I am wrong, but it seems like Apache GitHub
integration is currently fairly lackluster. It does not seem to
seamlessly integrate with a lot of GitHub main features. For example, it
does not seem to integrate with GitHub issues, which is a big part of
what makes a GitHub rep
[
https://issues.apache.org/jira/browse/OLINGO-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15576190#comment-15576190
]
Anil Maddhirala commented on OLINGO-414:
Hi Michael Bolz,
what is maven artifact
[
https://issues.apache.org/jira/browse/OLINGO-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15576209#comment-15576209
]
Michael Bolz commented on OLINGO-1034:
--
Hi [~Santosh Kumar],
Thanks for creation of
Hi all,
I think I agree more with Alexandre and Ramesh to
> "Put it on the GitHub repo and wait for the project to reach an adequate
> maturity."
Or to repeat myself:
> IMHO I also think we should keep the barrier for contributions low. Hence
> using a GitHub repository as starting point coul
[
https://issues.apache.org/jira/browse/OLINGO-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15576253#comment-15576253
]
Michael Bolz commented on OLINGO-414:
-
Hi [~maddhirala],
The patch/fix should be incl
13 matches
Mail list logo