|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Ok, so the actual problem here is that description.properties is being compiled to Java at all; with the Maven HPI plugin this does not happen.
No localizer output needs to be generated for this case; when the Jelly view is rendered, it seems to use the description.properties file directly.
For Maven builds, the plugin parent POM explicitly sets the fileMask property to Messages.properties, so that only files matching that pattern will be considered by the localizer: https://github.com/jenkinsci/jenkins/blob/54af1e0/plugins/pom.xml#L114-L129
It seems that the org.jvnet.localizer.GeneratorTask used by the Gradle JPI plugin's LocalizerTask doesn't have a fileMask property (though it does extend MatchingTask, so it should be possible to set the includes or excludes.
So I think the simplest solution would be if the Gradle JPI plugin set the includes property by default to the value **/Messages.properties.