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

ValidationMessages.properties should not be included in terasoluna-gfw-common #256

Closed
making opened this issue Jan 26, 2015 · 0 comments
Closed
Milestone

Comments

@making
Copy link
Contributor

making commented Jan 26, 2015

As default behavior, multiple ValidationMessages.properties are not available. So, ValidationMessages.properties under terasoluna-gfw-comons can be an obstacle to users.

http://stackoverflow.com/questions/11719198/read-several-validationmessages-properties-from-classpath

ValidationMessages.properties should be moved to blank project.

This issues is related to https://github.com/terasolunaorg/guideline/issues/648

@making making added this to the 1.0.2 milestone Jan 26, 2015
making added a commit that referenced this issue Jan 26, 2015
…onMessages

Moved ValidationMessages.properties to test resources #256
making added a commit that referenced this issue Jan 26, 2015
…onMessages

Moved ValidationMessages.properties to test resources #256
@making making closed this as completed Jan 26, 2015
@btshimizukza btshimizukza changed the title ValidationMessages.properties should not be included in terasoluna-gfw-comons ValidationMessages.properties should not be included in terasoluna-gfw-common Jan 29, 2015
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