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

Bug 364265

Summary:	Regression with "Java application" launches
Product:	[Modeling] Acceleo	Reporter:	Laurent Goubet <laurent.goubet>
Component:	Core	Assignee:	Project Inbox <acceleo-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	major
Priority:	P3	CC:	ed
Version:	3.2
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Laurent Goubet

2011-11-21 03:31:22 EST

All Acceleo plugins created before the integration of a com.google.collect dependency in the core of Acceleo now fails with "ClassNotFoundException : com.google.common.Predicate".

Comment 1 Laurent Goubet

2011-11-21 03:47:37 EST

The dependency towards com.google.collect is now reexported from the org.eclipse.acceleo.engine bundle. More of a hack than a fix, but it does make the transition transparent to users.

Comment 2 Ed Willink

2011-11-21 05:22:17 EST

This seems remarkably similar to Bug 339083 (Xtext).

Perhaps there is some missing API testing that would verify that all indirectly accessed plugins are referenced to ensure that a lack of accessibility in a standalone environment is a compile-time rather than run-time phenomenon. If you can think of a way API tools could help, it might be worth a Bugzilla.

Comment 3 Laurent Goubet

2011-11-21 05:26:01 EST

Ed,

The real issue was that I thought "adding APIs is not breaking the API" ... but that rule can obviously not be extended to "adding dependencies". Yet now that you mention it, API tooling should have warned me that I was adding a new dependency; I'll raise the corresponding bugzilla.