[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 120 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-26012008.jar:/srv/gump/public/workspace/ant-antlibs/dotnet/build/ant-dotnet-26012008.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.027 sec [au:antunit] Target: test-passing took 0.011 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.925 sec [au:antunit] Target: testWSDL took 0.887 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.902 sec [au:antunit] Target: testCSC took 0.753 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.22 sec [au:antunit] Target: test-passing took 0.009 sec [au:antunit] Target: test-failing took 0.002 sec [au:antunit] Target: test-failing-errorproperty took 0.103 sec [au:antunit] Target: test-failing-with-fail took 0.008 sec [au:antunit] Target: test-no-assembly took 0.011 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.455 sec [au:antunit] Target: testCSCintrinsicFileset took 0.711 sec [au:antunit] Target: testCSCresponseFile took 0.609 sec [au:antunit] Target: testILASM took 0.806 sec [au:antunit] Target: testCSCdll took 0.653 sec [au:antunit] Target: testILDASM took 0.733 sec [au:antunit] Target: testILDASM_empty took 0.046 sec [au:antunit] Target: testJsharp took 0.078 sec [au:antunit] Target: testCSCResources took 0.887 sec [au:antunit] Target: testCSC took 0.702 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: 4.311 sec [au:antunit] Target: testSchemaMustBeSet took 0.084 sec [au:antunit] Target: testLocalWsdlVB took 0.023 sec [au:antunit] Target: testInvalidExtraOps took 0.075 sec [au:antunit] Target: testSrcIsMissing took 0.014 sec [au:antunit] Target: testNoParams took 0.019 sec [au:antunit] Target: testBothSrc took 0.012 sec [au:antunit] Target: testSchemaFileMustHaveOneOptionOnly took 0.013 sec [au:antunit] Target: testLocalWsdl took 1.431 sec [au:antunit] Target: testSrcIsDir took 0.027 sec [au:antunit] Target: testLocalWsdlServerVB took 0.007 sec [au:antunit] Target: testLocalWsdlServer took 2.187 sec [au:antunit] Target: testNoSrc took 0.019 sec [au:antunit] Target:
svn commit: r615445 - in /ant/ivy/core/trunk: ./ doc/use/ src/example/chained-resolvers/ src/example/chained-resolvers/chainedresolvers-project/ src/example/dependence/dependee/ src/example/dependence
Author: xavier
Date: Sat Jan 26 03:33:09 2008
New Revision: 615445
URL: http://svn.apache.org/viewvc?rev=615445view=rev
Log:
IMPROVEMENT: Review settings loading in Ant (IVY-703)
Modified:
ant/ivy/core/trunk/CHANGES.txt
ant/ivy/core/trunk/build.xml
ant/ivy/core/trunk/doc/use/settings.html
ant/ivy/core/trunk/src/example/chained-resolvers/build.xml
ant/ivy/core/trunk/src/example/chained-resolvers/chainedresolvers-project/build.xml
ant/ivy/core/trunk/src/example/dependence/dependee/build.xml
ant/ivy/core/trunk/src/example/dependence/depender/build.xml
ant/ivy/core/trunk/src/example/dual/build.xml
ant/ivy/core/trunk/src/example/dual/project/build.xml
ant/ivy/core/trunk/src/example/multi-project/common/common.xml
ant/ivy/core/trunk/src/java/org/apache/ivy/ant/IvyAntSettings.java
ant/ivy/core/trunk/src/java/org/apache/ivy/ant/IvyConfigure.java
ant/ivy/core/trunk/test/java/org/apache/ivy/ant/IvyAntSettingsTest.java
ant/ivy/core/trunk/test/java/org/apache/ivy/ant/IvyCleanCacheTest.java
ant/ivy/core/trunk/test/java/org/apache/ivy/ant/IvyConfigureTest.java
Modified: ant/ivy/core/trunk/CHANGES.txt
URL:
http://svn.apache.org/viewvc/ant/ivy/core/trunk/CHANGES.txt?rev=615445r1=615444r2=615445view=diff
==
--- ant/ivy/core/trunk/CHANGES.txt (original)
+++ ant/ivy/core/trunk/CHANGES.txt Sat Jan 26 03:33:09 2008
@@ -66,6 +66,7 @@
- NEW: Add ability for buildlist task to start build from specified module in
the list (IVY-697) (thanks to Mirko Bulovic)
- NEW: Cache dynamic revision resolution (IVY-694)
+- IMPROVEMENT: Review settings loading in Ant (IVY-703)
- IMPROVEMENT: Move useOrigin to repository cache manager (IVY-700)
- IMPROVEMENT: Make IBiblio resolver compatible with maven proxy (IVY-466)
- IMPROVEMENT: Use namespace aware validation (IVY-553)
Modified: ant/ivy/core/trunk/build.xml
URL:
http://svn.apache.org/viewvc/ant/ivy/core/trunk/build.xml?rev=615445r1=615444r2=615445view=diff
==
--- ant/ivy/core/trunk/build.xml (original)
+++ ant/ivy/core/trunk/build.xml Sat Jan 26 03:33:09 2008
@@ -47,7 +47,7 @@
/classpath
/taskdef
-ivy:settings id=ivy.instance /
+ivy:settings id=ivy.instance override=true/
/target
target name=install depends=init-ivy-home, jar
Modified: ant/ivy/core/trunk/doc/use/settings.html
URL:
http://svn.apache.org/viewvc/ant/ivy/core/trunk/doc/use/settings.html?rev=615445r1=615444r2=615445view=diff
==
--- ant/ivy/core/trunk/doc/use/settings.html (original)
+++ ant/ivy/core/trunk/doc/use/settings.html Sat Jan 26 03:33:09 2008
@@ -33,7 +33,7 @@
Multiple settings can be defined in a build script. Every task can reference
its own settings.
All Ivy variables set during the settings are available in the Ant project as
long as they were not set in Ant before (Ant properties are immutable).
-Moreover, the variables are exposed under two names: the variable name, and
the variable name suffixed by dot + the settings id (if any).
+Moreover, the variables are exposed under two names: the variable name, and
the variable name suffixed by dot + the settings id.
For instance, if you load a settings with the id 'myid', and define a variable
my.variable=my.value in the Ivy settings, both my.variable and my.variable.myid
will now be available as properties in Ant and equal to 'my.value'. If you
later load another settings with the id 'yourid', and in this settings assign
the variable 'my.variable' the value 'your.value', in the Ant project you will
have:
code
my.variable=my.value
@@ -47,10 +47,11 @@
trth class=ant-attAttribute/thth
class=ant-descDescription/thth class=ant-reqRequired/th/tr
/thead
tbody
-trtdid/tdtdThe settings id useable in the refId attributes of the
ivy task that needs a setting. Note that the ivy tasks will search by default
for the settings with the id ivy.instance./tdtdYes/td/tr
+trtdid/tdtdThe settings id useable in the settingsRef attributes
of the ivy task that needs a setting. Note that the ivy tasks will search by
default for the settings with the id ivy.instance, which is the default
value./tdtdNo, defaults to ivy.instance/td/tr
trtdfile/tdtdpath to the settings file to use/td
-td rowspan=2No. If a file is provided, url is ignored. If none are
provided, then it attempts to find a file at ${ivy.settings.file}, and if this
file does not exist, it uses a a href=../tutorial/defaultconf.htmldefault
settings file/a/td/tr
+td rowspan=2No. If a file is provided, url is ignored. If none are
provided, then it attempts to find a file at ${ivy.settings.file}, and if this
file does not exist, it uses a [[tutorial/defaultconf default settings
file]]/td/tr
trtdurl/tdtdurl
[jira] Created: (IVY-712) NPE when calling retrieve if some artifacts are not available locally
NPE when calling retrieve if some artifacts are not available locally - Key: IVY-712 URL: https://issues.apache.org/jira/browse/IVY-712 Project: Ivy Issue Type: Bug Components: Core Affects Versions: 2.0.0-beta-1 Reporter: Xavier Hanin Assignee: Xavier Hanin Fix For: 2.0.0-beta-2 When calling retrieve after a resolve with some artifacts which failed to be downloaded, Ivy throws a NullPointerException. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVY-712) NPE when calling retrieve if some artifacts are not available locally
[ https://issues.apache.org/jira/browse/IVY-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Hanin resolved IVY-712. -- Resolution: Fixed NPE when calling retrieve if some artifacts are not available locally - Key: IVY-712 URL: https://issues.apache.org/jira/browse/IVY-712 Project: Ivy Issue Type: Bug Components: Core Affects Versions: 2.0.0-beta-1 Reporter: Xavier Hanin Assignee: Xavier Hanin Fix For: 2.0.0-beta-2 When calling retrieve after a resolve with some artifacts which failed to be downloaded, Ivy throws a NullPointerException. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (IVY-713) Ivy files are not retrieved when using useOrigin=true
Ivy files are not retrieved when using useOrigin=true - Key: IVY-713 URL: https://issues.apache.org/jira/browse/IVY-713 Project: Ivy Issue Type: Bug Affects Versions: 2.0.0-beta-1 Reporter: Xavier Hanin If you use useOrigin=true in the cache, and call retrieve with an ivypattern to retrieve also Ivy files, these Ivy files are not retrieved. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
