DO NOT REPLY [Bug 17844] Standardized deployment files for Ant optional task jars (drag + drop tasks)
https://issues.apache.org/bugzilla/show_bug.cgi?id=17844 Jan Mat [EMAIL PROTECTED] changed: What|Removed |Added CC|[EMAIL PROTECTED] | -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 21414] Bugzilla Report Generator Task
https://issues.apache.org/bugzilla/show_bug.cgi?id=21414 Jan Mat [EMAIL PROTECTED] changed: What|Removed |Added CC|[EMAIL PROTECTED] | -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 41534] quiet Formatter for Ant's JUnit Task
https://issues.apache.org/bugzilla/show_bug.cgi?id=41534 --- Comment #2 from Mathias Ricken [EMAIL PROTECTED] 2008-03-19 00:56:22 PST --- Created an attachment (id=21682) -- (https://issues.apache.org/bugzilla/attachment.cgi?id=21682) Patch file based on Ant revision 638724 I have created and attached a patch file based on Apache Ant 1.8.0alpha, revision 638724. I hope it will help in implementing this enhancement in version 1.8.0. It also includes a second formatter, oneline, that prints one line per test on success and full output on failures or errors. This second formatter has been in the modified code on my website for over a year, just not in the patch file I submitted here. http://www.superscalar.org/files/apache-ant-1.7.0-quiet/ -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[jira] Commented: (IVY-651) Ivy should be able to handle downloadUrl in POM
[ https://issues.apache.org/jira/browse/IVY-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12580307#action_12580307 ] Damien B commented on IVY-651: -- Or maybe we can just give an the instruction of where the files should be copied (resolving the artifact pattern of the shared repository if any), instead of trying to use Ivy which is almost more difficult for something as easy as a file copy. Right now it's not really as easy as a file copy (in a ivy:install scenario), because putting the jar in the final repository has no effect, even by creating manually the md5 and sha1 files. What works is to put the manually downloaded jar, and putting it in the cache repository, which is a little bit counter-intuitive, given that several people can do an ivy:install on a repository, which means that the error will be reported over and over everytime the dependency is involved. Ivy should be able to handle downloadUrl in POM --- Key: IVY-651 URL: https://issues.apache.org/jira/browse/IVY-651 Project: Ivy Issue Type: Improvement Affects Versions: 2.0.0-alpha-2 Reporter: Nat Fix For: 2.0 In Maven2, sometimes there is no jar files in the specified location but the downloadUrl is specified in POM. Ivy should be able to redirect to download the correct jar files from the specified location. For example, http://repo1.maven.org/maven2/com/bea/wlplatform/commonj-twm/1.1/commonj-twm-1.1.pom -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
DO NOT REPLY [Bug 44628] Could not create task or type of type: xmlvalidate (debian stable)
https://issues.apache.org/bugzilla/show_bug.cgi?id=44628 --- Comment #2 from Ralf Hauser [EMAIL PROTECTED] 2008-03-19 06:06:52 PST --- debian splits ant. There is an ant-optional package. This latter one further suggests to install the following packages: libbsf-java liboro-java libxalan2-java junit jython antlr libjdepend-java libgnumail-java libxml-commons-resolver1.1-java libcommons-net-java libjsch-java javacc -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 44635] New: XSLT split one CDATA block into several
https://issues.apache.org/bugzilla/show_bug.cgi?id=44635 Summary: XSLT split one CDATA block into several Product: Ant Version: 1.6.5 Platform: PC OS/Version: Windows XP Status: NEW Keywords: XSLTBug Severity: major Priority: P3 Component: Core tasks AssignedTo: notifications@ant.apache.org ReportedBy: [EMAIL PROTECTED] Hello. I have a problem with simple xslt transformation. ?xml version=1.0 encoding=windows-1251? xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xsl:output method=xml encoding=UTF-8 indent=no omit-xml-declaration=no cdata-section-elements=string/ xsl:template match=* xsl:copy xsl:for-each select=@* xsl:copy/ /xsl:for-each xsl:apply-templates/ /xsl:copy /xsl:template /xsl:stylesheet It's copy one xml-doc to another. I try to copy the next document ?xml version=1.0 encoding=UTF-8? property name=propertyComment string![CDATA[leave blank for no input, console to read from the console window, and any path to a file to read from that file]]/string /property And this is the ant-script, that i use: ?xml version=1.0 encoding=windows-1251? project default=help basedir=. target name=help xslt basedir=. destdir=.\1\ style=test.xsl force=true in=test.xml out=test.xml.new processor=trax /xslt /target /project In the output dcument I have several CDATA instead of one in source document: ?xml version=1.0 encoding=UTF-8? property name=propertyComment string![CDATA[leave blank for no input, con]]![CDATA[sole to read from the console w]]![CDATA[indow, and any path to a file to]]![CDATA[ read from that file]]/string /property When I use Microsoft xslt processor it outputs only one CDATA block in this case. Why trax output several CDATA blocks? Can I fixed it? All documents that i've mentioned are attached. Best regards, Victor -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[EMAIL PROTECTED]: Project dotnet-antlib-test (in module ant-antlibs) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project dotnet-antlib-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 115 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - dotnet-antlib-test : Task and Type Libraries for Apache Ant Full details are available at: http://vmgump.apache.org/gump/public/ant-antlibs/dotnet-antlib-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/ant-antlibs/dotnet-antlib-test/gump_work/build_ant-antlibs_dotnet-antlib-test.html Work Name: build_ant-antlibs_dotnet-antlib-test (Type: Build) Work ended in a state of : Failed Elapsed: 19 secs Command Line: /usr/lib/jvm/java-1.5.0-sun/bin/java -Djava.awt.headless=true -Xbootclasspath/p:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dant-testutil.jar=/srv/gump/public/workspace/ant/build/lib/ant-testutil.jar test [Working Directory: /srv/gump/public/workspace/ant-antlibs/dotnet] CLASSPATH: /usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/ant-antlibs/dotnet/build/test-classes:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-trax.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant-antlibs/antunit/build/ant-antunit-19032008.jar:/srv/gump/public/workspace/ant-antlibs/dotnet/build/ant-dotnet-19032008.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar - [au:antunit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.022 sec [au:antunit] Target: test-passing took 0.005 sec [au:antunit] Build File: /srv/gump/public/workspace/ant-antlibs/dotnet/src/tests/antunit/dir with spaces/wsdl-test.xml [au:antunit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.919 sec [au:antunit] Target: testWSDL took 0.873 sec [au:antunit] Build File: /srv/gump/public/workspace/ant-antlibs/dotnet/src/tests/antunit/dotnetexec-test.xml [au:antunit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.823 sec [au:antunit] Target: testCSC took 0.801 sec [au:antunit] Build File: /srv/gump/public/workspace/ant-antlibs/dotnet/src/tests/antunit/nunit/nunit-test.xml [au:antunit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.267 sec [au:antunit] Target: test-passing took 0 sec [au:antunit] Target: test-failing took 0.007 sec [au:antunit] Target: test-failing-errorproperty took 0.139 sec [au:antunit] Target: test-failing-with-fail took 0.009 sec [au:antunit] Target: test-no-assembly took 0.014 sec [au:antunit] Build File: /srv/gump/public/workspace/ant-antlibs/dotnet/src/tests/antunit/old-core-test.xml [au:antunit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 5.5 sec [au:antunit] Target: testCSCintrinsicFileset took 0.77 sec [au:antunit] Target: testCSCresponseFile took 0.594 sec [au:antunit] Target: testILASM took 0.715 sec [au:antunit] Target: testCSCdll took 0.621 sec [au:antunit] Target: testILDASM took 0.76 sec [au:antunit] Target: testILDASM_empty took 0.054 sec [au:antunit] Target: testJsharp took 0.061 sec [au:antunit] Target: testCSCResources took 0.8 sec [au:antunit] Target: testCSC took 0.734 sec [au:antunit] Build File: /srv/gump/public/workspace/ant-antlibs/dotnet/src/tests/antunit/wsdl2dotnet-test.xml [au:antunit] Tests run: 15, Failures: 0, Errors: 0, Time elapsed: 3.526 sec [au:antunit] Target: testSchemaMustBeSet took 0.027 sec [au:antunit] Target: testLocalWsdlVB took 0.028 sec [au:antunit] Target: testInvalidExtraOps took 0.011 sec [au:antunit] Target: testSrcIsMissing took 0.033 sec [au:antunit] Target: testNoParams took 0.108 sec [au:antunit] Target: testBothSrc took 0.015 sec [au:antunit] Target: testSchemaFileMustHaveOneOptionOnly took 0.017 sec [au:antunit] Target: testLocalWsdl took 1.386 sec [au:antunit] Target: testSrcIsDir took 0.028 sec [au:antunit] Target: testLocalWsdlServerVB took 0.012 sec [au:antunit] Target: testLocalWsdlServer took 1.572 sec [au:antunit] Target: testNoSrc took 0.022 sec [au:antunit] Target:
[jira] Commented: (IVYDE-87) Problem with vfs ftp and dynamic revisions
[
https://issues.apache.org/jira/browse/IVYDE-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12580465#action_12580465
]
Nicolas Lalevée commented on IVYDE-87:
--
About the Bundle-Version, I didn't mean to change it in the patch. I forgot to
revert it before creating the patch. I just change it locally so I can generate
an update site easily.
And about the patch, I am confused by the OSGI spec:
{quote}
If the class or resource is in a package that is imported using Import-
Package or was imported dynamically in a previous load, then the
request is delegated to the exporting bundle's class loader.
{quote}
The failure initially comes from Ivy code, calling commons-vfs code loading
some common-vfs class.
AFAIU these common-vfs classes
(org.apache.commons.vfs.impl.StandardFileSystemManager for instance),
Package-Imported from Ivy, should be loaded by the bundle common-vfs.
The code loading the classes of common-vfs is something like:
getClass().getClassLoader().loadClass(className);
So the class loader returned by the above code should be the common-vfs one,
not the Ivy one.
So the import package I introduced should not be needed:
org.apache.commons.vfs.provider.local,
org.apache.commons.vfs.provider.sftp,
org.apache.commons.vfs.provider.url
I should have missed something there.
And Guillaume, I am not sure you put your ivy console ouput in your comment
(the one at 14/Mar/08 07:14 AM). Could you retry cleaning the console, do a
resolve and copy paste every thing you have in there ?
Note also that the container that disapear is mainly a UI bug. You should be
able to do a resolve by doing a work around: edit your ivy library in the build
path editor and click Finish.
Problem with vfs ftp and dynamic revisions
--
Key: IVYDE-87
URL: https://issues.apache.org/jira/browse/IVYDE-87
Project: IvyDE
Issue Type: Bug
Affects Versions: 1.3.0
Environment: Eclipse 3.2 and IvyDE 1.2
Eclipse 3.3 (MyEclipse 6.0.1) and IvyDE 1.3
(org.apache.ivyde.eclipse_1.3.0.2007120912.jar)
Reporter: Guillaume
Attachments: FileZilla Server.log, IVY-738.patch,
ivy-settings-ivyde1_2.xml, ivy-settings-ivyde1_3.xml, ivy.xml,
ivy_console_log.txt, test_ant.txt, test_ant_debug.txt, test_ivyde.txt
Configuration (attachments follow)
The repository structure is a simple filesystem (on the same machine than
Eclipse and Ant for the test) :
The folder ftpuser_home\external-lib\junit\junit exists and has two
subfolders named after version numbers :
3.8.1 which contains ivy-3.8.1.xml, jars and so on
3.8.2 which contains ivy-3.8.2.xml, jars and so on
User has proper rights to list directory contents which proves to be ok with
ant task.
Using Eclipse 3.3 and IvyDE 1.3 (snapshot build -
org.apache.ivyde.eclipse_1.3.0.2007120912.jar) :
JUnit 3.8.+ gets resolved to the latest 3.8.x version available on my
repository (3.8.2 in this test) with an ant resolve task. But it isn't
resolved at all with IvyDE.
In ant, the related logs are pretty simple (ant ivy settings are pointing to
the same ivy settings file than ivyde) :
[ivy:retrieve] found junit#junit;3.8.2 in ftp
[ivy:retrieve] [3.8.2] junit#junit;3.8.+
Ivy Console summary :
{code}
WARNINGS
module not found: junit#junit;3.8.+
ftp: tried
ftp://:[EMAIL PROTECTED]/external-lib/junit/junit/3.8.+/ivy-3.8.+.xml
ftp://:[EMAIL
PROTECTED]/external-lib/junit/junit/[revision]/ivy-[revision].xml
::
:: UNRESOLVED DEPENDENCIES ::
::
:: junit#junit;3.8.+: not found
::
{code}
FTP logs :
{code}
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) USER
repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 331 Password
required for repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) PASS
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 230 Logged on
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) TYPE I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 200 Type set to I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM -
[jira] Created: (IVY-781) The retrieve task should preserve directory structure reflected in organisation's dotted notation
The retrieve task should preserve directory structure reflected in organisation's dotted notation - Key: IVY-781 URL: https://issues.apache.org/jira/browse/IVY-781 Project: Ivy Issue Type: Bug Components: Ant Affects Versions: 2.0.0-beta-2 Reporter: Carlton Brown Priority: Minor For any publish-capable m2compatible resolver, ivy:publish will map dotted notation into a nested directory structure. Currently, ivy:retrieve does not behave the same way. When you retrieve an artifact with organisation org.ivy.foo, it retrieves into a directory named org.ivy.foo. For consistency, it should map to a directory structure like org/ivy/foo the same way as ivy:publish does. I think this should be the default behavior. If someone decides they want it flattened, there could be an attribute flattenOrgNamespace or some such. This could be either a bug or an improvement, but I decided it was inconsistent and non-intuitive for publish and retrieve to handle dotted notation differently, so it could be considered a bug. WDYT? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-780) ivy properties defined in an include file not available in the file that includes it
[ https://issues.apache.org/jira/browse/IVY-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12580484#action_12580484 ] Nascif Abousalh-Neto commented on IVY-780: -- This problem got in our way when we tried to implement a multi-tier repository system, where each development branch would have its own configuration that would be linked together using include files. We thought our design would work out of the box and it didn't because of this behavior. Would be nice to see the expected behavior implemented. ivy properties defined in an include file not available in the file that includes it Key: IVY-780 URL: https://issues.apache.org/jira/browse/IVY-780 Project: Ivy Issue Type: Bug Reporter: Shawn Castrianni Now that I check the code again, it seems that any property defined in an included file is not available in the file in which it has been included. As long as we have an history for the class (Jan 24, 2007) it has been like that. I'm not sure why though, I see no added value in preventing included file to set properties in the including files. Do anybody see any reason behind this? Would it hurt to change that? Xavier -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[EMAIL PROTECTED]: Project test-ant (in module ant) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project test-ant has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 115 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - test-ant : Java based build tool Full details are available at: http://vmgump.apache.org/gump/public/ant/test-ant/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/ant/test-ant/gump_work/build_ant_test-ant.html Work Name: build_ant_test-ant (Type: Build) Work ended in a state of : Failed Elapsed: 11 mins 33 secs Command Line: /usr/lib/jvm/java-1.5.0-sun/bin/java -Djava.awt.headless=true -Xbootclasspath/p:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/srv/gump/public/workspace/xml-xalan/build/serializer.jar:/srv/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dtest.haltonfailure=false -Dant.home=/srv/gump/public/workspace/ant/dist run-tests [Working Directory: /srv/gump/public/workspace/ant] CLASSPATH: /usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/ant/build/testcases:/srv/gump/public/workspace/ant/src/tests/junit:/srv/gump/public/workspace/ant/src/etc/testcases:/srv/gump/public/workspace/ant/build/lib/ant-stylebook.jar:/srv/gump/public/workspace/ant/build/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/build/lib/ant-swing.jar:/srv/gump/public/workspace/ant/build/lib/ant-junit.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/build/lib/ant-javamail.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-bcel.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-regexp.jar:/srv/gump/public/workspace/ant/build/lib/ant-trax.jar:/srv/gump/public/workspace/ant/build/lib/ant-commons-net.jar:/srv/gump/public/workspace/ant/build/lib/ant-jsch.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-log4j.jar:/srv/gump/public/workspace/ant/build/lib/ant-antlr.jar:/srv/gump/public/workspace/ant/build/li b/ant-commons-logging.jar:/srv/gump/public/workspace/ant/build/lib/ant-jdepend.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-bsf.jar:/srv/gump/public/workspace/ant/build/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/build/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-oro.jar:/srv/gump/public/workspace/ant/build/lib/ant.jar:/srv/gump/public/workspace/ant/build/lib/ant-jai.jar:/srv/gump/packages/antlr-2.7.6/antlr.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-19032008.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-19032008.jar:/srv/gump/public/workspace/apache-commons/net/dist/commons-net-19032008.jar:/srv/gump/packages/jaf-1.1ea/activation.jar:/srv/gump/public/workspace/jakarta-bcel/target/bcel-5.3-SNAPSHOT.jar:/srv/gump/public/workspace/jakarta-bsf/build/lib/bsf.jar:/srv/gump/public/workspace/logging-log4j-12/dist/lib/log4j-19032008.jar:/srv/gump/public/workspace/jakarta- oro/jakarta-oro-19032008.jar:/srv/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-19032008.jar:/srv/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar:/srv/gump/packages/jdepend-2.6/lib/jdepend.jar:/srv/gump/packages/jsch/jsch-0.1.28.jar:/srv/gump/public/workspace/xml-stylebook/bin/stylebook-1.0-b3_xalan-2.jar:/srv/gump/public/workspace/ant-antlibs/antunit/build/ant-antunit-19032008.jar:/srv/gump/public/workspace/junit/dist/junit-19032008.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/jakarta-tomcat-4.0/dist/common/lib/jasper-compiler.jar:/srv/gump/public/workspace/jakarta-tomcat-4.0/dist/common/lib/jasper-runtime.jar:/srv/gump/public/workspace/xml-commons/java/build/which.jar:/srv/gump/public/workspace/rhino/build/rhino_19032008/js.jar:/srv/gump/packages/bsh-2.0b4/bsh-commands-2.0b4.jar:/srv/gump/packages/bsh- 2.0b4/bsh-classpath-2.0b4.jar:/srv/gump/packages/bsh-2.0b4/bsh-core-2.0b4.jar:/srv/gump/packages/bsh-2.0b4/bsh-bsf-2.0b4.jar:/srv/gump/packages/bsh-2.0b4/bsh-2.0b4.jar:/srv/gump/packages/bsh-2.0b4/bsh-reflect-2.0b4.jar:/srv/gump/packages/bsh-2.0b4/bsh-util-2.0b4.jar:/srv/gump/public/workspace/apache-commons/codec/dist/commons-codec-19032008.jar -
[EMAIL PROTECTED]: Project test-ant-no-xerces (in module ant) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project test-ant-no-xerces has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 115 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - test-ant-no-xerces : Java based build tool Full details are available at: http://vmgump.apache.org/gump/public/ant/test-ant-no-xerces/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/ant/test-ant-no-xerces/gump_work/build_ant_test-ant-no-xerces.html Work Name: build_ant_test-ant-no-xerces (Type: Build) Work ended in a state of : Failed Elapsed: 11 mins 13 secs Command Line: /usr/lib/jvm/java-1.5.0-sun/bin/java -Djava.awt.headless=true org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dtest.haltonfailure=false -Dant.home=/srv/gump/public/workspace/ant/dist run-tests [Working Directory: /srv/gump/public/workspace/ant] CLASSPATH: /usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/ant/build/testcases:/srv/gump/public/workspace/ant/src/tests/junit:/srv/gump/public/workspace/ant/src/etc/testcases:/srv/gump/public/workspace/ant/build/lib/ant-stylebook.jar:/srv/gump/public/workspace/ant/build/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/build/lib/ant-swing.jar:/srv/gump/public/workspace/ant/build/lib/ant-junit.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/build/lib/ant-javamail.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-bcel.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-regexp.jar:/srv/gump/public/workspace/ant/build/lib/ant-trax.jar:/srv/gump/public/workspace/ant/build/lib/ant-commons-net.jar:/srv/gump/public/workspace/ant/build/lib/ant-jsch.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-log4j.jar:/srv/gump/public/workspace/ant/build/lib/ant-antlr.jar:/srv/gump/public/workspace/ant/build/li b/ant-commons-logging.jar:/srv/gump/public/workspace/ant/build/lib/ant-jdepend.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-bsf.jar:/srv/gump/public/workspace/ant/build/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/build/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-oro.jar:/srv/gump/public/workspace/ant/build/lib/ant.jar:/srv/gump/public/workspace/ant/build/lib/ant-jai.jar:/srv/gump/packages/antlr-2.7.6/antlr.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-19032008.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-19032008.jar:/srv/gump/public/workspace/apache-commons/net/dist/commons-net-19032008.jar:/srv/gump/packages/jaf-1.1ea/activation.jar:/srv/gump/public/workspace/jakarta-bcel/target/bcel-5.3-SNAPSHOT.jar:/srv/gump/public/workspace/jakarta-bsf/build/lib/bsf.jar:/srv/gump/public/workspace/logging-log4j-12/dist/lib/log4j-19032008.jar:/srv/gump/public/workspace/jakarta- oro/jakarta-oro-19032008.jar:/srv/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-19032008.jar:/srv/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar:/srv/gump/packages/jdepend-2.6/lib/jdepend.jar:/srv/gump/packages/jsch/jsch-0.1.28.jar:/srv/gump/public/workspace/xml-stylebook/bin/stylebook-1.0-b3_xalan-2.jar:/srv/gump/public/workspace/ant-antlibs/antunit/build/ant-antunit-19032008.jar:/srv/gump/public/workspace/junit/dist/junit-19032008.jar:/srv/gump/public/workspace/jakarta-tomcat-4.0/dist/common/lib/jasper-compiler.jar:/srv/gump/public/workspace/jakarta-tomcat-4.0/dist/common/lib/jasper-runtime.jar:/srv/gump/public/workspace/xml-commons/java/build/which.jar:/srv/gump/public/workspace/rhino/build/rhino_19032008/js.jar:/srv/gump/packages/bsh-2.0b4/bsh-commands-2.0b4.jar:/srv/gump/packages/bsh-2.0b4/bsh-classpath-2.0b4.jar:/srv/gump/packages/bsh-2.0b4/bsh-core-2.0b4.ja r:/srv/gump/packages/bsh-2.0b4/bsh-bsf-2.0b4.jar:/srv/gump/packages/bsh-2.0b4/bsh-2.0b4.jar:/srv/gump/packages/bsh-2.0b4/bsh-reflect-2.0b4.jar:/srv/gump/packages/bsh-2.0b4/bsh-util-2.0b4.jar:/srv/gump/public/workspace/apache-commons/codec/dist/commons-codec-19032008.jar - at org.apache.tools.ant.Project.executeTargets(Project.java:1176) at org.apache.tools.ant.Main.runBuild(Main.java:762) at org.apache.tools.ant.Main.startAnt(Main.java:217) at org.apache.tools.ant.Main.start(Main.java:179) at
