In a multimodule project you need to attach the site descriptor of parent poms to the reactor.
Thus the site descriptor you attach will depend on your profile... Thus you are in a maven anti-pattern (ie artifacts attached to the reactor should not depend on the profiles active at the time) You will likely have to find a different way, as I believe the rest if the maven developers will agree with me that this is a bad plan, and hence there will not be support for trying to solve your actual problem with the technique that us giving you thus problem HTH Stephen On Friday, 24 January 2014, Benjamin Damm <bd...@silverspringnet.com> wrote: > Hello Mavens, > > Is there a way to rename site.xml to something else? I want to use the > site framework to produce two "trees" of sites, each quite distinct from > each other because they are based on two different profiles, and I was > hoping, two different site.xml from the superpom at the top. > > In other words, I'm trying to achieve two trees of sites, each with a > different site.xml at the top, but otherwise retaining the same structure > (in terms of modules). I also plan to use profiles to use different > site.xml files at the module level; that part works fine already because I > can repoint the entire site document structure by using siteDirectory. > > It's the site.xml at the very top that's giving me trouble. No matter > what I seem to do, I can only have one site.xml at the top of the module > hierarchy. Does anyone know if there's a way around this limitation? > Scouring the source code of the site plugin has so far not revealed > anything. > > Thank you, > -Ben > > -- > Benjamin Damm > Silver Spring Networks > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org <javascript:;> > For additional commands, e-mail: users-h...@maven.apache.org<javascript:;> > > -- Sent from my phone
