On Fri, Mar 10, 2017 at 8:53 AM, paul b <pblake...@gmail.com> wrote: > I have several projects that are multi module projects that are like the > following > > Project1 > +-module1 > +-pom.xml > +-module2 > +-pom.xml > > Each project is configuration controlled in git as their own project > > Now, I have created a parent project with the following flat structure. > This is because I would like to keep each project with its own git project. > That seems sensible for me???
A basic rule for deciding where you should separate things into their own git repository is whether the two things need to be built together. If they need to be built together, then keep them in the same repository. The structure you've defined is not "sensible". > Parent > +-pom.xml > Project1 > +-module1 > +-pom.xml > +-module2 > +-pom.xml > > Project2 > +-module1 > +-pom.xml > +-module2 > +-pom.xml > > The parent pom references each project like the following > > <modules> > <module>../project1</module> > <module>../project2</module> > </modules> > > This is fine as per maven documentation and all works ok locally but when I > build this from Jenkins I run into issues. This is because Jenkins cant > find the pom file for each project. Basically this is down to the flat > directory structure! Is there any way in Jenkins that I can get over this > issue? Fix the problem in your repository structure, not in Jenkins. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAA5t8VoW1Xy6Bsxh1QEqqH%3DE0gePLkjM8CVe3254qT-85vy%3D6Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
