On 07/04/2010, at 11:09 AM, Andrew Hughes wrote: > I tried that and it failed.... however I *think* there is another reason for > this not working... > > I have > ./pom.xml (organization pom, with site.xml skin== acme-maven-site-skin > e.t.a...) > ./acme-maven-site-skin/pom.xml (this is the actual jar skin module) > > The reactor build order "install site" *appears *to try and build > 1. parent (install) > 2. parent (site) > 3. acme-maven-site-skin (install) > 4. acme-maven-site-skin (site) > > This fails at #2 because "acme-maven-site-skin (install)" has not been > executed yet and the skin is not in the repository. > > Is it weird/wrong that I have a skin as a module under the organization pom?
No, but it's weird to build the site for the org. POM and skin. Take a look at that sample project I pointed to and the structure - you'll see the skin is referenced from the documentation and the modules, but not the parent of the skin to avoid this conflict. That's where the site is run from, to ensure you don't build useless sites for things like the parent POM and skin. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
