On Monday 08 March 2004 21:17, Leo Sutic wrote:
> What error messages do you get? I managed to build fortress/container
> just fine when I did the release.

Not sure if you can call it an "error message", more like instructions "do 
this".... (see below)

The http://nagoya.apache.org/wiki/apachewiki.cgi?MavenForrestPlugin says;

<quote>
Installing the plugin
dead easy! 

1) install maven-beta-9 or later, if you don't have it yet 2) install the 
plugin 

 wget 
http://lsd.student.utwente.nl/repository/forrest/jars/maven-forrest-plugin-1.1.jar 
$MAVEN_HOME/plugins/
</quote>

And the 
http://lsd.student.utwente.nl/repository/forrest/jars/maven-forrest-plugin-1.1.jar 
URL doesn't resolve anymore.


Niclas
 

[EMAIL PROTECTED] container]$ maven
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0-beta-10

avalon:info:
avalon:header:
    [echo]
            __
           /  \    Apache
          /    \__________________________________
         /  /\  \  \/  /    \ |  |  /   \|   \|  |
        /  /  \  \    /  /\  \|  |_|  O  |  \ \  |
       /__/    \__\__/__/  \__\_____\__ /|__|\___|     Build System


    [echo]
    Requirements
    ============

    To build, you need maven-beta-9 or later and the latest version
    of the maven-forrest-plugin installed. To install it, copy the
    contents of the xml-forrest directory into forrest cvs, then
    follow the instructions at

    http://nagoya.apache.org/wiki/apachewiki.cgi?MavenForrestPlugin

    under "building the plugin yourself".

    Building a single component
    ===========================

    Change into the component's subdirectory, and use maven as normal.
    Common usage includes:

        maven java:jar      # builds the jar
        maven site          # builds the website, including javadocs
        maven dist          # builds source and binary distributions

    Building all components
    =======================

    Change into the main avalon directory and use one of the goals
    listed below. A maven reactor will be started
    to build all components. Available goals:

        maven avalon:jars      # builds all jars
        maven avalon:site      # builds the website, including javadocs
        maven avalon:dist      # builds source and binary distributions


    Special goals
    =============

    These are nonstandard goals available from the main avalon
    directory:

        maven avalon:info
            # echo the documentation you're reading now

        maven avalon:seed
            # create a new component; see below for more info

        maven avalon:write-gump-module.xml
            # create a module descriptor for gump; see below for more info

    Creating a distribution
    =======================

    All project.xml files normally specify a <version></version> ending in
    '-dev'. When building files to upload to www.apache.org/dist,
    you should override this. To do so, pass in an override.version
    property:

        maven -Doverride.version=1.3 dist

    Now, manually inspect the generated distributions to make sure
    they are correct. Drop them into a few environments (a cocoon
    installation, a phoenix installation, etc) and make sure everything
    still works as normal.

    Next, you should sign releases using PGP. See

        http://nagoya.apache.org/wiki/apachewiki.cgi?SigningReleases

    for documentation on how to do so. This is not an optional step:
    the build will assure further on that there are .asc files for
    every release.

    Once you are satisfied that the release is correct, you need to
    upload the file to the official avalon distribution location.
    This requires an SSH account on the daedalus.apache.org
    installation, a working 'scp' command on your path, and a running
    ssh-agent (like the ssh-agent program that comes with OpenSSH or
    the Pageant utility that comes with Putty) so you do not have to
    enter your SSH key password.
    To upload the files, run the 'avalon:deploy' target inside
    the component subdirectory, again making sure to override the
    version:

        maven -Doverride.version=1.3 avalon:deploy

    If your username on the daedalus.apache.org machine is not the same
    as your local username, you can override it using the
    'maven.username' variable:

        maven -Doverride.version=1.3 -Dmaven.username=johndoe avalon:deploy

    In addition to uploading the distributions, this will also result
    in a file named target/announcement-1.3.txt, containing an auto-
    generated announcement for sending to mailing lists. If you want
    to have the announcement sent to [EMAIL PROTECTED] and
    [EMAIL PROTECTED] automatically, use
    '-Dsend.announce=true':

        maven -Doverride.version=1.3 -Dsend.announce=true avalon:deploy

    If this is not an official distribution yet, but a release
    candidate, you will want to override the directory on the server
    where the files are sent to (normally
    /www/www.apache.org/dist/avalon/). To do so, specify the
    'remote.dist.dir' property:

        maven -Doverride.version=1.3 
-Dremote.dist.dir=~/public_html/release-candidates avalon:deploy

    Summary:

        maven dist -Doverride.version=1.3
            ### now check and test distributions ###
        cd target/distributions
        for i in *.zip; \
            do gpg --output i.asc --detach-sig --armor i; \
        done
        cd ../..
        maven -Doverride.version=1.3 \
            -Dsend.announce=true avalon:deploy

    For a little more info about building distributions, try

        maven avalon:dist-sign

    which will output the commands you need to use. Unfortunately,
    you'll still really have to do that manually.

    Adding a new component
    ======================

    The easiest way to get a new component set up is the
    'avalon:seed' goal. This will generate a skeleton project for
    you. You need to specify a few properties:

        component.name      the human-readable name for your component
        component.id        the artifact id used for your component's
                            build artifacts (jar files, zip files, etc)
        component.dir       the name of the directory to put the
                            component in
        use.forrest         'false' if you want to use the regular
                            maven xdoc plugin rather than the forrest
                            plugin for handling your xdocs

    Example:

        maven -Dcomponent.name=My-Component \
            -Dcomponent.id=my-component \
            -Dcomponent.dir=mycomponent \
            avalon:seed

    Note that existing files in the specified directory will *not*
    be replaced. So if you are converting an existing component to
    build using maven, you will need to remove any existing ant
    build.xml file, for example.

    Gump integration
    ================

    Since gump cannot directly call maven, this script contains
    functionality for generating basic ant buildfiles as well as gump
    descriptors.

    When you call the 'avalon:seed' goal, a build.xml file is
    generated for you which can be called from gump. Since Gump handles
    classpath management, there is no need to do so in the buildfile,
    keeping it nice and simple.

    Once you have added dependency information to your project.xml
    file, change into the component subdirectory and run the
    'avalon:seed-gump' target. You have to specify the
    component.dir property once again. This will generate a file
    gump-integration/project/.xml that contains a gump
    descriptor for your component.

    Example:

        cd mycomponent
        maven avalon:seed-gump
            -Dcomponent.dir=mycomponent

    After creating this descriptor, you still need to reference it from
    the gump module descriptor at

        gump-integration/project/avalon.xml

    One way to do this is to autogenerate the file based on the
    contents of the 'gump-integration/project' directory:

        cd ~/cvs/avalon/buildsystem
        maven avalon:seed-gump-module

    Note this won't work if the file mentioned above already exists.

    As an alternative, you can call

        maven avalon:setup-gump

    inside the repo base directory, but this will result in
    corrupt gump definitions because the component.dir is then
    not properly set.

BUILD SUCCESSFUL
Total time:  5 seconds
-- 
+---------//-------------------+
|   http://www.bali.ac         |
|  http://niclas.hedhman.org   |
+------//----------------------+

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to