Photoshop Element 7 not working with Babylon 8

I recently added Babylon 8 to my software.  I use it a lot as well as Elements 7 in my work.  Element 7 worked fine when I had Babylon 7 but when I upgraded to Babylon 8 Photoshop Element 7 stopped working.  Any ideas as to why and how to fix?

You seem to have done most of the recommended troubleshooting procedures with FCP 7.
All I can suggest is that you create a new User Account in System Preferences and try to install it under that.
As you know, FCP 7 is now 4 years old (prehistoric in computer years) and was discontinued two years ago when Apple stopped supporting it, so there is little wonder that problems are arising with the latest OS, which can only get worse as the OS is updated.
The alternatives are to move to something like Premiere Pro, if you  prefer a traditional interface/workflow or get Final Cut Pro X if you want to have cutting edge 21st. century technology supported by Apple.

Similar Messages

  • Photoshop Elements not working with Yosemite

    After upgrading OS to Yosemite I could not get Photoshop Elements 11 to work properly - sluggish operation and brushes not working.  I upgraded to Elements 13 but it gets sluggish as time passes and some of the filters don't work.  It is frustrating to say the least as I do lots of photo processing and it just takes too long now.  Can anybody help?

    Hi,
    We sincerely apologize for the problem customers are facing while using a trackpad with Photoshop Elements 11 & 12 on Mac OSX 10.10 (Yosemite).
    We have been actively working with Apple to resolve this problem as quickly as possible. We're hopeful this will get completely resolved in an upcoming update of Yosemite(MAC 10.10).
    In the meanwhile, you have two options to work around this problem:
    1. Option1: Use a mouse instead of the trackpad
    2. Option2: Install a plug-in which should workaround the problem
    Plug-in installation instructions:
    1. Close Photoshop Elements
    2. Download this zip file to a location you can easily find (e.g. your desktop)
    3. Unzip the file, WhiteWindowWorkaround.plugin, and move it to the Plug-In folder:
    • For Elements 12 – //Applications/Adobe Photoshop Elements 12/Support Files/Plug-Ins/
    • For Elements 11 - //Applications/Adobe Photoshop Elements 11/Support Files/Plug-Ins/
    You can verify the plug-in is installed by launching the Photoshop Elements Editor and choosing Help > System Info... Scroll to the bottom of the text in the dialog and look for the plug-in name "WhiteWindowWorkaround.plugin".
    Note: This plugin is a temporary workaround and should be used until this issue is addressed in Mac OSX 10.10 (Yosemite). Please remove this plugin once the issue is officially resolved by Apple.
    If you are using a stylus in conjunction with a trackpad, you might see issues with your trackpad. Workaround in this particular case is to use mouse instead of the trackpad.
    Hope this helps!
    Regards,
    vaishali

  • Will Photoshop Elements 10 work with Microsoft 8.1 operating system?

    When selecting the option e-mail from the Elements Organizer to share a picture, the program stops with a note from Elements Organizer stating they could not finish creating the e-mail message. I never experienced this problem when it was operating in my older computer running on Windows XP.  Will Photoshop Elements 10 work with Windows 8.1?

    Depends on what e-mail client you're using. I believe that for W8 you need to install the Windows 7 version of Windows Live Mail.
    Cheers,
    Neale
    Insanity is hereditary, you get it from your children
    If this post or another user's post resolves the original issue, please mark the posts as correct and/or helpful accordingly. This helps other users with similar trouble get answers to their questions quicker. Thanks.

  • I keep trying to download Photoshop CS3 and a get a 404 error page, does Photoshop CS3 not working with a new Mac operating system?

    I keep trying to download Photoshop CS3 and a get a 404 error page, does Photoshop CS3 not working with a new Mac operating system?

    you must also use a browser that allows cookies.  try a different browser or download from adobe.com
    Downloads available:
    Suites and Programs:  CC 2014 | CC | CS6 | CS5.5 | CS5 | CS4 | CS3
    Acrobat:  XI, X | 9,8 | 9 standard
    Premiere Elements:  12 | 11, 10 | 9, 8, 7
    Photoshop Elements:  12 | 11, 10 | 9,8,7
    Lightroom:  5.5 (win), 5.5 (mac) | 5.4 (win), 5.4 (mac) | 5 | 4 | 3
    Captivate:  8 | 7 | 6 | 5
    Contribute:  CS5 | CS4, CS3
    Download and installation help for Adobe links
    Download and installation help for Prodesigntools links are listed on most linked pages.  They are critical; especially steps 1, 2 and 3.  If you click a link that does not have those steps listed, open a second window using the Lightroom 3 link to see those 'Important Instructions'.

  • Can Photoshop Element 9 work with Lightroom 5?

    Can Photoshop Element 9 work with Photoshop Lightroom 5?

    Hi David_B,
    Thanks for your reply! I've installed PS many times (since version 3, I think), and nothing like this has ever happened. I use and teach PS and LR for a living. The tech person I spoke with told me it is not unusual to have this happen when upgrading to CC 2014.
    What happened is that PS CC2014 would not open the image in PS if I used the Photo>Edit In>PS 2014 command unless I used Photo>Edit In>Open as Smart Object. Once opened as a smart object, PS would not save the file. I think it said Error 2.
    The tech took control of my computer, removed PS and LR and all the associated files a few times. He told me I'd have to have a high level person help me, but they didn't call me, so I phoned in. After waiting an hour to get to the correct person (not a high level tech) he said he'd have to uninstall everything again and start over and that it would take over an hour. I don't have the time right now to fix it as I'm headed out of town until the end of the month to teach LR.
    In the meantime, LR works, but I'm using a trial version that expires in 30 days. It exports to PS ok, but I had to reload all my plug-ins, and apparently LR can't find Photomatix. LR is not installed in my usual applications folder - the tech put it on my system backup drive.
    My case number is: 185696477
    Thanks so much for your willingness to help!
    Terry

  • Does photoshop elements 13 work with windows vista?

    I have V10 and a Windows Vista PC that is fast and paid for,
    Thinking of purchasing new software from Adobe.
    Does photoshop elements 13 work with Windows Vista?

    No. Windows 7 or Windows 8.x only.
    System requirements | Adobe Photoshop Elements

  • Hello, Will Photoshop Elements 6 work with Windows 7?

    Will Photoshop Elements 6 work with Windows 7?
    Thankyou,
    Julie

    PSE6 would install and work on windows 7 fine. There might be some issues where application interacts with OS, so you can expect some issues in OS dialog boxes that are opened in application like import dialog box.

  • Will Photoshop Elements 12 work with Mac OS X v10.9.4? Need to make sure before opening package... Thanks!

    Will Photoshop Elements 12 work with Mac OS X v10.9.4? I need to make sure before opening package... Thanks in advance!

    Yes, PSE versions 6 through 12 work in 10.9, although PSE 11 is a bit buggy. All other versions are fine, including PSE 12.

  • Photoshop CS5 not working with Lucida Grande Regular font

    On my iMac Intel Core 2 Duo 2.66 GHz, I am running OS 10.6.7.
    When using Photoshop CS5, if I try to use the font, Lucida Grande Regular, it causes an error.
    "Could not use the type tool because of a program error."
    When I try to open an existing file that has type layers that include the font Lucida Grande Regular, Photoshop will not open the file. I have several of these files that I want to use. I can open them on another Macintosh and everything works fine.
    First I get a message window that says, " Some text layers might need to be updated before they can be used for vector based output. Do you want to update these layers now?" I click on update and then get the following message. "Could not complete your request because of a program error."
    I have updated Photoshop CS5 to the latest version, 12.0.4.
    I have run the FontTest.jsx script and it shows an error for Lucida Grande Regular.
    (IOError: General Photoshop error occurred. This functionality may not be available in this version of Photoshop.
    - <no additional information available>)
    The other 100+ fonts on my machine did not create errors.
    Since Lucida Grande Regular is an essential font for Mac OS X, I re-installed OS 10.6 in order to have a new version of Lucida Grande Regular. After that re-install I am having the same problems with the font not working in Photoshop.
    It also does not work with Adobe InDesign CS5. The font does work in Microsoft Word.
    The program Font Book verifies Lucida Grande Regular.
    Other fonts including, Lucida Grande Bold, work fine in Photoshop and InDesign.
    What can I do to get Photoshop CS5 to work with Lucida Grande Regular?

    Wow, I'm so glad I found this thread. This problem has been dogging me for years, and it's so sporadic that I've been afraid of breathing the wrong way lest I somehow incur that diabolical Program Error dialog. I'd managed to reach a truce with Photoshop CS5, getting it into a barely working state, and avoiding all updates... until Lion came along today. Then I updated to CS5 12.0.4, and the Program Errors were back again.
    Now I see that the problem does seem to be related to the Lucida Grande font. If there's a layer with that font in it, not only can I not edit that text, but I can't marquee select anything, nor drag any shapes. Deleting caches and massaging fonts are completely ineffectual measures... but if I delete the Lucida layers entirely, we're back in business.
    At least so far.
    Funny to think that of all the innovations I'd like to see Photoshop adopt, the fixing of this one issue is the thing I'd like to see most. I'll be keeping my eye on this thread, and any updates by Mr. Cox.

  • New Mac: Why are CC and Photoshop Elements not working when Lightroom and Reader are fine

    Last week I changed computers (swapping an old Mac for a 13-in MacBook Pro Retina running OSX Yosemite 10.10.3. I copied all my data over to the new machine using Migration Assistant.
    All programs work fine (including my copy of Lightroom 3 and Reader XI). But my CC and Photoshop Elements 10 do not. I have tried uninstalling both, but whenever I try to reinstall PE10 from its disk or download it just stops almost at the end. I then I get an "initiation failed" message, along with a request to download the now defunct "Support Advisor" app!
    I cannot download Adobe Application Manager, or the CC desktop app either - for the former I get an "initiation failed" message, along with the "download Support Advisor" app" message again! For the latter I get a message saying "Adobe Creative Cloud Is Needed to Resolve this problem - however it is missing or damaged." Then I get a message and a link to download Creative Cloud. Then when I've downloaded it and I click on the installer... it runs for a bit and then I get the message again: "Adobe Creative Cloud Is Needed to Resolve this problem - however it is missing or damaged." And I get a prompt and link to download the CC app. Guess what happens next? And so it goes on. And on and on, in a tedious circle.
    This is incredibly annoying and frustrating as I have work to do! Anyone have any ideas what's happening?
    Cheers
    K

    do not use migration to install adobe programs.
    you should uninstall and clean whatever you've done, Use the CC Cleaner Tool to solve installation problems | CC, CS3-CS6
    then dl the cc desktop app to your new computer and use it to install your adobe cc programs, Download Adobe Creative Cloud apps | Free Adobe CC trial
    if you have non-subscription adobe programs, use the installation files for them:
    Downloadable installation files available:
    Suites and Programs:  CC 2014 | CC | CS6 | CS5.5 | CS5 | CS4, CS4 Web Standard | CS3
    Acrobat:  XI, X | 9,8 | 9 standard
    Premiere Elements:  13 | 12 | 11, 10 | 9, 8, 7 win | 8 mac | 7 mac
    Photoshop Elements:  13 |12 | 11, 10 | 9,8,7 win | 8 mac | 7 mac
    Lightroom:  5.7.1| 5 | 4 | 3
    Captivate:  8 | 7 | 6 | 5.5, 5 | 1
    Contribute:  CS5 | CS4, CS3 | 3,2
    FrameMaker:  12, 11, 10, 9, 8, 7.2
    Download and installation help for Adobe links
    Download and installation help for Prodesigntools links are listed on most linked pages.  They are critical; especially steps 1, 2 and 3.  If you click a link that does not have those steps listed, open a second window using the Lightroom 3 link to see those 'Important Instructions'.

  • Can Photoshop Elements 12 work with Photoshop Premiere 13?

    I already have Photoshop Elements 12 and was bought Premiere 13 for xmas and they are not recognising each other. Each keep asking if I want to download the trial version of each? I dont know if you can use Photoshop Elements 12 with Photoshop Premiere 13 so I downloaded the trial version of Photoshop Elements 13 to see if they would work together but they dont. I am trying to do a slideshow in Photoshop Elements 12 and when it comes to the output I want to put it onto a DVD and give it as a present. It does say to transfer to Photoshop Premier (which I have on my wondows 8 computer) but when I click on the link to transfer, it only gives me the option to trial it? And I already have it?

    jasperthesiamese
    Several key factors here....the new Elements Organizer 13  is markedly different than Elements Organizer 12. The Elements Organizer/Create/Slideshow of version 12 and earlier is gone and is replaced by Elements Organizer with different slideshow opportunities very much unlike what you have in 12.
    Photoshop Elements and Premiere Elements integration comes with the same version of the programs on the same computer. But, there are special considerations in this case since we are dealing with a new Elements Organizer in 13.
    However, if you want to salvage your already made Elements Organizer 12 slideshow project and open it in Elements Organizer 13, it is possible. You can also get 1080p and 720p slideshow out of it. You know that already if you have Premiere Elements 13 and its Elements Organizer 13. If interested in this salvage...on to Elements Organizer 12 catalog conversion in Elements Organizer 13.
    Elements Organizer 13
    File Menu
    Manage Catalogs
    Catalog Manager and hit its Convert Button
    In the dialog that opens, look for the name of the Elements Organizer 12 catalog.... Convert Button
    The converted Elements Organizer 12 catalog should open in Elements Organizer 13.
    When you go to double click the slideshow thumbnail (Slide Show Project) in the converted catalog in Elements Organizer 13, Elements Organizer 13 wants to convert the slideshow into the format of its new slideshow feature there. You should see
    Once the converted Slideshow opens, you will see opportunities for Edit, Save, Export including options to Play or Exit.
    If you want to get that converted slideshow into Premiere Elements, then you export to 1080p or 720p and then bring that into
    the Premiere Elements 13 Editor using Add Media/FIles and Folders.
    Please review and let me know if I have targeted your questions.
    Thank you.
    ATR

  • Photoshop Elements not working right after not using for several months?

    Have Photoelements #10 on this computer. Have been away, using #10 on another computer, now back and PhotoElements #10 is NOT working properly?

    Hi,
    Please try couple of probable solutions as mentioned below:
    Solution 1:
    1. Close Elements.
    2. Launch the Photoshop Elements Welcome Screen and hold down ctrl + alt + shift as you click Editor.
    3. Continue to hold the keys until you see a message box asking if you want to delete Photoshop Elements settings file; click Yes. Elements will open with default preferences.
    Solution 2: In case any network printer is attached try to launch without network or printer uninstall or make different printer as default.
    Solution 3: Try launching with anti-virus off or removing PSE from conflicting list.
    Solution 4:
    On the drive on which you have installed PSE,on my machine it is on C:
    Go  to C:\Program Files\Adobe\Photoshop Elements  10\Locales\<locale>\Plug-Ins\Import-Exportand you will find twain  plug-in. Remove that plug-in from that location and copy it somewhere  else.
    Now launch PSE and check if it works.
    For related post for Twain please see this:http://forums.adobe.com/message/2954743#2954743
    Thanks,
    Garry

  • Does Photoshop Elements 11 work with Windows 8.1?

    Hi,
    Recently got a new pc as old one died.  Installed Adobe Premiere Elements 11 and Adobe Photoshop Elements 11,   put in my serial numbers.   Premiere seems to work.   Photoshop organizer seems to work.
    Photoshop Editor won't open any photos to edit.  Not a one.  Not any different type.   Not if I  "Open as" a "RAW" as others here have suggested.
    I've uninstalled and reinstalled the program.  Nothing.
    I contacted chat support and they refused to help me on version 11 as its "only supported by the community".   Great. 
    Is there a compatibility issue?    Is there something else I am missing?
    Your help would be greatly appreciated.

    You are much more likely to get answers about Elements issues in the Elements forums.
    So I've moved your posted from the Photoshop forum to the Elements forum.

  • Installing the patch to make adobe photoshop elements 9 work with windows 7 computer

    Adobe Photoshop Elements 9 has been installed in our new computer with windows 7.However, we can not get pictures to download from our digital camera into
    the new computer. A computer tech tried to do this several times and each time it said the "patch" had been installed correctly, connecting camera and computer program, but then it would suddenly say the patch install had failed. Has anyone encountered this problem and found the solution?

    Hello brokelynn,
    How impatient are they expressed in  kilo$$   - and what's on those photos  ;-))
    I can not clearly understand:
    - have you updated to windows 7 - or just updated windows 7 to the newest patches?
    - what do you mean by: I tried adding some actions
       - did you add some entries under actions - or do you use just tags named something like ^actions^?
       -> where you successful to do that, or went something wrong while doing this?
    Regards
    Thomas
    ps: maybe you want to try what I described here: http://forums.adobe.com/message/5751885#5751885

  • Wlcompile - nested javac elements not working with ant 1.6.1

    Hi
    I have a problem with Ant 1.6.1 and wlcompile.
    I get the following error: The <wlcompile> type doesn’t support the nested “javac”
    element.
    Heres the error msg I get in debug mode:
    BUILD FAILED
    C:\P2Development\dev\testing\test.xml:3: The <wlcompile> type doesn't support
    the nested "javac" element.
         at org.apache.tools.ant.IntrospectionHelper.throwNotSupported(IntrospectionHelper.java:573)
         at org.apache.tools.ant.IntrospectionHelper.getNestedCreator(IntrospectionHelper.java:624)
         at org.apache.tools.ant.IntrospectionHelper.getElementCreator(IntrospectionHelper.java:691)
         at org.apache.tools.ant.UnknownElement.handleChild(UnknownElement.java:529)
         at org.apache.tools.ant.UnknownElement.handleChildren(UnknownElement.java:320)
         at org.apache.tools.ant.UnknownElement.configure(UnknownElement.java:176)
         at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:152)
         at org.apache.tools.ant.Task.perform(Task.java:363)
         at org.apache.tools.ant.Target.execute(Target.java:301)
         at org.apache.tools.ant.Target.performTasks(Target.java:328)
         at org.apache.tools.ant.Project.executeTarget(Project.java:1215)
         at org.apache.tools.ant.Project.executeTargets(Project.java:1063)
         at org.apache.tools.ant.Main.runBuild(Main.java:632)
         at org.apache.tools.ant.Main.startAnt(Main.java:183)
         at org.apache.tools.ant.launch.Launcher.run(Launcher.java:197)
         at org.apache.tools.ant.launch.Launcher.main(Launcher.java:56)
    I’m using windows 2000. I’ve tried with weblogic.jar from Weblogic Server 8.1
    SP1 and SP2. I’ve tried with JDK 1.4.1_02 and 1.4.2_04. If I’m using Ant 1.5.3
    then everything works perfectly.
    I’ve tried to remove the WLS included Ant version to avoid conflicts with Ant
    1.6.1 and Ant 1.5.3 (that comes with Weblogic server). I’ve tried to uninstall
    Weblogic Server and just keep weblogic.jar, but I still get the same error. I’ve
    tried to put weblogic.jar on the classpath, still not working. I’ve tried to remove
    all jar files from $ANT_HOME/lib except those jar files needed to run my test
    project - ant.jar and ant-launcher.jar, but still doesn’t work. If I change $ANT_HOME
    to Ant 1.5.3 and run Ant 1.5.3 then everything works. So it seems to have something
    to do with Ant 1.6.1.
    Here’s my example code:
    <project name="wlcompile_test" default="test" basedir=".">
         <target name="test" depends="init">
    <wlcompile srcdir="${src.dir}" destdir="${build.dir}">
    <javac debug="${build.debuginfo}" debuglevel="${build.debuglevel}"
    nowarn="${build.nowarn}" deprecation="${build.deprecated}" source="${build.source.version}"/>
    </wlcompile>
         </target>
    <target name="clean" depends="init">
    <delete dir="${build.dir}"/>
    </target>
    <target name="init">
    <taskdef name="wlcompile" classname="weblogic.ant.taskdefs.build.WLCompileTask"
    classpath="C:\P2Development\weblogic.jar"/>
    <property name="src.dir" value="src"/>
    <property name="build.dir" value="classes"/>
    <property name="build.compiler" value="modern"/>
    <property name="build.compiler.pedantic" value="true"/>
    <property name="build.debuginfo" value="true"/>
    <property name="build.debuglevel" value="lines,vars,source"/>
    <property name="build.deprecated" value="false"/>
    <property name="build.nowarn" value="off"/>
    <property name="build.source.version" value="1.4"/>
    <mkdir dir="${build.dir}"/>
    </target>
    </project>
    And I try to run “ant test”
    It doesn’t work with Ant 1.6.1 and weblogic.jar from WLS 8.1 SP1 and SP2. But
    it works perfectly if I change to Ant 1.5.3.
    Here’s a link to the Ant wlcompile task documentation from BEA:
    http://e-docs.bea.com/wls/docs81/programming/environment.html#1098348
    Regards,
    Tobias Wallter

    Yes, this one is fixed in 8.1 SP3. If you need a patch before then,
    contact [email protected] and reference CR136493.
    -- Rob
    Tobias Wallter wrote:
    Hi
    I have a problem with Ant 1.6.1 and wlcompile.
    I get the following error: The <wlcompile> type doesn?t support the nested ?javac?
    element.
    Heres the error msg I get in debug mode:
    BUILD FAILED
    C:\P2Development\dev\testing\test.xml:3: The <wlcompile> type doesn't support
    the nested "javac" element.
         at org.apache.tools.ant.IntrospectionHelper.throwNotSupported(IntrospectionHelper.java:573)
         at org.apache.tools.ant.IntrospectionHelper.getNestedCreator(IntrospectionHelper.java:624)
         at org.apache.tools.ant.IntrospectionHelper.getElementCreator(IntrospectionHelper.java:691)
         at org.apache.tools.ant.UnknownElement.handleChild(UnknownElement.java:529)
         at org.apache.tools.ant.UnknownElement.handleChildren(UnknownElement.java:320)
         at org.apache.tools.ant.UnknownElement.configure(UnknownElement.java:176)
         at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:152)
         at org.apache.tools.ant.Task.perform(Task.java:363)
         at org.apache.tools.ant.Target.execute(Target.java:301)
         at org.apache.tools.ant.Target.performTasks(Target.java:328)
         at org.apache.tools.ant.Project.executeTarget(Project.java:1215)
         at org.apache.tools.ant.Project.executeTargets(Project.java:1063)
         at org.apache.tools.ant.Main.runBuild(Main.java:632)
         at org.apache.tools.ant.Main.startAnt(Main.java:183)
         at org.apache.tools.ant.launch.Launcher.run(Launcher.java:197)
         at org.apache.tools.ant.launch.Launcher.main(Launcher.java:56)
    I?m using windows 2000. I?ve tried with weblogic.jar from Weblogic Server 8.1
    SP1 and SP2. I?ve tried with JDK 1.4.1_02 and 1.4.2_04. If I?m using Ant 1.5.3
    then everything works perfectly.
    I?ve tried to remove the WLS included Ant version to avoid conflicts with Ant
    1.6.1 and Ant 1.5.3 (that comes with Weblogic server). I?ve tried to uninstall
    Weblogic Server and just keep weblogic.jar, but I still get the same error. I?ve
    tried to put weblogic.jar on the classpath, still not working. I?ve tried to remove
    all jar files from $ANT_HOME/lib except those jar files needed to run my test
    project - ant.jar and ant-launcher.jar, but still doesn?t work. If I change $ANT_HOME
    to Ant 1.5.3 and run Ant 1.5.3 then everything works. So it seems to have something
    to do with Ant 1.6.1.
    Here?s my example code:
    <project name="wlcompile_test" default="test" basedir=".">
         <target name="test" depends="init">
    <wlcompile srcdir="${src.dir}" destdir="${build.dir}">
    <javac debug="${build.debuginfo}" debuglevel="${build.debuglevel}"
    nowarn="${build.nowarn}" deprecation="${build.deprecated}" source="${build.source.version}"/>
    </wlcompile>
         </target>
    <target name="clean" depends="init">
    <delete dir="${build.dir}"/>
    </target>
    <target name="init">
    <taskdef name="wlcompile" classname="weblogic.ant.taskdefs.build.WLCompileTask"
    classpath="C:\P2Development\weblogic.jar"/>
    <property name="src.dir" value="src"/>
    <property name="build.dir" value="classes"/>
    <property name="build.compiler" value="modern"/>
    <property name="build.compiler.pedantic" value="true"/>
    <property name="build.debuginfo" value="true"/>
    <property name="build.debuglevel" value="lines,vars,source"/>
    <property name="build.deprecated" value="false"/>
    <property name="build.nowarn" value="off"/>
    <property name="build.source.version" value="1.4"/>
    <mkdir dir="${build.dir}"/>
    </target>
    </project>
    And I try to run ?ant test?
    It doesn?t work with Ant 1.6.1 and weblogic.jar from WLS 8.1 SP1 and SP2. But
    it works perfectly if I change to Ant 1.5.3.
    Here?s a link to the Ant wlcompile task documentation from BEA:
    http://e-docs.bea.com/wls/docs81/programming/environment.html#1098348
    Regards,
    Tobias Wallter

Maybe you are looking for