Page Comparison

...

First set up a Maven .settings profile with property values applicable to your environment.  The following example shows a nightly build toward the 3.x nightly build 1 release of Power Edition with both the Messaging and Analytics optional modules purchased:

...
<servers>
  <server>
    <id>NEXUS_ID</id>
    <username>MY_NEXUS_USERNAME</username>
    <password>MY_NEXUS_PASSWORD</password>
  </server>
</servers>


<profile>
  <id>smartgwt</id>
  <properties>
    <version>3.x<1</version>
    <edition>power</edition>
    <build>nightly</build>
    <messaging>true</messaging>
    <analytics>true</analytics>
    <isc.username>MY_ISOMORPHIC_ACCOUNT_USERNAME</isc.username>
    <isc.password>MY_ISOMORPHIC_ACCOUNT_PASSWORD</isc.password>
    <repo.id>NEXUS_ID</repo.id>
    <repo.url>MY_NEXUS_REPO_URL</repo.url>
  </properties>
</profile>

...

You can override these settings on the command line.  For example, this would download and deploy the 2.5 Power Edition release build instead of the 3.x 1 nightly build as shown in the .settings file above, then deploy it to the central corporate repo (if you have one):

...

This would install the 2011-12-02 nightly of 3.0.x 1 on my workstation (i.e., my local maven cache) for evaluation in my private workspace (e.g., when I want to check whether or not some bug has been resolved) before I deploy to my corporate repo:

mvn clean install -Psmartgwt -Dversion=3.0.1 -Ddate=2011-12-02

Deploy the 3.x 0.1 2011-12-02 build to the central corporate Maven repo once it's been verified.  Since "clean" isn't specified as a goal, this won't download the package from SmartClient.com again since it was already installed locally:

mvn deploy -Psmartgwt -Dversion=3.0.1 -Ddate=2011-12-02

Notes

The build figures out where to get your downloads based on version, edition, build, and date properties.  You could figure out which values to use by looking over the hyperlinks available from the  The version numbering scheme you see on the Download page/s might be a bit unfamiliar to you, but to help you alongmostly you should be able to use the following examples as your guide:

1. The version property should always take the form major.minor[.revision] for release builds (-Dbuild=release).  e.g., 2.5 | 2.5.1 | 3.0For nightly builds (-Dbuild=nightly), the version property should take the form of the appropriate Isomorphic codeline3.0 | 3.0.1.
2. GA releases work just the way you'd expect.  -Dversion=3.0 -Dbuild=release gets you the 3.0 GA build.
3. Isomorphic nightly builds always take major.minor form.  e.g., At release version there is no nightly build named 3.0.1.  Only 3.0p, which holds the current mainline is at 3.x.  The release line is at contents of the current release line at a point in time.  Said differently, the URL for progress toward a 3.0.2 patch release will be the same as it was during development of the the 3.0.x.  So So to have a look at progress being made toward a 3.1 release as of 12/19/2011, for example, use -Drelease=nightly 1 release.  So
   1. If for example the current production release is 3.0 and you want the nightly build from the mainline (the 'bleeding edge' 3.1 feature release), use -Dbuild=nightly -Dversion=3.x 1 -Ddate=2011-12-19To have a look at progress being made toward a 02
   2. If what you want instead is a nightly build of the 3.0.1 patch release (bug fixes only), use -Dbuild=nightly, -Dversion=3.0.x -Drelease=nightly -1, -Ddate=2011-12-1902
4. The date property is applicable to nightly builds only.

...