Versions Compared

Old Version 17

changes.mady.by.user Daniel Keir Haywood

Saved on

compared with

New Version Current

changes.mady.by.user Daniel Keir Haywood

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

-D modules=

applib

core

runtimes

progmodel

profilestores

security

viewer

release

support

examples

skin

clean install?

-D build=full?

site-deploy?

-D site=full?

Description

standard

Y

Y

Y

Y

Y

Y

Y

 

 

 

 

 

Y

Y

Y

The standard set for a smoke test; if this builds we're probably ok. In fact, are also modules that make up the site, ie mvn site-deploy

all

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

 

 

 

Every module that can be built using mvn clean install. Can't necessarily be deployed, though; see 'Deployability' section below

skin

 

 

 

 

 

 

 

 

 

 

Y

Y

Y

 

 

Prereq for running site-deploy

applib

Y

 

 

 

 

 

 

 

 

 

 

Y

Y

Y

Y

Just the applib module

core

 

Y

 

 

 

 

 

 

 

 

 

Y

Y

Y

Y

Just the core modules

runtimes

 

 

Y

 

 

 

 

 

 

 

 

Y

Y

Y

Y

Just the runtime implementations

progmodel

 

 

 

Y

 

 

 

 

 

 

 

Y

Y

Y

Y

Just the progmodel implementations

profilestores

 

 

 

 

Y

 

 

 

 

 

 

Y

Y

Y

Y

Just the profilestore implementations

security

 

 

 

 

 

Y

 

 

 

 

 

Y

Y

Y

Y

Just the security implementations

viewers

 

 

 

 

 

 

Y

 

 

 

 

Y

Y

Y

Y

Just the viewer modules.

release

 

 

 

 

 

 

 

Y

 

 

 

Y

Y

Y

Y

Just the release modules.

support

 

 

 

 

 

 

 

 

Y

 

 

Y

 

 

 

Just the support modules.

examples

 

 

 

 

 

 

 

 

 

Y

 

Y

Y

 

 

Just the examples modules.

Notes:

  • most profiles that support mvn clean install also support -D build=full (basically, also builds Javadoc JARs). The exception is any profile that includes the 'release' module (we hit problems building javadoc for 'release'; it also doesn't really make sense).
  • similarly, most profiles supporting mvn site-deploy also support -D site=full (basically, full reports, Javadoc, JXR, metrics, code coverage etc). The exception again is those profiles including 'release'
  • the prereqs to building the site are (a) to build the skin, and (b) to install the JIMI package into the local repo using mvn install:install-file -D groupId=com.java -D artifactId=jimi -D version=1.0 -D packaging=jar -D file=/path/to/file
  • running site-deploy also requires specifying where to deploy to. To deploy locally, use -D deploy=local, which will deploy to /tmp/m2-sites/isis.

Typical Use Cases

The first time you run these, you'll need to omit the -o (offline) flag in order to download plugins and dependencies. Thereafter though the -o flag is strongly recommended!

...