Barrie, Honestly, the purpose of my email about splitting the list was not to return attention to this thread :-)
You are correct that my thought process when I wrote that did not take into account the possibility of sparse checkouts. What I learned from that thread and other discussions was the following general principles: 1) Within a single aggregate project structure, .. pathnames may be used to share between modules. The release plugin checks out once at the top of the tree. 2) Across top level maven projects, .. pathnames are a very bad idea. Even if you arrange by some internal convention to always check out the same projects in the same relative locations, the release plugin will change the relative locations. 3) If you really want to share something across projects in a case (2), the local repository is the place to go. This is only worth it for very large resources that are prohibitively large/slow to unpack more than once. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
