Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SympleTypeEnum has not been actualized in OCLCST #422

Closed
eclipse-ocl-bot opened this issue Sep 19, 2024 · 11 comments
Closed

SympleTypeEnum has not been actualized in OCLCST #422

eclipse-ocl-bot opened this issue Sep 19, 2024 · 11 comments

Comments

@eclipse-ocl-bot
Copy link
Collaborator

| --- | --- |
| Bugzilla Link | 288526 |
| Status | CLOSED FIXED |
| Importance | P3 minor |
| Reported | Sep 03, 2009 13:03 EDT |
| Modified | May 27, 2011 02:47 EDT |
| Reporter | Adolfo Sanchez-Barbudo Herrera |

Description

Resolution https://bugs.eclipse.org/bugs/show_bug.cgi?id=282882 didn't properly fix the SympleTypeEnum of the CST metamodel.

I'll attach a patch for this.

@eclipse-ocl-bot
Copy link
Collaborator Author

By Adolfo Sanchez-Barbudo Herrera on Sep 03, 2009 13:05

Created attachment 146423 (attachment deleted)
Fixing patch

I need +1 to patch

@eclipse-ocl-bot
Copy link
Collaborator Author

By Adolfo Sanchez-Barbudo Herrera on Sep 03, 2009 13:07

My apologies.

I didn't properly set the component.

P.S: Assigning to me.

@eclipse-ocl-bot
Copy link
Collaborator Author

By Ed Willink on Sep 03, 2009 15:14

+1 Well caught. Hopefully this finishes this completely.

@eclipse-ocl-bot
Copy link
Collaborator Author

By Ed Willink on Sep 03, 2009 16:19

Two missing @SInCE 3.0's.

Found another:

ToStringVisitor.visitInvalidLiteralExp should now return "invalid". Can you do that at the same time please?

@eclipse-ocl-bot
Copy link
Collaborator Author

By Adolfo Sanchez-Barbudo Herrera on Sep 03, 2009 16:27

(In reply to comment #4)

Two missing @SInCE 3.0's.

Found another:

ToStringVisitor.visitInvalidLiteralExp should now return "invalid". Can you do
that at the same time please?

Ok Ed,

I think that I had disactivated API tooling warnings, in that workspace. I'll fix all toguether and commit

Thanks for pointing it out.

Cheers,
Adolfo.

@eclipse-ocl-bot
Copy link
Collaborator Author

By Adolfo Sanchez-Barbudo Herrera on Sep 04, 2009 06:14

Created attachment 146487
Final patch including commented changes

At the end, I hadn't configured the API Baseline in the workspace in which I created the patch >.<.

Another point, is that if your regenerate, you lose @SInCE :\

:notepad_spiral: ocl288526.patch

@eclipse-ocl-bot
Copy link
Collaborator Author

By Adolfo Sanchez-Barbudo Herrera on Sep 04, 2009 06:19

Committed to HEAD.

@eclipse-ocl-bot
Copy link
Collaborator Author

By Ed Willink on Sep 04, 2009 08:37

(In reply to comment #6)

Another point, is that if your regenerate, you lose @SInCE :\

For EMF auto-generation if you put @SInCE within the user-comments section, it is preserved.

@eclipse-ocl-bot
Copy link
Collaborator Author

By Ed Willink on Sep 04, 2009 09:42

Since the LPG templates do not provide all the NLS annotations you have to transfer them across manually. Fairly easy while in the Synchronize with Repository Perspective to just compare evetything with a yellow warning.

I've restored them as part of the commit for 287993.

When committing, the commits should very rarely have any yellow warnings (or red errors).

@eclipse-ocl-bot
Copy link
Collaborator Author

By Adolfo Sanchez-Barbudo Herrera on Sep 04, 2009 13:06

Ed,

Thank's for the advise. I'll take it into acount ;)

Cheers,
Adolfo.

@eclipse-ocl-bot
Copy link
Collaborator Author

By Ed Willink on May 27, 2011 02:47

Closing after over 18 months in resolved state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant