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???
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?
--
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/f98e4736-188b-4a86-b036-b66ed140f420%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
