Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 346101

Summary:	API Analysis Ant Task from source
Product:	[Eclipse Project] PDE	Reporter:	Nicolas Bros <nicolas.bros>
Component:	API Tools	Assignee:	PDE API Tools Inbox <pde-apitools-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	curtis.windatt.public, gdupe, Michael_Rennie
Version:	3.7
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Nicolas Bros

2011-05-17 10:34:09 EDT

The API Analysis ant task takes a target platform as input.
For testing in a continuous integration process, we'd like it to work with sources instead of binary in order to be able to include the result into the built product. Otherwise, the analysis can't run on binaries that have not yet been built.

Comment 1 Curtis Windatt

2011-05-17 12:16:03 EDT

I don't see this ever being worked on.  It would be a huge undertaking.  Couldn't you simply run the analysis task after the build step?  The results could still be packaged into the final product.

Comment 2 Nicolas Bros

2011-05-19 10:09:30 EDT

I couldn't make it work on plug-in projects. I believe the apiuse ant task expects plug-in jars as input (attribute "location"). So, it appears it must be done after the creation of the p2 repository (action "site.p2" with Buckminster).

Comment 3 Michael Rennie

2011-05-25 12:02:05 EDT

The idea backing this enhancement (supporting source analysis) is captured in bug 247509. As Curtis mentioned though, it is a massive amount of work and currently there are no plans to do it.

I'l leave the bug open as it is asking for specific use of source analysis support.

Comment 4 Lars Vogel

2019-11-14 02:14:59 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.