ICEfaces
  1. ICEfaces
  2. ICE-7063

The bundle process for ICEfaces EE 2 cannot complete on Windows

    Details

    • Workaround Exists:
      Yes
    • Workaround Description:
      Run the bundle procedure on a non-Windows machine

      Description

      The bundle targets will eventually fail when run on a Windows box due to:

         [delete] Deleting directory C:\svn\repo\icefaces-ee2\trunk\icefaces-ee\bundle\ICEfaces-EE-2.0.0.Beta-bin\icefaces\lib\myfaces

         [delete] Deleting directory C:\svn\repo\icefaces-ee2\trunk\icefaces-ee\bundle\ICEfaces-EE-2.0.0.Beta-bin\icefaces\ace

      BUILD FAILED

      C:\svn\repo\icefaces-ee2\trunk\icefaces-ee\build.xml:53: The following error occurred while executing this line:
      C:\svn\repo\icefaces-ee2\trunk\icefaces-ee\build.xml:183: The following error occurred while executing this line:
      C:\svn\repo\icefaces-ee2\trunk\icefaces-ee\icefaces\build.xml:101: The following error occurred while executing this line:
      C:\svn\repo\icefaces-ee2\trunk\icefaces-ee\icefaces\build.xml:190: Unable to delete file C:\svn\repo\icefaces-ee2\trunk\icefaces-ee\bundle\ICEfaces-EE-2.0.0.Beta-bin\icefaces\ace\tools\smartsprites\smartsprites-0.3.0-dev.jar

        Activity

        Hide
        Deryk Sinotte added a comment -

        The theory was that, during the bundling process, the smartsprites.jar was added to the classpath to actually execute a process to generate the sprites After Googling a bit, I found this forum entry that likely explains what is going on:

        http://www.coderanch.com/t/108053/tools/unable-delete-or-rename-old

        "If you use any classpath in any target of your build on your Windows machine,
        you should never try to delete any of the jars that are used in these classpaths
        at any time later during this Ant build because all the jars remain locked. "

        So if the smartsprites.jar is being used on the classpath to actually "do" something, we can't delete it on Windows.

        Show
        Deryk Sinotte added a comment - The theory was that, during the bundling process, the smartsprites.jar was added to the classpath to actually execute a process to generate the sprites After Googling a bit, I found this forum entry that likely explains what is going on: http://www.coderanch.com/t/108053/tools/unable-delete-or-rename-old "If you use any classpath in any target of your build on your Windows machine, you should never try to delete any of the jars that are used in these classpaths at any time later during this Ant build because all the jars remain locked. " So if the smartsprites.jar is being used on the classpath to actually "do" something, we can't delete it on Windows.
        Hide
        Deryk Sinotte added a comment -

        I've adjusted the line (both trunk and maintenance branch) where we delete the "ace" directory for the ICEfaces binary bundle so that it doesn't fail when it gets an error. This way is should continue to work the same on non-Window machines. For Windows bundles, the "ace" directory will remain behind (but can be removed manually if required).

        <delete dir="$

        {bundle.dir.bin}

        /ace" failonerror="false"/>

        Show
        Deryk Sinotte added a comment - I've adjusted the line (both trunk and maintenance branch) where we delete the "ace" directory for the ICEfaces binary bundle so that it doesn't fail when it gets an error. This way is should continue to work the same on non-Window machines. For Windows bundles, the "ace" directory will remain behind (but can be removed manually if required). <delete dir="$ {bundle.dir.bin} /ace" failonerror="false"/>

          People

          • Assignee:
            Deryk Sinotte
            Reporter:
            Deryk Sinotte
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: