[EMAIL PROTECTED]: Project dotnet-antlib-test (in module ant-antlibs) failed

2008-01-24 Thread Gump Integration Build 
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 114 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-24012008.jar:/srv/gump/public/workspace/ant-antlibs/dotnet/build/ant-dotnet-24012008.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.08 sec
[au:antunit] Target: test-passing took 0.015 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.142 sec
[au:antunit] Target: testWSDL took 1.078 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.781 sec
[au:antunit] Target: testCSC took 0.745 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.272 sec
[au:antunit] Target: test-passing took 0.003 sec
[au:antunit] Target: test-failing took 0.003 sec
[au:antunit] Target: test-failing-errorproperty took 0.102 sec
[au:antunit] Target: test-failing-with-fail took 0.005 sec
[au:antunit] Target: test-no-assembly took 0.03 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.883 sec
[au:antunit] Target: testCSCintrinsicFileset took 0.761 sec
[au:antunit] Target: testCSCresponseFile took 0.664 sec
[au:antunit] Target: testILASM took 0.965 sec
[au:antunit] Target: testCSCdll took 0.673 sec
[au:antunit] Target: testILDASM took 0.751 sec
[au:antunit] Target: testILDASM_empty took 0.114 sec
[au:antunit] Target: testJsharp took 0.114 sec
[au:antunit] Target: testCSCResources took 0.782 sec
[au:antunit] Target: testCSC took 0.804 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.452 sec
[au:antunit] Target: testSchemaMustBeSet took 0.028 sec
[au:antunit] Target: testLocalWsdlVB took 0.021 sec
[au:antunit] Target: testInvalidExtraOps took 0.01 sec
[au:antunit] Target: testSrcIsMissing took 0.014 sec
[au:antunit] Target: testNoParams took 0.051 sec
[au:antunit] Target: testBothSrc took 0.018 sec
[au:antunit] Target: testSchemaFileMustHaveOneOptionOnly took 0.018 sec
[au:antunit] Target: testLocalWsdl took 1.292 sec
[au:antunit] Target: testSrcIsDir took 0.046 sec
[au:antunit] Target: testLocalWsdlServerVB took 0.027 sec
[au:antunit] Target: testLocalWsdlServer took 1.591 sec
[au:antunit] Target: testNoSrc took 0.013 sec
[au:antunit] Target:

[jira] Commented: (IVYDE-70) The project ivy configuration is not taken into account on the first run

2008-01-24 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12562078#action_12562078
 ] 

Nicolas Lalevée commented on IVYDE-70:
--

Still not sucessfull with the former solution. I asked help there :
http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.platform/msg71811.html
If I have no response I will go forward the second solution.


 The project ivy configuration is not taken into account on the first run
 

 Key: IVYDE-70
 URL: https://issues.apache.org/jira/browse/IVYDE-70
 Project: IvyDE
  Issue Type: Bug
Affects Versions: 1.3.0
 Environment: Eclipse 3.2
Reporter: Nicolas Lalevée

 Starting with an empty workspace, I import a project which already have its 
 Ivy preferences configured.
 After the import the classpath is made of some ibiblio jars, whereas I was 
 expecting the ones from my internal repository. After a resolve, the 
 classpath has the proper jars, from my internal repository.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (IVYDE-69) Order alphabetically the entries in the class path container

2008-01-24 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/IVYDE-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicolas Lalevée updated IVYDE-69:
-

Attachment: IVYDE-69-r614873.patch

Here is a patch that will keep the default ordering as Ivy one. To have the 
alphabetical order the user will have to confiure it in its project preference 
page.

 Order alphabetically the entries in the class path container
 

 Key: IVYDE-69
 URL: https://issues.apache.org/jira/browse/IVYDE-69
 Project: IvyDE
  Issue Type: New Feature
  Components: classpath container
Affects Versions: 1.3.0
Reporter: Nicolas Lalevée
Priority: Minor
 Attachments: IVYDE-69-r614873.patch, IVYDE-69.patch


 Just a tiny contribution to make entries ordered alphabetically to make 
 easier to parse visually

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.