Note that EWS does support OAuth in Office 365, for both code and client-credential flow. The only difference to the Rest APIs is the permissions. EWS only supports "full access to mailbox" while Rest APIs do only support the granular permissions specific to a class of resources (Calendar, Mail, Contact). We recently updated the permission strings in the Application registration portal to better signal what is available for EWS. From a OAuth protocol point of view there is no difference. Note that maybe you had some issues in the preview phase where we marked the "full access to mailbox" permission as "admin only", meaning they required an admin to consent. With GA we removed this restriction. All permissions are now consent-able by an end-user. More here: https://msdn.microsoft.com/en-us/library/office/dn903761(v=exchg.150).aspx
I agree on the "push-pr-merge" when we have a stable release to rely on, but perhaps we should have a bit more restricted push-policy until then?
I would also suggest in autodeploying snapshots to the maven snapshot repo. The following needs to be handled when we try to do that:
username and password should be encrypted (even if this sounds like an easy step for travis maybe it could be usefull to create another jira-account (@ossrh) which only has privileges to deploy to the snapshot repo)
deployment should only be done by one of the 3 builds and only if all verification is successful
KISS (keep it simple and stupid)
@pathikrit the mentioned python-script looks a little stuffed. Maybe there is a more lightweight alternative
@ahaarrestad dont think push-policy should be restricted since a snapshot release will always be a snapshot and not a stable one
Hi... just getting started here.
Wondering what happened to 1.3? Was it ever released (ie: maven released) ? or is the 2.0-snapshot the only available version in sonatype.org ?
If the answer is yes... do you know when 2.0 will be released?
Would be nice to have a stable/released version to base my app. on.
We are currently planing the 2.0 release milestone. Therefore everybody is invited to declare issues that need to be fixed before the deployment is done. Maybe for not breaking packages again a restructuring of the classes in packages and subpage would be useful. This could be handled like it is in the ews-managed-api.
while thinking on that package restructuring I would suggest in not doing this with the 2.0 release since this would force every user to update their imports which could be dangerous if people just change maven dependency from snapshot to stable. Maybe we can include these restructuring into another major release. I think this would make live easier.
Can anybody tell me if the old timezone setting problem from ews 1.2 has been fixed already?
Dunno what specific problem you are referring to, but there have been tons of timezone/data parsing fixes, like OfficeDev/ews-java-api#6
You can just use UTC, the date and time will be shown in the user's timezone anyway.
Thanks for the response on 2.0. Agree that re-org on imports type of change would be nicer in next version. So what about 1.3? Seems it never did get released?
Nope, and 1.4, 1.5, 1.6, 1.7 etc. weren't released either ;)
for that matter 2.0 wasn't released either. only snapshots are available.
Have noticed something a little strange with getUserAvailability(). Testing with exchange 2010 server. It seems that the TimeWindow start & end should be set in UTC, but the calendar events (CalendarEvent) coming back (ie: start & end times) are in local time. Is this correct? or am I missing something here? ( I was comparing to the 1.1.5 version of this pkg, where all times send & rec'd were in UTC ).
( oops... for 1.1.5 version... only times rec'd in UTC, not sent )