454490 – [releng] Publish JDiff reports for API and all / non-api types between releases

Bug 454490 - [releng] Publish JDiff reports for API and all / non-api types between releases

Summary: [releng] Publish JDiff reports for API and all / non-api types between releases

Status:	NEW

Alias:	None

Product:	TMF
Classification:	Modeling
Component:	Xtext (show other bugs)
Version:	2.8.0
Hardware:	All All

Importance:	P3 enhancement (vote)
Target Milestone:	---
Assignee:	Project Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2014-12-08 15:41 EST by Sebastian Zarnekow
Modified:	2016-08-05 07:58 EDT (History)
CC List:	3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Sebastian Zarnekow

2014-12-08 15:41:51 EST

Clients that applied a lot of customizing often need to check the API changes after a new release to make sure their assumptions and customizing is still valid. In some cases it may have become obsolete, too. JDiff reports may help to find the API changes between releases.

Comment 1 Sebastian Zarnekow

2014-12-08 15:42:39 EST

Scheduled for 2.8 since I think this will provide a very nice starting point for a destilled migration hints doc for each release.

Comment 2 Sebastian Zarnekow

2015-04-30 09:17:49 EDT

Candidate to detect changes with our definition of API and in general: http://jqassistant.org/

Comment 3 Sebastian Zarnekow

2015-04-30 09:18:10 EDT

see http://jqassistant.org/detecting-differences-between-jar-files/

Comment 4 Dennis Huebner

2016-08-05 07:58:20 EDT

@see
https://hudson.eclipse.org/xtext/job/xtext-xtend-api-diff/

and published reports:
http://www.eclipse.org/modeling/tmf/javadoc/