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

Bug 463311

Summary:	api_description not working for one case (at least)
Product:	[Technology] CBI	Reporter:	David Williams <david_williams>
Component:	maven-plugins	Assignee:	CBI Inbox <cbi-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	1.1.1
Hardware:	PC
OS:	Linux
Whiteboard:
Bug Depends on:
Bug Blocks:	463085

Description David Williams

2015-03-27 12:43:35 EDT

See bug 463085 for details. 

In short, for org.eclipse.help.base, the .api_description is being generated during the build (directly under /target/ like it appears they all are. 

But, for some reason, it is not being "packaged" into the (binary) code jar. 

Bit of mystery, so thought I'd open this bug in CBI, since those api_descriptions are generated by a CBI plugin (and packaged by a CBI plugin). 

I am wondering, if, at a minimum, the CBI plugin is "eating" some exception instead of logging it, or allow it to be "thrown upward". I've looked in all the logs I know of, and can find no sign of "error" or "warning".

Comment 1 David Williams

2015-03-28 17:57:44 EDT

I'm pretty sure "the bug" we are seeing isn't related to CBI code 

Not that I understand better what it does. The CBI plugin creates the .apibuild.xml file. While appears to be correct in our "bug" case. 

And then another task/profile runs "eclipserun" to create the .api_description. 
Which appears to be correct, in our case. 

And then another "resource task" "packages" in with the jar ... and that's the part that is not happening! 

Mysterious, but not the CBI plugin.