-
Notifications
You must be signed in to change notification settings - Fork 473
Providing explicit support for Groovy source code (fixes #13) #94
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
952fe05
Providing explicit support for Groovy source code (fixes #13)
fvgh 9635398
SkipFilesNamed's equality is based on its serialized representation. …
nedtwigg 0628870
Fixed some grammar and spelling errors in README. Also gave each sec…
nedtwigg dbfb2c3
Reduced visibility of GroovyExtension.NAME and EXCLUDE_JAVA_DEFAULT.
nedtwigg 115b987
Improved formatting for the gradle plugin README block.
nedtwigg c8377d1
Publish ext-greclipse 2.3.0.
nedtwigg 97f06c3
Now that greclipse is in jcenter, we can strip out the snapshot stuff.
nedtwigg 196c29d
Added a workaround for the new varargs ambiguity for GroovyExtension …
nedtwigg 4eac44d
Supporting dedicated configuration for groovy source.
fvgh b9c1358
Fixed greclipseFormat ping/pong. Provided proposal for format.
fvgh 4becbed
Fixes according to review by @jbduncan (as far as possible, using the…
fvgh cdf45fc
As agreed in previous review: Femoval of unnecessary '\f'
fvgh 25d57ad
Fixed description/values of Groovy-Eclipse configuration example and …
fvgh b24bf3f
Make GroovyDefaultTargetTest platform independent. Focus on the subje…
fvgh 8fd9a2f
Changed excludeJava to use the same idiom we use for paddedCell().
nedtwigg cc69b88
ext-greclipse is now in mavenCentral, so the tests can be against mav…
nedtwigg f6c1c7a
Rather than copy-pasting JavaExtension.LICENSE_HEADER_DELIMITER, we c…
nedtwigg d78a2b6
Renamed greclipseFormat to just greclipse.
nedtwigg 5a863b9
Minor corrections to groovy section of plugin-gradle/README.md
nedtwigg 027892f
Update changelog and congratulate Frank on his contribution!!
nedtwigg File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
This is naaasty. Here's a better way, maybe:
The advantage of this approach is it gets all of our DSL on the
Optional version argument -> config builder
pattern. The downside is it deprecates our main usecase for the sole purpose of accommodating the multiple-config-file-in-groovy usecase.I'm inclined to avoid the question altogether by only allowing a single config file for both JavaExtension and GroovyExtension. It makes the docs simpler, and users can always concatenate groovy settings themselves. @fvgh how much will this limitation hurt GroovyExtension users?
I'm open to the deprecation path discussed above, but I don't have the time to do the proper testing, update the docs, etc.
@fvgh on an unrelated note, your ext-spotless-greclipse is in jcenter, but not mavencentral. I'm gonna wait til we're sure we've got it right to sync to mavencentral.
Uh oh!
There was an error while loading. Please reload this page.
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.
How about replacing format file varargs...
...with two separate single-argument and iterable versions?
...or a version where we require at least one format file?
Uh oh!
There was an error while loading. Please reload this page.
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.
greclipseFormatFile 'mycfg1.prop', 'mycfg2.prop'
. This will break all of your workarounds, I believe. It also breaks the workaround I've implemented in the previous commit.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.
I can see how it would break my single-arg-and-iterable workaround, but not for my other one.
I'm not really familiar with Groovy, but if it were Java, I believe this would be syntactically correct if used with my latter workaround:
Uh oh!
There was an error while loading. Please reload this page.
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.
Unless, are we thinking of "breakage" in terms of "
'mycfg1.prop'
will still be interpreted as thegreclipseVersion
rather than the 1stgreclipseFormatFile
"? (In which case, I'd agree.)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.
My example above is from the README (loosely).