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

Bug 492293

Summary:	[pivot] Make nullFree Collections the default
Product:	[Modeling] OCL	Reporter:	Ed Willink <ed>
Component:	Core	Assignee:	OCL Inbox <mdt-ocl-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	M7
Hardware:	PC
OS:	Windows NT
Whiteboard:

Description Ed Willink

2016-04-23 03:34:24 EDT

In UML all collections are null-free.

In OCL they are alamost always null-free and so having to declare them assuch is really tedious.

Change the default so that UML2AS / ES2AS interprets undeclared null-free as null-free.

Comment 1 Ed Willink

2016-05-23 04:46:32 EDT

Default changed for M7.

Comment 2 Ed Willink

2016-12-13 11:54:15 EST

Adding WFRs to QVTi detects that collection type declarations are not parsed as null-free by default.

Fixing this detects that ToString/PrettyPrint serialization omits multiplicities for not-null-free rather than null-free.

Repairing tests finds yet more not-null-free defaults.

Not-null-free however seems correct for superclasses.

Comment 3 Ed Willink

2016-12-13 15:45:25 EST

testSerialize_SimpleUML2RDBMS_qvti suspended for QVTd M4

Comment 4 Ed Willink

2016-12-15 11:12:51 EST

Many new nullFree defaults fixed for M5.

(In reply to Ed Willink from comment #3)
> testSerialize_SimpleUML2RDBMS_qvti suspended for QVTd M4

Re-enabled for M5