Hi,
We have a standard maven multi module layout, like this :
project
- - -project-external-api (1.2.1-SNAPSHOT) -> contains wsdl and stubs of
external client needed by the project
- - -project-core (1.2.1-SNAPSHOT) -> core of the project
- - -project-ws (1.2.1-SNAPSHOT) -> webapp of the project
- - -project-ws-api (1.2.1-SNAPSHOT) -> wsdl exposed by the project
- pom.xml (1.2.1-SNAPSHOT)
the root pom.xml references the 3 modules :
<modules>
<module>project-external-api</module>
<module>project-core</module>
<module>project-ws-api</module>
<module>project-ws</module>
</modules>
We would like to make a new release of the project, but there's a problem
: project-external-api and and project-ws-api haven't changed since the
last release...
what should we do ?
1) mvn release on the root pom.xml, that will tag and release the full
directory, even if some projects haven't changed
2) mvn release only on the project-ws pom and project-core...but we will
first have to manually change the dependencies versions
3) change the modules of the root pom.xml, so that it will only build and
release project-ws and project-core...but we will first have to manually
change the dependencies versions, and the project-external-api and
project-ws-api will have their parents still pointing to the 1.2.1-SNAPHSOT
root pom.xml
any other idea ?
What are the best practices for this kind of situation ? have we missed
something in maven multi modules setup ?
Thanxs for your help
Max
