Mailing-List: contact isis-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: isis-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of dkhaywood@gmail.com designates
 74.125.82.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:reply-to:organization:user-agent:mime-version
         :to:subject:content-type;
        b=Sx1qi8+6UQaUJGckyboQXLBjtoWYqlVuYuEUguvfQoHOY9lLVpb6qb7C1yDwccE+mo
         zaB3S6fMFDBlJdUxG2HROQiQGvZ64Ec7ACQWyAIJAt8tuVmuUWV7wjIotwaFZ1QcA9tU
         5QJ4fCAz/cUdz7wG/ImvGU+S4RfDOVDUqs+zk=
Message-ID: <4CD1A83C.4030502@gmail.com>
Date: Wed, 03 Nov 2010 18:21:48 +0000
From: Dan Haywood <dkhaywood@gmail.com>
Reply-To: dan@haywood-associates.co.uk
Organization: Haywood Associates Ltd.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
 rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: isis-dev@incubator.apache.org
Subject: slight change to way of doing build and site
Content-Type: multipart/mixed;
 boundary="------------000200000403040105030304"

--------------000200000403040105030304
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dear all,

As you know, our trunk/pom.xml currently has a set of profiles that us 
to perform builds of different "widths" (ie which modules), different 
"depths" (just the minimum, or full javadocs, reports etc), and 
different types (default lifecycle vs site lifecycle).  As things are, 
we use -P and a comma separated list to activate multiple profiles, eg 
-P all,build-all.

However, I've been looking at the release process that we've inherited 
from the ASF parent, and it looks like this approach of using -P is 
incompatible.  So, I've used the very similar mechanism of activating 
profiles by specifying a -D property.

Basically, to activate profile with id xxx-yyy, instead of -P xxx-yyy, 
you use -D xxx=yyy

~~~~
Therefore, the new ways to build are:

mvn clean install -o                                          # the 
modules-standard profile is activated by default
mvn clean install -D modules=standard -o    # explicitly activating the 
modules-standard profile
mvn clean install -D build=full -o                    # modules-standard 
and also the build-full profile
mvn clean install -D modules=all -o               # explicitly 
activating modules-all profile
mvn clean install -D modules=all -D build=full -o   # explicitly 
activating both modules-all and build-full


To build the site docs:

prereqs are pretty much as before:
a) mvn install:install-file -D groupId=com.java -D artifactId=jimi  -D 
version=1.0 -D packaging=jar -D file=/path/to/file
b) mvn clean install -D modules=skin -o     # explicitly activate the 
modules-skin profile

and then:
mvn site-deploy -D modules=standard -D deploy=local 
-o                     # activate modules-standard and deploy-local profile
mvn site-deploy -D modules=standard -D deploy=local -D site=full -o  # 
activate modules-standard,deploy-local, site-full


~~~~
All the above is also documented in trunk/pom.xml, which I've just this 
minute committed (rev 1030591).

Thx
Dan


--------------000200000403040105030304--