redeploy strategy after using installer

[tabs.vs.spaces]

What is the strategy for redeploying changes after running the toro
installer? I am trying to add a new skin.

The directory that is built has build.xml (but build.properties is
empty) and pom.xml. I added tomcat.home and portal.webapp.home to
build.properties to get ant to work.

There are quite a few ant tasks available. I tried ant deploy-war,
hoping it would be the equivalent of uPortal's ant deploy, but this
gave me an error. (see below).

deploy-war:
Unresolvable reference ${maven.repo} might be a misuse of property
expansion syntax.

Suggestions?

[Nick]

See comments below.

On Nov 14, 2:04 pm, "tabs.vs.spaces" <tabs.vs.spa...@gmail.com> wrote:
> What is the strategy for redeploying changes after running the toro
> installer? I am trying to add a new skin.

Currently, there is no support for skin installation using the
installer. You would have to install skins the same way in uPortal.

>
> The directory that is built has build.xml (but build.properties is
> empty) and pom.xml. I added tomcat.home and portal.webapp.home to
> build.properties to get ant to work.

All the ant properties are inherited from ant.installer.properties.

>
> There are quite a few ant tasks available. I tried ant deploy-war,
> hoping it would be the equivalent of uPortal's ant deploy, but this
> gave me an error. (see below).

To run the installer from the command line from an exploded tmp
directory, you would run
ant -Dbasedir=.

The only target that should be run is the driver target, which has
conditional tasks based on the properties that are set in
ant.installer.properties.