1 Reply Latest reply: Apr 23, 2013 10:05 AM by vinaykumar2 RSS

    Error while using ant of webcenter spaces.

    vinaykumar2
      Hi All.

      I am using jdev 11.1.1.5 . we using webcenter spaces application.While doing clean stage of ant option , i got this error.


      BUILD FAILED
      C:\siemens_repositories\workspace_siemens_occ\dev\OCCDesignWebCenterSpaces\WebCenterSpacesExtensionLibrary\internal-targets.xml:54: Problem: failed to create task or type if
      Cause: The name is undefined.
      Action: Check the spelling.
      Action: Check that any custom tasks/types have been declared.
      Action: Check that any <presetdef>/<macrodef> declarations have taken place.


      Total time: 0 seconds


      ------------------------------------------------------------------------------------------------------------------------------


      build.xml is as below


      <?xml version="1.0" encoding="US-ASCII" ?>
      <project name="Portal" default="all" basedir=".">
      <!-- initialize properties for use by the build -->
      <property environment="env"/>
      <property file="build.properties"/>
      <tstamp/>

      <!-- define the ojdeploy ant task -->
      <taskdef name="ojdeploy"
      classname="oracle.jdeveloper.deploy.ant.OJDeployAntTask"
      uri="oraclelib:OJDeployAntTask"
      classpath="${oracle.jdeveloper.ant.library}"/>

      <target name="all" depends="deploy"/>

      <target name="clean">
      <delete includeemptydirs="true">
      <fileset dir="${oracle.jdeveloper.workspace.dir}" includes="**/deploy/**/*"/>
      <fileset dir="${oracle.jdeveloper.workspace.dir}" includes="**/classes/**/*"/>
      </delete>
      </target>

      <target name="deploy">
      <ora:ojdeploy xmlns:ora="oraclelib:OJDeployAntTask"
      executable="${oracle.jdeveloper.ojdeploy.path}"
      ora:buildscript="${oracle.jdeveloper.deploy.dir}/ojdeploy-build.xml"
      ora:statuslog="${oracle.jdeveloper.deploy.dir}/ojdeploy-statuslog.xml">
      <ora:deploy>
      <ora:parameter name="workspace"
      value="${oracle.jdeveloper.workspace.path}"/>
      <ora:parameter name="profile"
      value="${oracle.jdeveloper.deploy.profile.name}"/>
      </ora:deploy>
      </ora:ojdeploy>
      </target>
      </project>
        • 1. Re: Error while using ant of webcenter spaces.
          vinaykumar2
          i got the solution.the jdev version mismatch.and i used forward slash

          this is my config.properties

          #My properties
          #CUSTOMER - all properties need to be provided proper values
          #Fri Jul 30 00:00:00 PDT 2010
          ############ User Inputs Required ###################

          ## Enter the base directory where JDeveloper is installed.
          ## For example:
          ## On Windows, if JDeveloper is installed in the directory
          ## C:\MYJDEV, enter the path as: C:\\MYJDEV
          ## On Linux, if JDeveloper is installed in the directory /scratch/MYJDEV,
          ## enter the path as: /scratch/mywork/MYJDEV
          ## Note that the JDeveloper directory contains other folders such as jdeveloper,
          ## wlserver_10.3, modules, and so on.
          ####jdeveloper.install.home.directory=C:/Oracle/Middleware
          jdeveloper.install.home.directory=C:/Oracle/Middleware

          ## Enter the wlst executable
          ## For example:
          ## On Windows, wlst.cmd
          ## On Linux, wlst.sh
          #wlst.executable=wlst.cmd
          wlst.executable=wlst.cmd

          ## Enter the absolute path of the DesignWebCenterSpaces project.
          ## For example:
          ## On Windows, enter the path as:
          ## extending.spaces.home.dir=C:\\JDeveloper\\mywork\\DesignWebCenterSpaces
          ## On Linux, enter the path as:
          ## extending.spaces.home.dir=/scratch/mywork/DesignWebCenterSpaces
          ####extending.spaces.home.dir=C:/siemens/Tag_2.0.0.19/OCCDesignWebCenterSpaces
          extending.spaces.home.dir=C:/siemens_repositories/workspace_siemens_occ/dev/OCCDesignWebCenterSpaces

          ## Enter the path for ojdeploy executable
          ## For example:
          ## On Windows, enter the path as:
          ## oracle.jdeveloper.ojdeploy.path=${jdeveloper.install.home.directory}\\jdeveloper\\jdev\\bin\\ojdeploy.exe
          ## On Linux, enter the path as:
          ## oracle.jdeveloper.ojdeploy.path=${jdeveloper.install.home.directory}/jdeveloper/jdev/bin/ojdeploy
          #oracle.jdeveloper.ojdeploy.path=${jdeveloper.install.home.directory}\\jdeveloper\\jdev\\bin\\ojdeploy.exe
          oracle.jdeveloper.ojdeploy.path=${jdeveloper.install.home.directory}/jdeveloper/jdev/bin/ojdeploy.exe

          ## Enter the port number on which the WLS Administration Console is running.
          ## The URL of the Administration Console contains the port number.
          ## For example: http://myhost.com:7001/console
          ####wls.port=7001
          wls.port=7001


          ## Enter the host machine on which the Spaces application is running and where
          ## the custom shared library is to be deployed.
          ####wls.host=delvmpllsocc06.sapient.com
          #wls.host=yorke.med.siemens.de
          wls.host=192.168.0.93

          ## Enter the host and port number on which the Spaces application is running
          ## For example, if the Spaces application is running at: http://myhost.com:8888/webcenter
          ## wc.host=myhost.com, wc.port=8888, and wc.protocol=http
          ####wc.port=8888
          ####wc.host=delvmpllsocc06.sapient.com
          #wc.port=8887
          #wc.host=yorke.med.siemens.de


          ## Specify whether the Spaces URL protocol is http or https.
          wc.protocol=http

          ## For security purposes, administrator user name and password details
          ## are stored in secure files.
          ## Obtain the location of these secure files from your systems administrator
          ## or run WLST commands to generate these files as follows:
          ## 1. Navigate to: WC_ORACLE_HOME/common/bin
          ## 2. Enter the command: wlst.sh
          ## 3. At the WLST command prompt, connect to the Administration Server
          ## for Oracle WebCenter:
          ## connect('<admin_user>','<admin_pwd>', '<host>:<port>')
          ## Where admin_user is the user name of the administrator, admin_pwd is
          ## the administrator's password, host is the WebCenter instance, and port is
          ## the Administration Server port.
          ## 4. Run the following command to create a user configuration file and key file
          ## in a specified location:
          ## storeUserConfig('<userConfigFile>', <userKeyFile>')
          ## Where userConfigFile is the name and location of the file storing user details
          ## and userKeyFile is the name and location of the file storing passwords.
          ## For example:
          ## storeUserConfig('C:/myFiles/myuserconfigfile.secure', 'C:/myFiles/myuserkeyfile.secure')
          ## For example:
          ## On Windows, enter the path as:
          ## wls.userkey=C:\\JDeveloper\\mywork\\ps1userkeyfile.secure
          ## wls.userconfig=C:\\JDeveloper\\mywork\\ps1userconfigfile.secure
          ## On Linux, enter the path as:
          ## wls.userkey=/scratch/myfiles/ps1userkeyfile.secure
          ## wls.userconfig=/scratch/myfiles/ps1userconfigfile.secure
          ## Use the wls.userconfig property to set the userConfigFile path and
          ## the wls.userkey property to set the userKeyFile path.
          ####wls.userkey=C:/siemens/Tag_2.0.0.19/OCCDesignWebCenterSpaces/myuserkeyfile.secure
          ####wls.userconfig=C:/siemens/Tag_2.0.0.19/OCCDesignWebCenterSpaces/myuserconfigfile.secure
          wls.userkey=C:/siemens_repositories/workspace_siemens_occ/dev/OCCDesignWebCenterSpaces/keyfile.secure
          wls.userconfig=C:/siemens_repositories/workspace_siemens_occ/dev/OCCDesignWebCenterSpaces/config.secure



          ## Enter the targets on which the shared library is to be deployed.
          wls.target=WC_Spaces,AdminServer

          ## Enter the targets on which the webcenter.ear file is to be deployed.
          wls.webcenter.app.target=WC_Spaces

          ## Enter the name of the Spaces application (webcenter).
          ## Obtain this information from your systems administrator or from the
          ## WLS Administration Console as follows:
          ## 1. Login to WLS Administration Console.
          ## 2. Navigate to Deployments> webcenter>Overview
          ## The application's name displays here.
          webcenter.app.name=webcenter

          ## Use the restart.implementation.version.suffix property to override the next default
          ## implementation version number for your shared library.
          ## You can obtain the current implementation version from your
          ## systems administrator or from the WLS Administration Console as follows:
          ## 1. Login to WLS Administration Console.
          ## 2. Navigate to Deployments> [your-shared-library-name] >Overview
          ## The version number displays here. For example: 11.1.1.2.5
          ## The current implementation version is the last number, that is, 5 in this example.
          ## By default, the implementation version increments by 1 each time that you rebuild
          ## your shared library (using Run Ant Target>clean-stage).
          ## You can restart at a higher value if necessary. For example, if the current value is
          ## 11.1.1.2.20 and you want the next new version to be 11.1.1.2.41 rather than
          ## 11.1.1.2.21, do so by resetting the restart.implementation.version.suffix property to 40.
          ## Note:
          ## The first time you run Run Ant Target>clean-stage, the manifestImpl.properties file
          ## is created and the manifest.implementation.version property is set to
          ## 11.1.1.2.1. This initial version number is derived from the default.implementation.version
          ## set in build.properties (11.1.1.2) and appended with the restart.implementation.version.suffix property below.
          ## For example, if the restart.implementation.version.suffix is set to 1, the initial
          ## manifest.implementation.version will be 11.1.1.2.1.
          ## During subsequent builds, the restart.implementation.version.suffix and the lastNumber property
          ## in manifestImpl.properties are compared, and the higher of the two numbers is incremented by 1.
          ## If, for any reason, the manifestImpl.properties file is deleted, the file is recreated the next time
          ## that you run Run Ant Target>clean-stage, and the implementation version resets using the
          ## restart.implementation.version.suffix only (as if for the first time). For example, 11.1.1.2.1,
          ## if the restart.implementation.version.suffix=1
          ####restart.implementation.version.suffix=2
          ####restart.implementation.version.suffix.ear=2
          ###This change is probably not really necessary.
          restart.implementation.version.suffix=11.1.1.5
          restart.implementation.version.suffix.ear=11.1.1.5