[jira] [Resolved] (OLINGO-331) Build 2.0.0 release

["Michael Bolz (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OLINGO-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Bolz resolved OLINGO-331.
---------------------------------

    Resolution: Fixed

Hello,

Apache Olingo 2.0.0 has been released. 

This release is available for download:
http://olingo.apache.org/download.html

[Release Notes - Olingo - Version 2.0.0|https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314520&version=12327170]:
---------------------------------------------------

Sub-task
[OLINGO-308] - POST a new entry where ID is server generated
[OLINGO-310] - JSON request is always wrapped in object with "d" property only, even for requests
[OLINGO-320] - Documentation for Delta Token Support
[OLINGO-335] - Run Code CleanUp on the whole repository
[OLINGO-336] - Change version in pom to 2.0.0-SNAPSHOT

Bug
[OLINGO-172] - NavigationProperty not appear in $metadata
[OLINGO-235] - Maxlength shouldn't be check when query the odata with Olingo
[OLINGO-237] - Add library version to debug output
[OLINGO-239] - ClassHelper doesn't find classes when there's a space in the path
[OLINGO-241] - API is missing to expose the entity in the OdataResponse
[OLINGO-243] - Function returning entity expects wrong "Accept" header and returns wrong "Content-Type".
[OLINGO-245] - Wrong EDM property type when setDefaultNaming is false
[OLINGO-251] - Handling insert (OData POST of entity) with reverenced to an existing entity
[OLINGO-252] - ODataErrorContext incomplete
[OLINGO-255] - Client can't parse expanded inline nav prop which is null
[OLINGO-256] - Incorrect Content-Length for ChangeSet in $batch
[OLINGO-257] - Potential resource leak
[OLINGO-275] - Set ETag for inline entries correctly
[OLINGO-284] - Incorrect length validation for Edm.Binary
[OLINGO-293] - Unable to POST an entity with a DateTime type field using underlying JPA model
[OLINGO-295] - ReferentialConstraints can be null but are still returned with a wrapper
[OLINGO-298] - Incompatibility with jsr311
[OLINGO-305] - case-sensitive vs case-insensitive
[OLINGO-306] - Servlet ConcurrentModificationException
[OLINGO-312] - Reading resource via Classloader
[OLINGO-329] - Not all JPA data types handled correctly
[OLINGO-330] - Wrong exception message for matrix parameter in odata path
[OLINGO-333] - Function Import With no ReturnType results in a NullPointer
[OLINGO-334] - Parsing metadata: FunctionImport reads only first parameter

Improvement
[OLINGO-56] - jpa ref web app to feature aslo Create/Updae and Delete samples
[OLINGO-104] - JPA Documentation Update: Adding Non JPA Entities as Function Import Return Types
[OLINGO-127] - Support JoinColumns and handle Optional attribute ReferencedColumnName
[OLINGO-165] - Remove deprecated methods and variables
[OLINGO-232] - Add "getEntitySets()" and "getAssociationSets()" methods to the EdmEntityContainer
[OLINGO-258] - Deprecated method usage
[OLINGO-296] - Tolerate EdmSingle as JSON String or Number
[OLINGO-311] - Minor Client Issues
[OLINGO-325] - Remove unused code - EdmTypeConvertor

New Feature
[OLINGO-47] - $batch support
[OLINGO-105] - Not able to cache the ODataResponse
[OLINGO-185] - support for Clob
[OLINGO-196] - A means should be exposed for de-serializing error streams
[OLINGO-224] - Delta Token feature support in Olingo
[OLINGO-297] - Unable to create FunctionImport with empty return type
[OLINGO-303] - Functionality to read inline delta feeds
[OLINGO-323] - V2 library client improvements

Task
[OLINGO-331] - Build 2.0.0 release

Kind Regards,
Michael


> Build 2.0.0 release
> -------------------
>
>                 Key: OLINGO-331
>                 URL: https://issues.apache.org/jira/browse/OLINGO-331
>             Project: Olingo
>          Issue Type: Task
>          Components: MISC
>    Affects Versions: V2 2.0.0
>            Reporter: Michael Bolz
>            Assignee: Michael Bolz
>             Fix For: V2 2.0.0
>
>
> Build 2.0.0 release (formerly version 1.3.0).
> Release timeline/plan is:
> - From now on no new issues for "1.3.0" are allowed. All new issues should
> be assigned with version "V2 2.1.0"
> - Code freeze next wednesday (2nd of july)
> - Checks, last preparations and release at the end of next week (~ 4th of
> july). 



--
This message was sent by Atlassian JIRA
(v6.2#6252)