Cool.... I think we could get away with a simple warring of target/docs as a goal, and as per this one, you guys could customise with a preGoal.
Sounds reasonable? -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers James CE Johnson <[EMAIL PROTECTED]> wrote on 26/08/2002 02:21:57 AM: > [EMAIL PROTECTED] wrote: > > >James CE Johnson <[EMAIL PROTECTED]> wrote on 26/08/2002 01:27:36 AM: > > > > > > > >>[EMAIL PROTECTED] wrote: > >>Moving [webapp]-war.xml out of ${maven.conf.dir} will cause us to make a > >> > >> > >>few minor changes but nothing drastic. I'll probably end up creating a > >>src/site/... to keep the site's jboss-web.xml and web.xml files and > >> > >> > >whatnot. > > > > > >>I was just wondering if someone else might already be doing this kind of > >> > >> > >>thing and we could use it instead of using our home-grown solution. > >> > >> > > > >Not yet, but I like the idea to capture the project state in a single file > >(WAR) that can be archived somewhere. > > > >A few questions on the goal you're using: > > > >| <copy file="${maven.conf.dir}/site-web.xml" > >| tofile="${webapp.test.dir}/${maven.id}-site.war/WEB-INF/web.xml"/> > >Is web.xml necessary? > > > > Probably not for most folks but our project isn't a public project so we > have to password-protect even the project docs site :-( > > >| <copy file="${maven.conf.dir}/site-jboss-web.xml" > >| tofile="${webapp.test.dir}/${maven.id}-site.war/WEB-INF/jboss-web.xml"/> > >JBoss's customised web.xml, right - what's in it? > > > > For the docs site, only this: > > <jboss-web> > > <!-- Use the JaasSecurityMgr other security domain for > authentication and authorization of secured web content. --> > <security-domain>java:/jaas/other</security-domain> > > </jboss-web> > > For the actual application we also define references to datasources & > other j2ee muck. > > >| <copy file="${maven.conf.dir}/tests-config.xml" > >| > >tofile="${webapp.test.dir}/${maven.id}-site.war/WEB-INF/classes/config.xml"/> > >What do you use this one for? > > > > We have a Configuration singleton for application-specific stuff. In the > past we polluted web.xml with a bunch of config stuff coming in as > servlet or global parameters. About half-way through that project we > realized how gross it had become and began moving things out but it was > too late. This time, we're keeping web.xml "pure" and putting the > app-specific stuff in our custom config.xml. I'm not entirely sure why > we're putting it in the docs site though... Probably a mistake. > > > > >| <copy > >todir="${webapp.test.dir}/${maven.id}-site.war/WEB-INF/classes"> > >| <fileset dir="${maven.conf.dir}" > >|includes="users.properties,roles.properties"/> > >Ditto..? > > > > Those define usernames/passwords/roles to JBoss for very basic secuity. > > > > -- > To unsubscribe, e-mail: <mailto:turbine-maven-user- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:turbine-maven-user- > [EMAIL PROTECTED]> >
