I think that it is more sense to make the site as a separate module. does it take so much effort?
What do you think guys? Thanks; /Gurkan ________________________________ From: Mark Struberg <[email protected]> To: [email protected] Sent: Tuesday, January 20, 2009 2:48:00 PM Subject: Re: maven generated site - 1st try Some of them maintain a separate site module (also via maven) which is not part of the release process (manual site:deploy) LieGrue, strub --- Gurkan Erdogdu <[email protected]> schrieb am Di, 20.1.2009: > Von: Gurkan Erdogdu <[email protected]> > Betreff: Re: maven generated site - 1st try > An: [email protected] > Datum: Dienstag, 20. Januar 2009, 7:55 > Thanks Mark ! > > I will look at it this evening :) > > How other project are using the mvn:site for its different > versions? Maybe Matthias can help us on this . > Matthias, how do you use mvn:site within MyFaces project? > > Thanks; > > /Gurkan > > > > > ________________________________ > From: Mark Struberg <[email protected]> > To: [email protected] > Sent: Tuesday, January 20, 2009 2:05:03 AM > Subject: maven generated site - 1st try > > Hi! > > I'v committed the first version of a general > OpenWebBeans site maven configuration. > > You can find all the stuff under src/site > > simply run > $> mvn clean site > $> firefox target/site/index.html & > > This will take a few seconds since all modules and hence > also all impl test cases will run subsequently. > If you like to NOT run mvn nested then simply use > $> mvn -N clean site > > Don't be afraid, the links to the submodule sites do > not work locally, but only after being site:deploy ed. > So just imagine it and open > openwebbeans-impl/target/site/index.html manually ;) > > Any comments/wishes/slaps etc are welcome! > > Open discussion: how do we generally cope with multiple > versions of OpenWebBeans in the future? What about a 1.1 or > 1.2 Impl site concurrently? > > LieGrue, > strub
