-
-
Notifications
You must be signed in to change notification settings - Fork 23
Grails5 update #109
Grails5 update #109
Conversation
…resolution strategy
puneetbehl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In Gradle, api and implementation are two different configurations that you can use to declare dependencies in your build.gradle file for a Java or Grails project. They serve different purposes and have different visibility scopes, and understanding when to use each one is important for managing your project's dependencies effectively.
api:- Use for dependencies that are part of your module's public API.
- Accessible to other modules that depend on your module.
dependencies {
api 'com.example:public-library:1.0'
}implementation:- Use for internal dependencies not exposed to other modules.
- Not visible to modules that depend on your module.
dependencies {
implementation 'com.example:internal-library:1.0'
}- Example with both
apiandimplementation:
dependencies {
api 'com.example:public-library:1.0' // Public API dependency
implementation 'com.example:internal-library:1.0' // Internal dependency
}Using these configurations helps manage dependencies' visibility and reduces potential conflicts.
I would suggest to check out The Java Library Plugin documentation.
Explicitly cast to the `org.grails.datastore.mapping.config.Property` class
… into grails5-update
758e5af to
671e544
Compare
671e544 to
df6745a
Compare
|
@guillermocalvo Please resolve the conflicts |
|
@guillermocalvo Could you please take a look into this? |
Dependency scopes are fixed now
Update module to groovy 3, grails 5, compliance with stricter compiler