nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

iwodcmd vs. iwodstart

gwen1

Should iwodcmd start be the recommended way to trigger all deployments? Or just ones that are heavily used? Is there any functionality lost by not using iwodstart? Will the java based commands eventually not be available?

Thanks,
Gwen

Find more posts tagged with

Comments

Migrateduser

There's no loss in functionality by going with the newer iwodcmd versus the older iwodstart. As your post suggests, iwodcmd is more light-weight since it doesn't incur the overhead of a JVM for the command line tool.

The implementation technology for future command line tools isn't known, but backward compatibility should be maintained.

Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com