[GUMP@brutus]: Project xml-security (in module xml-security) failed

2005-02-13 Thread Sam Ruby
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 xml-security has an issue affecting its community integration.
This issue affects 4 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- opensaml :  OpenSAML 1.0.1 is a set of open source Java and C++ 
librarie...
- wss4j :  Web Services Security (WS-Security) Java Implementation
- xml-security :  XML-Signature Syntax and Processing
- xml-security-tests :  XML-Signature Syntax and Processing


Full details are available at:
http://brutus.apache.org/gump/public/xml-security/xml-security/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [xmlsec.jar] identifier set to project name
 -DEBUG- Dependency on jce exists, no need to add for property lib.jce.
 -INFO- Failed with reason build failed
 -DEBUG- Extracted fallback artifacts from Gump Repository



The following work was performed:
http://brutus.apache.org/gump/public/xml-security/xml-security/gump_work/build_xml-security_xml-security.html
Work Name: build_xml-security_xml-security (Type: Build)
Work ended in a state of : Failed
Elapsed: 5 secs
Command Line: java -Djava.awt.headless=true -Dant.build.clonevm=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
 org.apache.tools.ant.Main 
-Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only 
-Djce.download.sha1=c1f0e975e8c8e0a0105787b249a50615b485d109 
-Dlib.jce=/usr/local/gump/packages/jce/jce-jdk13-116.jar 
-Djce.download.md5=85c64cd754719a4bc8da7e9aa0e113fd jar 
[Working Directory: /usr/local/gump/public/workspace/xml-security]
CLASSPATH: 
/opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/xml-security/build/classes:/usr/local/gump/public/workspace/xml-security:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/packages/jce/jce-jdk13-116.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar
-
Buildfile: build.xml
  [taskdef] Could not load definitions from resource clovertasks. It could not 
be found.

manifest:
[mkdir] Created dir: 
/home/gump/workspaces2/public/workspace/xml-security/build/classes/META-INF

init:

 [echo] ---
 [echo] - Apache-XML-Security-J v1.2.0 [2000-2004] ---
 [echo] ---
 [echo] Building with Apache Ant version 1.7alpha compiled on February 13 
2005
 [echo] Java 1.4.2_05 located at /opt/__versions__/jdk1.4.2_05/jre 
 [echo] ---


do.check.libs.jce:

do.check.libs:

do.build.src:

env.mk.dirs:
[mkdir] Created dir: 
/home/gump/workspaces2/public/workspace/xml-security/build/docs
[mkdir] Created dir: 
/home/gump/workspaces2/public/workspace/xml-security/build/test
[mkdir] Created dir: 
/home/gump/workspaces2/public/workspace/xml-security/build/libs
[mkdir] Created dir: 
/home/gump/workspaces2/public/workspace/xml-security/build/dist
[mkdir] Created dir: 
/home/gump/workspaces2/public/workspace/xml-security/build/samples

do.check.bindist:

build.src:
[javac] Compiling 149 source files to 
/home/gump/workspaces2/public/workspace/xml-security/build/classes
[javac] 
/home/gump/workspaces2/public/workspace/xml-security/src/org/apache/xml/security/utils/resolver/implementations/ResolverFragment.java:92:
 cannot resolve symbol
[javac] symbol  : constructor CachedXPathAPIHolder (org.w3c.dom.Document)
[javac] location: class

[GUMP@brutus]: Project xml-security (in module xml-security) failed

2005-02-13 Thread Sam Ruby
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 xml-security has an issue affecting its community integration.
This issue affects 4 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- opensaml :  OpenSAML 1.0.1 is a set of open source Java and C++ 
librarie...
- wss4j :  Web Services Security (WS-Security) Java Implementation
- xml-security :  XML-Signature Syntax and Processing
- xml-security-tests :  XML-Signature Syntax and Processing


Full details are available at:
http://brutus.apache.org/gump/public/xml-security/xml-security/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [xmlsec.jar] identifier set to project name
 -DEBUG- Dependency on jce exists, no need to add for property lib.jce.
 -INFO- Failed with reason build failed
 -DEBUG- Extracted fallback artifacts from Gump Repository



The following work was performed:
http://brutus.apache.org/gump/public/xml-security/xml-security/gump_work/build_xml-security_xml-security.html
Work Name: build_xml-security_xml-security (Type: Build)
Work ended in a state of : Failed
Elapsed: 5 secs
Command Line: java -Djava.awt.headless=true -Dant.build.clonevm=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
 org.apache.tools.ant.Main 
-Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only 
-Djce.download.sha1=c1f0e975e8c8e0a0105787b249a50615b485d109 
-Dlib.jce=/usr/local/gump/packages/jce/jce-jdk13-116.jar 
-Djce.download.md5=85c64cd754719a4bc8da7e9aa0e113fd jar 
[Working Directory: /usr/local/gump/public/workspace/xml-security]
CLASSPATH: 
/opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/xml-security/build/classes:/usr/local/gump/public/workspace/xml-security:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/packages/jce/jce-jdk13-116.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar
-
Buildfile: build.xml
  [taskdef] Could not load definitions from resource clovertasks. It could not 
be found.

