What I would like to see is that when a project explicitly specifies
it's scm information, that m-release-p would treat that as a
separately releasable item... so that if you have an aggregator
project with no scm information, m-r-p would (perhaps with some
hinting) see that as not requiring a rele
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
I think you mis-understand how I am suggesting you use the aggregator pom
I am suggesting that you have a local aggregator pom one level up...
you don't need to check that pom out at all. You just use that pom
locally to group all the source you have checked out and construct a
reactor from th
> I am suggesting that you have a local aggregator pom one level up...
> you don't need to check that pom out at all. You just use that pom
> locally to group all the source you have checked out and construct a
> reactor from the checkout...
OK, but you have to write a pom just for the current re
enhancement request submitted: http://jira.codehaus.org/browse/MRELEASE-688
--
View this message in context:
http://maven.40175.n5.nabble.com/Relesa-a-project-and-all-its-snapshot-dependencies-without-an-aggregator-tp4527536p4530954.html
Sent from the Maven - Users mailing list archive at Nabble.
