Yeah, it didn't work :'( I've just moved the site out into it's own entirely isolated module/repository, with no parent.
I've done a snapshot deploy with positive results :) Thanks Brett :) On Wed, Apr 7, 2010 at 2:47 PM, Brett Porter <[email protected]> wrote: > That sounds bizarre. You said organization, which is generally a parent > with no modules. If that's the case, why ever run the site goal on there? > > If you have modules and its actually the root of a multi-module build, then > you can't change the type. > > This may well work for you, but it's bound to cause some confusion down the > track. I'm not sure what your release patterns will look like. > > On 07/04/2010, at 2:57 PM, Andrew Hughes wrote: > > > Thanks Brett :) > > > > I got a workaround by making the "oganization" pom the skin, by: > > > > <type>jar</> > > then I moved all of the ./acme-maven-site-skin/src/main/resources into > the > > parent (../). This effectively makes the organization pom also the maven > > site skin. > > > > In my case there might not be any draw backs > > > > > > On Wed, Apr 7, 2010 at 11:21 AM, Brett Porter <[email protected]> wrote: > > > >> > >> 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 > >> [email protected] > >> http://brettporter.wordpress.com/ > >> > >> > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > -- > Brett Porter > [email protected] > http://brettporter.wordpress.com/ > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
