Re: Build artifacts in public maven repository?

Hi Gab, Thanks for this clarification. @all Before proceeding on this deployment issue I suggest to wait for the f2f meeting with Chemistry and OpenCMIS which takes place in a few weeks. It is not unlikely that a change in the project structure is one outcome of this meeting that has also an

Re: Client API create* calls

Agree +1 Am 25.03.2010 um 19:31 schrieb Florian Müller: > Hi, > > I would like to change the signatures of the create* calls of the client API. > The properties of the object to create are currently passed as > List>. I would like to change that to Map > (key=property id, value=property val

Client API create* calls

Hi, I would like to change the signatures of the create* calls of the client API. The properties of the object to create are currently passed as List>. I would like to change that to Map (key=property id, value=property value) because it's much simpler to use. Any objections? Florian

[jira] Commented: (CMIS-39) Arrange shapshots deploy to http://incubator.apache.org/chemistry/

[ https://issues.apache.org/jira/browse/CMIS-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849718#action_12849718 ] Gabriele Columbro commented on CMIS-39: --- See related mail thread: http://dev.day.com/di

[jira] Resolved: (CMIS-181) Correct version history link in Atom binding

[ https://issues.apache.org/jira/browse/CMIS-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Hübel resolved CMIS-181. - Resolution: Fixed > Correct version history link in Atom binding >

[jira] Resolved: (CMIS-182) Missing document properties in InMemory server

[ https://issues.apache.org/jira/browse/CMIS-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Hübel resolved CMIS-182. - Resolution: Fixed > Missing document properties in InMemory server > --

[jira] Resolved: (CMIS-180) Provide via link in in-memory provider only for PWC

[ https://issues.apache.org/jira/browse/CMIS-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Hübel resolved CMIS-180. - Resolution: Fixed > Provide via link in in-memory provider only for PWC > -

[jira] Created: (CMIS-182) Missing document properties in InMemory server

Missing document properties in InMemory server -- Key: CMIS-182 URL: https://issues.apache.org/jira/browse/CMIS-182 Project: Chemistry Issue Type: Bug Components: opencmis-server-inmemory

[jira] Commented: (CMIS-181) Correct version history link in Atom binding

[ https://issues.apache.org/jira/browse/CMIS-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849648#action_12849648 ] Joeri Samson commented on CMIS-181: --- In the spec it only says that the version-history link

[jira] Issue Comment Edited: (CMIS-181) Correct version history link in Atom binding

[ https://issues.apache.org/jira/browse/CMIS-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849648#action_12849648 ] Joeri Samson edited comment on CMIS-181 at 3/25/10 10:14 AM: - In

[jira] Created: (CMIS-181) Correct version history link in Atom binding

Correct version history link in Atom binding Key: CMIS-181 URL: https://issues.apache.org/jira/browse/CMIS-181 Project: Chemistry Issue Type: Bug Components: opencmis-provider, opencmis-

[jira] Commented: (CMIS-181) Correct version history link in Atom binding

[ https://issues.apache.org/jira/browse/CMIS-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849642#action_12849642 ] Jens Hübel commented on CMIS-181: - The id in the link must according to spec be the version s

[jira] Created: (CMIS-180) Provide via link in in-memory provider only for PWC

Provide via link in in-memory provider only for PWC --- Key: CMIS-180 URL: https://issues.apache.org/jira/browse/CMIS-180 Project: Chemistry Issue Type: Bug Components: opencmis-serve

Re: Build artifacts in public maven repository?

Hey Jens, On Mar 24, 2010, at 1:55 PM, Jens Hübel wrote: Just one little remark: If you make fundamental changes, like changing .pom files, group- ids, etc. that influence the whole build and the layout of the maven repository please, please, write a short notice to the mailing list befor