manifest:
[mkdir] Created dir: 
/home/gump/workspaces2/public/workspace/xml-security/build/classes/META-INF

init:

 [echo] ---
 [echo] - Apache-XML-Security-J v1.2.0 [2000-2004] ---
 [echo] ---
 [echo] Building with Apache Ant version 1.7alpha compiled on February 13 
2005
 [echo] Java 1.4.2_05 located at /opt/__versions__/jdk1.4.2_05/jre 
 [echo] ---


do.check.libs.jce:

do.check.libs:

do.build.src:

env.mk.dirs:
[mkdir] Created dir: 
/home/gump/workspaces2/public/workspace/xml-security/build/docs
[mkdir] Created dir: 
/home/gump/workspaces2/public/workspace/xml-security/build/test
[mkdir] Created dir: 
/home/gump/workspaces2/public/workspace/xml-security/build/libs
[mkdir] Created dir: 
/home/gump/workspaces2/public/workspace/xml-security/build/dist
[mkdir] Created dir: 
/home/gump/workspaces2/public/workspace/xml-security/build/samples

do.check.bindist:

build.src:
[javac] Compiling 149 source files to 
/home/gump/workspaces2/public/workspace/xml-security/build/classes
[javac] 
/home/gump/workspaces2/public/workspace/xml-security/src/org/apache/xml/security/utils/resolver/implementations/ResolverFragment.java:92:
 cannot resolve symbol
[javac] symbol  : constructor CachedXPathAPIHolder (org.w3c.dom.Document)
[javac] location: class

can't verify the signature if xml doc is created from xml-bean

2005-02-13 Thread David Han
Hi

I have a xml doc created by apache-xml bean. This xml
doc can be signed, encrypted (RSA), decrypted but
signature can't be verified!

If I create exactly the same xml doc using Document
instead of apache xml bean, everything is OK!

Any idea? It seems to me I have to take away all
xml-bean code from my workspace.

Best Regards
David Han




__ 
Do you Yahoo!? 
All your favorites on one personal page – Try My Yahoo!
http://my.yahoo.com 


diffrent build.xml

2005-02-13 Thread Raul Benito
Hi all, I need some historic background in the xml-sec library.
I need to know why there are three different(but similar) build*.xml
files, and if we can get rid off of two of them (build-deprecated.xml
and build-ant1.5.xml) and concentrate only in build.xml
Any insight will be appreciate.
Regards,

Raul
-- 
http://r-bg.com


Re: diffrent build.xml

2005-02-13 Thread Davanum Srinivas
+1 from me to remove the old ones.

-- dims


On Sun, 13 Feb 2005 19:25:08 +0100, Raul Benito
<[EMAIL PROTECTED]> wrote:
> Hi all, I need some historic background in the xml-sec library.
> I need to know why there are three different(but similar) build*.xml
> files, and if we can get rid off of two of them (build-deprecated.xml
> and build-ant1.5.xml) and concentrate only in build.xml
> Any insight will be appreciate.
> Regards,
> 
> Raul
> --
> http://r-bg.com
> 


-- 
Davanum Srinivas - http://webservices.apache.org/~dims/


RE: diffrent build.xml

2005-02-13 Thread Axl Mattheus
Raul

The original build.xml was quite a monster. I then created build-ant1.5.xml
to leverage ant 1.5+ functionality. I am not sure where build-deprecated.xml
comes from; I remember a mail doing the rounds about a year ago around the
renaming of the build file.

For all I know, you can safely remove the afore-mentioned files. It may be
prudent to state that pre ant 1.5 will not hack it anymore if you want to
build the source.

Ax/

+1 kill all funny build files...

-Original Message-
From: Raul Benito [mailto:[EMAIL PROTECTED] 
Sent: 13 February 2005 08:25
To: security-dev@xml.apache.org
Subject: diffrent build.xml

Hi all, I need some historic background in the xml-sec library.
I need to know why there are three different(but similar) build*.xml
files, and if we can get rid off of two of them (build-deprecated.xml
and build-ant1.5.xml) and concentrate only in build.xml
Any insight will be appreciate.
Regards,

Raul
-- 
http://r-bg.com





RE: diffrent build.xml

2005-02-13 Thread Axl Mattheus
Raul

The original build.xml was quite a monster. I then created build-ant1.5.xml
to leverage ant 1.5+ functionality. I am not sure where build-deprecated.xml
comes from; I remember a mail doing the rounds about a year ago around the
renaming of the build file.

For all I know, you can safely remove the afore-mentioned files. It may be
prudent to state that pre ant 1.5 will not hack it anymore if you want to
build the source.

Ax/

+1 kill all funny build files...

-Original Message-
From: Raul Benito [mailto:[EMAIL PROTECTED] 
Sent: 13 February 2005 08:25
To: security-dev@xml.apache.org
Subject: diffrent build.xml

Hi all, I need some historic background in the xml-sec library.
I need to know why there are three different(but similar) build*.xml
files, and if we can get rid off of two of them (build-deprecated.xml
and build-ant1.5.xml) and concentrate only in build.xml
Any insight will be appreciate.
Regards,

Raul
-- 
http://r-bg.com