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

Use GoF Bridge pattern to decouple compiler implementation from its use #19

Open

ghost opened this issue Jun 17, 2015 · 1 comment

Labels

Milestone

ghost commented Jun 17, 2015

This would

allow for future flexibility
make compiler use easier for tools ( e.g. a maven plugin, or an IDE )
completely hide all compilation details to a user
allow us to work on improved versions / algos without causing breakage to users ( humans or tools )

Member

nobeh commented Jun 17, 2015

I agree with the general design patterns. As per Maven, we already have a Maven plugin supporting jabsc at: https://github.com/CrispOSS/jabsc-maven-plugin and example usage at https://github.com/CrispOSS/jabsc-maven-plugin-example

nobeh added the enhancement label

nobeh added this to the 1.0.0 milestone

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