I have a post-build action that runs Sonar analysis on our projects. I can't say that I know whether this worked before since we have very few multi-module projects but after the release:perform phase when doing a Maven release, it updates and checks in the POMs with the next DEV version and then immediately calls the Sonar action. When Sonar attempts to run, it can't find some JAR's that are part of the multi-module project because it actually hasn't done a build yet for the new DEV version.
Am I doing something wrong or is this a problem with the release process or am I missing something simple? -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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.
