The Incident Archive

Ojdeploy uses /jdev/bin/jdev.conf which in turn uses /ide/bin/ide.conf do any changes made here will make an impact on ojdeploy. If you want to add something to improve performance extra memory or different gc try changing these files and see if it makes any difference for you: Example: AddVMOption -Xmx3G AddVMOption -Xms1G AddVMOption -Xgc:throughput Also I have found when using an ant task to call ojdeploy the less you invoke it the better the performance - so I guess an exec with a buildfile would work the fastest. - yet to take metrics so don't quote me on this just yet...

Real DOCS:  http://docs.oracle.com/cd/E26098_01/user.1112/e17455/deploying_apps.htm#OJDUG645 OJDeploy Documentation if you run it from the command line - I keep looking for this so I though I would post it here so I remeber. Oracle JDeveloper Deploy 11.1.2.1.0.6081 Copyright (c) 2003, 2010, Oracle and/or its affiliates. All rights reserved. Usage:   ojdeploy -profile <name> -workspace <jws> [ -project <name> ] [ <options> ]   ojdeploy -buildfile <ojbuild.xml> [ <options> ]   ojdeploy -buildfileschema Arguments:   -profile               the name of the Profile to deploy   -workspace      full path to the JDeveloper Workspace file(.jws)   -project              name of the JDeveloper Project within the .jws where the Profile can be...