[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 67 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: 22 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-08012008.jar:/srv/gump/public/workspace/ant-antlibs/dotnet/build/ant-dotnet-08012008.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.008 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: 1.116 sec [au:antunit] Target: testWSDL took 1.093 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: 1.06 sec [au:antunit] Target: testCSC took 1.025 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.295 sec [au:antunit] Target: test-passing took 0.01 sec [au:antunit] Target: test-failing took 0.008 sec [au:antunit] Target: test-failing-errorproperty took 0.134 sec [au:antunit] Target: test-failing-with-fail took 0.004 sec [au:antunit] Target: test-no-assembly took 0.007 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: 6.159 sec [au:antunit] Target: testCSCintrinsicFileset took 0.747 sec [au:antunit] Target: testCSCresponseFile took 0.761 sec [au:antunit] Target: testILASM took 0.878 sec [au:antunit] Target: testCSCdll took 0.585 sec [au:antunit] Target: testILDASM took 0.793 sec [au:antunit] Target: testILDASM_empty took 0.048 sec [au:antunit] Target: testJsharp took 0.014 sec [au:antunit] Target: testCSCResources took 0.792 sec [au:antunit] Target: testCSC took 1.285 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.895 sec [au:antunit] Target: testSchemaMustBeSet took 0.038 sec [au:antunit] Target: testLocalWsdlVB took 0.065 sec [au:antunit] Target: testInvalidExtraOps took 0.084 sec [au:antunit] Target: testSrcIsMissing took 0.012 sec [au:antunit] Target: testNoParams took 0.018 sec [au:antunit] Target: testBothSrc took 0.013 sec [au:antunit] Target: testSchemaFileMustHaveOneOptionOnly took 0.015 sec [au:antunit] Target: testLocalWsdl took 1.547 sec [au:antunit] Target: testSrcIsDir took 0.029 sec [au:antunit] Target: testLocalWsdlServerVB took 0.005 sec [au:antunit] Target: testLocalWsdlServer took 1.577 sec [au:antunit] Target: testNoSrc took 0.032 sec [au:antunit] Target:
[jira] Created: (IVY-696) StackOverflowError when configuration extends itself
StackOverflowError when configuration extends itself
Key: IVY-696
URL: https://issues.apache.org/jira/browse/IVY-696
Project: Ivy
Issue Type: Bug
Components: Core
Affects Versions: 2.0.0-beta-1
Reporter: Johannes Rudolph
Priority: Minor
I filed this as a bug though it is a clear usage error. But since this might
happen more often I think it should be handled more gracefully and
informatively:
If a configuration is specified to extend itself like in here:
{quote}
configurations
conf name=compile visibility=public extends=compile/
conf name=runtime/
/configurations
{quote}
Ivy doesn't complain but fails with a StackOverflowError:
{quote}
--- Nested Exception ---
java.lang.StackOverflowError
at java.util.HashMap.getEntry(HashMap.java:344)
at java.util.LinkedHashMap.get(LinkedHashMap.java:280)
at
org.apache.ivy.core.module.descriptor.DefaultModuleDescriptor.getConfiguration(DefaultModuleDescriptor.java:368)
at
org.apache.ivy.core.resolve.IvyNode.addRootModuleConfigurations(IvyNode.java:596)
at
org.apache.ivy.core.resolve.IvyNode.addRootModuleConfigurations(IvyNode.java:599)
at
org.apache.ivy.core.resolve.IvyNode.addRootModuleConfigurations(IvyNode.java:599)
at
org.apache.ivy.core.resolve.IvyNode.addRootModuleConfigurations(IvyNode.java:599)
{quote}
This might as well be valid for arbitrary configuration inheritance cycles, but
I didn't tested this.
--
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-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 67 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- Optional dependency rhino failed with reason build failed -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: 12 mins 12 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-08012008.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-08012008.jar:/srv/gump/public/workspace/apache-commons/net/dist/commons-net-08012008.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-08012008.jar:/srv/gump/public/workspace/jakarta- oro/jakarta-oro-08012008.jar:/srv/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-08012008.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-08012008.jar:/srv/gump/public/workspace/junit/dist/junit-08012008.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:rhino-gump-07012008.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-bs f-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-08012008.jar - at org.apache.tools.ant.Project.executeTargets(Project.java:1176) at org.apache.tools.ant.Main.runBuild(Main.java:758) at org.apache.tools.ant.Main.startAnt(Main.java:217) at org.apache.tools.ant.Main.start(Main.java:179)
[jira] Assigned: (IVY-466) Make IBiblio resolver compatible with maven proxy
[ https://issues.apache.org/jira/browse/IVY-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Hanin reassigned IVY-466: Assignee: Xavier Hanin Make IBiblio resolver compatible with maven proxy - Key: IVY-466 URL: https://issues.apache.org/jira/browse/IVY-466 Project: Ivy Issue Type: Improvement Reporter: Xavier Hanin Assignee: Xavier Hanin Fix For: 2.0 Maven proxy (http://maven-proxy.codehaus.org/) is a commonly used proxy for maven repositories, with which the Ivy IBiblio resolver is not compatible for the moment. Indeed, it seems that the AapacheURLLister used by Ivy is not able to list the revisions on the proxy. Using maven metadata files when available should both make this works and improve performance on maven repositories directly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (IVY-637) m2 incompatibility - IVY does not recognize property section
[ https://issues.apache.org/jira/browse/IVY-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilles Scokart reassigned IVY-637: -- Assignee: Gilles Scokart m2 incompatibility - IVY does not recognize property section Key: IVY-637 URL: https://issues.apache.org/jira/browse/IVY-637 Project: Ivy Issue Type: Bug Components: Core Affects Versions: 2.0.0-alpha-2 Reporter: David Yuctan Hodge Assignee: Gilles Scokart Priority: Critical Fix For: 2.0.0-beta-2 Ivy does not recognize the property section for example http://repo1.maven.org/maven2/org/mortbay/jetty/project/6.1.5/project-6.1.5.pom This is related to IVY-636 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (IVY-697) add ability for buildlist task to start build from specified module in the list
add ability for buildlist task to start build from specified module in the list --- Key: IVY-697 URL: https://issues.apache.org/jira/browse/IVY-697 Project: Ivy Issue Type: New Feature Components: Ant Reporter: Mirko Bulovic Priority: Minor Fix For: 2.0.0-beta-1 The buildlist task creates a list of modules in dependency order. This enhancement makes it possible to start the build from the specified module in that build list. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVY-697) add ability for buildlist task to start build from specified module in the list
[ https://issues.apache.org/jira/browse/IVY-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirko Bulovic updated IVY-697: -- Attachment: restartFrom.patch This patch provides the described functionality (including unit test and documentation). add ability for buildlist task to start build from specified module in the list --- Key: IVY-697 URL: https://issues.apache.org/jira/browse/IVY-697 Project: Ivy Issue Type: New Feature Components: Ant Reporter: Mirko Bulovic Priority: Minor Fix For: 2.0.0-beta-1 Attachments: restartFrom.patch The buildlist task creates a list of modules in dependency order. This enhancement makes it possible to start the build from the specified module in that build list. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
svn commit: r610291 - in /ant/ivy/core/trunk: ./ doc/resolver/ src/java/org/apache/ivy/plugins/resolver/ src/java/org/apache/ivy/util/url/ test/java/org/apache/ivy/plugins/resolver/ test/java/org/apac
Author: xavier Date: Tue Jan 8 23:40:34 2008 New Revision: 610291 URL: http://svn.apache.org/viewvc?rev=610291view=rev Log: IMPROVEMENT: Make IBiblio resolver compatible with maven proxy (IVY-466) Added: ant/ivy/core/trunk/src/java/org/apache/ivy/util/url/ContextualSAXHandler.java (with props) ant/ivy/core/trunk/test/java/org/apache/ivy/plugins/resolver/Maven2LocalTest.java (with props) ant/ivy/core/trunk/test/java/org/apache/ivy/util/url/archiva-listing.html (with props) ant/ivy/core/trunk/test/java/org/apache/ivy/util/url/fixed-archiva-listing.html (with props) ant/ivy/core/trunk/test/java/org/apache/ivy/util/url/maven-proxy-listing.html (with props) ant/ivy/core/trunk/test/repositories/m2/org/apache/test-metadata/ ant/ivy/core/trunk/test/repositories/m2/org/apache/test-metadata/1.0/ ant/ivy/core/trunk/test/repositories/m2/org/apache/test-metadata/1.0/test-metadata-1.0.jar (with props) ant/ivy/core/trunk/test/repositories/m2/org/apache/test-metadata/1.0/test-metadata-1.0.pom (with props) ant/ivy/core/trunk/test/repositories/m2/org/apache/test-metadata/1.1/ ant/ivy/core/trunk/test/repositories/m2/org/apache/test-metadata/1.1/test-metadata-1.1.jar (with props) ant/ivy/core/trunk/test/repositories/m2/org/apache/test-metadata/1.1/test-metadata-1.1.pom (with props) ant/ivy/core/trunk/test/repositories/m2/org/apache/test-metadata/1.2/ ant/ivy/core/trunk/test/repositories/m2/org/apache/test-metadata/1.2/test-metadata-1.2.jar (with props) ant/ivy/core/trunk/test/repositories/m2/org/apache/test-metadata/1.2/test-metadata-1.2.pom (with props) ant/ivy/core/trunk/test/repositories/m2/org/apache/test-metadata/maven-metadata.xml (with props) Modified: ant/ivy/core/trunk/CHANGES.txt ant/ivy/core/trunk/doc/resolver/ibiblio.html ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/resolver/IBiblioResolver.java ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/resolver/RepositoryResolver.java ant/ivy/core/trunk/src/java/org/apache/ivy/util/url/ApacheURLLister.java ant/ivy/core/trunk/test/java/org/apache/ivy/util/url/ApacheURLListerTest.java Modified: ant/ivy/core/trunk/CHANGES.txt URL: http://svn.apache.org/viewvc/ant/ivy/core/trunk/CHANGES.txt?rev=610291r1=610290r2=610291view=diff == --- ant/ivy/core/trunk/CHANGES.txt (original) +++ ant/ivy/core/trunk/CHANGES.txt Tue Jan 8 23:40:34 2008 @@ -60,6 +60,7 @@ = - NEW: Introduce RepositoryManagementEngine (IVY-665 - not completed yet) +- IMPROVEMENT: Make IBiblio resolver compatible with maven proxy (IVY-466) - IMPROVEMENT: Use namespace aware validation (IVY-553) - IMPROVEMENT: use ModuleRevisionId instead of ModuleId in IvySettings#getResolver (IVY-691) - IMPROVEMENT: Flexible cache management (IVY-399 - not completed yet) Modified: ant/ivy/core/trunk/doc/resolver/ibiblio.html URL: http://svn.apache.org/viewvc/ant/ivy/core/trunk/doc/resolver/ibiblio.html?rev=610291r1=610290r2=610291view=diff == --- ant/ivy/core/trunk/doc/resolver/ibiblio.html (original) +++ ant/ivy/core/trunk/doc/resolver/ibiblio.html Tue Jan 8 23:40:34 2008 @@ -42,6 +42,8 @@ /url /code +span class=sincesince 2.0/span When used in m2compatible mode with the default pattern, this resolver uses maven-metadata.xml files if present to list the revisions available on the repository. This is especially useful when using a maven specific proxy, which does not serve directory listing. This can be disable by using the useMavenMetadata flag. + h1Attributes/h1 This resolver shares the a href=../configuration/resolvers.html#commoncommon attributes/a of standard resolvers. table class=ivy-attributes @@ -56,6 +58,8 @@ trtdm2compatible/tdtdTrue if this resolver should be maven2 compatible, false otherwise span class=sincesince 1.3/span/td tdNo, defaults to false/td/tr trtdusepoms/tdtdTrue if this resolver should use maven poms when it is already in m2compatible mode, false otherwise span class=sincesince 1.4/span/td +tdNo, defaults to true/td/tr +trtduseMavenMetadata/tdtdTrue if this resolver should use maven-metadata.xml files to list available revisions, false to use directory listing span class=sincesince 2.0/span/td tdNo, defaults to true/td/tr /tbody /table Modified: ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/resolver/IBiblioResolver.java URL: http://svn.apache.org/viewvc/ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/resolver/IBiblioResolver.java?rev=610291r1=610290r2=610291view=diff == --- ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/resolver/IBiblioResolver.java (original) +++
