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

Remove scriptExtensions config option #46

Closed
keeganwitt opened this issue Aug 6, 2015 · 2 comments
Closed

Remove scriptExtensions config option #46

keeganwitt opened this issue Aug 6, 2015 · 2 comments
Assignees
Milestone

Comments

@keeganwitt
Copy link
Member

Instead having to make sure your <scriptExtensions> match what you declared in your <sources> when using a non-standard Groovy file extensions to get stubs to work, GMavenPlus should detect the extensions from the declared sources and automatically use those.

@keeganwitt keeganwitt self-assigned this Aug 6, 2015
@keeganwitt keeganwitt added this to the 1.6 milestone Aug 6, 2015
@keeganwitt
Copy link
Member Author

Obviously this is a breaking change for any builds using scriptExtensions.

keeganwitt added a commit that referenced this issue Aug 6, 2015
@keeganwitt
Copy link
Member Author

We are also inconsistent without this change because the compile mojo only accepts .groovy files, even though the stubs by default accept groovy, gvy, gy, and gsh files. These are obviously incompatible with each other, so the fact the stub generation is more generous is irrelevant.

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