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

Change artifactId to the normal scala version naming convention #76

Merged
merged 1 commit into from Apr 23, 2015

Conversation

dnadolny
Copy link
Contributor

Right now the artifactId includes the full scala version in it, eg scalagen_2.9.3, scalagen_2.10.1, etc.
This was the convention for 2.9.x, but for 2.10+ the convention is to only have the major/minor scala version, eg scalagen_2.10.

Also, would you be able to bump the version and do a release?

Right now the artifactId includes the full scala version in it, eg
scalagen_2.9.3, scalagen_2.10.1, etc.
This was the convention for 2.9.x, but for 2.10+ the convention is to
only have the major/minor scala version, eg scalagen_2.10.
@mangolas
Copy link
Contributor

We haven't been working in this project for a long time and the original author has left our company. We don't mind merging pull requests but more than that I can't promise. I gave you rights to do push and if you are motivated to keep this project alive, we can also transfer the whole repository to you.

We at the Mysema are using Clojure as our weapon of choice, so maintaining Scala tools is quite low on priority.

mangolas pushed a commit that referenced this pull request Apr 23, 2015
Change artifactId to the normal scala version naming convention
@mangolas mangolas merged commit eb90da4 into timowest:master Apr 23, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants