svn commit: r738412 - /ant/core/trunk/src/tests/antunit/taskdefs/zip-test.xml

2009-01-28 Thread bodewig
Author: bodewig
Date: Wed Jan 28 09:22:05 2009
New Revision: 738412

URL: http://svn.apache.org/viewvc?rev=738412view=rev
Log:
turn Jesse's testcase in PR 45902 into an AntUnit test (failed before applying 
revision 738330 and passes after it)

Modified:
ant/core/trunk/src/tests/antunit/taskdefs/zip-test.xml

Modified: ant/core/trunk/src/tests/antunit/taskdefs/zip-test.xml
URL: 
http://svn.apache.org/viewvc/ant/core/trunk/src/tests/antunit/taskdefs/zip-test.xml?rev=738412r1=738411r2=738412view=diff
==
--- ant/core/trunk/src/tests/antunit/taskdefs/zip-test.xml (original)
+++ ant/core/trunk/src/tests/antunit/taskdefs/zip-test.xml Wed Jan 28 09:22:05 
2009
@@ -60,4 +60,48 @@
 unzip src=${output}/test.zip dest=${output}/out/
 au:assertFileExists file=${output}/out/WEB-INF/lib/ant.jar/
   /target
+
+target name=testIssue45902
+
description=https://issues.apache.org/bugzilla/show_bug.cgi?id=45902;
+  mkdir dir=${input}/src/p/
+  mkdir dir=${output}/
+  touch file=${input}/src/p/X.java/
+  touch file=${input}/src/p/x.properties/
+  mkdir dir=${input}/build/
+  copy todir=${input}/build
+fileset dir=${input}/src includes=**/*.java/
+  /copy
+
+  jar jarfile=${output}/jar.jar
+fileset dir=${input}/build/
+fileset dir=${input}/src excludes=**/*.java/
+  /jar
+  copy file=${output}/jar.jar tofile=${output}/reference.jar/
+
+  sleep seconds=1/
+  touch file=${input}/src/p/y.properties/
+  sleep seconds=1/
+  delete file=${input}/src/p/y.properties/
+  jar jarfile=${output}/jar.jar
+fileset dir=${input}/build/
+fileset dir=${input}/src excludes=**/*.java/
+  /jar
+  au:assertDestIsUptodate src=${output}/jar.jar
+   dest=${output}/reference.jar/
+
+  sleep seconds=1/
+  jar jarfile=${output}/jar.jar
+fileset dir=${input}/build/
+fileset dir=${input}/src excludes=**/*.java/
+  /jar
+  au:assertDestIsUptodate src=${output}/jar.jar
+   dest=${output}/reference.jar/
+
+  jar jarfile=${output}/jar.jar
+fileset dir=${input}/build/
+fileset dir=${input}/src excludes=**/*.java/
+  /jar
+  au:assertDestIsUptodate src=${output}/jar.jar
+   dest=${output}/reference.jar/
+/target
 /project




DO NOT REPLY [Bug 45902] Up-to-date checks for JARs broken due to comparison of dir timestamps

2009-01-28 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=45902


Stefan Bodewig bode...@apache.org changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |




--- Comment #3 from Stefan Bodewig bode...@apache.org  2009-01-28 01:23:06 
PST ---
I have a few issues that I'm going to raise on the dev list.

I've created an AntUnit test from your testcase: svn revision 738412 ( 
https://svn.apache.org/viewcvs.cgi?view=revrev=738412 )


-- 
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] Created: (IVY-1021) add flag or exclude option to ivy:install to avoid source or javadoc packages

2009-01-28 Thread Brian Matzon (JIRA)
add flag or exclude option to ivy:install to avoid source or javadoc packages
-

 Key: IVY-1021
 URL: https://issues.apache.org/jira/browse/IVY-1021
 Project: Ivy
  Issue Type: Improvement
  Components: Ant
Affects Versions: 2.0
 Environment: ivy  beta 2 is affected
Reporter: Brian Matzon
Priority: Critical


Changes comitted in IVY-325 results in ivy:install to install source and 
javadoc files. This is all fine, except if people dont use [type] in their 
pattern it will fail because its trying to download multiple files with the 
same name (but different type).

This is a change in behavior since 2.0 beta2.

it would be nice to either add a flag to avoid this behavior or add and 
exclude/include section, like the dependencies.

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



svn commit: r738418 - /ant/antlibs/antunit/trunk/src/main/org/apache/ant/antunit/antlib.xml

2009-01-28 Thread bodewig
Author: bodewig
Date: Wed Jan 28 09:44:06 2009
New Revision: 738418

URL: http://svn.apache.org/viewvc?rev=738418view=rev
Log:
make assertPropertyContains casesensitive flag do something useful

Modified:
ant/antlibs/antunit/trunk/src/main/org/apache/ant/antunit/antlib.xml

Modified: ant/antlibs/antunit/trunk/src/main/org/apache/ant/antunit/antlib.xml
URL: 
http://svn.apache.org/viewvc/ant/antlibs/antunit/trunk/src/main/org/apache/ant/antunit/antlib.xml?rev=738418r1=738417r2=738418view=diff
==
--- ant/antlibs/antunit/trunk/src/main/org/apache/ant/antunit/antlib.xml 
(original)
+++ ant/antlibs/antunit/trunk/src/main/org/apache/ant/antunit/antlib.xml Wed 
Jan 28 09:44:06 2009
@@ -104,7 +104,8 @@
 sequential
   au:assertPropertySet message=@{message} name=@{name}/
   au:assertTrue message=@{message}
-contains string=@{name} substring=@{value}/
+contains string=@{name} substring=@{value}
+  casesensitive=@{casesensitive}/
   /au:assertTrue
 /sequential
   /macrodef




svn commit: r738424 - /ant/core/trunk/docs/manual/CoreTasks/conditions.html

2009-01-28 Thread bodewig
Author: bodewig
Date: Wed Jan 28 09:53:15 2009
New Revision: 738424

URL: http://svn.apache.org/viewvc?rev=738424view=rev
Log:
document resourcecontains condition

Modified:
ant/core/trunk/docs/manual/CoreTasks/conditions.html

Modified: ant/core/trunk/docs/manual/CoreTasks/conditions.html
URL: 
http://svn.apache.org/viewvc/ant/core/trunk/docs/manual/CoreTasks/conditions.html?rev=738424r1=738423r2=738424view=diff
==
--- ant/core/trunk/docs/manual/CoreTasks/conditions.html (original)
+++ ant/core/trunk/docs/manual/CoreTasks/conditions.html Wed Jan 28 09:53:15 
2009
@@ -758,6 +758,40 @@
   /tr
 /table
 
+h4resourcecontains/h4
+pTests whether a resource contains a given (sub)string./p
+pThe resources to check are specified via references or - in the
+  case of file resources via the resource attribute.  bSince Ant 1.7.1/b
+/p
+table border=1 cellpadding=2 cellspacing=0
+  tr
+td width=12% valign=topbAttribute/b/td
+td width=78% valign=topbDescription/b/td
+td width=10% valign=topbRequired/b/td
+  /tr
+  tr
+td valign=topresource/td
+td valign=topName of a file that is the resource to test.
+/td
+td align=center rowspan=2One of the two/td
+  /tr
+  tr
+td valign=toprefid/td
+td valign=topReference to a resource defined inside the project./td
+  /tr
+  tr
+td valign=topsubstring/td
+td valign=topThe string to search for./td
+td valign=top align=centerYes/td
+  /tr
+  tr
+td valign=topcasesensitive/td
+td valign=topPerform a case sensitive comparision.  Default is
+true./td
+td valign=top align=centerNo/td
+  /tr
+/table
+
 h4hasmethod/h4
 
 p Tests for a class having a method or field. If the class is not found 




svn commit: r738426 - /ant/antlibs/antunit/trunk/src/main/org/apache/ant/antunit/antlib.xml

2009-01-28 Thread bodewig
Author: bodewig
Date: Wed Jan 28 09:55:10 2009
New Revision: 738426

URL: http://svn.apache.org/viewvc?rev=738426view=rev
Log:
make assertResource(Doesnt)Contain(s) casesensitive flag do something useful

Modified:
ant/antlibs/antunit/trunk/src/main/org/apache/ant/antunit/antlib.xml

Modified: ant/antlibs/antunit/trunk/src/main/org/apache/ant/antunit/antlib.xml
URL: 
http://svn.apache.org/viewvc/ant/antlibs/antunit/trunk/src/main/org/apache/ant/antunit/antlib.xml?rev=738426r1=738425r2=738426view=diff
==
--- ant/antlibs/antunit/trunk/src/main/org/apache/ant/antunit/antlib.xml 
(original)
+++ ant/antlibs/antunit/trunk/src/main/org/apache/ant/antunit/antlib.xml Wed 
Jan 28 09:55:10 2009
@@ -140,7 +140,8 @@
   default=Expected resource '@{resource}' to contain value 
'@{value}' but was '$...@{resource}}'/
 sequential
   au:assertTrue message=@{message}
-   resourcecontains resource=@{resource} substring=@{value}/
+   resourcecontains resource=@{resource} substring=@{value}
+  casesensitive=@{casesensitive}/
   /au:assertTrue
 /sequential
   /macrodef
@@ -153,7 +154,8 @@
   default=Didn't expect resource '@{resource}' to contain value 
'@{value}' but was '$...@{resource}}'/
 sequential
   au:assertFalse message=@{message}
-   resourcecontains resource=@{resource} substring=@{value}/
+   resourcecontains resource=@{resource} substring=@{value}
+  casesensitive=@{casesensitive}/
   /au:assertFalse
 /sequential
   /macrodef




svn commit: r738428 - /ant/antlibs/antunit/trunk/docs/assertions.html

2009-01-28 Thread bodewig
Author: bodewig
Date: Wed Jan 28 09:59:28 2009
New Revision: 738428

URL: http://svn.apache.org/viewvc?rev=738428view=rev
Log:
sync docs with antlib

Modified:
ant/antlibs/antunit/trunk/docs/assertions.html

Modified: ant/antlibs/antunit/trunk/docs/assertions.html
URL: 
http://svn.apache.org/viewvc/ant/antlibs/antunit/trunk/docs/assertions.html?rev=738428r1=738427r2=738428view=diff
==
--- ant/antlibs/antunit/trunk/docs/assertions.html (original)
+++ ant/antlibs/antunit/trunk/docs/assertions.html Wed Jan 28 09:59:28 2009
@@ -28,7 +28,7 @@
 assertions that are specializations of the a
 href=assert.htmllt;assertTruegt;/a task./p
 
-h2a name=assertFalseAssertFalse/a/h2
+h2a name=assertFalseassertFalse/a/h2
 
 h3Description/h3
 
@@ -172,6 +172,53 @@
   name=foo casesensitive=false/gt;
 /pre
 
+h2a name=assertPropertyContainsassertPropertyContains/a/h2
+
+pAsserts that a given property is set and holds a certain
+value as substring./p
+
+table border=1 cellpadding=2 cellspacing=0
+tr
+  td valign=topbAttribute/b/td
+  td valign=topbDescription/b/td
+  td align=center valign=topbRequired/b/td
+/tr
+tr
+  td valign=topname/td
+  td valign=topName of the property./td
+  td valign=top align=centerYes/td
+/tr
+tr
+  td valign=topvalue/td
+  td valign=topExpected substring value./td
+  td valign=top align=centerYes/td
+/tr
+tr
+  td valign=topmessage/td
+  td valign=topMessage for the exception if the condition
+doesn't hold true. Defaults to Expected property
+'emname/em' to contain value 'emvalue/em' but was
+'emvalue of property name/em'./td
+  td align=centerNo./td
+/tr
+tr
+  td valign=topcasesensitive/td
+  td valign=topPerform a case sensitive comparision.
+Default is true./td
+  td valign=top align=centerNo/td
+/tr
+/table
+
+h3Examples/h3
+
+pMake the build fail with the message foo doesn't contain bar if the
+  property foo doesn't contain the value bar regardless of case:/p
+
+pre
+  lt;assertPropertyContains message=foo doesn't contain bar value=bar
+  name=foo casesensitive=false/gt;
+/pre
+
 h2a name=assertFileExistsassertFileExists/a/h2
 
 pAsserts that a given file exists./p
@@ -238,7 +285,7 @@
   lt;assertFileDoesntExist file=${ant.home}/lib/ant.jar/gt;
 /pre
 
-h2a name=assertDestIsUpToDateassertDestIsUpToDate/a/h2
+h2a name=assertDestIsUptodateassertDestIsUptodate/a/h2
 
 pAsserts that a dest file is more recent than the source
   file./p
@@ -277,7 +324,7 @@
   lt;assertDestIsUptodate dest=${ant.file} 
src=${ant.home}/lib/ant.jar/gt;
 /pre
 
-h2a name=assertDestIsOutofDateassertDestIsOutofDate/a/h2
+h2a name=assertDestIsOutofdateassertDestIsOutofdate/a/h2
 
 pAsserts that a source file is more recent than the dest
   file./p




DO NOT REPLY [Bug 46617] New: support for source attribute for javac with build.compiler=gcj

2009-01-28 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=46617

   Summary: support for source attribute for javac with
build.compiler=gcj
   Product: Ant
   Version: unspecified
  Platform: All
OS/Version: All
Status: NEW
  Keywords: PatchAvailable
  Severity: enhancement
  Priority: P2
 Component: Core tasks
AssignedTo: notifications@ant.apache.org
ReportedBy: p...@touk.pl


Created an attachment (id=23186)
 -- (https://issues.apache.org/bugzilla/attachment.cgi?id=23186)
support for source attribute for javac with build.compiler=gcj

When build.compiler is set to gcj, ant ignores source attribute, so it is not
possible to compile code compatibile with java  1.5 with gcj using ant.

I have attached a simple patch for ant-1.7.1 sources that fixes it. Please
consider applying this patch to ant sources.


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.


[g...@vmgump]: Project test-ant (in module ant) failed

2009-01-28 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 gene...@gump.apache.org.

Project test-ant has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 37 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- Optional dependency jakarta-tomcat-4.0 prerequisite 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/gump_work/build_ant_test-ant.html
Work Name: build_ant_test-ant (Type: Build)
Work ended in a state of : Failed
Elapsed: 19 mins 46 secs
Command Line: /usr/lib/jvm/java-6-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-6-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/src/etc/testcases/taskdefs/optional/out:/srv/gump/public/workspace/ant/build/lib/ant-stylebook.jar:/srv/gump/public/workspace/ant/build/lib/ant-swing.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/build/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-regexp.jar:/srv/gump/public/workspace/ant/build/lib/ant-commons-net.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-log4j.jar:/srv/gump/public/workspace/ant/build/lib/ant-commons-logging.jar:/srv/gump/public/workspace/ant/build/lib/ant-jai.jar:/srv/gump/public/workspace/ant/build/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/build/lib/ant-launcher.jar:/srv/gump/publ
 
ic/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-apache-oro.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-bcel.jar:/srv/gump/public/workspace/ant/build/lib/ant-trax.jar:/srv/gump/public/workspace/ant/build/lib/ant-antlr.jar:/srv/gump/public/workspace/ant/build/lib/ant-junit.jar:/srv/gump/public/workspace/ant/build/lib/ant-jsch.jar:/srv/gump/public/workspace/ant/build/lib/ant-javamail.jar:/srv/gump/public/workspace/ant/build/lib/ant.jar:/srv/gump/packages/antlr-2.7.6/antlr.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-28012009.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-28012009.jar:/srv/gump/public/workspace/apache-commons/net/dist/commons-net-28012009.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-28012009.jar:/srv/gump/public/workspace/jakarta-oro/jakarta-oro-28012009.jar:/srv/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-28012009.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.38.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-28012009.jar:/srv/gump/public/workspace/junit/dist/junit-28012009.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:jasper-compiler-gump-25012009.jar:jasper-runtime-gump-25012009.jar:/srv/gump/public/workspace/xml-commons/java/build/which.jar:/srv/gump/public/workspace/rhino/build/rhino_28012009/js.jar:/srv/gump/packages/bsh-2.0b4/bsh-commands
 

[g...@vmgump]: Project test-ant-no-xerces (in module ant) failed

2009-01-28 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 gene...@gump.apache.org.

Project test-ant-no-xerces has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 181 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 jakarta-tomcat-4.0 prerequisite 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: 19 mins 21 secs
Command Line: /usr/lib/jvm/java-6-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-6-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/src/etc/testcases/taskdefs/optional/out:/srv/gump/public/workspace/ant/build/lib/ant-stylebook.jar:/srv/gump/public/workspace/ant/build/lib/ant-swing.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/build/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-regexp.jar:/srv/gump/public/workspace/ant/build/lib/ant-commons-net.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-log4j.jar:/srv/gump/public/workspace/ant/build/lib/ant-commons-logging.jar:/srv/gump/public/workspace/ant/build/lib/ant-jai.jar:/srv/gump/public/workspace/ant/build/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/build/lib/ant-launcher.jar:/srv/gump/publ
 
ic/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-apache-oro.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-bcel.jar:/srv/gump/public/workspace/ant/build/lib/ant-trax.jar:/srv/gump/public/workspace/ant/build/lib/ant-antlr.jar:/srv/gump/public/workspace/ant/build/lib/ant-junit.jar:/srv/gump/public/workspace/ant/build/lib/ant-jsch.jar:/srv/gump/public/workspace/ant/build/lib/ant-javamail.jar:/srv/gump/public/workspace/ant/build/lib/ant.jar:/srv/gump/packages/antlr-2.7.6/antlr.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-28012009.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-28012009.jar:/srv/gump/public/workspace/apache-commons/net/dist/commons-net-28012009.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-28012009.jar:/srv/gump/public/workspace/jakarta-oro/jakarta-oro-28012009.jar:/srv/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-28012009.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.38.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-28012009.jar:/srv/gump/public/workspace/junit/dist/junit-28012009.jar:jasper-compiler-gump-25012009.jar:jasper-runtime-gump-25012009.jar:/srv/gump/public/workspace/xml-commons/java/build/which.jar:/srv/gump/public/workspace/rhino/build/rhino_28012009/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/pa
 
ckages/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-28012009.jar
-
[au:antunit] Target: testunion took 0.018 sec
[au:antunit] Target: testhttpurl1 took 0.692 sec
[au:antunit] Target: testresource took 0.008 sec
[au:antunit] 

[jira] Created: (IVYDE-158) NullPointerException from IvyDE on startup.

2009-01-28 Thread Paul Loveridge (JIRA)
NullPointerException from IvyDE on startup.
---

 Key: IVYDE-158
 URL: https://issues.apache.org/jira/browse/IVYDE-158
 Project: IvyDE
  Issue Type: Bug
 Environment: Eclipse Ganymede, Windows XP Pro, java 6, IvyDE 
2.0.0.beta1
Reporter: Paul Loveridge


When starting eclipse all projects with any ivy dependency library in their 
build path generate this error :

An internal error occurred during: Resolve project 'acceptance' and 
ivy file 'ivy.xml' dependencies.

I also notice that although the ivy.xml file is still present in the project 
root the library entry (which usually appears underneath the JRE System Library 
entry) is not present.

Work Around
---
If I remove the ivy library from the build path , close the dialog and then 
re-open the dialog and re-attached the ivy library then everything compiles 
correctly.  


Stack Trace
---
java.lang.NullPointerException
at 
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainerConfiguration.setConfStatus(IvyClasspathContainerConfiguration.java:361)
at 
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainerConfiguration.getModuleDescriptor(IvyClasspathContainerConfiguration.java:688)
at 
org.apache.ivyde.eclipse.cpcontainer.IvyResolveJob.run(IvyResolveJob.java:197)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

ivysettings.xml
---
?xml version=1.0 encoding=utf-8?
ivysettings
classpath file=${ivy.settings.dir}/lib/ivysvnresolver.jar /  
classpath file=${ivy.settings.dir}/lib/trilead.jar /  
classpath file=${ivy.settings.dir}/lib/svnkit.jar /  
properties file=${ivy.settings.dir}/ivy.properties override=true /
typedef name=svn 
classname=fm.last.ivy.plugins.svnresolver.SvnResolver /
settings defaultResolver=trunkresolver /
caches defaultCacheDir=${ivy.cache.dir} /
resolvers checkModified=${ivy.resolver.default.check.modified}
svn name=ivysvn 
 repositoryRoot=${repository.root}
 userName=${svn.user} 
 userPassword=${svn.password}
 ivy

pattern=${ivy.repository}/[organisation]/[module]/[revision]/ivy.xml /
 artifact

pattern=${ivy.repository}/[organisation]/[module]/[revision]/[artifact].[ext] 
/
/svn
filesystem name=filesystem
ivy pattern=${trunk.dir}/[module]/ivy.xml /
artifact pattern=${trunk.dir}/[module]/module.jar /
/filesystem
chain name=trunkresolver returnFirst=true 
resolver ref=ivysvn /
resolver ref=filesystem /
/chain
/resolvers
/ivysettings

ivyconfs.xml

configurations
conf name=dev visibility=public extends=test,db2,oracle,sqlserver 
description=Test and all JDBC drivers/
conf name=compile visibility=public description=Resources only 
required by compile, usually ones that are container provided at runtime/
conf name=runtime visibility=public description=Dependencies for 
distribution/
conf name=test visibility=public extends=compile,runtime 
description=Compile + anything that running unit tests depends on/   
conf name=db2 visibility=public description=DB2 JDBC driver set/
conf name=oracle visibility=public description=Oracle JDBC driver 
set/
conf name=sqlserver visibility=public description=SQLServer JDBC 
driver set/
conf name=activemq visibility=private description=ActiveMQ runtime/ 

/configurations

ivy.properties
--
org.name=tallyman
repository.root=***REDEDACTED**
ivy.repository=/tallyman/ivyrepos/trunk
ivy.resolver.default.check.modified=true
trunk.dir=${ivy.settings.dir}/..
ivy.cache.dir=${trunk.dir}/.ivycache
svn.user=
svn.password=

I've redacted the repository.root but it's just a standard http: based svn 
location, of the form http://server/svn/product - I'm making sure I don't end 
up in the smelly stuff with my manager.

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



[Ant Wiki] Update of Proposals/EnhancedTestReports by PetarTahchiev

2009-01-28 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Ant Wiki for change 
notification.

The following page has been changed by PetarTahchiev:
http://wiki.apache.org/ant/Proposals/EnhancedTestReports

--
  
   * Standard serializable Java types for tests. Must include log entries and 
exceptions. These can be marshalled over RMI or serialised to text files. 
Enables a tight coupling of reporting across processes. It is however, hard to 
maintain stability, especially with OSS code that can be changed by anyone. The 
limit of these type's use would probably be the junit test runner and ant 
itself, both from the same point release of Ant.
  
-  * Streamed XHTML with standard class names. Here an inline CSS sheet 
provides the styles, and tests are streamed to disk as marked up div/span 
clauses. oes not directly scale well to presenting very large test runs; 
postprocessing is required. XSL can still generate alternate reports, though 
the XPath patterns are more complex //d...@class=error] instead of //error. 
+  * Streamed XHTML with standard class names. Here an inline CSS sheet 
provides the styles, and tests are streamed to disk as marked up div/span 
clauses. Does not directly scale well to presenting very large test runs; 
postprocessing is required. XSL can still generate alternate reports, though 
the XPath patterns are more complex //d...@class=error] instead of //error. 
  
   * Atom. Here every test result would be presented as an Atom entry, possibly 
using streamed XHTML as above. Enables remote systems to poll for changes, and 
for browsers to present results as is. Does not directly scale well to 
presenting very large test runs; postprocessing is required. XPath is even more 
complex. 
  
@@ -75, +75 @@

   * SmartFrog team (SteveLoughran)
   * TestNG: AlexandruPopescu 
   * Maven SureFire: DanFabulich, BrettPorter
+  * Cactus framework: Petar Tahchiev
  
  == Plan and Timetable ==
  
@@ -164, +165 @@

   * list tests by tag
   * list tests by execution time
   * list tests that are partial failures, unfinished
+  * might be a good idea to have a 'sort-by-column' feature. This way you sort 
columns by test-name, execution-time, test-status, etc. (Petar Tahchiev) 
   * for tests that are published to a web site, integrate with searching 
(allow a search box in the HTML)
   * list failing tests by exception name
   * For live output, provide an ongoing status page that updates regularly.
@@ -199, +201 @@

  === Integration with Issue Trackers ===
  
  What would this look like? Perhaps and element with URLs to related issues?
+ 
+ Petar Tahchiev: This could be easily integrated with Maven, since Maven keeps 
track of the Issue Management System in the POM. This way we might only keep 
the ISSUE # in the xml and the maven surefire-reports plugin can construct the 
URLs.
+ 
+ === Integration with SCM ===
+ 
+ I would really like the idea of polling some info from the SCM, like for 
instance the user, who added the test-case(or the test-method). This way if a 
test is failing and you can't realize why is this happening, you can consult 
with the guy who wrote the test-case.
  
  
  === Generate Google Charts ===


DO NOT REPLY [Bug 46612] bug in default XSLT processor: Predicate ignored for self::some_qname

2009-01-28 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=46612





--- Comment #4 from Daniel B. d...@smart.net  2009-01-28 07:44:47 PST ---
(In reply to comment #3)
 Ant uses the XSLT processor of the JDK or whatever you specify via the 
 endorsed
 standards mechanism (or the task's factory configuration) - ...
 
 In any case it is a bug in the processor, not in Ant, 

Yes, I know.  Did you read the last paragraph of my report?


 and there is nothing we could do.

You could tell me what Ant does:

- mainly, what the task's factory configuration does.  (Does it do 
  nothing special and probably therefore cause use of the JDK's default 
  XSLT processor, or does it possibly so something else?), and

- whether Ant does anything different than calling the JDk's 
  normal/default API methods for transforming, and, if so, what Ant does.

And even though it's not part of Ant, since you (or someone reading this)
likely know better than I do, what is the default XSLT transformer for
JDK 1.6(.11) (so in case Sun is going to also say it's not our bug, see
xyz, I can jump directly to xyz to report the problem)?  Is it Xalan,
or something else?  Which version?


(I'm trying to get enough information to be able to reproduce the
bug outside of Ant without spending as much time as I did beating 
against the bug in the first place.)



Hey, you changed the status to RESOLVED INVALID before the upstream bug 
in Ant's _default_ XSLT transformer for the _core_ XSLT task was fixed.  

If the bug were a non-default transformer, I'd agree, but this isn't
some optional task or a custom configuration. 

Why not track upstream bugs that affect Ant to make sure they get fixed
(e.g., the way Debian GNU/Linux tracks such bugs, tracking the bug in 
the Debian bug system (marked as reported upstream, not for the Debian 
maintainer to actually fix but just to monitor for a fix from upstream)
until the bug is fixed by the upstream maintainer?  (Wouldn't you
track in and report it upstream if the bug were in the default XML 
processor used for reading build.xml files?)


-- 
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] Created: (IVYDE-159) Explicit ordering of configurations

2009-01-28 Thread Will Gorman (JIRA)
Explicit ordering of configurations
---

 Key: IVYDE-159
 URL: https://issues.apache.org/jira/browse/IVYDE-159
 Project: IvyDE
  Issue Type: Improvement
Reporter: Will Gorman


In IvyDE, I can select which configurations are used in the eclipse 
environment, but I can't specify in which order the jar files are listed in the 
classpath.  This is important in our JUnit environment, because we have mock 
jars that override the default jars for testing.  In our Ant environment, the 
test configuration appears in the classpath before the default configuration, 
but I can't specify that in IvyDE.

-- 
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 46612] ant -diagnostics should talk about the XSLT processor

2009-01-28 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=46612


Stefan Bodewig bode...@apache.org changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |
Summary|bug in default XSLT |ant -diagnostics should talk
   |processor: Predicate ignored|about the XSLT processor
   |for self::some_qname|




--- Comment #5 from Stefan Bodewig bode...@apache.org  2009-01-28 08:43:52 
PST ---
Sorry if I sounded too harsh.

If you run ant -diagnostics it may help you - hmm, I just now realize it only
talks about the XML parser but not the XSLT processor, reopening because of
that.

The XSLT task allows you to configure the factory, that's why I talked about
it.  Yes, the default is to go with whatever the system provides.

What the system provides depends on your vendor.  Sun has decided to ship a
(pretty old and buggy) version of XSLTC, a variant of Apache Xalan-J that
doesn't seem to become Xalan's main line anytime as their processor with Java5
and I think they still do with Java6.  I may be wrong, though.

Point 13 in http://java.sun.com/j2se/1.5.0/compatibility.html is the best hint
I can give.  See also point 9 of that list.

I happen to be involved with XMLUnit as well and we've gotten lots of problem
reports because of Java5's XSLT processor.  I've come to the conclusion to
recommend the endorsed standards mechanism and the latest release of Xalan or
Saxon to anybody doing XSLT since the default in Sun classlibs is seriously
broken (and you've just hit one symptom).

I've resolved it as INVALID because it is not an Ant bug.  We (the Ant
community) don't think of the JDK as our upstream and even if we did, since we
don't bundle a JDK and have different release cycles this would be impossible
to track.

The problem you see likely doesn't affect people using Apple's JVM on a Mac,
IBM's on anything, OpenJDK 6 or Apache Harmony, for example (they will see
different bugs).

IMHO there is a difference between a distribution that bundles packages and a
single package that happens to depend on another package which may be provided
by several different vendors.

And no, we wouldn't track an issue in Xerces (which happens to be the default
parser for most JDKs - in different versions, of course) here either.


-- 
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 46612] ant -diagnostics should talk about the XSLT processor

2009-01-28 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=46612


Stefan Bodewig bode...@apache.org changed:

   What|Removed |Added

 CC||notifications@ant.apache.org
 AssignedTo|notifications@ant.apache.org|bode...@apache.org
   Severity|normal  |enhancement
 Status|REOPENED|NEW
 OS/Version|Windows XP  |All
   Target Milestone|--- |1.8.0




-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug.
You are the assignee for the bug.


DO NOT REPLY [Bug 46617] support for source attribute for javac with build.compiler=gcj

2009-01-28 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=46617


Stefan Bodewig bode...@apache.org changed:

   What|Removed |Added

 CC||notifications@ant.apache.org
 AssignedTo|notifications@ant.apache.org|bode...@apache.org
   Target Milestone|1.7.1   |1.8.0
Version|unspecified |1.7.1




--- Comment #1 from Stefan Bodewig bode...@apache.org  2009-01-28 08:50:13 
PST ---
Do you know which version of gcj was/is the first to support -source?


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug.
You are the assignee for the bug.


DO NOT REPLY [Bug 46617] support for source attribute for javac with build.compiler=gcj

2009-01-28 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=46617





--- Comment #2 from Paweł Zuzelski p...@touk.pl  2009-01-28 08:53:59 PST ---
(In reply to comment #1)
 Do you know which version of gcj was/is the first to support -source?
 

No, I don't know. I use 4.3.2.

BTW in gcj it is -fsource not -source


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug.

[jira] Commented: (IVY-996) Remove excessive HEAD requests for URL repository

2009-01-28 Thread Eric Anderson (JIRA)

[ 
https://issues.apache.org/jira/browse/IVY-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12668076#action_12668076
 ] 

Eric Anderson commented on IVY-996:
---

Thank you very much for your help. As soon as there is a way for me to run with 
this in Eclipse, I can get my guys to test it.

 Remove excessive HEAD requests for URL repository
 -

 Key: IVY-996
 URL: https://issues.apache.org/jira/browse/IVY-996
 Project: Ivy
  Issue Type: Improvement
  Components: Core
Affects Versions: 2.0-RC2
Reporter: Eric Anderson
Assignee: Xavier Hanin
 Fix For: trunk


 h3. Fixing useless extra HEAD requests
 When searching for an artifact named project version 2.2.+ for 
 organization org, Ivy attempts HEAD requests for completely not possible 
 versions.
 IE: /org/project/0.9.2/ivy-0.9.2.xml
 This is not terribly painful unless you have thousands of builds and are not 
 on the same network as your ivy server. 
 h3. Are HEAD requests even necessary?
 Simply getting a directory listing should be good enough to determine if 
 there is an artifact (for choosing latest-release). Now, after one is chosen, 
 if no ivy.xml file exists, I could understand trying the next one, but trying 
 all of them, just to select the latest one anyways seems like a complete 
 waste.

-- 
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 42940] Zip ExtraField header size is hard coded as 4 bytes

2009-01-28 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=42940





--- Comment #6 from Paul M. Suchko suchko...@mellon.com  2009-01-28 10:14:28 
PST ---
Yes.  That is correct.

I removed everything from the file except what was needed to reproduce the
problem in ANT.


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug.


[jira] Created: (IVY-1022) Forced resolver behavior is inappropriate for ivy:install

2009-01-28 Thread Carlton Brown (JIRA)
Forced resolver behavior is inappropriate for ivy:install
-

 Key: IVY-1022
 URL: https://issues.apache.org/jira/browse/IVY-1022
 Project: Ivy
  Issue Type: Bug
  Components: Ant
Affects Versions: 2.0
Reporter: Carlton Brown


I tried to install a certain revision of a module from a chained resolver to an 
fs resolver, and observed that Ivy installed a revision other than what I 
specified.   After investigation I noticed that the chain contained a forced fs 
resolver.   I removed the forced resolver from the chain, replacing it with an 
equivalent un-forced fs resolver.   The install worked correctly after that.   

I think that ivy:install should not be doing any dynamic version resolution at 
all.   It should in every case use the literal module identifiers that are 
passed to it.   This being the case, install should ignore a force attribute 
wherever it is encountered.

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



[jira] Updated: (IVY-987) Error message: impossible to get artifacts when data has not been loaded , on certain modules only

2009-01-28 Thread Maarten Coene (JIRA)

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

Maarten Coene updated IVY-987:
--

Affects Version/s: (was: 2.0-RC2)
   2.0

The problem still exists in the 2.0.0 release.

I think it is caused because all the dependencies defined in a pom are forced 
to the revision in the pom.
It seems to me that the latest-revision ConflictManager doesn't handle the 
situation correctly when there is more than 1 forced version of the same module 
requested.

Xavier: what should the conflict manager do in this situation?

 Error message: impossible to get artifacts when data has not been loaded , 
 on certain modules only
 

 Key: IVY-987
 URL: https://issues.apache.org/jira/browse/IVY-987
 Project: Ivy
  Issue Type: Bug
Affects Versions: 2.0
 Environment: ubuntu 8.04, java .1.6.0_06 Java HotSpot(TM) Client VM, 
 calling external ant 1.7  from netbeans 6.1 IDE, ivy ant task in ants home 
 lib dir 
Reporter: K. Rekk

 I found a similiar post here:
 http://www.mail-archive.com/ivy-u...@ant.apache.org/msg01766.html
  Everything worked fine with 2.0.0 beta .
 
  It's just a simple test and dom4j seems to cause the problem with
  standard ivysettings :
 dependencies
 dependency org=dom4j name=dom4j rev=1.6.1/
  dependency org=log4j name=log4j rev=1.2.9/
 dependency org=junit name=junit rev=4.5/
 /dependencies
  /ivy-module
 Removing dom4j makes it work again.
 So I dont know, is it dom4j or ivy causing the problem?
  output:
 
  init:
  deps-jar:
  ivy-retrieve:
  No ivy:settings found for the default reference 'ivy.instance'.  A
  default instance will be used
  no settings file found, using default...
  :: loading settings :: url =
  jar:file:/home/kostja/VZG/soa-workarea-ref/tools/ant/lib/ivy-2.0.0-rc2.jar!/org/apache/ivy/core/settings/ivysettings.xml
  :: resolving dependencies :: gbv.de#test;work...@myhome
 confs: [default]
 found dom4j#dom4j;1.6.1 in public
 found xml-apis#xml-apis;1.0.b2 in public
 found jaxme#jaxme-api;0.3 in public
 found jaxen#jaxen;1.1-beta-6 in public
 found jdom#jdom;1.0 in public
 found xerces#xmlParserAPIs;2.6.2 in public
 found xerces#xercesImpl;2.6.2 in public
 found xom#xom;1.0b3 in public
 found com.ibm.icu#icu4j;2.6.1 in public
 found org.ccil.cowan.tagsoup#tagsoup;0.9.7 in public
 found msv#xsdlib;20030807 in public
 found msv#relaxngDatatype;20030807 in public
 found pull-parser#pull-parser;2 in public
 found xpp3#xpp3;1.1.3.3 in public
 found stax#stax-api;1.0 in public
 found log4j#log4j;1.2.9 in public
 found junit#junit;4.5 in public
 
  :: problems summary ::
   ERRORS
 impossible to get artifacts when data has not been loaded.
  IvyNode = xalan#xalan;2.5.1
  :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
  /home/kostja/VZG/soa-workarea-ref/projects/Test/build.xml:15: impossible
  to resolve dependencies:
 java.lang.IllegalStateException: impossible to get artifacts
  when data has not been loaded. IvyNode = xalan#xalan;2.5.1
  BUILD FAILED (total time: 0 seconds)

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



[jira] Assigned: (IVY-1006) Support for opensll sha1 and md5 checksum

2009-01-28 Thread Maarten Coene (JIRA)

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

Maarten Coene reassigned IVY-1006:
--

Assignee: Maarten Coene

 Support for opensll sha1 and md5 checksum
 -

 Key: IVY-1006
 URL: https://issues.apache.org/jira/browse/IVY-1006
 Project: Ivy
  Issue Type: Bug
  Components: Maven Compatibility
Affects Versions: 2.0-RC2
Reporter: Finn Bock
Assignee: Maarten Coene

 Checksum files created by openssl have a different format and some of these 
 files have moved to the maven repo:
 http://repo2.maven.org/maven2/xalan/xalan/2.7.1/xalan-2.7.1.jar.sha1
 I think ivy should match mavens support for these checksum files.

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



[jira] Updated: (IVY-1006) Support for opensll sha1 and md5 checksum

2009-01-28 Thread Maarten Coene (JIRA)

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

Maarten Coene updated IVY-1006:
---

Affects Version/s: 2.0

 Support for opensll sha1 and md5 checksum
 -

 Key: IVY-1006
 URL: https://issues.apache.org/jira/browse/IVY-1006
 Project: Ivy
  Issue Type: Bug
  Components: Maven Compatibility
Affects Versions: 2.0-RC2, 2.0
Reporter: Finn Bock
Assignee: Maarten Coene

 Checksum files created by openssl have a different format and some of these 
 files have moved to the maven repo:
 http://repo2.maven.org/maven2/xalan/xalan/2.7.1/xalan-2.7.1.jar.sha1
 I think ivy should match mavens support for these checksum files.

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



svn commit: r738662 - in /ant/ivy/core/trunk: ./ src/java/org/apache/ivy/util/ test/repositories/checksums/allright/

2009-01-28 Thread maartenc
Author: maartenc
Date: Wed Jan 28 23:14:05 2009
New Revision: 738662

URL: http://svn.apache.org/viewvc?rev=738662view=rev
Log:
FIX: Support for opensll sha1 and md5 checksum (IVY-1006)

Added:

ant/ivy/core/trunk/test/repositories/checksums/allright/allright-1.0.jar.sha1

ant/ivy/core/trunk/test/repositories/checksums/allright/allright-with-openssl-1.0.jar
   (with props)

ant/ivy/core/trunk/test/repositories/checksums/allright/allright-with-openssl-1.0.jar.sha1
Modified:
ant/ivy/core/trunk/CHANGES.txt
ant/ivy/core/trunk/src/java/org/apache/ivy/util/ChecksumHelper.java
ant/ivy/core/trunk/test/repositories/checksums/allright/ivy-1.0.xml
ant/ivy/core/trunk/test/repositories/checksums/allright/ivy-1.0.xml.md5

Modified: ant/ivy/core/trunk/CHANGES.txt
URL: 
http://svn.apache.org/viewvc/ant/ivy/core/trunk/CHANGES.txt?rev=738662r1=738661r2=738662view=diff
==
--- ant/ivy/core/trunk/CHANGES.txt (original)
+++ ant/ivy/core/trunk/CHANGES.txt Wed Jan 28 23:14:05 2009
@@ -93,6 +93,7 @@
 - IMPROVEMENT: Error message is not clear when specifying an invalid value for 
checksums (IVY-977)
 - IMPROVEMENT: catch AccessControlException on System.getProperties() 
(IVY-1015)
 
+- FIX: Support for opensll sha1 and md5 checksum (IVY-1006)
 - FIX: TTL does not work as expected (IVY-1012)
 - FIX: Listing of URL's under a given URL does not handle fully specified 
URL's (IVY-959) (thanks to Randy Nott)
 - FIX: ivy:buildnumber returns wrong result when resolve fails (IVY-970)

Modified: ant/ivy/core/trunk/src/java/org/apache/ivy/util/ChecksumHelper.java
URL: 
http://svn.apache.org/viewvc/ant/ivy/core/trunk/src/java/org/apache/ivy/util/ChecksumHelper.java?rev=738662r1=738661r2=738662view=diff
==
--- ant/ivy/core/trunk/src/java/org/apache/ivy/util/ChecksumHelper.java 
(original)
+++ ant/ivy/core/trunk/src/java/org/apache/ivy/util/ChecksumHelper.java Wed Jan 
28 23:14:05 2009
@@ -55,13 +55,19 @@
 String csFileContent = FileUtil.readEntirely(
 new BufferedReader(new 
FileReader(checksumFile))).trim().toLowerCase(Locale.US);
 String expected;
-int spaceIndex = csFileContent.indexOf(' ');
-if (spaceIndex != -1) {
-expected = csFileContent.substring(0, spaceIndex);
+if (csFileContent.indexOf(' ')  -1
+ (csFileContent.startsWith(md) || 
csFileContent.startsWith(sha))) {
+int lastSpaceIndex = csFileContent.lastIndexOf(' ');
+expected = csFileContent.substring(lastSpaceIndex + 1);
 } else {
-expected = csFileContent;
+int spaceIndex = csFileContent.indexOf(' ');
+if (spaceIndex != -1) {
+expected = csFileContent.substring(0, spaceIndex);
+} else {
+expected = csFileContent;
+}
 }
-
+
 String computed = computeAsString(dest, 
algorithm).trim().toLowerCase(Locale.US);
 if (!expected.equals(computed)) {
 throw new IOException(invalid  + algorithm + : expected= + 
expected +  computed=

Added: 
ant/ivy/core/trunk/test/repositories/checksums/allright/allright-1.0.jar.sha1
URL: 
http://svn.apache.org/viewvc/ant/ivy/core/trunk/test/repositories/checksums/allright/allright-1.0.jar.sha1?rev=738662view=auto
==
--- 
ant/ivy/core/trunk/test/repositories/checksums/allright/allright-1.0.jar.sha1 
(added)
+++ 
ant/ivy/core/trunk/test/repositories/checksums/allright/allright-1.0.jar.sha1 
Wed Jan 28 23:14:05 2009
@@ -0,0 +1 @@
+1acaeaa173e330150b59da1b2fd6bc8597b6992c
\ No newline at end of file

Added: 
ant/ivy/core/trunk/test/repositories/checksums/allright/allright-with-openssl-1.0.jar
URL: 
http://svn.apache.org/viewvc/ant/ivy/core/trunk/test/repositories/checksums/allright/allright-with-openssl-1.0.jar?rev=738662view=auto
==
Binary file - no diff available.

Propchange: 
ant/ivy/core/trunk/test/repositories/checksums/allright/allright-with-openssl-1.0.jar
--
svn:mime-type = application/octet-stream

Added: 
ant/ivy/core/trunk/test/repositories/checksums/allright/allright-with-openssl-1.0.jar.sha1
URL: 
http://svn.apache.org/viewvc/ant/ivy/core/trunk/test/repositories/checksums/allright/allright-with-openssl-1.0.jar.sha1?rev=738662view=auto
==
--- 
ant/ivy/core/trunk/test/repositories/checksums/allright/allright-with-openssl-1.0.jar.sha1
 (added)
+++ 
ant/ivy/core/trunk/test/repositories/checksums/allright/allright-with-openssl-1.0.jar.sha1
 Wed Jan 28 23:14:05 2009
@@ -0,0 +1 @@
+SHA1(allright-with-openssl-1.0.jar)= 

[jira] Resolved: (IVY-1006) Support for opensll sha1 and md5 checksum

2009-01-28 Thread Maarten Coene (JIRA)

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

Maarten Coene resolved IVY-1006.


   Resolution: Fixed
Fix Version/s: trunk

Should be fixed in SVN trunk.
Could you give it a try?

thanks for the report!
Maarten

 Support for opensll sha1 and md5 checksum
 -

 Key: IVY-1006
 URL: https://issues.apache.org/jira/browse/IVY-1006
 Project: Ivy
  Issue Type: Bug
  Components: Maven Compatibility
Affects Versions: 2.0-RC2, 2.0
Reporter: Finn Bock
Assignee: Maarten Coene
 Fix For: trunk


 Checksum files created by openssl have a different format and some of these 
 files have moved to the maven repo:
 http://repo2.maven.org/maven2/xalan/xalan/2.7.1/xalan-2.7.1.jar.sha1
 I think ivy should match mavens support for these checksum files.

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



svn commit: r738761 - in /ant/core/trunk: CONTRIBUTORS WHATSNEW contributors.xml docs/manual/CoreTasks/javac.html src/main/org/apache/tools/ant/taskdefs/Javac.java src/main/org/apache/tools/ant/taskde

2009-01-28 Thread bodewig
Author: bodewig
Date: Thu Jan 29 05:23:52 2009
New Revision: 738761

URL: http://svn.apache.org/viewvc?rev=738761view=rev
Log:
support source/target on gcj.  PR 46617.  Based on patch by Paweł Zuzelski

Modified:
ant/core/trunk/CONTRIBUTORS
ant/core/trunk/WHATSNEW
ant/core/trunk/contributors.xml
ant/core/trunk/docs/manual/CoreTasks/javac.html
ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/Javac.java
ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/compilers/Gcj.java

Modified: ant/core/trunk/CONTRIBUTORS
URL: 
http://svn.apache.org/viewvc/ant/core/trunk/CONTRIBUTORS?rev=738761r1=738760r2=738761view=diff
==
Binary files - no diff available.

Modified: ant/core/trunk/WHATSNEW
URL: 
http://svn.apache.org/viewvc/ant/core/trunk/WHATSNEW?rev=738761r1=738760r2=738761view=diff
==
--- ant/core/trunk/WHATSNEW (original)
+++ ant/core/trunk/WHATSNEW Thu Jan 29 05:23:52 2009
@@ -655,6 +655,10 @@
these were eliminated in the interest of behaving in the manner
of a path.
 
+ * javac's source and target attributes are no longer ignored when
+   using gcj.
+   Bugzilla Issue 46617.
+
 Changes from Ant 1.7.0 TO Ant 1.7.1
 =
 

Modified: ant/core/trunk/contributors.xml
URL: 
http://svn.apache.org/viewvc/ant/core/trunk/contributors.xml?rev=738761r1=738760r2=738761view=diff
==
--- ant/core/trunk/contributors.xml (original)
+++ ant/core/trunk/contributors.xml Thu Jan 29 05:23:52 2009
@@ -924,6 +924,10 @@
 lastGaspar/last
   /name
   name
+firstPaweł/first
+lastZuzelski/last
+  /name
+  name
 firstPeter/first
 middleB./middle
 lastWest/last

Modified: ant/core/trunk/docs/manual/CoreTasks/javac.html
URL: 
http://svn.apache.org/viewvc/ant/core/trunk/docs/manual/CoreTasks/javac.html?rev=738761r1=738760r2=738761view=diff
==
--- ant/core/trunk/docs/manual/CoreTasks/javac.html (original)
+++ ant/core/trunk/docs/manual/CoreTasks/javac.html Thu Jan 29 05:23:52 2009
@@ -358,9 +358,11 @@
 td valign=topValue of the code-source/code command-line
 switch; will be ignored by all implementations prior to
 codejavac1.4/code (or codemodern/code when Ant is not
-running in a 1.3 VM) and codejikes/code.br If you use this
-attribute together with codejikes/code, you must make sure
-that your version of jikes supports the code-source/code
+running in a 1.3 VM), codegcj/code and codejikes/code.br
+If you use this attribute together with codegcj/code
+or codejikes/code, you must make sure that your version
+supports the code-source/code (or code-fsource/code for
+gcj)
 switch.  By default, no code-source/code argument will be used
 at all.br
 bNote that the default value depends on the JVM that is running

Modified: ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/Javac.java
URL: 
http://svn.apache.org/viewvc/ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/Javac.java?rev=738761r1=738760r2=738761view=diff
==
--- ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/Javac.java (original)
+++ ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/Javac.java Thu Jan 29 
05:23:52 2009
@@ -186,13 +186,16 @@
 }
 
 /**
- * Value of the -source command-line switch; will be ignored
- * by all implementations except modern and jikes.
+ * Value of the -source command-line switch; will be ignored by
+ * all implementations except modern, jikes and gcj (gcj uses
+ * -fsource).
+ *
+ * pIf you use this attribute together with jikes or gcj, you
+ * must make sure that your version of jikes supports the -source
+ * switch./p
  *
- * If you use this attribute together with jikes, you must make
- * sure that your version of jikes supports the -source switch.
- * Legal values are 1.3, 1.4, 1.5, and 5 - by default, no
- * -source argument will be used at all.
+ * pLegal values are 1.3, 1.4, 1.5, and 5 - by default, no
+ * -source argument will be used at all./p
  *
  * @param v  Value to assign to source.
  */

Modified: 
ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/compilers/Gcj.java
URL: 
http://svn.apache.org/viewvc/ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/compilers/Gcj.java?rev=738761r1=738760r2=738761view=diff
==
--- ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/compilers/Gcj.java 
(original)
+++ ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/compilers/Gcj.java 
Thu Jan 29 05:23:52 2009
@@ -114,6 +114,16 @@
 

DO NOT REPLY [Bug 46617] support for source attribute for javac with build.compiler=gcj

2009-01-28 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=46617


Stefan Bodewig bode...@apache.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED




--- Comment #4 from Stefan Bodewig bode...@apache.org  2009-01-28 21:24:30 
PST ---
committed as svn revision 738761 ( 
https://svn.apache.org/viewcvs.cgi?view=revrev=738761 )

I've also added support for -ftarget while I was at it.


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug.


DO NOT REPLY [Bug 46622] New: Obsolete bookmark anchor

2009-01-28 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=46622

   Summary: Obsolete bookmark anchor
   Product: Ant
   Version: unspecified
  Platform: PC
   URL: http://ant.apache.org/manual/tasksoverview.html
OS/Version: other
Status: NEW
  Severity: normal
  Priority: P4
 Component: Documentation
AssignedTo: notifications@ant.apache.org
ReportedBy: suchko...@mellon.com


The last bookmark at the top of the page which refers to VisualAge Java tasks
appears to be obsolete and should be removed.


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.