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

Bug 321525

Summary:	Add warning for bad invoke
Product:	[Modeling] Acceleo	Reporter:	Ed Willink <ed>
Component:	Core	Assignee:	Project Inbox <acceleo-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	laurent.goubet, stephane.begaudeau
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows Vista
Whiteboard:

Description Ed Willink

2010-08-02 12:26:43 EDT

Forked from Bug 319252.

Acceleo fails if an [template invoke ...] refers to a not-exported package.

It would be helpful if Acceleo provided edit-time warnings of the validity of
the invoke call.

Comment 1 Stephane Begaudeau

2011-05-06 04:52:37 EDT

If a Java service is in the workspace and if that class is in a dependency of the Acceleo Project (recursively) and if the package containing the class has not been exported then the invoke operation will be marked by a warning.

It will not detect:
- Java services that have are not in the workspace (investigating in the deployed plugins would be very time consuming).
- Java services that do not exists (they can be in a plugin)

You can see an example in the following screenshot: https://lh3.googleusercontent.com/_R0aPxLxg16E/TcOyCT2CnVI/AAAAAAAAARU/d5QVxkdH3Ak/Services.png

(MyClass does not exists, GenerateJava is exported and Service is not exported).

The fix will be contributed on HEAD, it will be available in Acceleo 3.1.0 RC1.

Comment 2 Laurent Goubet

2011-08-18 04:21:58 EDT

Closing our "resolved" and "verified" bugs.

Comment 3 Ed Willink

2011-08-18 04:29:16 EDT

Definitely not fixed in 3.1.0.

And rather irritatingly, Acceleo rebuilds whenever anything in the project changes, which would only be justifiable if it was checking.

Having a 'build' project with about 10 *.mtl and about 10 *.mwe2 and 20 primary *.java is pretty painful since they seem to trigger each other into spurious builds. When EGIT gets to work, it is generally necessary to switch off 'Build Automatically' till the progress stabilizes.

Comment 4 Laurent Goubet

2011-08-18 04:32:27 EDT

Ed,

Thanks for the feedback, this is an issue we thought resolved. (I was just bulk-closing all "resolved" and "fixed" issues... :p.)

Comment 5 Laurent Goubet

2016-03-23 11:22:44 EDT

This had indeed been fixed in 3.1.0. As Stéphane mentionned, it will only mark as warning those classes that can indeed be found in the project's dependencies and have not been exported.