-
Notifications
You must be signed in to change notification settings - Fork 38
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
Artifact name convention #24
Comments
That is not the convention in Grails 3 as far as I am aware. Other than for core plugins |
I thought so, and I also think its a good idea to distinguish the plugin artifact from dependencies to avoid naming collisions with artifacts. E.g. the joda-time jar has the same name, so the risk to have a naming clash is eminent:
Other plugins I use, have the said convention:
|
They can be distinguished by their group id, all plugins are published under the |
Yes, but if you create a war file, an artifact filename can clash with the plugin jar filename, or? |
The plugin artifact currently is named "joda-time-.jar".
Normally plugins use the convention
The text was updated successfully, but these errors were encountered: