You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ant.apache.org by "Boring, Jeff W (N-Viper)" <je...@lmco.com> on 2009/08/18 16:05:34 UTC
Unable to delete file
We have a 20+ Java projects (Eclipse Projects) each with its own
build.xml. We group projects into components; every component has a
build.xml for building the projects in the component. The component
build.xml files are nothing more than ant (element) calls delegating to
the project builds. Finally, there is a simple master build.xml that
makes ant calls to the component build.xml files.
>From the master build.xml, a call to the first project build produces a
jar. This project build.xml can delete the jar but no other build.xml
can - always gets the "unable to delete file" message. Note that the
file CAN be deleted in windows. I've tried sleeping for 60 secs,
thinking something just needed time to clean out but that didn't work.
The compile & jar targets are listed below as is the ant diagnostics
report. Any help would be much appreciated.
Jeff
Jeff W. Boring
Lockheed Martin
<target name="compileProd" description="">
<echo message="Executing Compile Prod Target" />
<javac destdir="${build.production.dir}" fork="true" debug="on"
memorymaximumsize="256m">
<classpath path="${p.classpath}" />
<src path="${source.dir}"/>
</javac>
</target>
<target name="createProdArtifacts" description="Creates deployment
artifacts (jar/war)" >
<echo message="create Prod artifacts" />
<jar destfile="${basedir}/${local.artifact.filename}"
basedir="${build.production.dir}" />
</target>
[diagnostics] ------- Ant diagnostics report -------
[diagnostics] Apache Ant version 1.7.1 compiled on June 27 2008
[diagnostics]
[diagnostics] -------------------------------------------
[diagnostics] Implementation Version
[diagnostics] -------------------------------------------
[diagnostics] core tasks : 1.7.1
[diagnostics] optional tasks : not available
[diagnostics]
[diagnostics] -------------------------------------------
[diagnostics] ANT PROPERTIES
[diagnostics] -------------------------------------------
[diagnostics] ant.version: Apache Ant version 1.7.1 compiled on June 27
2008
[diagnostics] ant.java.version: 1.5
[diagnostics] ant.core.lib: D:\dev\lib\apache-ant-1.7.1\lib\ant.jar
[diagnostics] ant.home: D:\dev\lib\apache-ant-1.7.1
[diagnostics]
[diagnostics] -------------------------------------------
[diagnostics] ANT_HOME/lib jar listing
[diagnostics] -------------------------------------------
[diagnostics] ant.home: D:\dev\lib\apache-ant-1.7.1
[diagnostics] ant-antlr.jar (5752 bytes)
[diagnostics] ant-apache-bcel.jar (8611 bytes)
[diagnostics] ant-apache-bsf.jar (3939 bytes)
[diagnostics] ant-apache-log4j.jar (3056 bytes)
[diagnostics] ant-apache-oro.jar (39627 bytes)
[diagnostics] ant-apache-regexp.jar (3762 bytes)
[diagnostics] ant-apache-resolver.jar (4071 bytes)
[diagnostics] ant-commons-logging.jar (3910 bytes)
[diagnostics] ant-commons-net.jar (47026 bytes)
[diagnostics] ant-contrib.jar (194050 bytes)
[diagnostics] ant-jai.jar (21348 bytes)
[diagnostics] ant-javamail.jar (6998 bytes)
[diagnostics] ant-jdepend.jar (8132 bytes)
[diagnostics] ant-jmf.jar (6593 bytes)
[diagnostics] ant-jsch.jar (30797 bytes)
[diagnostics] ant-junit.jar (93518 bytes)
[diagnostics] ant-launcher.jar (12143 bytes)
[diagnostics] ant-netrexx.jar (9881 bytes)
[diagnostics] ant-nodeps.jar (431580 bytes)
[diagnostics] ant-starteam.jar (35355 bytes)
[diagnostics] ant-stylebook.jar (2330 bytes)
[diagnostics] ant-swing.jar (6738 bytes)
[diagnostics] ant-testutil.jar (14941 bytes)
[diagnostics] ant-trax.jar (6881 bytes)
[diagnostics] ant-weblogic.jar (14205 bytes)
[diagnostics] ant.jar (1323005 bytes)
[diagnostics] xercesImpl.jar (1223877 bytes)
[diagnostics] xml-apis.jar (194354 bytes)
[diagnostics]
[diagnostics] -------------------------------------------
[diagnostics] USER_HOME/.ant/lib jar listing
[diagnostics] -------------------------------------------
[diagnostics] user.home: d:\data\boringj
[diagnostics] No such directory.
[diagnostics]
[diagnostics] -------------------------------------------
[diagnostics] Tasks availability
[diagnostics] -------------------------------------------
[diagnostics] image : Missing dependency javax.media.jai.PlanarImage
[diagnostics] sshexec : Missing dependency com.jcraft.jsch.UserInfo
[diagnostics] scp : Missing dependency com.jcraft.jsch.UserInfo
[diagnostics] jdepend : Missing dependency jdepend.xmlui.JDepend
[diagnostics] A task being missing/unavailable should only matter if you
are trying to use it
[diagnostics]
[diagnostics] -------------------------------------------
[diagnostics] org.apache.env.Which diagnostics
[diagnostics] -------------------------------------------
[diagnostics] Not available.
[diagnostics] Download it at http://xml.apache.org/commons/
[diagnostics]
[diagnostics] -------------------------------------------
[diagnostics] XML Parser information
[diagnostics] -------------------------------------------
[diagnostics] XML Parser : org.apache.xerces.jaxp.SAXParserImpl
[diagnostics] XML Parser Location:
D:\dev\lib\apache-ant-1.7.1\lib\xercesImpl.jar
[diagnostics] Namespace-aware parser :
org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser
[diagnostics] Namespace-aware parser Location:
D:\dev\lib\apache-ant-1.7.1\lib\xercesImpl.jar
[diagnostics]
[diagnostics] -------------------------------------------
[diagnostics] System properties
[diagnostics] -------------------------------------------
[diagnostics] java.runtime.name : Java(TM) 2 Runtime Environment,
Standard Edition
[diagnostics] sun.boot.library.path : D:\bea\jdk150_06\jre\bin
[diagnostics] java.vm.version : 1.5.0_06-b05
[diagnostics] ant.library.dir : D:\dev\lib\apache-ant-1.7.1\lib
[diagnostics] java.vm.vendor : Sun Microsystems Inc.
[diagnostics] java.vendor.url : http://java.sun.com/
[diagnostics] path.separator : ;
[diagnostics] java.vm.name : Java HotSpot(TM) Client VM
[diagnostics] file.encoding.pkg : sun.io
[diagnostics] user.country : US
[diagnostics] sun.os.patch.level : Service Pack 3
[diagnostics] java.vm.specification.name : Java Virtual Machine
Specification
[diagnostics] user.dir :
D:\EIIProd\dataIntegration\DevTools\ProductBuild
[diagnostics] java.runtime.version : 1.5.0_06-b05
[diagnostics] java.awt.graphicsenv : sun.awt.Win32GraphicsEnvironment
[diagnostics] java.endorsed.dirs : D:\bea\jdk150_06\jre\lib\endorsed
[diagnostics] os.arch : x86
[diagnostics] java.io.tmpdir : C:\DOCUME~1\boringj\LOCALS~1\Temp\
[diagnostics] line.separator :
[diagnostics]
[diagnostics] java.vm.specification.vendor : Sun Microsystems Inc.
[diagnostics] user.variant :
[diagnostics] os.name : Windows XP
[diagnostics] ant.home : D:\dev\lib\apache-ant-1.7.1
[diagnostics] sun.jnu.encoding : Cp1252
[diagnostics] java.library.path :
D:\bea\jdk150_06\bin;.;C:\WINDOWS\system32;C:\WINDOWS;D:\bea\jdk150_06\b
in;D:\oracle\product\10.2.0\client_1\bin;C:\Ent\Appl\Prod\Oracle8i\bin;C
:\WINDOWS\system32;c:\ent\appl\prod\perl\5.00502\bin\mswin32-x86;c:\ent\
appl\prod\perl\5.00502\bin;C:\WINDOWS;C:\WINDOWS\system32\wbem;c:\ent\ap
pl\prod\bin;D:\dev\lib\apache-ant-1.7.1\bin;D:\dev\lib\apache-maven-2.0.
9\bin;C:\Program Files\QuickTime\QTSystem\
[diagnostics] java.specification.name : Java Platform API Specification
[diagnostics] java.class.version : 49.0
[diagnostics] sun.management.compiler : HotSpot Client Compiler
[diagnostics] os.version : 5.1
[diagnostics] user.home : d:\data\boringj
[diagnostics] user.timezone : America/New_York
[diagnostics] java.awt.printerjob : sun.awt.windows.WPrinterJob
[diagnostics] file.encoding : Cp1252
[diagnostics] java.specification.version : 1.5
[diagnostics] user.name : boringj
[diagnostics] java.class.path :
D:\dev\lib\apache-ant-1.7.1\lib\ant-launcher.jar;D:\EIIProd\dataIntegrat
ion\DevTools\ProductBuild\.\;C:\Program
Files\Altova\xmlspy\XMLSpyInterface.jar;D:\bea\jdk150_06\;C:\Program
Files\Java\jre6\lib\ext\QTJava.zip;D:\dev\lib\apache-ant-1.7.1\lib\ant-a
ntlr.jar;D:\dev\lib\apache-ant-1.7.1\lib\ant-apache-bcel.jar;D:\dev\lib\
apache-ant-1.7.1\lib\ant-apache-bsf.jar;D:\dev\lib\apache-ant-1.7.1\lib\
ant-apache-log4j.jar;D:\dev\lib\apache-ant-1.7.1\lib\ant-apache-oro.jar;
D:\dev\lib\apache-ant-1.7.1\lib\ant-apache-regexp.jar;D:\dev\lib\apache-
ant-1.7.1\lib\ant-apache-resolver.jar;D:\dev\lib\apache-ant-1.7.1\lib\an
t-commons-logging.jar;D:\dev\lib\apache-ant-1.7.1\lib\ant-commons-net.ja
r;D:\dev\lib\apache-ant-1.7.1\lib\ant-contrib.jar;D:\dev\lib\apache-ant-
1.7.1\lib\ant-jai.jar;D:\dev\lib\apache-ant-1.7.1\lib\ant-javamail.jar;D
:\dev\lib\apache-ant-1.7.1\lib\ant-jdepend.jar;D:\dev\lib\apache-ant-1.7
.1\lib\ant-jmf.jar;D:\dev\lib\apache-ant-1.7.1\lib\ant-jsch.jar;D:\dev\l
ib\apache-ant-1.7.1\lib\ant-junit.jar;D:\dev\lib\apache-ant-1.7.1\lib\an
t-launcher.jar;D:\dev\lib\apache-ant-1.7.1\lib\ant-netrexx.jar;D:\dev\li
b\apache-ant-1.7.1\lib\ant-nodeps.jar;D:\dev\lib\apache-ant-1.7.1\lib\an
t-starteam.jar;D:\dev\lib\apache-ant-1.7.1\lib\ant-stylebook.jar;D:\dev\
lib\apache-ant-1.7.1\lib\ant-swing.jar;D:\dev\lib\apache-ant-1.7.1\lib\a
nt-testutil.jar;D:\dev\lib\apache-ant-1.7.1\lib\ant-trax.jar;D:\dev\lib\
apache-ant-1.7.1\lib\ant-weblogic.jar;D:\dev\lib\apache-ant-1.7.1\lib\an
t.jar;D:\dev\lib\apache-ant-1.7.1\lib\xercesImpl.jar;D:\dev\lib\apache-a
nt-1.7.1\lib\xml-apis.jar;D:\bea\jdk150_06\lib\tools.jar
[diagnostics] java.vm.specification.version : 1.0
[diagnostics] sun.arch.data.model : 32
[diagnostics] java.home : D:\bea\jdk150_06\jre
[diagnostics] java.specification.vendor : Sun Microsystems Inc.
[diagnostics] user.language : en
[diagnostics] awt.toolkit : sun.awt.windows.WToolkit
[diagnostics] java.vm.info : mixed mode
[diagnostics] java.version : 1.5.0_06
[diagnostics] java.ext.dirs : D:\bea\jdk150_06\jre\lib\ext
[diagnostics] sun.boot.class.path :
D:\bea\jdk150_06\jre\lib\rt.jar;D:\bea\jdk150_06\jre\lib\i18n.jar;D:\bea
\jdk150_06\jre\lib\sunrsasign.jar;D:\bea\jdk150_06\jre\lib\jsse.jar;D:\b
ea\jdk150_06\jre\lib\jce.jar;D:\bea\jdk150_06\jre\lib\charsets.jar;D:\be
a\jdk150_06\jre\classes
[diagnostics] java.vendor : Sun Microsystems Inc.
[diagnostics] file.separator : \
[diagnostics] java.vendor.url.bug :
http://java.sun.com/cgi-bin/bugreport.cgi
[diagnostics] sun.cpu.endian : little
[diagnostics] sun.io.unicode.encoding : UnicodeLittle
[diagnostics] sun.desktop : windows
[diagnostics] sun.cpu.isalist :
[diagnostics]
[diagnostics] -------------------------------------------
[diagnostics] Temp dir
[diagnostics] -------------------------------------------
[diagnostics] Temp dir is C:\DOCUME~1\boringj\LOCALS~1\Temp\
[diagnostics] Temp dir is writeable
[diagnostics] Temp dir alignment with system clock is 0 ms
[diagnostics]
[diagnostics] -------------------------------------------
[diagnostics] Locale information
[diagnostics] -------------------------------------------
[diagnostics] Timezone Eastern Standard Time offset=-14400000
[diagnostics]
[diagnostics] -------------------------------------------
[diagnostics] Proxy information
[diagnostics] -------------------------------------------
[diagnostics] Java1.5+ proxy settings:
[diagnostics] Direct connection
Re: Unable to delete file
Posted by Brian Pontarelli <br...@pontarelli.com>.
Sorry for my last post. Just saw maven and ivy and figured the thread
had shifted from the subject. Is the file locked? There are tools out
there to check if some process has a lock on a file. It could also be
a permission issue. Sometimes the file is also being held by the OS
and you can't delete it. Otherwise it could be that the OS doesn't
want to delete it for some reason such as a hard link or other type of
reference.
Sent from my iPhone
On Aug 18, 2009, at 1:45 PM, "Boring, Jeff W (N-Viper)" <jeff.w.boring@lmco.com
> wrote:
> Derek - No. It's just a normal windows pc with NTFS.
>
> Greg - I'm working on it. Thanks for asking!
>
> Jeff
>
> -----Original Message-----
> From: Cole, Derek E
> Sent: Tuesday, August 18, 2009 3:28 PM
> To: Ant Users List
> Subject: RE: Unable to delete file
>
> Is the file being stored on an NFS?
>
> -----Original Message-----
> From: Greg Roodt [mailto:groodt@gmail.com]
> Sent: Tuesday, August 18, 2009 2:12 PM
> To: Ant Users List
> Subject: Re: Unable to delete file
>
> Im sure the intentions are good, but these suggestions are not solving
> the problem at hand.
>
> Jeff, I suggest giving us a bit more to work with. Is there any easy
> way
> to reproduce the behavior you are seeing? Its almost certainly some
> sort
> of file path problem.
>
>
>
> On Tue, Aug 18, 2009 at 7:03 PM, Brian Pontarelli
> <br...@pontarelli.com>wrote:
>
>>
>> Another option is using Savant. Savant provides a nice wrapper around
>> Ant that allows you to create plugins which can be used between
>> projects. The plugins are simply Ant build scripts which are
>> downloaded prior to executing Ant. It also allows you to create
>> targets specific to your project or define all your targets inside
> your project without using any plugins.
>>
>> Lastly, Savant manages dependencies well and doesn't do any magic
>> upgrading or version mangling. All dependencies are explicit and it
>> also has a notion of local integration builds that allow you to work
>> across multiple projects easily.
>>
>> You can also setup local Savant repository to ensure all your
>> dependencies are secure and Savant also allows you to secure the
>> repository using SSL and HTTP basic authentication.
>>
>> For all the Inversoft projects I use two separate repositories with
> Savant:
>>
>> http://savant.inversoft.org - for all 3rd party and open
>> source dependencies as well as the standard Savant plugins (uses HTTP
>> only with no
>> authentication)
>>
>> https://savant.inversoft.com - for Inversoft dependencies (uses
>
>> SSL and HTTP basic authentication)
>>
>> -bp
>>
>>
>>
>> On Aug 18, 2009, at 11:43 AM, Boring, Jeff W (N-Viper) wrote:
>>
>> Maven is not an option but thanks guys for the opinions! Any ideas
>> about
>>> the unable to delete?
>>>
>>>
>>>
>>> Jeff
>>>
>>> Lockheed Martin
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: Dominique Devienne [mailto:ddevienne@gmail.com]
>>> Sent: Tuesday, August 18, 2009 12:29 PM
>>> To: Ant Users List
>>> Subject: Re: Unable to delete file
>>>
>>>
>>>
>>> On Tue, Aug 18, 2009 at 10:21 AM, Martin Gainty<mg...@hotmail.com>
>>> wrote:
>>>
>>> here in the US DOD vendors are converting their build.xml and
>>>>
>>> implementing to maven for:
>>>
>>> offline repository(secure from middle-eastern attackers)
>>>>
>>>
>>> version-specific SCM tagging
>>>>
>>>
>>> security (ability to enforce SSH handshake to ftp via sftp and scp)
>>>>
>>>
>>>
>>>>
>>>
>>>>
>>> http://www.sonatype.com/people/2009/04/how-to-convert-from-ant-to-
>>> mav
>>> en-
>>> in-5-minutes/
>>>
>>>
>>>
>>> I'm sure Maven has come a long way since I looked at it,
>>>
>>> and it does encapsulate a lot of good practices, but it's
>>> my-way-or-the-highway
>>>
>>> philosophy went against the grain for me.
>>>
>>>
>>>
>>> Using Ant doesn't "force" you to have a badly designed monolithic
>>>
>>> build, although I grant you it doesn't prevent it like Maven does.
>>> In
>>>
>>> the past, if something's wrong with your Maven build, good luck
>>>
>>> troubleshooting it, whereas Ant is easier IMHO, although again this
>>> is
>>>
>>> an old experience (and the Maven user list didn't help me solve it
>>>
>>> either. Hopefully their community has evolved since).
>>>
>>>
>>>
>>> Code with non clear dependencies is bad in any build system. Your
>>> blog
>>>
>>> post IMHO confuses cleaning the code and switching build system. The
>>>
>>> declarative nature of poms is good, but it can be leveraged using
>>>
>>> Ivy+Ant rather than Maven.
>>>
>>>
>>>
>>> All this to say that going from Ant to Maven is a lot more complex
>>>
>>> that you make it sound, and that Ant is not really the issue here,
>>> but
>>>
>>> the design of the code and its build. --DD
>>>
>>>
>>>
>>> ---
>>> ------------------------------------------------------------------
>>>
>>> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
>>>
>>> For additional commands, e-mail: user-help@ant.apache.org
>>>
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For
>> additional
>
>> commands, e-mail: user-help@ant.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
Re: Unable to delete file
Posted by glenn opdycke-hansen <gl...@gmail.com>.
I recall that an Ant build on a windows machine could have problems on
delete because an extra file explorer window was open on the folder and held
a lock preventing the delete. Good luck on you issue.
-glenn
RE: Unable to delete file
Posted by "Boring, Jeff W (N-Viper)" <je...@lmco.com>.
Derek - No. It's just a normal windows pc with NTFS.
Greg - I'm working on it. Thanks for asking!
Jeff
-----Original Message-----
From: Cole, Derek E
Sent: Tuesday, August 18, 2009 3:28 PM
To: Ant Users List
Subject: RE: Unable to delete file
Is the file being stored on an NFS?
-----Original Message-----
From: Greg Roodt [mailto:groodt@gmail.com]
Sent: Tuesday, August 18, 2009 2:12 PM
To: Ant Users List
Subject: Re: Unable to delete file
Im sure the intentions are good, but these suggestions are not solving
the problem at hand.
Jeff, I suggest giving us a bit more to work with. Is there any easy way
to reproduce the behavior you are seeing? Its almost certainly some sort
of file path problem.
On Tue, Aug 18, 2009 at 7:03 PM, Brian Pontarelli
<br...@pontarelli.com>wrote:
>
> Another option is using Savant. Savant provides a nice wrapper around
> Ant that allows you to create plugins which can be used between
> projects. The plugins are simply Ant build scripts which are
> downloaded prior to executing Ant. It also allows you to create
> targets specific to your project or define all your targets inside
your project without using any plugins.
>
> Lastly, Savant manages dependencies well and doesn't do any magic
> upgrading or version mangling. All dependencies are explicit and it
> also has a notion of local integration builds that allow you to work
> across multiple projects easily.
>
> You can also setup local Savant repository to ensure all your
> dependencies are secure and Savant also allows you to secure the
> repository using SSL and HTTP basic authentication.
>
> For all the Inversoft projects I use two separate repositories with
Savant:
>
> http://savant.inversoft.org - for all 3rd party and open
> source dependencies as well as the standard Savant plugins (uses HTTP
> only with no
> authentication)
>
> https://savant.inversoft.com - for Inversoft dependencies (uses
> SSL and HTTP basic authentication)
>
> -bp
>
>
>
> On Aug 18, 2009, at 11:43 AM, Boring, Jeff W (N-Viper) wrote:
>
> Maven is not an option but thanks guys for the opinions! Any ideas
> about
>> the unable to delete?
>>
>>
>>
>> Jeff
>>
>> Lockheed Martin
>>
>>
>>
>> -----Original Message-----
>> From: Dominique Devienne [mailto:ddevienne@gmail.com]
>> Sent: Tuesday, August 18, 2009 12:29 PM
>> To: Ant Users List
>> Subject: Re: Unable to delete file
>>
>>
>>
>> On Tue, Aug 18, 2009 at 10:21 AM, Martin Gainty<mg...@hotmail.com>
>> wrote:
>>
>> here in the US DOD vendors are converting their build.xml and
>>>
>> implementing to maven for:
>>
>> offline repository(secure from middle-eastern attackers)
>>>
>>
>> version-specific SCM tagging
>>>
>>
>> security (ability to enforce SSH handshake to ftp via sftp and scp)
>>>
>>
>>
>>>
>>
>>>
>> http://www.sonatype.com/people/2009/04/how-to-convert-from-ant-to-mav
>> en-
>> in-5-minutes/
>>
>>
>>
>> I'm sure Maven has come a long way since I looked at it,
>>
>> and it does encapsulate a lot of good practices, but it's
>> my-way-or-the-highway
>>
>> philosophy went against the grain for me.
>>
>>
>>
>> Using Ant doesn't "force" you to have a badly designed monolithic
>>
>> build, although I grant you it doesn't prevent it like Maven does. In
>>
>> the past, if something's wrong with your Maven build, good luck
>>
>> troubleshooting it, whereas Ant is easier IMHO, although again this
>> is
>>
>> an old experience (and the Maven user list didn't help me solve it
>>
>> either. Hopefully their community has evolved since).
>>
>>
>>
>> Code with non clear dependencies is bad in any build system. Your
>> blog
>>
>> post IMHO confuses cleaning the code and switching build system. The
>>
>> declarative nature of poms is good, but it can be leveraged using
>>
>> Ivy+Ant rather than Maven.
>>
>>
>>
>> All this to say that going from Ant to Maven is a lot more complex
>>
>> that you make it sound, and that Ant is not really the issue here,
>> but
>>
>> the design of the code and its build. --DD
>>
>>
>>
>> ---------------------------------------------------------------------
>>
>> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
>>
>> For additional commands, e-mail: user-help@ant.apache.org
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For additional
> commands, e-mail: user-help@ant.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
RE: Unable to delete file
Posted by "Cole, Derek E" <de...@lmco.com>.
Is the file being stored on an NFS?
-----Original Message-----
From: Greg Roodt [mailto:groodt@gmail.com]
Sent: Tuesday, August 18, 2009 2:12 PM
To: Ant Users List
Subject: Re: Unable to delete file
Im sure the intentions are good, but these suggestions are not solving the problem at hand.
Jeff, I suggest giving us a bit more to work with. Is there any easy way to reproduce the behavior you are seeing? Its almost certainly some sort of file path problem.
On Tue, Aug 18, 2009 at 7:03 PM, Brian Pontarelli <br...@pontarelli.com>wrote:
>
> Another option is using Savant. Savant provides a nice wrapper around
> Ant that allows you to create plugins which can be used between
> projects. The plugins are simply Ant build scripts which are
> downloaded prior to executing Ant. It also allows you to create
> targets specific to your project or define all your targets inside your project without using any plugins.
>
> Lastly, Savant manages dependencies well and doesn't do any magic
> upgrading or version mangling. All dependencies are explicit and it
> also has a notion of local integration builds that allow you to work
> across multiple projects easily.
>
> You can also setup local Savant repository to ensure all your
> dependencies are secure and Savant also allows you to secure the
> repository using SSL and HTTP basic authentication.
>
> For all the Inversoft projects I use two separate repositories with Savant:
>
> http://savant.inversoft.org - for all 3rd party and open
> source dependencies as well as the standard Savant plugins (uses HTTP
> only with no
> authentication)
>
> https://savant.inversoft.com - for Inversoft dependencies (uses
> SSL and HTTP basic authentication)
>
> -bp
>
>
>
> On Aug 18, 2009, at 11:43 AM, Boring, Jeff W (N-Viper) wrote:
>
> Maven is not an option but thanks guys for the opinions! Any ideas
> about
>> the unable to delete?
>>
>>
>>
>> Jeff
>>
>> Lockheed Martin
>>
>>
>>
>> -----Original Message-----
>> From: Dominique Devienne [mailto:ddevienne@gmail.com]
>> Sent: Tuesday, August 18, 2009 12:29 PM
>> To: Ant Users List
>> Subject: Re: Unable to delete file
>>
>>
>>
>> On Tue, Aug 18, 2009 at 10:21 AM, Martin Gainty<mg...@hotmail.com>
>> wrote:
>>
>> here in the US DOD vendors are converting their build.xml and
>>>
>> implementing to maven for:
>>
>> offline repository(secure from middle-eastern attackers)
>>>
>>
>> version-specific SCM tagging
>>>
>>
>> security (ability to enforce SSH handshake to ftp via sftp and scp)
>>>
>>
>>
>>>
>>
>>>
>> http://www.sonatype.com/people/2009/04/how-to-convert-from-ant-to-mav
>> en-
>> in-5-minutes/
>>
>>
>>
>> I'm sure Maven has come a long way since I looked at it,
>>
>> and it does encapsulate a lot of good practices, but it's
>> my-way-or-the-highway
>>
>> philosophy went against the grain for me.
>>
>>
>>
>> Using Ant doesn't "force" you to have a badly designed monolithic
>>
>> build, although I grant you it doesn't prevent it like Maven does. In
>>
>> the past, if something's wrong with your Maven build, good luck
>>
>> troubleshooting it, whereas Ant is easier IMHO, although again this
>> is
>>
>> an old experience (and the Maven user list didn't help me solve it
>>
>> either. Hopefully their community has evolved since).
>>
>>
>>
>> Code with non clear dependencies is bad in any build system. Your
>> blog
>>
>> post IMHO confuses cleaning the code and switching build system. The
>>
>> declarative nature of poms is good, but it can be leveraged using
>>
>> Ivy+Ant rather than Maven.
>>
>>
>>
>> All this to say that going from Ant to Maven is a lot more complex
>>
>> that you make it sound, and that Ant is not really the issue here,
>> but
>>
>> the design of the code and its build. --DD
>>
>>
>>
>> ---------------------------------------------------------------------
>>
>> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
>>
>> For additional commands, e-mail: user-help@ant.apache.org
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For additional
> commands, e-mail: user-help@ant.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
Re: Unable to delete file
Posted by Greg Roodt <gr...@gmail.com>.
Im sure the intentions are good, but these suggestions are not solving the
problem at hand.
Jeff, I suggest giving us a bit more to work with. Is there any easy way to
reproduce the behavior you are seeing? Its almost certainly some sort of
file path problem.
On Tue, Aug 18, 2009 at 7:03 PM, Brian Pontarelli <br...@pontarelli.com>wrote:
>
> Another option is using Savant. Savant provides a nice wrapper around Ant
> that allows you to create plugins which can be used between projects. The
> plugins are simply Ant build scripts which are downloaded prior to executing
> Ant. It also allows you to create targets specific to your project or define
> all your targets inside your project without using any plugins.
>
> Lastly, Savant manages dependencies well and doesn't do any magic upgrading
> or version mangling. All dependencies are explicit and it also has a notion
> of local integration builds that allow you to work across multiple projects
> easily.
>
> You can also setup local Savant repository to ensure all your dependencies
> are secure and Savant also allows you to secure the repository using SSL and
> HTTP basic authentication.
>
> For all the Inversoft projects I use two separate repositories with Savant:
>
> http://savant.inversoft.org - for all 3rd party and open source
> dependencies as well as the standard Savant plugins (uses HTTP only with no
> authentication)
>
> https://savant.inversoft.com - for Inversoft dependencies (uses SSL
> and HTTP basic authentication)
>
> -bp
>
>
>
> On Aug 18, 2009, at 11:43 AM, Boring, Jeff W (N-Viper) wrote:
>
> Maven is not an option but thanks guys for the opinions! Any ideas about
>> the unable to delete?
>>
>>
>>
>> Jeff
>>
>> Lockheed Martin
>>
>>
>>
>> -----Original Message-----
>> From: Dominique Devienne [mailto:ddevienne@gmail.com]
>> Sent: Tuesday, August 18, 2009 12:29 PM
>> To: Ant Users List
>> Subject: Re: Unable to delete file
>>
>>
>>
>> On Tue, Aug 18, 2009 at 10:21 AM, Martin Gainty<mg...@hotmail.com>
>> wrote:
>>
>> here in the US DOD vendors are converting their build.xml and
>>>
>> implementing to maven for:
>>
>> offline repository(secure from middle-eastern attackers)
>>>
>>
>> version-specific SCM tagging
>>>
>>
>> security (ability to enforce SSH handshake to ftp via sftp and scp)
>>>
>>
>>
>>>
>>
>>>
>> http://www.sonatype.com/people/2009/04/how-to-convert-from-ant-to-maven-
>> in-5-minutes/
>>
>>
>>
>> I'm sure Maven has come a long way since I looked at it,
>>
>> and it does encapsulate a lot of good practices, but it's
>> my-way-or-the-highway
>>
>> philosophy went against the grain for me.
>>
>>
>>
>> Using Ant doesn't "force" you to have a badly designed monolithic
>>
>> build, although I grant you it doesn't prevent it like Maven does. In
>>
>> the past, if something's wrong with your Maven build, good luck
>>
>> troubleshooting it, whereas Ant is easier IMHO, although again this is
>>
>> an old experience (and the Maven user list didn't help me solve it
>>
>> either. Hopefully their community has evolved since).
>>
>>
>>
>> Code with non clear dependencies is bad in any build system. Your blog
>>
>> post IMHO confuses cleaning the code and switching build system. The
>>
>> declarative nature of poms is good, but it can be leveraged using
>>
>> Ivy+Ant rather than Maven.
>>
>>
>>
>> All this to say that going from Ant to Maven is a lot more complex
>>
>> that you make it sound, and that Ant is not really the issue here, but
>>
>> the design of the code and its build. --DD
>>
>>
>>
>> ---------------------------------------------------------------------
>>
>> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
>>
>> For additional commands, e-mail: user-help@ant.apache.org
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
>
>
Re: Unable to delete file
Posted by Brian Pontarelli <br...@pontarelli.com>.
Another option is using Savant. Savant provides a nice wrapper around
Ant that allows you to create plugins which can be used between
projects. The plugins are simply Ant build scripts which are
downloaded prior to executing Ant. It also allows you to create
targets specific to your project or define all your targets inside
your project without using any plugins.
Lastly, Savant manages dependencies well and doesn't do any magic
upgrading or version mangling. All dependencies are explicit and it
also has a notion of local integration builds that allow you to work
across multiple projects easily.
You can also setup local Savant repository to ensure all your
dependencies are secure and Savant also allows you to secure the
repository using SSL and HTTP basic authentication.
For all the Inversoft projects I use two separate repositories with
Savant:
http://savant.inversoft.org - for all 3rd party and open source
dependencies as well as the standard Savant plugins (uses HTTP only
with no authentication)
https://savant.inversoft.com - for Inversoft dependencies (uses SSL
and HTTP basic authentication)
-bp
On Aug 18, 2009, at 11:43 AM, Boring, Jeff W (N-Viper) wrote:
> Maven is not an option but thanks guys for the opinions! Any ideas
> about
> the unable to delete?
>
>
>
> Jeff
>
> Lockheed Martin
>
>
>
> -----Original Message-----
> From: Dominique Devienne [mailto:ddevienne@gmail.com]
> Sent: Tuesday, August 18, 2009 12:29 PM
> To: Ant Users List
> Subject: Re: Unable to delete file
>
>
>
> On Tue, Aug 18, 2009 at 10:21 AM, Martin Gainty<mg...@hotmail.com>
> wrote:
>
>> here in the US DOD vendors are converting their build.xml and
> implementing to maven for:
>
>> offline repository(secure from middle-eastern attackers)
>
>> version-specific SCM tagging
>
>> security (ability to enforce SSH handshake to ftp via sftp and scp)
>
>>
>
>>
> http://www.sonatype.com/people/2009/04/how-to-convert-from-ant-to-maven-
> in-5-minutes/
>
>
>
> I'm sure Maven has come a long way since I looked at it,
>
> and it does encapsulate a lot of good practices, but it's
> my-way-or-the-highway
>
> philosophy went against the grain for me.
>
>
>
> Using Ant doesn't "force" you to have a badly designed monolithic
>
> build, although I grant you it doesn't prevent it like Maven does. In
>
> the past, if something's wrong with your Maven build, good luck
>
> troubleshooting it, whereas Ant is easier IMHO, although again this is
>
> an old experience (and the Maven user list didn't help me solve it
>
> either. Hopefully their community has evolved since).
>
>
>
> Code with non clear dependencies is bad in any build system. Your blog
>
> post IMHO confuses cleaning the code and switching build system. The
>
> declarative nature of poms is good, but it can be leveraged using
>
> Ivy+Ant rather than Maven.
>
>
>
> All this to say that going from Ant to Maven is a lot more complex
>
> that you make it sound, and that Ant is not really the issue here, but
>
> the design of the code and its build. --DD
>
>
>
> ---------------------------------------------------------------------
>
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
>
> For additional commands, e-mail: user-help@ant.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
RE: Unable to delete file
Posted by "Boring, Jeff W (N-Viper)" <je...@lmco.com>.
Maven is not an option but thanks guys for the opinions! Any ideas about
the unable to delete?
Jeff
Lockheed Martin
-----Original Message-----
From: Dominique Devienne [mailto:ddevienne@gmail.com]
Sent: Tuesday, August 18, 2009 12:29 PM
To: Ant Users List
Subject: Re: Unable to delete file
On Tue, Aug 18, 2009 at 10:21 AM, Martin Gainty<mg...@hotmail.com>
wrote:
> here in the US DOD vendors are converting their build.xml and
implementing to maven for:
> offline repository(secure from middle-eastern attackers)
> version-specific SCM tagging
> security (ability to enforce SSH handshake to ftp via sftp and scp)
>
>
http://www.sonatype.com/people/2009/04/how-to-convert-from-ant-to-maven-
in-5-minutes/
I'm sure Maven has come a long way since I looked at it,
and it does encapsulate a lot of good practices, but it's
my-way-or-the-highway
philosophy went against the grain for me.
Using Ant doesn't "force" you to have a badly designed monolithic
build, although I grant you it doesn't prevent it like Maven does. In
the past, if something's wrong with your Maven build, good luck
troubleshooting it, whereas Ant is easier IMHO, although again this is
an old experience (and the Maven user list didn't help me solve it
either. Hopefully their community has evolved since).
Code with non clear dependencies is bad in any build system. Your blog
post IMHO confuses cleaning the code and switching build system. The
declarative nature of poms is good, but it can be leveraged using
Ivy+Ant rather than Maven.
All this to say that going from Ant to Maven is a lot more complex
that you make it sound, and that Ant is not really the issue here, but
the design of the code and its build. --DD
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
Re: Unable to delete file
Posted by Dominique Devienne <dd...@gmail.com>.
On Tue, Aug 18, 2009 at 10:21 AM, Martin Gainty<mg...@hotmail.com> wrote:
> here in the US DOD vendors are converting their build.xml and implementing to maven for:
> offline repository(secure from middle-eastern attackers)
> version-specific SCM tagging
> security (ability to enforce SSH handshake to ftp via sftp and scp)
>
> http://www.sonatype.com/people/2009/04/how-to-convert-from-ant-to-maven-in-5-minutes/
I'm sure Maven has come a long way since I looked at it,
and it does encapsulate a lot of good practices, but it's my-way-or-the-highway
philosophy went against the grain for me.
Using Ant doesn't "force" you to have a badly designed monolithic
build, although I grant you it doesn't prevent it like Maven does. In
the past, if something's wrong with your Maven build, good luck
troubleshooting it, whereas Ant is easier IMHO, although again this is
an old experience (and the Maven user list didn't help me solve it
either. Hopefully their community has evolved since).
Code with non clear dependencies is bad in any build system. Your blog
post IMHO confuses cleaning the code and switching build system. The
declarative nature of poms is good, but it can be leveraged using
Ivy+Ant rather than Maven.
All this to say that going from Ant to Maven is a lot more complex
that you make it sound, and that Ant is not really the issue here, but
the design of the code and its build. --DD
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
RE: Unable to delete file
Posted by Martin Gainty <mg...@hotmail.com>.
Jeff-
here in the US DOD vendors are converting their build.xml and implementing to maven for:
offline repository(secure from middle-eastern attackers)
version-specific SCM tagging
security (ability to enforce SSH handshake to ftp via sftp and scp)
http://www.sonatype.com/people/2009/04/how-to-convert-from-ant-to-maven-in-5-minutes/
free free to ping me offline if you need any help in this area
Martin Gainty
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.
> Date: Tue, 18 Aug 2009 10:05:34 -0400
> From: jeff.w.boring@lmco.com
> Subject: Unable to delete file
> To: user@ant.apache.org
> CC: nirav.shah@lmco.com; adil.karamat@lmco.com
>
> We have a 20+ Java projects (Eclipse Projects) each with its own
> build.xml. We group projects into components; every component has a
> build.xml for building the projects in the component. The component
> build.xml files are nothing more than ant (element) calls delegating to
> the project builds. Finally, there is a simple master build.xml that
> makes ant calls to the component build.xml files.
>
>
>
> From the master build.xml, a call to the first project build produces a
> jar. This project build.xml can delete the jar but no other build.xml
> can - always gets the "unable to delete file" message. Note that the
> file CAN be deleted in windows. I've tried sleeping for 60 secs,
> thinking something just needed time to clean out but that didn't work.
>
>
>
> The compile & jar targets are listed below as is the ant diagnostics
> report. Any help would be much appreciated.
>
>
>
> Jeff
>
>
>
> Jeff W. Boring
>
> Lockheed Martin
>
>
>
>
>
> <target name="compileProd" description="">
>
> <echo message="Executing Compile Prod Target" />
>
> <javac destdir="${build.production.dir}" fork="true" debug="on"
> memorymaximumsize="256m">
>
> <classpath path="${p.classpath}" />
>
> <src path="${source.dir}"/>
>
> </javac>
>
> </target>
>
>
>
> <target name="createProdArtifacts" description="Creates deployment
> artifacts (jar/war)" >
>
> <echo message="create Prod artifacts" />
>
> <jar destfile="${basedir}/${local.artifact.filename}"
> basedir="${build.production.dir}" />
>
> </target>
>
>
>
> [diagnostics] ------- Ant diagnostics report -------
>
> [diagnostics] Apache Ant version 1.7.1 compiled on June 27 2008
>
> [diagnostics]
>
> [diagnostics] -------------------------------------------
>
> [diagnostics] Implementation Version
>
> [diagnostics] -------------------------------------------
>
> [diagnostics] core tasks : 1.7.1
>
> [diagnostics] optional tasks : not available
>
> [diagnostics]
>
> [diagnostics] -------------------------------------------
>
> [diagnostics] ANT PROPERTIES
>
> [diagnostics] -------------------------------------------
>
> [diagnostics] ant.version: Apache Ant version 1.7.1 compiled on June 27
> 2008
>
> [diagnostics] ant.java.version: 1.5
>
> [diagnostics] ant.core.lib: D:\dev\lib\apache-ant-1.7.1\lib\ant.jar
>
> [diagnostics] ant.home: D:\dev\lib\apache-ant-1.7.1
>
> [diagnostics]
>
> [diagnostics] -------------------------------------------
>
> [diagnostics] ANT_HOME/lib jar listing
>
> [diagnostics] -------------------------------------------
>
> [diagnostics] ant.home: D:\dev\lib\apache-ant-1.7.1
>
> [diagnostics] ant-antlr.jar (5752 bytes)
>
> [diagnostics] ant-apache-bcel.jar (8611 bytes)
>
> [diagnostics] ant-apache-bsf.jar (3939 bytes)
>
> [diagnostics] ant-apache-log4j.jar (3056 bytes)
>
> [diagnostics] ant-apache-oro.jar (39627 bytes)
>
> [diagnostics] ant-apache-regexp.jar (3762 bytes)
>
> [diagnostics] ant-apache-resolver.jar (4071 bytes)
>
> [diagnostics] ant-commons-logging.jar (3910 bytes)
>
> [diagnostics] ant-commons-net.jar (47026 bytes)
>
> [diagnostics] ant-contrib.jar (194050 bytes)
>
> [diagnostics] ant-jai.jar (21348 bytes)
>
> [diagnostics] ant-javamail.jar (6998 bytes)
>
> [diagnostics] ant-jdepend.jar (8132 bytes)
>
> [diagnostics] ant-jmf.jar (6593 bytes)
>
> [diagnostics] ant-jsch.jar (30797 bytes)
>
> [diagnostics] ant-junit.jar (93518 bytes)
>
> [diagnostics] ant-launcher.jar (12143 bytes)
>
> [diagnostics] ant-netrexx.jar (9881 bytes)
>
> [diagnostics] ant-nodeps.jar (431580 bytes)
>
> [diagnostics] ant-starteam.jar (35355 bytes)
>
> [diagnostics] ant-stylebook.jar (2330 bytes)
>
> [diagnostics] ant-swing.jar (6738 bytes)
>
> [diagnostics] ant-testutil.jar (14941 bytes)
>
> [diagnostics] ant-trax.jar (6881 bytes)
>
> [diagnostics] ant-weblogic.jar (14205 bytes)
>
> [diagnostics] ant.jar (1323005 bytes)
>
> [diagnostics] xercesImpl.jar (1223877 bytes)
>
> [diagnostics] xml-apis.jar (194354 bytes)
>
> [diagnostics]
>
> [diagnostics] -------------------------------------------
>
> [diagnostics] USER_HOME/.ant/lib jar listing
>
> [diagnostics] -------------------------------------------
>
> [diagnostics] user.home: d:\data\boringj
>
> [diagnostics] No such directory.
>
> [diagnostics]
>
> [diagnostics] -------------------------------------------
>
> [diagnostics] Tasks availability
>
> [diagnostics] -------------------------------------------
>
> [diagnostics] image : Missing dependency javax.media.jai.PlanarImage
>
> [diagnostics] sshexec : Missing dependency com.jcraft.jsch.UserInfo
>
> [diagnostics] scp : Missing dependency com.jcraft.jsch.UserInfo
>
> [diagnostics] jdepend : Missing dependency jdepend.xmlui.JDepend
>
> [diagnostics] A task being missing/unavailable should only matter if you
> are trying to use it
>
> [diagnostics]
>
> [diagnostics] -------------------------------------------
>
> [diagnostics] org.apache.env.Which diagnostics
>
> [diagnostics] -------------------------------------------
>
> [diagnostics] Not available.
>
> [diagnostics] Download it at http://xml.apache.org/commons/
>
> [diagnostics]
>
> [diagnostics] -------------------------------------------
>
> [diagnostics] XML Parser information
>
> [diagnostics] -------------------------------------------
>
> [diagnostics] XML Parser : org.apache.xerces.jaxp.SAXParserImpl
>
> [diagnostics] XML Parser Location:
> D:\dev\lib\apache-ant-1.7.1\lib\xercesImpl.jar
>
> [diagnostics] Namespace-aware parser :
> org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser
>
> [diagnostics] Namespace-aware parser Location:
> D:\dev\lib\apache-ant-1.7.1\lib\xercesImpl.jar
>
> [diagnostics]
>
> [diagnostics] -------------------------------------------
>
> [diagnostics] System properties
>
> [diagnostics] -------------------------------------------
>
> [diagnostics] java.runtime.name : Java(TM) 2 Runtime Environment,
> Standard Edition
>
> [diagnostics] sun.boot.library.path : D:\bea\jdk150_06\jre\bin
>
> [diagnostics] java.vm.version : 1.5.0_06-b05
>
> [diagnostics] ant.library.dir : D:\dev\lib\apache-ant-1.7.1\lib
>
> [diagnostics] java.vm.vendor : Sun Microsystems Inc.
>
> [diagnostics] java.vendor.url : http://java.sun.com/
>
> [diagnostics] path.separator : ;
>
> [diagnostics] java.vm.name : Java HotSpot(TM) Client VM
>
> [diagnostics] file.encoding.pkg : sun.io
>
> [diagnostics] user.country : US
>
> [diagnostics] sun.os.patch.level : Service Pack 3
>
> [diagnostics] java.vm.specification.name : Java Virtual Machine
> Specification
>
> [diagnostics] user.dir :
> D:\EIIProd\dataIntegration\DevTools\ProductBuild
>
> [diagnostics] java.runtime.version : 1.5.0_06-b05
>
> [diagnostics] java.awt.graphicsenv : sun.awt.Win32GraphicsEnvironment
>
> [diagnostics] java.endorsed.dirs : D:\bea\jdk150_06\jre\lib\endorsed
>
> [diagnostics] os.arch : x86
>
> [diagnostics] java.io.tmpdir : C:\DOCUME~1\boringj\LOCALS~1\Temp\
>
> [diagnostics] line.separator :
>
> [diagnostics]
>
> [diagnostics] java.vm.specification.vendor : Sun Microsystems Inc.
>
> [diagnostics] user.variant :
>
> [diagnostics] os.name : Windows XP
>
> [diagnostics] ant.home : D:\dev\lib\apache-ant-1.7.1
>
> [diagnostics] sun.jnu.encoding : Cp1252
>
> [diagnostics] java.library.path :
> D:\bea\jdk150_06\bin;.;C:\WINDOWS\system32;C:\WINDOWS;D:\bea\jdk150_06\b
> in;D:\oracle\product\10.2.0\client_1\bin;C:\Ent\Appl\Prod\Oracle8i\bin;C
> :\WINDOWS\system32;c:\ent\appl\prod\perl\5.00502\bin\mswin32-x86;c:\ent\
> appl\prod\perl\5.00502\bin;C:\WINDOWS;C:\WINDOWS\system32\wbem;c:\ent\ap
> pl\prod\bin;D:\dev\lib\apache-ant-1.7.1\bin;D:\dev\lib\apache-maven-2.0.
> 9\bin;C:\Program Files\QuickTime\QTSystem\
>
> [diagnostics] java.specification.name : Java Platform API Specification
>
> [diagnostics] java.class.version : 49.0
>
> [diagnostics] sun.management.compiler : HotSpot Client Compiler
>
> [diagnostics] os.version : 5.1
>
> [diagnostics] user.home : d:\data\boringj
>
> [diagnostics] user.timezone : America/New_York
>
> [diagnostics] java.awt.printerjob : sun.awt.windows.WPrinterJob
>
> [diagnostics] file.encoding : Cp1252
>
> [diagnostics] java.specification.version : 1.5
>
> [diagnostics] user.name : boringj
>
> [diagnostics] java.class.path :
> D:\dev\lib\apache-ant-1.7.1\lib\ant-launcher.jar;D:\EIIProd\dataIntegrat
> ion\DevTools\ProductBuild\.\;C:\Program
> Files\Altova\xmlspy\XMLSpyInterface.jar;D:\bea\jdk150_06\;C:\Program
> Files\Java\jre6\lib\ext\QTJava.zip;D:\dev\lib\apache-ant-1.7.1\lib\ant-a
> ntlr.jar;D:\dev\lib\apache-ant-1.7.1\lib\ant-apache-bcel.jar;D:\dev\lib\
> apache-ant-1.7.1\lib\ant-apache-bsf.jar;D:\dev\lib\apache-ant-1.7.1\lib\
> ant-apache-log4j.jar;D:\dev\lib\apache-ant-1.7.1\lib\ant-apache-oro.jar;
> D:\dev\lib\apache-ant-1.7.1\lib\ant-apache-regexp.jar;D:\dev\lib\apache-
> ant-1.7.1\lib\ant-apache-resolver.jar;D:\dev\lib\apache-ant-1.7.1\lib\an
> t-commons-logging.jar;D:\dev\lib\apache-ant-1.7.1\lib\ant-commons-net.ja
> r;D:\dev\lib\apache-ant-1.7.1\lib\ant-contrib.jar;D:\dev\lib\apache-ant-
> 1.7.1\lib\ant-jai.jar;D:\dev\lib\apache-ant-1.7.1\lib\ant-javamail.jar;D
> :\dev\lib\apache-ant-1.7.1\lib\ant-jdepend.jar;D:\dev\lib\apache-ant-1.7
> .1\lib\ant-jmf.jar;D:\dev\lib\apache-ant-1.7.1\lib\ant-jsch.jar;D:\dev\l
> ib\apache-ant-1.7.1\lib\ant-junit.jar;D:\dev\lib\apache-ant-1.7.1\lib\an
> t-launcher.jar;D:\dev\lib\apache-ant-1.7.1\lib\ant-netrexx.jar;D:\dev\li
> b\apache-ant-1.7.1\lib\ant-nodeps.jar;D:\dev\lib\apache-ant-1.7.1\lib\an
> t-starteam.jar;D:\dev\lib\apache-ant-1.7.1\lib\ant-stylebook.jar;D:\dev\
> lib\apache-ant-1.7.1\lib\ant-swing.jar;D:\dev\lib\apache-ant-1.7.1\lib\a
> nt-testutil.jar;D:\dev\lib\apache-ant-1.7.1\lib\ant-trax.jar;D:\dev\lib\
> apache-ant-1.7.1\lib\ant-weblogic.jar;D:\dev\lib\apache-ant-1.7.1\lib\an
> t.jar;D:\dev\lib\apache-ant-1.7.1\lib\xercesImpl.jar;D:\dev\lib\apache-a
> nt-1.7.1\lib\xml-apis.jar;D:\bea\jdk150_06\lib\tools.jar
>
> [diagnostics] java.vm.specification.version : 1.0
>
> [diagnostics] sun.arch.data.model : 32
>
> [diagnostics] java.home : D:\bea\jdk150_06\jre
>
> [diagnostics] java.specification.vendor : Sun Microsystems Inc.
>
> [diagnostics] user.language : en
>
> [diagnostics] awt.toolkit : sun.awt.windows.WToolkit
>
> [diagnostics] java.vm.info : mixed mode
>
> [diagnostics] java.version : 1.5.0_06
>
> [diagnostics] java.ext.dirs : D:\bea\jdk150_06\jre\lib\ext
>
> [diagnostics] sun.boot.class.path :
> D:\bea\jdk150_06\jre\lib\rt.jar;D:\bea\jdk150_06\jre\lib\i18n.jar;D:\bea
> \jdk150_06\jre\lib\sunrsasign.jar;D:\bea\jdk150_06\jre\lib\jsse.jar;D:\b
> ea\jdk150_06\jre\lib\jce.jar;D:\bea\jdk150_06\jre\lib\charsets.jar;D:\be
> a\jdk150_06\jre\classes
>
> [diagnostics] java.vendor : Sun Microsystems Inc.
>
> [diagnostics] file.separator : \
>
> [diagnostics] java.vendor.url.bug :
> http://java.sun.com/cgi-bin/bugreport.cgi
>
> [diagnostics] sun.cpu.endian : little
>
> [diagnostics] sun.io.unicode.encoding : UnicodeLittle
>
> [diagnostics] sun.desktop : windows
>
> [diagnostics] sun.cpu.isalist :
>
> [diagnostics]
>
> [diagnostics] -------------------------------------------
>
> [diagnostics] Temp dir
>
> [diagnostics] -------------------------------------------
>
> [diagnostics] Temp dir is C:\DOCUME~1\boringj\LOCALS~1\Temp\
>
> [diagnostics] Temp dir is writeable
>
> [diagnostics] Temp dir alignment with system clock is 0 ms
>
> [diagnostics]
>
> [diagnostics] -------------------------------------------
>
> [diagnostics] Locale information
>
> [diagnostics] -------------------------------------------
>
> [diagnostics] Timezone Eastern Standard Time offset=-14400000
>
> [diagnostics]
>
> [diagnostics] -------------------------------------------
>
> [diagnostics] Proxy information
>
> [diagnostics] -------------------------------------------
>
> [diagnostics] Java1.5+ proxy settings:
>
> [diagnostics] Direct connection
>
>
>
_________________________________________________________________
Hotmail® is up to 70% faster. Now good news travels really fast.
http://windowslive.com/online/hotmail?ocid=PID23391::T:WLMTAGL:ON:WL:en-US:WM_HYGN_faster:082009