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.

Sign up for GitHub

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

Jump to bottom

Problematic namespace for runtime shader map internal #254

Closed
minborg opened this issue Sep 10, 2016 · 2 comments
Closed

Problematic namespace for runtime shader map internal #254

minborg opened this issue Sep 10, 2016 · 2 comments
Assignees
@minborg
Labels
bug fixed
Milestone
3.0.0-EA2 Forest

Comments

@minborg
Copy link
Contributor

minborg commented Sep 10, 2016

Common modules that are included in runtime using the maven shader plugin are exposed as internal. However, may other modules need to use these modules. We should consider a new name or not moving them in the shade process.
@minborg minborg added the bug label Sep 10, 2016
@minborg minborg added this to the 3.0.1 Forest milestone Sep 10, 2016
@minborg minborg self-assigned this Sep 12, 2016
@minborg
Copy link
Contributor Author

minborg commented Sep 12, 2016

Code Generator and Tuple shall be exposed, MapStream shall not be exposed.

@minborg
Copy link
Contributor Author

minborg commented Sep 13, 2016

injector, tupe and logger are moved to the public API

@minborg minborg added the fixed label Sep 13, 2016
@minborg minborg closed this as completed Oct 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@minborg minborg

Labels
bug fixed
Projects
None yet
Milestone
3.0.0-EA2 Forest
Development

No branches or pull requests
1 participant
@minborg