Here are some properties of dev-target install as distinct from target-* installs:
1. It contains source code for all the plugins.
2. It contains Sapphire plugins. This makes it possible to only load the plugins you want to work on into your workspace.
3. It will only be touched by commandline build if you invoke create-dev-target or another target that includes it (like quick-start). This makes it possible to leave your workspace open for many commandline build operations.
I do use target-* installs in a pinch, like when the command-line build is failing as the build will not get far enough to create dev-target in this situation (needs to finish building Sapphire).
On 09/14/2011 04:09 PM, Konstantin Komissarchik wrote:
> Here are some properties of dev-target install as distinct from target-*
> installs:
>
> 1. It contains source code for all the plugins.
> 2. It contains Sapphire plugins. This makes it possible to only load the
> plugins you want to work on into your workspace.
> 3. It will only be touched by commandline build if you invoke
> create-dev-target or another target that includes it (like quick-start).
> This makes it possible to leave your workspace open for many commandline
> build operations.
>
> I do use target-* installs in a pinch, like when the command-line build
> is failing as the build will not get far enough to create dev-target in
> this situation (needs to finish building Sapphire).
>
> - Konstantin
So if the dev-target is created properly during "ant clean-start" then
ideal target platfrom to use will be "dev-target" for all our Local
Sapphire build and development. Right ?