On Tue, Dec 8, 2009 at 9:22 PM, henrib <hen...@apache.org> wrote: > > > > Niall Pemberton wrote: >> >> .... >> I don't really under stand the "commons-parent pom is just above >> jexl's trunk" comment as in our subversion hierarchy its not *above* >> and the only way it can find it is by downloading/installing in your >> local repo in the usual manner - unless you've put it there >> specifically? >> ... >> > It is installed in the local repository but if I dont put it "physically" > above (../jexl where jexl is the trunk itself), the site is not generated > correctly.
Sounds to me like you don't have commons-parent installed in your local m2 repository - which would explain all this. Niall > Niall Pemberton wrote: >> >> Also I don't understand what you mean by "...rc publishing fails later >> when the site is regenerated from what was published" - I guess this >> is using the release plugin? Or is it something else? >> > > Correct, this is using the release plugin. In the publication process, the > uploaded source is re-downloaded, and regenerates the build (if I did > understand correctly). This regenerated build does not end up looking the > same because which I believe is caused by the failure to find the parent > pom. > There is actually a warning at the beginning of the build stating so. > -- > View this message in context: > http://n4.nabble.com/Using-maven-2-on-non-MSFT-platform-to-build-JEXL-tp955440p955671.html > Sent from the Commons - Dev mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
