-
-
Notifications
You must be signed in to change notification settings - Fork 957
#14729 - Corrupt Jar & War Files #14745
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
Changes from 22 commits
76258eb
2840260
e676573
d81908d
a7afb88
3e93a26
10220b5
275654c
f48b76a
dd1a96d
88f123e
8a4414b
c5e4693
7e130b6
03ac9b2
ce686fe
7f68731
ef1bfc6
8f68c88
3105623
7241f65
faf6c12
25d0c1d
00e5a7b
9da8344
a121b8f
745f5d5
26732d7
649f1b4
562c070
1975eab
2c5701b
d760235
d4da849
9ec8a49
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -46,6 +46,12 @@ ext { | |
|
||
allprojects { | ||
repositories { | ||
// workaround for https://github.com/spring-gradle-plugins/dependency-management-plugin/issues/164 | ||
maven { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm starting to think we should ditch the Dependency Management Plugin, and only use Gradle Platforms. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I 100% agree but we need the ability for end users to easily set versions. I am debating whats better: ditch the dependency plugin inside of grails core or keep it to align with what end user apps use. If gradle platforms supported property overrides, I would have suggested we already switch. I came close to writing a Gradle plugin to just add this support too. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think property version overrides are a really good feature but when needed it can be accomplished with Gradle Platforms as well, only not as easily, as you have to declare the dependency you want to be able to override beforehand. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I still maintain we shouldn't use both in end user apps - we should one or the other. The property overrides make it very easy to set versions. We should discuss this more outside of this PR. |
||
name = 'localGrailsBom' | ||
url = file("$rootDir/grails-bom/build/repo") | ||
content { includeModule 'org.apache.grails', 'grails-bom' } | ||
} | ||
maven { url = 'https://repo.grails.org/grails/restricted' } | ||
// mavenLocal() // Keep, this will be uncommented and used by CI (groovy-joint-workflow) | ||
maven { url = 'https://repository.apache.org/content/groups/snapshots' } | ||
|
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
Uh oh!
There was an error while loading. Please reload this page.