Problems with aggregator is that it imposes the structure of your projects. I
would like to put my projects sources as I want and not as Maven aggregator
wants.
Another problem with aggregator is when a project is used within several
others projects (common dependencies). In this case, under which aggregator
sources should be put? Just one? What about if this aggregator does not need
to be released, but another project needs this common dependency to be
released. Put it in all projects
Another way to make it would be to change the way modules are managed. Not
use physical path but artifact coordinates.
Instead of
<modules>
<module>module1</module>
<module>../../module2</module>
...
</modules>
we would have
<modules>
<module>
<groupId>com.mycompany</groupId>
<artifactId>module1</artifactId>
<version>${project.version}</version>
</module>
...
</modules>
But this might duplicate dependencies information. So why don't release
according to dependencies directly?
--
View this message in context:
http://maven.40175.n5.nabble.com/Relesa-a-project-and-all-its-snapshot-dependencies-without-an-aggregator-tp4527536p4527637.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
