[
https://issues.apache.org/jira/browse/OPENMEETINGS-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16674288#comment-16674288
]
ASF subversion and git services commented on OPENMEETINGS-1636:
---------------------------------------------------------------
Commit bc31afe2d36abe18613b2c742afd7b911e26bc82 in openmeetings's branch
refs/heads/4.0.x from [~ankushmishra]
[ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=bc31afe ]
OPENMEETINGS-1636 Upgrade Caldav4j to 1.0.0-rc.1 (#12)
* * Updated CalDAV4j to 1.0-SNAPSHOT
* Converted all code from HttpClient 3.x to 4.x
* Added documentation where ever it was needed.
* Now credentials are stored in HttpClientContext objects per CalendarPanel.
This is necessary as HttpClient objects, no more contain states, and context
objects contain states.
* Fixed issues which arose during testing.
- TimeZone caching for iCal4j is set to MapTimeZonecache
- Fixed iCalUtils to parse MeetingMembers correctly.
- Changed listToMap to only require Appointment Objects.
- Fixed handling of Appointment paths in various places.
- Removed the need for MultiGetHandler, except for fetching ETags
- Also, fixed a DAO update issue.
* Fixed a minor issue with parsing VEVENT CHAIR from iCal
* Fixes based on the PR review
> Upgrade AppointmentManager from HttpClient 3.x to 4.x
> -----------------------------------------------------
>
> Key: OPENMEETINGS-1636
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1636
> Project: Openmeetings
> Issue Type: Improvement
> Components: HTML5/Calendar
> Reporter: Ankush Mishra
> Assignee: Ankush Mishra
> Priority: Minor
> Fix For: 4.0.7
>
>
> I had been waiting for
> [JCR-2406|https://issues.apache.org/jira/browse/JCR-2406] to close. Since,
> that has been completed for a couple of months, I opened another Issue for
> CalDAV4j [here|https://github.com/caldav4j/caldav4j/issues/63] , which I will
> try to first release to the Central Repo soon, with 3.x, after which I will
> get to work on the migration.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)