Thanks to Alan @linaizhong for pointing this one out.
generate-github-travis-build-summary-with-grails.sh uses github repository name when constructing the grails plugin class name; that works OK only when the github repository name AND the app.name in application.properties are the same, for example:
github repo name
app.name
generated grails plugin name
ala-web-theme
ala-web-theme
AlaWebThemeGrailsPlugin.groovy
collectory-plugin
collectory
CollectoryPluginGrailsPlugin.groovy
Depending on in where/how the BASH script affected by this BUG was used it would build a wrong grails plugin file name (for example: CollectoryPluginGrailsPlugin.groovy) and fail all subsequent processing, like extracting the version number from the grails plugin file, etc.)
Solution is obvious: do not use github repository name; use the value extracted from app.name field in application.properties when building/creating the grails plugin file name; because that works always, regardless on the github repository name.
Thanks to Alan @linaizhong for pointing this one out.
generate-github-travis-build-summary-with-grails.sh uses github repository name when constructing the grails plugin class name; that works OK only when the github repository name AND the
app.name
inapplication.properties
are the same, for example:Depending on in where/how the
BASH
script affected by this BUG was used it would build a wrong grails plugin file name (for example: CollectoryPluginGrailsPlugin.groovy) and fail all subsequent processing, like extracting the version number from the grails plugin file, etc.)Solution is obvious: do not use github repository name; use the value extracted from
app.name
field inapplication.properties
when building/creating the grails plugin file name; because that works always, regardless on the github repository name.