|
||||||||
|
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/groups/opt_out.
Sure Tony,
In my maven builds there is a "modules" section under "configure" the issue was these modules pointed to a directory that didn't exist, and that's what it was trying to read the pom.xml from (so the pom.xml didn't exist either) and instead of throwing a file not found jenkins complains about POM_PACKAGING being null.
When I deleted a module, it forced jenkins to grab everything (including the pom) from version control again, and so pom.xml was present again and POM_PACKAGING wasn't null anymore.
Hope this helps.