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

Use generic stand-in for contributors/developers #117

Closed
eneufeld opened this issue Jul 15, 2021 · 0 comments · Fixed by #124
Closed

Use generic stand-in for contributors/developers #117

eneufeld opened this issue Jul 15, 2021 · 0 comments · Fixed by #124
Assignees

Comments

@eneufeld
Copy link
Contributor

We should use "Eclipse emf.cloud Project" as the generic stand-in for all committers and contributors in all poms and package.jsons to avoid having to manually maintain it.
E-mail address: https://accounts.eclipse.org/mailing-list/emfcloud-dev
Web-site the project page: https://projects.eclipse.org/projects/ecd.emfcloud

For details see the discussion in eclipse-glsp/glsp#246

@ndoschek ndoschek self-assigned this Sep 8, 2021
ndoschek added a commit that referenced this issue Sep 8, 2021
- Use generic stand-in for contributors/developers
- Rename r2020-09 to targetplatform and update its occurrences
- Fix Workspace warning (plugin.properties not existing in workspace)
ndoschek added a commit that referenced this issue Sep 9, 2021
- Use generic stand-in for contributors/developers
- Rename r2020-09 to targetplatform and update its occurrences
- Use specific versions for emfjson-jackson and jetty update site to speed up targetplatform resolving
- Fix Workspace warning (plugin.properties not existing in workspace)
ndoschek added a commit that referenced this issue Sep 13, 2021
#125, #123, #117 Fix dependencies, reuse TransactionChangeRecorder and use generic stand-in for contributors/developers
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants