You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by le...@apache.org on 2003/05/31 00:48:37 UTC

cvs commit: avalon-excalibur maven-common.xml

leosimons    2003/05/30 15:48:37

  Modified:    .        maven-common.xml
  Log:
  basic doc generation support
  
  Revision  Changes    Path
  1.2       +45 -0     avalon-excalibur/maven-common.xml
  
  Index: maven-common.xml
  ===================================================================
  RCS file: /home/cvs/avalon-excalibur/maven-common.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- maven-common.xml	30 May 2003 22:13:11 -0000	1.1
  +++ maven-common.xml	30 May 2003 22:48:36 -0000	1.2
  @@ -29,4 +29,49 @@
               ----------------------------------------------------------------
           </echo>
       </goal>
  +
  +    <!-- ==========================================================
  +          Doc Generation
  +         ==========================================================
  +
  +         For now, I've just copy-pasted the relevant snippets from
  +         the ant build that call forrest. We need a forrest plugin.
  +
  +         ========================================================== -->
  +
  +    <postGoal name="xdoc">
  +        <attainGoal name="forrest:generate"/>
  +    </postGoal>
  +
  +    <property file="${user.home}/build.properties"/>
  +    <property file="${basedir}/../ant.properties"/>
  +    <property file="${basedir}/ant.properties"/>
  +    <property file="${user.home}/.ant.properties"/>
  +    <property file="${basedir}/../libraries.properties"/>
  +    <property file="${basedir}/../default.properties"/>
  +    <property file="${basedir}/default.properties"/>
  +
  +    <goal name="forrest:docs" description="Transforms forrest docs">
  +
  +        <mkdir dir="${docs.dir}"/>
  +
  +        <ant antfile="${basedir}/../forrestbuild.xml"/>
  +
  +        <copy todir="${maven.build.dir}/docs/">
  +          <fileset dir="${build.docs}">
  +            <include name="**"/>
  +          </fileset>
  +        </copy>
  +
  +   </goal>
  +
  +    <!-- ==========================================================
  +          Cleanup of ant artifacts
  +         ========================================================== -->
  +
  +    <postGoal name="clean">
  +        <delete dir="${build.dir}"/>
  +        <delete dir="${dist.dir}"/>
  +    </postGoal>
  +
   </project>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@avalon.apache.org
For additional commands, e-mail: cvs-help@avalon.apache.org


Re: cvs commit: maven

Posted by Leo Simons <le...@apache.org>.
try this:

- install ant if needed
- install forrest if needed
- install maven beta-9 if needed
- update excalibur cvs
- change to avalon-excalibur/compatibility
- try 'maven test', 'maven xdoc', 'maven jar', 'maven dist'

that should work sort-of as expected. Still lots of work to do, but 
things are going smoother than expected. Of particular interest is the 
small size of maven.xml + project.xml for compatibility. Combined with 
the already available dependency info in the gump descriptor porting 
everything should be a snap this way.

I've sort-of enabled documentation building by having the generated 
forrest docs copied over the maven-generated docs. This means all maven 
project reports and stuff like that are available; you only need to link 
to them from the forrest book.xml or tab.xml file(s). This is kinda 
temporary until someone writes the much-discussed forrest plugin.

- Leo

leosimons@apache.org wrote:
> leosimons    2003/05/30 15:48:37
> 
>   Modified:    .        maven-common.xml



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org