Re: [logging] RC on ibiblio ?

2006-04-05 Thread Nicolas De Loof


I agree about NOT making non-final jars available on ibiblio (httpclient 
beeing an exception)
So could the next RC be uploaded to 
http://cvs.apache.org/maven-snapshot-repository/ ?


Please also consider using the new groupId recommandation for apache 
commons-X : org.apache.commons.X


Martin Cooper a écrit :

On 4/5/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
  

On 4/5/06, Martin Cooper <[EMAIL PROTECTED]> wrote:



Right. But is there any reason we couldn't create a Maven 2 parallel to
  

the


Maven 1 repo we have at http://cvs.apache.org/repository/? We could
  

deploy


RCs there.
  

It's already there:
   http://cvs.apache.org/maven-snapshot-repository




Oh, that's what that is. ;-) The name threw me.

--
Martin Cooper


You can use 'mvn deploy:deploy-file' to deploy the RC, and Maven will
  

generate a pom for it.  That should be fine since Logging has no
required dependencies.

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





  


This message contains information that may be privileged or confidential and is 
the property of the Capgemini Group. It is intended only for the person to whom 
it is addressed. If you are not the intended recipient,  you are not authorized 
to read, print, retain, copy, disseminate,  distribute, or use this message or 
any part thereof. If you receive this  message in error, please notify the 
sender immediately and delete all  copies of this message.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r391906 - in /jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/env: jexl/JexlEvaluator.java jsp/ELEvaluator.java

2006-04-05 Thread rahul
Author: rahul
Date: Wed Apr  5 22:36:30 2006
New Revision: 391906

URL: http://svn.apache.org/viewcvs?rev=391906&view=rev
Log:
Make null expressions trivially evaluate to null.

Modified:

jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/env/jexl/JexlEvaluator.java

jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/env/jsp/ELEvaluator.java

Modified: 
jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/env/jexl/JexlEvaluator.java
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/env/jexl/JexlEvaluator.java?rev=391906&r1=391905&r2=391906&view=diff
==
--- 
jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/env/jexl/JexlEvaluator.java
 (original)
+++ 
jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/env/jexl/JexlEvaluator.java
 Wed Apr  5 22:36:30 2006
@@ -62,6 +62,9 @@
  */
 public Object eval(final Context ctx, final String expr)
 throws SCXMLExpressionException {
+if (expr == null) {
+return null;
+}
 JexlContext jexlCtx = null;
 if (ctx instanceof JexlContext) {
 jexlCtx = (JexlContext) ctx;
@@ -86,6 +89,9 @@
  */
 public Boolean evalCond(final Context ctx, final String expr)
 throws SCXMLExpressionException {
+if (expr == null) {
+return null;
+}
 JexlContext jexlCtx = null;
 if (ctx instanceof JexlContext) {
 jexlCtx = (JexlContext) ctx;
@@ -110,6 +116,9 @@
  */
 public Node evalLocation(final Context ctx, final String expr)
 throws SCXMLExpressionException {
+if (expr == null) {
+return null;
+}
 JexlContext jexlCtx = null;
 if (ctx instanceof JexlContext) {
 jexlCtx = (JexlContext) ctx;

Modified: 
jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/env/jsp/ELEvaluator.java
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/env/jsp/ELEvaluator.java?rev=391906&r1=391905&r2=391906&view=diff
==
--- 
jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/env/jsp/ELEvaluator.java
 (original)
+++ 
jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/env/jsp/ELEvaluator.java
 Wed Apr  5 22:36:30 2006
@@ -72,6 +72,9 @@
  */
 public Object eval(final Context ctx, final String expr)
 throws SCXMLExpressionException {
+if (expr == null) {
+return null;
+}
 VariableResolver vr = null;
 if (ctx instanceof VariableResolver) {
 vr = (VariableResolver) ctx;
@@ -97,6 +100,9 @@
  */
 public Boolean evalCond(final Context ctx, final String expr)
 throws SCXMLExpressionException {
+if (expr == null) {
+return null;
+}
 VariableResolver vr = null;
 if (ctx instanceof VariableResolver) {
 vr = (VariableResolver) ctx;
@@ -122,6 +128,9 @@
  */
 public Node evalLocation(final Context ctx, final String expr)
 throws SCXMLExpressionException {
+if (expr == null) {
+return null;
+}
 VariableResolver vr = null;
 if (ctx instanceof VariableResolver) {
 vr = (VariableResolver) ctx;



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [compress] Interface is ready

2006-04-05 Thread Hariharasudhan R
I meant to mail to Chris and hit the reply button on your mail by mistake..

On 4/5/06, Sandy McArthur <[EMAIL PROTECTED]> wrote:
>
> On 4/5/06, Sandy McArthur <[EMAIL PROTECTED]> wrote:
> > On 4/5/06, Hariharasudhan R <[EMAIL PROTECTED]> wrote:
> > > Hi Sandy,
> > >
> > > Does this work with Solaris tar, since Solaris tar is different from
> GNU tar
> > > ?
> > > If not , is there a plan to do so ?
> > > Won't making TarEntry an interface with Solaris/GNU implementations be
> a
> > > good idea ?
> > > This is just an idea off the top of my head.. I've not delved too much
> into
> > > the code..
> >
> > No clue. I don't really have access Solaris. I personally have access
> > to Linux, Mac OS X, Win32 and at work I can access AIX but that is
> > becoming less and less available as we move to linux.
>
> I should add that Chris Grobmeier has the "ball" for compress as best
> as I can tell. My involvement is largely limited to responding to his
> request for feedback on the programming API.
>
> > > On 4/4/06, C. Grobmeier <[EMAIL PROTECTED]> wrote:
> > > >
> > > > -BEGIN PGP SIGNED MESSAGE-
> > > > Hash: SHA1
> > > >
> > > > Hello Sandy,
> > > >
> > > > thousand thanks for your comments and the time you have spent for
> this.
> > > > I will work through this all and prepare another draft soon.
> > > >
> > > > Thank you very much,
> > > > Chris
> > > >
> > > > > The following is a stream of things I don't think are right in the
> > > > > order I observe them while skimming the code. I've never used the
> > > > > compress code so excuse any suggestions that miss the point.
> > > > >
> > > > > * Archiver: too many overloaded methods. Especially with setters.
> > > > > Having setFoo(File) and setFoo(String) will breaks the JavaBean
> > > > > property conventions and could cause problems with scripting
> tools. If
> > > > > you're going to do something like this then use different names
> eg:
> > > > > setDestinationFile(File) and setDestinationFilename(String) and
> let
> > > > > the latter be a virtual property that really just creates a new
> File
> > > > > and calls setDestinationFile(File).
> > > > >
> > > > > * Archive: doesn't do much, only contains one static method:
> > > > > getInstnace(ArchiverType). Because it's static you cannot subclass
> it
> > > > > so there is no way to extend it's behavior for when someone else
> want
> > > > > to implement CabArchiver. The type-safe enum example I gave in the
> > > > > other email makes this class unnecessary.
> > > > >
> > > > > * ArchiveType/CompressorType: make them type safe enums. Actually
> I
> > > > > think it's a mistake to distinguish between Archive types and
> > > > > Compression types. Making them separate you have one library that
> does
> > > > > two things and I think you should treat them as one thing and do
> that
> > > > > one thing well or have two libs that each do one thing.
> > > > >
> > > > >
> > > > > * TarConstants: is package scoped and, with the exception of one
> line
> > > > > in TarOutputStream, is only used by TarEntry. It looks to me the
> logic
> > > > > in TarOutputStream that uses TarConstansts could be easily pushed
> into
> > > > > TarEnrty and then the constants in TarConstants should be moved to
> > > > > where they are used.
> > > > >
> > > > > * TarInputStream: skimming it I don't it. It looks like it's
> taking
> > > > > the InputStream concept and corrupting it with the notion of many
> > > > > separate streams for each file in one stream. This is confusing
> > > > > because it doesn't fit the expectations of an InputStream. IMO it
> > > > > should be it's something similar to an Iterator that takes a raw
> > > > > InputStream and provides a way to get at metadata sequentially
> from
> > > > > the raw InputStream. From the meta data you should be able to get
> an
> > > > > InputStream which is just for that file in the archive.
> > > > >
> > > > > * TarOutputStream: Same problem as TarInputStream but with an
> > > > > OutputStream. Because TarOutputStream subclasses OutputStream it
> makes
> > > > > write methods available. But using these methods are dangerous
> because
> > > > > if you write a different number of bytes than what was passed when
> > > > > putNextEntry(TarEntry) was called you corrupt the archive. A good
> API
> > > > > doesn't let the programmer make mistakes. I'd change this to be
> it's
> > > > > own object type that accepts TarEntrys with all the needed to add
> a
> > > > > file in one step that either succeeds or fails.
> > > > >
> > > > > * TarInputStream/TarOutputStream: I don't see why these classes
> should
> > > > > be public. Making them package private would make me care less
> what
> > > > > they are because they aren't part of the public API and can be
> changed
> > > > > at will.
> > > > >
> > > > >
> > > > > * ZipLong, ZipShort: these are both public, and I don't see why
> they
> > > > > need to be. They are only used inside the package with the
> exception
> > > > > of 3 places 

Re: [compress] Interface is ready

2006-04-05 Thread Hariharasudhan R
Hi Chris,

The only information that I was able to find that said anything useful about
the difference is found in this page.
http://java.sun.com/products/archive/j2se/1.2.2_017/install-docs.html

Snippet from this page (you'll find it at the bottom of the page) :

"Background: The original tar format supports a maximum path size of 99
characters. If you use Solaris tar, you will not see a problem, because
Solaris tar extends this format beyond 99 characters but in a Solaris-only
way. GNU tar has a different way of extending the format, so is incompatible
with the Solaris tar. WinZip and Cygnus GNU tar 1.11.8 do not support the
Solaris way. We recommended that you use Solaris tar to extract the archive,
or use the jar tool or WinZip to extract the zip version."

>> Note : WinRAR seems to work properly with Solaris tar archives, though..

I am trying to get docs on the tar implementation in Solaris. I will get
back once I get more information.
What's happening is that for files with long path size , they get extracted
as if they were present in the root directory.

I am very much interested in a version that works on Solaris. I dont know if
I'll have time to work right now on a Solaris tar implementation, but if
someone gets around to writing one I'll surely be able to help test it.
You could also try installing Solaris on x86 for testing, since it is free.

Thanks,
Hari.

On 4/6/06, C. Grobmeier <[EMAIL PROTECTED]> wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> > Does this work with Solaris tar, since Solaris tar is different from GNU
> tar
> > ?
> > If not , is there a plan to do so ?
> > Won't making TarEntry an interface with Solaris/GNU implementations be a
> > good idea ?
> > This is just an idea off the top of my head.. I've not delved too much
> into
> > the code..
>
> i have just used the old APIs which have been implemented bevor ages.
> In the old testcases [1] i see that there seem to be a difference
> between Posix Tar and GNU Tar. Is this what you meant? It seems there is
> work to do left. I am sorry that i am not to deep into tar yet. If you
> have documents for me to read just send me the urls.
>
> Thanks,
> Christian
>
>
> [1] org.apache.commons.compress.TarTestCase.java
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.2.1 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFENC85kv8rKBUE/T4RAvepAJ9UhbEJ/L1CfQnz42Z3zyMgBQXFOwCfXDxV
> BHUXlp3lDBNsE4bgTUFOfMU=
> =oVNZ
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


svn commit: r391888 - /jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java

2006-04-05 Thread dion
Author: dion
Date: Wed Apr  5 20:34:59 2006
New Revision: 391888

URL: http://svn.apache.org/viewcvs?rev=391888&view=rev
Log:
Ensure there are tests for the various supported numbers in a unary minus.

Modified:

jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java

Modified: 
jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java?rev=391888&r1=391887&r2=391888&view=diff
==
--- 
jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java
 (original)
+++ 
jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java
 Wed Apr  5 20:34:59 2006
@@ -16,6 +16,8 @@
 package org.apache.commons.jexl;
 
 import java.io.StringReader;
+import java.math.BigDecimal;
+import java.math.BigInteger;
 import java.util.ArrayList;
 import java.util.BitSet;
 import java.util.Calendar;
@@ -363,8 +365,25 @@
 throws Exception
{
JexlContext jc = JexlHelper.createContext();
-   assertExpression(jc, "-3", new Integer(-3));
+
+   jc.getVars().put("aByte", new Byte((byte)1));
+   jc.getVars().put("aShort", new Short((short)2));
+   jc.getVars().put("anInteger", new Integer(3));
+   jc.getVars().put("aLong", new Long(4));
+   jc.getVars().put("aFloat", new Float(5.5));
+   jc.getVars().put("aDouble", new Double(6.6));
+   jc.getVars().put("aBigInteger", new BigInteger("7"));
+   jc.getVars().put("aBigDecimal", new BigDecimal("8.8"));
+   assertExpression(jc, "-3", new Integer("-3"));
assertExpression(jc, "-3.0", new Float("-3.0"));
+   assertExpression(jc, "-aByte", new Byte((byte)-1));
+   assertExpression(jc, "-aShort", new Short((short)-2));
+   assertExpression(jc, "-anInteger", new Integer(-3));
+   assertExpression(jc, "-aLong", new Long(-4));
+   assertExpression(jc, "-aFloat", new Float(-5.5));
+   assertExpression(jc, "-aDouble", new Double(-6.6));
+   assertExpression(jc, "-aBigInteger", new BigInteger("-7"));
+   assertExpression(jc, "-aBigDecimal", new BigDecimal("-8.8"));
}
 
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r391864 - /jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/ScriptFactoryTest.java

2006-04-05 Thread dion
Author: dion
Date: Wed Apr  5 17:21:40 2006
New Revision: 391864

URL: http://svn.apache.org/viewcvs?rev=391864&view=rev
Log:
Add null behaviour checks

Modified:

jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/ScriptFactoryTest.java

Modified: 
jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/ScriptFactoryTest.java
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/ScriptFactoryTest.java?rev=391864&r1=391863&r2=391864&view=diff
==
--- 
jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/ScriptFactoryTest.java
 (original)
+++ 
jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/ScriptFactoryTest.java
 Wed Apr  5 17:21:40 2006
@@ -44,6 +44,29 @@
 }
 
 /**
+ * Ensure the factory can create a script from a String
+ * @throws Exception on a parse error
+ */
+public void testCreateFromSimpleString() throws Exception {
+String code = "(1 + 2) * 4";
+assertNotNull("No script created", ScriptFactory.createScript(code));
+}
+
+/**
+ * Ensure the factory throws an NPE on an null String
+ * @throws Exception on a parse error
+ */
+public void testCreateFromNullString() throws Exception {
+String code = null;
+try {
+assertNotNull("No script created", 
ScriptFactory.createScript(code));
+fail("Null script created");
+} catch (NullPointerException e) {
+// expected
+}
+}
+
+/**
  * Ensure the factory can create a script from a file.
  * @throws Exception on a parse error.
  */
@@ -53,6 +76,23 @@
 }
 
 /**
+ * Ensure the factory throws npe on a null file.
+ * @throws Exception on a parse error.
+ */
+public void testCreateFromNullFile() throws Exception {
+File testScript = null;
+try
+{
+assertNotNull("No script created", 
ScriptFactory.createScript(testScript));
+fail("Null script created");
+}
+catch (NullPointerException e)
+{
+// expected
+}
+}
+
+/**
  * Ensure the factory can create a script from a URL.
  * @throws Exception on a parse error.
  */
@@ -60,4 +100,19 @@
 URL testUrl = new File("src/test-scripts/test1.jexl").toURL();
 assertNotNull("No script created", 
ScriptFactory.createScript(testUrl));
 }
+
+/**
+ * Ensure the factory throws an NPE on an null URL
+ * @throws Exception on a parse error
+ */
+public void testCreateFromNullURL() throws Exception {
+URL code = null;
+try {
+assertNotNull("No script created", 
ScriptFactory.createScript(code));
+fail("Null script created");
+} catch (NullPointerException e) {
+// expected
+}
+}
+
 }



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r391862 - /jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java

2006-04-05 Thread dion
Author: dion
Date: Wed Apr  5 17:20:32 2006
New Revision: 391862

URL: http://svn.apache.org/viewcvs?rev=391862&view=rev
Log:
Better coverage for relational operators.
Add commented out test for property assignment.

Modified:

jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java

Modified: 
jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java?rev=391862&r1=391861&r2=391862&view=diff
==
--- 
jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java
 (original)
+++ 
jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java
 Wed Apr  5 17:20:32 2006
@@ -210,15 +210,36 @@
 assertExpression(jc, "a==true", Boolean.TRUE);
 assertExpression(jc, "a==false", Boolean.FALSE);
 assertExpression(jc, "true==false", Boolean.FALSE);
-assertExpression(jc, "num < 3", Boolean.FALSE);
+
+assertExpression(jc, "2 < 3", Boolean.TRUE);
+assertExpression(jc, "num < 5", Boolean.FALSE);
+assertExpression(jc, "num < num", Boolean.FALSE);
+assertExpression(jc, "num < null", Boolean.FALSE);
+assertExpression(jc, "num < 2.5", Boolean.FALSE);
+assertExpression(jc, "now2 < now", Boolean.FALSE); // test comparable
+//
+assertExpression(jc, "'6' <= '5'", Boolean.FALSE);
 assertExpression(jc, "num <= 5", Boolean.TRUE);
-assertExpression(jc, "num >= 5", Boolean.TRUE);
+assertExpression(jc, "num <= num", Boolean.TRUE);
+assertExpression(jc, "num <= null", Boolean.FALSE);
+assertExpression(jc, "num <= 2.5", Boolean.FALSE);
+assertExpression(jc, "now2 <= now", Boolean.FALSE); // test comparable
+
+//
 assertExpression(jc, "'6' >= '5'", Boolean.TRUE);
+assertExpression(jc, "num >= 5", Boolean.TRUE);
 assertExpression(jc, "num >= num", Boolean.TRUE);
 assertExpression(jc, "num >= null", Boolean.FALSE);
 assertExpression(jc, "num >= 2.5", Boolean.TRUE);
-assertExpression(jc, "num > 4", Boolean.TRUE);
 assertExpression(jc, "now2 >= now", Boolean.TRUE); // test comparable
+
+assertExpression(jc, "'6' > '5'", Boolean.TRUE);
+assertExpression(jc, "num > 4", Boolean.TRUE);
+assertExpression(jc, "num > num", Boolean.FALSE);
+assertExpression(jc, "num > null", Boolean.FALSE);
+assertExpression(jc, "num > 2.5", Boolean.TRUE);
+assertExpression(jc, "now2 > now", Boolean.TRUE); // test comparable
+
 assertExpression(jc, "\"foo\" + \"bar\" == \"foobar\"", Boolean.TRUE);
 
 }
@@ -895,6 +916,8 @@
 {
 JexlContext jc = JexlHelper.createContext();
 jc.getVars().put("aString", "Hello");
+Foo foo = new Foo();
+jc.getVars().put("foo", foo);
 Parser parser = new Parser(new StringReader(";"));
 parser.parse(new StringReader("aString = 'World';"));
 
@@ -902,6 +925,9 @@
 assertEquals("hello variable not changed", "world", 
jc.getVars().get("hello"));
 assertExpression(jc, "result = 1 + 1", new Long(2));
 assertEquals("result variable not changed", new Long(2), 
jc.getVars().get("result"));
+// todo: make sure properties can be assigned to, fall back to flat 
var if no property
+// assertExpression(jc, "foo.property1 = '99'", "99");
+// assertEquals("property not set", "99", foo.getProperty1());
 }
 
 public void testAntPropertiesWithMethods() throws Exception



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r391861 - /jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/Foo.java

2006-04-05 Thread dion
Author: dion
Date: Wed Apr  5 17:19:16 2006
New Revision: 391861

URL: http://svn.apache.org/viewcvs?rev=391861&view=rev
Log:
Add a simple bean property to Foo.

Modified:
jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/Foo.java

Modified: 
jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/Foo.java
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/Foo.java?rev=391861&r1=391860&r2=391861&view=diff
==
--- jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/Foo.java 
(original)
+++ jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/Foo.java 
Wed Apr  5 17:19:16 2006
@@ -28,6 +28,7 @@
 public class Foo {
 
 private boolean beenModified = false;
+private String property1 = "some value";
 
 public String bar()
 {
@@ -102,5 +103,13 @@
 public int getSize()
 {
 return 22;
+}
+
+public String getProperty1() {
+return property1;
+}
+
+public void setProperty1(String newValue) {
+property1 = newValue;
 }
 }



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [logging] RC on ibiblio ?

2006-04-05 Thread Henri Yandell
On 4/5/06, Martin Cooper <[EMAIL PROTECTED]> wrote:
> On 4/5/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> >
> > On 4/5/06, robert burrell donkin <[EMAIL PROTECTED]>
> > wrote:
> > > sadly policy dictates that we can't upload release candidates to ibiblio
> >
> > AFAIK is PMC decision what gets uploaded
>
>
> No, this is bigger than any individual PMC. Only official releases can be
> deployed outside of ASF infrastructure, meaning that RCs cannot be deployed
> to ibiblio or made available via mirrors.

+1.

>From this I infer:

* If it goes in the maven release repo, it should be available as a
zip/tar.gz too.
* The PMC has to consider it to be an official release.

I think that a beta can be an official release - that's the decision a
PMC would be having to decide upon - but you can't be doing partial
releases (to maven repo only). There are lots of betas and alphas on
the mirrors.

Hen

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [logging] RC on ibiblio ?

2006-04-05 Thread Martin Cooper
On 4/5/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
>
> On 4/5/06, Martin Cooper <[EMAIL PROTECTED]> wrote:
>
> > Right. But is there any reason we couldn't create a Maven 2 parallel to
> the
> > Maven 1 repo we have at http://cvs.apache.org/repository/? We could
> deploy
> > RCs there.
>
> It's already there:
>http://cvs.apache.org/maven-snapshot-repository


Oh, that's what that is. ;-) The name threw me.

--
Martin Cooper


You can use 'mvn deploy:deploy-file' to deploy the RC, and Maven will
> generate a pom for it.  That should be fine since Logging has no
> required dependencies.
>
> --
> Wendy
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


Re: [logging] RC on ibiblio ?

2006-04-05 Thread Martin Cooper
On 4/5/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
>
> On 4/5/06, robert burrell donkin <[EMAIL PROTECTED]>
> wrote:
> > sadly policy dictates that we can't upload release candidates to ibiblio
>
> AFAIK is PMC decision what gets uploaded


No, this is bigger than any individual PMC. Only official releases can be
deployed outside of ASF infrastructure, meaning that RCs cannot be deployed
to ibiblio or made available via mirrors.

--
Martin Cooper


-
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


Re: [logging] RC on ibiblio ?

2006-04-05 Thread Wendy Smoak
On 4/5/06, Martin Cooper <[EMAIL PROTECTED]> wrote:

> Right. But is there any reason we couldn't create a Maven 2 parallel to the
> Maven 1 repo we have at http://cvs.apache.org/repository/? We could deploy
> RCs there.

It's already there:
   http://cvs.apache.org/maven-snapshot-repository

You can use 'mvn deploy:deploy-file' to deploy the RC, and Maven will
generate a pom for it.  That should be fine since Logging has no
required dependencies.

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [logging] RC on ibiblio ?

2006-04-05 Thread Henri Yandell
On 4/5/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> On 4/5/06, robert burrell donkin <[EMAIL PROTECTED]> wrote:
> > sadly policy dictates that we can't upload release candidates to ibiblio
>
> AFAIK is PMC decision what gets uploaded

Yep. You can't upload snapshots to ibiblio - RC is a vague grey area
and I think it comes down to the lifetime expected of it. HttpClient
has had RC candidates out there for many months at a time (and thus on
ibiblio), with people dependent on them in production etc. Most other
Commons components just use 'RC' to mean a test-build for the real
thing; should never appear in a user product.

So - what does this RC mean? Is there a better name (so as not to
confuse with the general RC usage)?

Hen

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [logging] RC on ibiblio ?

2006-04-05 Thread Martin Cooper
On 4/5/06, robert burrell donkin <[EMAIL PROTECTED]>
wrote:
>
> On Wed, 2006-04-05 at 20:41 +1200, Simon Kitching wrote:
> > On Wed, 2006-04-05 at 10:05 +0200, Nicolas De Loof wrote:
> > > Hello,
> > >
> > > Can someone upload commons-logging RC on Maven2 ibiblio repository ?
> > > It would be very cool to also upload a POM and the sources jar...
> >
> > That would be a good idea.
>
> sadly policy dictates that we can't upload release candidates to ibiblio


Right. But is there any reason we couldn't create a Maven 2 parallel to the
Maven 1 repo we have at http://cvs.apache.org/repository/? We could deploy
RCs there.

--
Martin Cooper


> We should also provide a link on the downloads page or something
> > similar. Just today a work colleague was looking for a later version
> > than 1.0.4 in order to get log4j TRACE support. I told him there was an
> > RC out, but there was just no way for him to locate it...
>
> i've been at work off list and things look good. i think i'm just about
> ready to cut the final release candidate this weekend and try a release
> vote.
>
> > By the way, there is still an outstanding discussion about whether to
> > add JDK14Logger back into the commons-logging-api.jar file. It was there
> > in the previous release. It probably shouldn't be; it's not logical.
> > However it does no harm as far as I can see, and the point was made that
> > because the current RC doesn't include it, it isn't a drop-in
> > replacement.
>
> yep
>
> i agree that it's not logical but ATM it would be good to ship a fixed
> replacement. it's likely that tomcat 6 will ship a JCL library created
> by costin which is static bound to java.util.logging.
>
> > So I'm +1 on adding JDK14Logger back to the api jar, then cutting a new
> > RC and uploading to ibiblio + linking from useful places.
> >
> > Alternatively, we could just make the above change then hold a release
> > vote. I think we've given this RC enough time for feedback.
>
> i've got the feedback i wanted now (off list) so i think the time is
> right to cut another release candidate and hold a release vote next
> week. i'll probably give the vote two weeks this time.
>
> - robert
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


Re: [logging] RC on ibiblio ?

2006-04-05 Thread Carlos Sanchez
On 4/5/06, robert burrell donkin <[EMAIL PROTECTED]> wrote:
> sadly policy dictates that we can't upload release candidates to ibiblio

AFAIK is PMC decision what gets uploaded

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [logging] RC on ibiblio ?

2006-04-05 Thread robert burrell donkin
On Wed, 2006-04-05 at 20:41 +1200, Simon Kitching wrote:
> On Wed, 2006-04-05 at 10:05 +0200, Nicolas De Loof wrote:
> > Hello,
> > 
> > Can someone upload commons-logging RC on Maven2 ibiblio repository ?
> > It would be very cool to also upload a POM and the sources jar...
> 
> That would be a good idea. 

sadly policy dictates that we can't upload release candidates to ibiblio

> We should also provide a link on the downloads page or something
> similar. Just today a work colleague was looking for a later version
> than 1.0.4 in order to get log4j TRACE support. I told him there was an
> RC out, but there was just no way for him to locate it...

i've been at work off list and things look good. i think i'm just about
ready to cut the final release candidate this weekend and try a release
vote.

> By the way, there is still an outstanding discussion about whether to
> add JDK14Logger back into the commons-logging-api.jar file. It was there
> in the previous release. It probably shouldn't be; it's not logical.
> However it does no harm as far as I can see, and the point was made that
> because the current RC doesn't include it, it isn't a drop-in
> replacement. 

yep

i agree that it's not logical but ATM it would be good to ship a fixed
replacement. it's likely that tomcat 6 will ship a JCL library created
by costin which is static bound to java.util.logging.

> So I'm +1 on adding JDK14Logger back to the api jar, then cutting a new
> RC and uploading to ibiblio + linking from useful places. 
> 
> Alternatively, we could just make the above change then hold a release
> vote. I think we've given this RC enough time for feedback.

i've got the feedback i wanted now (off list) so i think the time is
right to cut another release candidate and hold a release vote next
week. i'll probably give the vote two weeks this time.

- robert


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [compress] Interface is ready

2006-04-05 Thread C. Grobmeier
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

> Does this work with Solaris tar, since Solaris tar is different from GNU tar
> ?
> If not , is there a plan to do so ?
> Won't making TarEntry an interface with Solaris/GNU implementations be a
> good idea ?
> This is just an idea off the top of my head.. I've not delved too much into
> the code..

i have just used the old APIs which have been implemented bevor ages.
In the old testcases [1] i see that there seem to be a difference
between Posix Tar and GNU Tar. Is this what you meant? It seems there is
work to do left. I am sorry that i am not to deep into tar yet. If you
have documents for me to read just send me the urls.

Thanks,
Christian


[1] org.apache.commons.compress.TarTestCase.java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFENC85kv8rKBUE/T4RAvepAJ9UhbEJ/L1CfQnz42Z3zyMgBQXFOwCfXDxV
BHUXlp3lDBNsE4bgTUFOfMU=
=oVNZ
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Commented: (JELLY-205) adds a new line to files that does not ends with one

2006-04-05 Thread Felipe Leme (JIRA)
[ 
http://issues.apache.org/jira/browse/JELLY-205?page=comments#action_12373426 ] 

Felipe Leme commented on JELLY-205:
---

Hi Paul,

Actually, I've committed the test cases and the fix itself (I'm not a Commons 
committer, but a Jakarta committer...); what I couldn't do was to mark the 
issue as closed (I don't have such permission on Jira).

-- Felipe


>  adds a new line to files that does not ends with one
> 
>
>  Key: JELLY-205
>  URL: http://issues.apache.org/jira/browse/JELLY-205
>  Project: jelly
> Type: Bug

>   Components: taglib.util
> Reporter: Felipe Leme
>  Attachments: JELLY-205.patch, JELLY-205.zip
>
> See attached test case (I will try to fix it and provide a full patch).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [jelly] website remake

2006-04-05 Thread Paul Libbrecht



Dion Gillard wrote:

good stuff!
Does this include the 'new' commons nav/styling changes?
Well... it caused me a few issues especially since the maven 1.1 reactor 
causes lng hogs (this is probably the leaks that Brett has been 
hunting for in Jelly)
Yes, it does include now (upload since about 20 minutes). The issue 
seems to be some way down how java.io.File objects are passed to the 
parser, or in the parser itself, in any case, deriving a file to a URL 
works, I patched the maven-xdoc-plugin-1.9.2/plugin.jelly by adding at 
line 471:
   value="x"/>
   test="${f.getClass().isAssignableFrom(navFile.getClass())}">

 
   
would love anyone else to test it...

thanks

paul

p.s. You could use your http://people.apache.org/ site to upload it btw.
Just don't need to bloat it for now, having this server at hand... so I 
thought that a temporary space as such is better
On 4/4/06, *Paul Libbrecht* <[EMAIL PROTECTED] 
> wrote:



Hello,

Since ages, the jelly-site is output wrong where, in particular, the
project info, project reports, and downloads are missing from the
navigation.
Can folks please check
 http://klein.activemath.org/~paul/JellyDoc/

before I can upload it ?

thanks

paul

PS: this was built with empty target dirs using maven-site...

-
To unsubscribe, e-mail: [EMAIL PROTECTED]

For additional commands, e-mail:
[EMAIL PROTECTED]





--
http://www.multitask.com.au/people/dion/
Chuck Norris sleeps with a night light. Not because Chuck Norris is 
afraid of the dark, but because the dark is afraid of Chuck Norris 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 39109] - [net] MVSFTPEntryParser.java only halfway implemented

2006-04-05 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39109





--- Additional Comments From [EMAIL PROTECTED]  2006-04-05 19:36 ---
this is my current comments in my working version of MVSFTPEntryParser.java. 
 
try to read it and let know if it is understandable. 
 
/* 
 * Very brief and imcomplete description of the zOS/MVS-filesystem.  
 * (Note: "zOS" is the operating system on the mainframe,  
 *and is the new name for MVS) 
 *  
 * The filesystem on the mainframe does not have hierarchal structure as  
 * for example the unix filesystem. 
 * For a more comprehensive description, please refer to the IBM manuals 
 * @LINK:www.ibm 
 *  
 * Dataset names 
 * = 
 *  
 * A dataset name consist of a number of qualifiers separated by '.', 
 * each qualifier can be at most 8 characters, and the total length 
 * of a dataset can be max 44 characters including the dots. 
 *  
 *  
 * Dataset organisation 
 *  
 *  
 * A dataset represents a piece of storage allocated on one or more disks.  
 * The structure of the storage is described with the field dataset  
organinsation (DSORG). 
 * There are a number of dataset organisations, but only two are usable for FTP 
transfer. 
 *  
 * DSORG: 
 * PS: sequential, or flat file 
 * PO: partitioned dataset 
 * PO-E: extended partitioned dataset 
 *  
 * The PS file is just a flat file, as you would find it on the unix 
 * file system. 
 *  
 * The PO and PO-E files, can be compared to a single level directory  
structure. 
 * A PO file consist of a number of dataset members, or files if you 
 * will. It is possible to CD into the file, and to retrieve the  
 * individual members. 
 *  
 *  
 * Dataset record format 
 * = 
 *  
 * The physical layout of the dataset is described on the dataset itself. 
 * There are a number of record formats (RECFM), but just a few is relavant for 
 
 * the FTP transfer. 
 *  
 * Any one beginning with either F or V can safely used by FTP transfer. 
 * All others should only be used with great care. 
 * F means a fixed number of records per allocated storage, and V means a 
variable  
 * number of records. 
 *  
 *  
 * Other notes 
 * === 
 * 
 * The file system supports automatically backup and retrieval of datasets. If 
a 
 * file is backed up, the ftp LIST command will return: 
 * ARCIVE Not Direct Access DeviceKJ.IOP998.ERROR.PL.UNITTEST 
 * 
 * 
 * Implementation notes 
 *  
 * 
 * Only datasets that have dsorg PS, PO or PO-E and have recfm  
 * beginning with F or V, is fully parsed. 
 *  
 * The following fields in FTPFile is used: 
 * FTPFile.Rawlisting: Always set. 
 * FTPFile.Type: DIRECTORY_TYPE or FILE_TYPE or UNKNOWN or null 
 * FTPFile.Name: name or null 
 * FTPFile.Timestamp: create time or null 
 *  
 */ 
 
 
 
/* Format of ZOS/MVS file list: 
 * 01 2  345  6 78 9  
 * Volume UnitReferred Ext Used Recfm Lrecl BlkSz Dsorg Dsname 
 * B10142 3390   2006/03/20  2   31  F   8080  PS  MDI.OKL.WORK 
 * ARCIVE Not Direct Access Device KJ.IOP998.ERROR.PL.UNITTEST 
 * B1N231 3390   2006/03/20  1   15  VB 256 27998  PO   PLU 
 * B1N231 3390   2006/03/20  1   15  VB 256 27998  PO-E PLB 
 *  
 */ 
 /* --- 
  * [0] Volume 
  * [1] Unit 
  * [2] Referred 
  * [3] Ext: number of extents 
  * [4] Used 
  * [5] Recfm: Record format 
  * [6] Lrecl: Logical record length 
  * [7] BlkSz: Block size 
  * [8] Dsorg: Dataset organisation. Many exists but only support: PS, PO, PO-E 
  * [9] Dsname: Dataset name 
  *  
  * Note: When volume is ARCIVE, it means the dataset is stored somewhere in 
  *   a tape archive. These entries is currently not supported by this 
  *   parser. A null value is returned. 
  *
  *  
  */ 
// dsorg last two tokens describe file: 
// 'PS': sequential file 
// 'PO': partioned dataset PDS 
// 'PO-E': PDS Library 
// '  ': unknown, probably archived. 

/* 
 * Format of a PDS: 
 *0 12  34 5 6  78 
 *   Name  VV.MM   Created   Changed  Size  Init   Mod   Id 
 *   TBSHELF   01.03 2002/09/12 2002/10/11 09:371111 0 KIL001 
 *   TBTOOL01.12 2002/09/12 2004/11/26 19:545128 0 KIL001 
 *  
 */ 
/* 
 * [0] Name 
 * [1] VV.MM: Version . modification 
 * [2] Created:  / MM / dd 
 * [3,4] Changed:  / MM / dd  HH:mm 
 * [5] Size: number of lines 
 * [6] Init: number of lines when first created 
 * [7] Mod: number of modified lines a last save 
 * [8] Id: User id for last update 
 *  
 */ 
 

-- 
Configure bugmail: http://issues.apac

svn commit: r391681 - /jakarta/commons/proper/fileupload/trunk/src/test/org/apache/commons/fileupload/ServletFileUploadTest.java

2006-04-05 Thread bayard
Author: bayard
Date: Wed Apr  5 10:20:26 2006
New Revision: 391681

URL: http://svn.apache.org/viewcvs?rev=391681&view=rev
Log:
Adding unit test for #38940 - filename being treated insensitive of case

Modified:

jakarta/commons/proper/fileupload/trunk/src/test/org/apache/commons/fileupload/ServletFileUploadTest.java

Modified: 
jakarta/commons/proper/fileupload/trunk/src/test/org/apache/commons/fileupload/ServletFileUploadTest.java
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/fileupload/trunk/src/test/org/apache/commons/fileupload/ServletFileUploadTest.java?rev=391681&r1=391680&r2=391681&view=diff
==
--- 
jakarta/commons/proper/fileupload/trunk/src/test/org/apache/commons/fileupload/ServletFileUploadTest.java
 (original)
+++ 
jakarta/commons/proper/fileupload/trunk/src/test/org/apache/commons/fileupload/ServletFileUploadTest.java
 Wed Apr  5 10:20:26 2006
@@ -122,6 +122,23 @@
 assertEquals("value2", multi1.getString());
 }
 
+public void testFilenameCaseSensitivity() 
+throws IOException, FileUploadException
+{
+List fileItems = parseUpload("-1234\r\n" +
+"Content-Disposition: form-data; name=\"FiLe\"; 
filename=\"FOO.tab\"\r\n" +
+"Content-Type: text/whatever\r\n" +
+"\r\n" +
+"This is the content of the file\n" +
+"\r\n" +
+"-1234--\r\n");
+assertEquals(1, fileItems.size());
+
+FileItem file = (FileItem) fileItems.get(0);
+assertEquals("FiLe", file.getFieldName());
+assertEquals("FOO.tab", file.getName());
+}
+
 /**
  * This is what the browser does if you submit the form without choosing a 
file.
  */



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [compress] Interface is ready

2006-04-05 Thread Sandy McArthur
On 4/5/06, Sandy McArthur <[EMAIL PROTECTED]> wrote:
> On 4/5/06, Hariharasudhan R <[EMAIL PROTECTED]> wrote:
> > Hi Sandy,
> >
> > Does this work with Solaris tar, since Solaris tar is different from GNU tar
> > ?
> > If not , is there a plan to do so ?
> > Won't making TarEntry an interface with Solaris/GNU implementations be a
> > good idea ?
> > This is just an idea off the top of my head.. I've not delved too much into
> > the code..
>
> No clue. I don't really have access Solaris. I personally have access
> to Linux, Mac OS X, Win32 and at work I can access AIX but that is
> becoming less and less available as we move to linux.

I should add that Chris Grobmeier has the "ball" for compress as best
as I can tell. My involvement is largely limited to responding to his
request for feedback on the programming API.

> > On 4/4/06, C. Grobmeier <[EMAIL PROTECTED]> wrote:
> > >
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA1
> > >
> > > Hello Sandy,
> > >
> > > thousand thanks for your comments and the time you have spent for this.
> > > I will work through this all and prepare another draft soon.
> > >
> > > Thank you very much,
> > > Chris
> > >
> > > > The following is a stream of things I don't think are right in the
> > > > order I observe them while skimming the code. I've never used the
> > > > compress code so excuse any suggestions that miss the point.
> > > >
> > > > * Archiver: too many overloaded methods. Especially with setters.
> > > > Having setFoo(File) and setFoo(String) will breaks the JavaBean
> > > > property conventions and could cause problems with scripting tools. If
> > > > you're going to do something like this then use different names eg:
> > > > setDestinationFile(File) and setDestinationFilename(String) and let
> > > > the latter be a virtual property that really just creates a new File
> > > > and calls setDestinationFile(File).
> > > >
> > > > * Archive: doesn't do much, only contains one static method:
> > > > getInstnace(ArchiverType). Because it's static you cannot subclass it
> > > > so there is no way to extend it's behavior for when someone else want
> > > > to implement CabArchiver. The type-safe enum example I gave in the
> > > > other email makes this class unnecessary.
> > > >
> > > > * ArchiveType/CompressorType: make them type safe enums. Actually I
> > > > think it's a mistake to distinguish between Archive types and
> > > > Compression types. Making them separate you have one library that does
> > > > two things and I think you should treat them as one thing and do that
> > > > one thing well or have two libs that each do one thing.
> > > >
> > > >
> > > > * TarConstants: is package scoped and, with the exception of one line
> > > > in TarOutputStream, is only used by TarEntry. It looks to me the logic
> > > > in TarOutputStream that uses TarConstansts could be easily pushed into
> > > > TarEnrty and then the constants in TarConstants should be moved to
> > > > where they are used.
> > > >
> > > > * TarInputStream: skimming it I don't it. It looks like it's taking
> > > > the InputStream concept and corrupting it with the notion of many
> > > > separate streams for each file in one stream. This is confusing
> > > > because it doesn't fit the expectations of an InputStream. IMO it
> > > > should be it's something similar to an Iterator that takes a raw
> > > > InputStream and provides a way to get at metadata sequentially from
> > > > the raw InputStream. From the meta data you should be able to get an
> > > > InputStream which is just for that file in the archive.
> > > >
> > > > * TarOutputStream: Same problem as TarInputStream but with an
> > > > OutputStream. Because TarOutputStream subclasses OutputStream it makes
> > > > write methods available. But using these methods are dangerous because
> > > > if you write a different number of bytes than what was passed when
> > > > putNextEntry(TarEntry) was called you corrupt the archive. A good API
> > > > doesn't let the programmer make mistakes. I'd change this to be it's
> > > > own object type that accepts TarEntrys with all the needed to add a
> > > > file in one step that either succeeds or fails.
> > > >
> > > > * TarInputStream/TarOutputStream: I don't see why these classes should
> > > > be public. Making them package private would make me care less what
> > > > they are because they aren't part of the public API and can be changed
> > > > at will.
> > > >
> > > >
> > > > * ZipLong, ZipShort: these are both public, and I don't see why they
> > > > need to be. They are only used inside the package with the exception
> > > > of 3 places ZipShort is used as a parameter type in a public method. I
> > > > don't see why those ZipShorts cannot be converted to shorts for the
> > > > public API and both of them made package private.
> > > >
> > > > * ZipOutputStream: has the same problems as TarOutputStream.
> > > >
> > > > * compress.archivers.zip: every class in this package is public, I
> > > > don't thi

Re: [compress] Interface is ready

2006-04-05 Thread Sandy McArthur
On 4/5/06, Hariharasudhan R <[EMAIL PROTECTED]> wrote:
> Hi Sandy,
>
> Does this work with Solaris tar, since Solaris tar is different from GNU tar
> ?
> If not , is there a plan to do so ?
> Won't making TarEntry an interface with Solaris/GNU implementations be a
> good idea ?
> This is just an idea off the top of my head.. I've not delved too much into
> the code..

No clue. I don't really have access Solaris. I personally have access
to Linux, Mac OS X, Win32 and at work I can access AIX but that is
becoming less and less available as we move to linux.

> On 4/4/06, C. Grobmeier <[EMAIL PROTECTED]> wrote:
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Hello Sandy,
> >
> > thousand thanks for your comments and the time you have spent for this.
> > I will work through this all and prepare another draft soon.
> >
> > Thank you very much,
> > Chris
> >
> > > The following is a stream of things I don't think are right in the
> > > order I observe them while skimming the code. I've never used the
> > > compress code so excuse any suggestions that miss the point.
> > >
> > > * Archiver: too many overloaded methods. Especially with setters.
> > > Having setFoo(File) and setFoo(String) will breaks the JavaBean
> > > property conventions and could cause problems with scripting tools. If
> > > you're going to do something like this then use different names eg:
> > > setDestinationFile(File) and setDestinationFilename(String) and let
> > > the latter be a virtual property that really just creates a new File
> > > and calls setDestinationFile(File).
> > >
> > > * Archive: doesn't do much, only contains one static method:
> > > getInstnace(ArchiverType). Because it's static you cannot subclass it
> > > so there is no way to extend it's behavior for when someone else want
> > > to implement CabArchiver. The type-safe enum example I gave in the
> > > other email makes this class unnecessary.
> > >
> > > * ArchiveType/CompressorType: make them type safe enums. Actually I
> > > think it's a mistake to distinguish between Archive types and
> > > Compression types. Making them separate you have one library that does
> > > two things and I think you should treat them as one thing and do that
> > > one thing well or have two libs that each do one thing.
> > >
> > >
> > > * TarConstants: is package scoped and, with the exception of one line
> > > in TarOutputStream, is only used by TarEntry. It looks to me the logic
> > > in TarOutputStream that uses TarConstansts could be easily pushed into
> > > TarEnrty and then the constants in TarConstants should be moved to
> > > where they are used.
> > >
> > > * TarInputStream: skimming it I don't it. It looks like it's taking
> > > the InputStream concept and corrupting it with the notion of many
> > > separate streams for each file in one stream. This is confusing
> > > because it doesn't fit the expectations of an InputStream. IMO it
> > > should be it's something similar to an Iterator that takes a raw
> > > InputStream and provides a way to get at metadata sequentially from
> > > the raw InputStream. From the meta data you should be able to get an
> > > InputStream which is just for that file in the archive.
> > >
> > > * TarOutputStream: Same problem as TarInputStream but with an
> > > OutputStream. Because TarOutputStream subclasses OutputStream it makes
> > > write methods available. But using these methods are dangerous because
> > > if you write a different number of bytes than what was passed when
> > > putNextEntry(TarEntry) was called you corrupt the archive. A good API
> > > doesn't let the programmer make mistakes. I'd change this to be it's
> > > own object type that accepts TarEntrys with all the needed to add a
> > > file in one step that either succeeds or fails.
> > >
> > > * TarInputStream/TarOutputStream: I don't see why these classes should
> > > be public. Making them package private would make me care less what
> > > they are because they aren't part of the public API and can be changed
> > > at will.
> > >
> > >
> > > * ZipLong, ZipShort: these are both public, and I don't see why they
> > > need to be. They are only used inside the package with the exception
> > > of 3 places ZipShort is used as a parameter type in a public method. I
> > > don't see why those ZipShorts cannot be converted to shorts for the
> > > public API and both of them made package private.
> > >
> > > * ZipOutputStream: has the same problems as TarOutputStream.
> > >
> > > * compress.archivers.zip: every class in this package is public, I
> > > don't think they all need to be.
> > >
> > >
> > > * compress.compressors.bzip2: This package seems fine. I don't get why
> > > CBZip2InputStream and CBZip2OutputStream start with the letter "C"
> > > though.
> > >
> > >
> > > * compress.exceptions: I don't get why the exceptions are segregated
> > > to their own package. Javadoc already keeps them separated so there
> > > isn't a need to put them in their own package. I'd put 

DO NOT REPLY [Bug 39217] New: - FTPClient throws exception when passive mode reply lacks parentheses

2006-04-05 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39217

   Summary: FTPClient throws exception when passive mode reply lacks
parentheses
   Product: Commons
   Version: unspecified
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: normal
  Priority: P2
 Component: Net
AssignedTo: commons-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]


Commons net version 1.4.1 (this doesn't appear in the Bugzilla dropdown)

When my application does a storeFile to an admittedly obscure FTP server
(ActiveState ftpd.tcl), it gets this exception from FTPClient:

 [java] java.lang.StringIndexOutOfBoundsException: String index out of 
range: -1
 [java] at java.lang.String.substring(String.java:1444)
 [java] at
org.apache.commons.net.ftp.FTPClient.__parsePassiveModeReply(FTPClient.java:341)
 [java] at
org.apache.commons.net.ftp.FTPClient._openDataConnection_(FTPClient.java:511)
 [java] at
org.apache.commons.net.ftp.FTPClient.__storeFile(FTPClient.java:388)
 [java] at
org.apache.commons.net.ftp.FTPClient.storeFile(FTPClient.java:1388)


Looking at that code in __parsePassiveModeReply it appears to require the reply
to be enclosed parentheses, which it should not, according to RFC 1123: 

 IMPLEMENTATION:
 The format of the 227 reply to a PASV command is not
 well standardized.  In particular, an FTP client cannot
 assume that the parentheses shown on page 40 of RFC-959
 will be present (and in fact, Figure 3 on page 43 omits
 them).  Therefore, a User-FTP program that interprets
 the PASV reply must scan the reply for the first digit
 of the host and port numbers.

 
My application and FTPClient work fine when connecting to a Fedora ftp server.
  Using Fedora command line ftp to do the ftp PUT to the ActiveState tcl ftp
server also works fine.

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

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [compress] Interface is ready

2006-04-05 Thread Hariharasudhan R
Hi Sandy,

Does this work with Solaris tar, since Solaris tar is different from GNU tar
?
If not , is there a plan to do so ?
Won't making TarEntry an interface with Solaris/GNU implementations be a
good idea ?
This is just an idea off the top of my head.. I've not delved too much into
the code..

Thanks,
Hari.

On 4/4/06, C. Grobmeier <[EMAIL PROTECTED]> wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello Sandy,
>
> thousand thanks for your comments and the time you have spent for this.
> I will work through this all and prepare another draft soon.
>
> Thank you very much,
> Chris
>
> > The following is a stream of things I don't think are right in the
> > order I observe them while skimming the code. I've never used the
> > compress code so excuse any suggestions that miss the point.
> >
> > * Archiver: too many overloaded methods. Especially with setters.
> > Having setFoo(File) and setFoo(String) will breaks the JavaBean
> > property conventions and could cause problems with scripting tools. If
> > you're going to do something like this then use different names eg:
> > setDestinationFile(File) and setDestinationFilename(String) and let
> > the latter be a virtual property that really just creates a new File
> > and calls setDestinationFile(File).
> >
> > * Archive: doesn't do much, only contains one static method:
> > getInstnace(ArchiverType). Because it's static you cannot subclass it
> > so there is no way to extend it's behavior for when someone else want
> > to implement CabArchiver. The type-safe enum example I gave in the
> > other email makes this class unnecessary.
> >
> > * ArchiveType/CompressorType: make them type safe enums. Actually I
> > think it's a mistake to distinguish between Archive types and
> > Compression types. Making them separate you have one library that does
> > two things and I think you should treat them as one thing and do that
> > one thing well or have two libs that each do one thing.
> >
> >
> > * TarConstants: is package scoped and, with the exception of one line
> > in TarOutputStream, is only used by TarEntry. It looks to me the logic
> > in TarOutputStream that uses TarConstansts could be easily pushed into
> > TarEnrty and then the constants in TarConstants should be moved to
> > where they are used.
> >
> > * TarInputStream: skimming it I don't it. It looks like it's taking
> > the InputStream concept and corrupting it with the notion of many
> > separate streams for each file in one stream. This is confusing
> > because it doesn't fit the expectations of an InputStream. IMO it
> > should be it's something similar to an Iterator that takes a raw
> > InputStream and provides a way to get at metadata sequentially from
> > the raw InputStream. From the meta data you should be able to get an
> > InputStream which is just for that file in the archive.
> >
> > * TarOutputStream: Same problem as TarInputStream but with an
> > OutputStream. Because TarOutputStream subclasses OutputStream it makes
> > write methods available. But using these methods are dangerous because
> > if you write a different number of bytes than what was passed when
> > putNextEntry(TarEntry) was called you corrupt the archive. A good API
> > doesn't let the programmer make mistakes. I'd change this to be it's
> > own object type that accepts TarEntrys with all the needed to add a
> > file in one step that either succeeds or fails.
> >
> > * TarInputStream/TarOutputStream: I don't see why these classes should
> > be public. Making them package private would make me care less what
> > they are because they aren't part of the public API and can be changed
> > at will.
> >
> >
> > * ZipLong, ZipShort: these are both public, and I don't see why they
> > need to be. They are only used inside the package with the exception
> > of 3 places ZipShort is used as a parameter type in a public method. I
> > don't see why those ZipShorts cannot be converted to shorts for the
> > public API and both of them made package private.
> >
> > * ZipOutputStream: has the same problems as TarOutputStream.
> >
> > * compress.archivers.zip: every class in this package is public, I
> > don't think they all need to be.
> >
> >
> > * compress.compressors.bzip2: This package seems fine. I don't get why
> > CBZip2InputStream and CBZip2OutputStream start with the letter "C"
> > though.
> >
> >
> > * compress.exceptions: I don't get why the exceptions are segregated
> > to their own package. Javadoc already keeps them separated so there
> > isn't a need to put them in their own package. I'd put them in the
> > compress package or a package closer to where they are used.
> >
> > --
> > Sandy McArthur
> >
> > "He who dares not offend cannot be honest."
> > - Thomas Paine
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.2.1 (Min

Configuration Cache

2006-04-05 Thread Marcus Malcom
Commons Project: Configuration

I was thinking about creating a "Configuration Cache". Essentially this
would would be very specific to a PropertiesConfiguration at the start
and would move to be more generic as needed. The cache would be a
centralized location to obtain instances of PropertiesConfiguration -
standardizing a singleton/multiton approach.

My first question is: Does anyone know if there's something out there
already that does this? (did I just miss something)

Second: If there isn't anything out there, would the commons group be
interested in a code submit on this?

Thanks!

-- 
Marcus Malcom
OCHIN
Software Engineer
[EMAIL PROTECTED]


signature.asc
Description: This is a digitally signed message part


Re: [logging] redux: include jdk logger in API jar?

2006-04-05 Thread Dennis Lundberg

robert burrell donkin wrote:

remy ran a regression test for RC6 (thanks :)

we no long ship the jdk logger in API jar. however, tomcat uses jdk
logger as it's default. so, by excluding the jdk logger, JCL 1.1 is no
longer a drop in replacement at least for tomcat.

so, i thought it'd be a good time to reconsider the decision to exclude
the jdk logger.

opinions?

- robert 


I think we should allow for a smooth upgrade path, especially for Tomcat 
users. If that means putting back the jdk logger, then let's do that.


--
Dennis Lundberg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Commented: (JELLY-173) Support for XML Schema

2006-04-05 Thread Paul Libbrecht (JIRA)
[ 
http://issues.apache.org/jira/browse/JELLY-173?page=comments#action_12373368 ] 

Paul Libbrecht commented on JELLY-173:
--

Felipe, Jelly is not dead but several committers are a bit... busy or tired...
I am currently giving a few cycles to polish things out (web-site is broken, 
gump-tests fail,...) and would like to go further but this is all pretty 
limited I fear.
Most other committers are such, I fear.

Wishing more involvement ?? Come over... patches will be welcome!
Checking this issue for resolvedness would be nice for example...
Going through other bug-lists to mark doable things for both a 1.1-b1 would 
also be nice.

> Support for XML Schema
> --
>
>  Key: JELLY-173
>  URL: http://issues.apache.org/jira/browse/JELLY-173
>  Project: jelly
> Type: New Feature

>   Components: taglib.xml
> Reporter: Felipe Leme

>
> There is a bug on the maven-ear-plugin regarding support to genera
> In order to fix a maven-ear-plugin bug 
> (http://jira.codehaus.org/browse/MPEAR-30), I need to generate a XML-Schema 
> based XML document, but looks like the taglib doesn't allow it.
> I can see 2 possible solutions:
> 1.Add more attributes to the  tag. Example:
> http://java.sun.com/xml/ns/j2ee";
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>  xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee 
> http://java.sun.com/xml/ns/j2ee/application_1_4.xsd";
>  version="1.4">
> 2.Create a new tag specifically for this purpose. Example:
> http://java.sun.com/xml/ns/j2ee";
>  xsi="http://www.w3.org/2001/XMLSchema-instance";
>  schemaLocation="http://java.sun.com/xml/ns/j2ee 
> http://java.sun.com/xml/ns/j2ee/application_1_4.xsd";
>  version="1.4">
> If there is another alternative, please let me know.
> -- Felipe

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Closed: (JELLY-205) adds a new line to files that does not ends with one

2006-04-05 Thread Paul Libbrecht (JIRA)
 [ http://issues.apache.org/jira/browse/JELLY-205?page=all ]
 
Paul Libbrecht closed JELLY-205:


Resolution: Fixed

Sorry, dumb of me... sure... clearly fixed... I don't think a unit-test is 
necessary.
paul

>  adds a new line to files that does not ends with one
> 
>
>  Key: JELLY-205
>  URL: http://issues.apache.org/jira/browse/JELLY-205
>  Project: jelly
> Type: Bug

>   Components: taglib.util
> Reporter: Felipe Leme
>  Attachments: JELLY-205.patch, JELLY-205.zip
>
> See attached test case (I will try to fix it and provide a full patch).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Commented: (JELLY-205) adds a new line to files that does not ends with one

2006-04-05 Thread Paul Libbrecht (JIRA)
[ 
http://issues.apache.org/jira/browse/JELLY-205?page=comments#action_12373358 ] 

Paul Libbrecht commented on JELLY-205:
--

Do I understand that you consider it fixed but have not unit-test for it ?
paul

>  adds a new line to files that does not ends with one
> 
>
>  Key: JELLY-205
>  URL: http://issues.apache.org/jira/browse/JELLY-205
>  Project: jelly
> Type: Bug

>   Components: taglib.util
> Reporter: Felipe Leme
>  Attachments: JELLY-205.patch, JELLY-205.zip
>
> See attached test case (I will try to fix it and provide a full patch).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Closed: (JELLY-203) [Util] [PATCH] Test cases for jelly-tags-util has wrong package

2006-04-05 Thread Paul Libbrecht (JIRA)
 [ http://issues.apache.org/jira/browse/JELLY-203?page=all ]
 
Paul Libbrecht closed JELLY-203:


Resolution: Fixed

Tastes fixed.
paul

> [Util] [PATCH] Test cases for jelly-tags-util has wrong package
> ---
>
>  Key: JELLY-203
>  URL: http://issues.apache.org/jira/browse/JELLY-203
>  Project: jelly
> Type: Bug

>   Components: taglib.util
> Reporter: Felipe Leme
> Priority: Minor
>  Attachments: JELLY-203
>
> Some of the test cases uses the class org.apache.commons.jelly.util.Customer, 
> but that class is located at org/apache/commons/jelly/tags/util. I'm 
> attaching a patch that fixes this issue.
> .

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[EMAIL PROTECTED]: Project commons-jelly-tags-define-test (in module commons-jelly) failed

2006-04-05 Thread commons-jelly-tags-define development
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 commons-jelly-tags-define-test has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 70 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-define-test :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-define-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -WARNING- Overriding Maven properties: 
[/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/build.properties]
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-define-test/gump_work/build_commons-jelly_commons-jelly-tags-define-test.html
Work Name: build_commons-jelly_commons-jelly-tags-define-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 13 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/dynabean/target/commons-jelly-tags-dynabean-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-05042006.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-4/jaxen-1.1-beta-4.jar
-
[junit] at junit.framework.TestResult.runProtected(TestResult.java:124)
[junit] at junit.framework.TestResult.run(TestResult.java:109)
[junit] at junit.framework.TestCase.run(TestCase.java:118)
[junit] at junit.framework.TestSuite.runTest(TestSuite.java:208)
[junit] at junit.framework.TestSuite.run(TestSuite.java:203)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:325)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:536)
[junit] Apr 5, 2006 5:25:15 AM 
org.apache.commons.jelly.expression.xpath.XPathExpression evaluate
[junit] SEVERE: Error constructing xpath
[junit] org.jaxen.XPathSyntaxException: Node-set expected
[junit] at org.jaxen.BaseXPath.(BaseXPath.java:131)
[junit] at org.jaxen.BaseXPath.(BaseXPath.java:156)
[junit] at org.jaxen.dom4j.Dom4jXPath.(Dom4jXPath.java:101)
[junit] at 
org.apache.commons.jelly.expression.xpath.XPathExpression.evaluate(XPathExpression.java:78)
[junit] at 
org.apache.commons.jelly.expression.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:256)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
[junit] at 
org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59)
[junit] at junit.framework.TestCase.runBare(TestCase.java:127)
[junit] at junit.framework.TestResult$1.protect(TestResult.java:106)
[junit] at junit.framework.TestResult.runProtected(TestResult.java:124)
[junit] at junit.framework.

[EMAIL PROTECTED]: Project commons-jelly-tags-define-test (in module commons-jelly) failed

2006-04-05 Thread commons-jelly-tags-define development
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 commons-jelly-tags-define-test has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 70 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-define-test :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-define-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -WARNING- Overriding Maven properties: 
[/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/build.properties]
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-define-test/gump_work/build_commons-jelly_commons-jelly-tags-define-test.html
Work Name: build_commons-jelly_commons-jelly-tags-define-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 13 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/dynabean/target/commons-jelly-tags-dynabean-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-05042006.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-4/jaxen-1.1-beta-4.jar
-
[junit] at junit.framework.TestResult.runProtected(TestResult.java:124)
[junit] at junit.framework.TestResult.run(TestResult.java:109)
[junit] at junit.framework.TestCase.run(TestCase.java:118)
[junit] at junit.framework.TestSuite.runTest(TestSuite.java:208)
[junit] at junit.framework.TestSuite.run(TestSuite.java:203)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:325)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:536)
[junit] Apr 5, 2006 5:25:15 AM 
org.apache.commons.jelly.expression.xpath.XPathExpression evaluate
[junit] SEVERE: Error constructing xpath
[junit] org.jaxen.XPathSyntaxException: Node-set expected
[junit] at org.jaxen.BaseXPath.(BaseXPath.java:131)
[junit] at org.jaxen.BaseXPath.(BaseXPath.java:156)
[junit] at org.jaxen.dom4j.Dom4jXPath.(Dom4jXPath.java:101)
[junit] at 
org.apache.commons.jelly.expression.xpath.XPathExpression.evaluate(XPathExpression.java:78)
[junit] at 
org.apache.commons.jelly.expression.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:256)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
[junit] at 
org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59)
[junit] at junit.framework.TestCase.runBare(TestCase.java:127)
[junit] at junit.framework.TestResult$1.protect(TestResult.java:106)
[junit] at junit.framework.TestResult.runProtected(TestResult.java:124)
[junit] at junit.framework.

svn commit: r391600 - /jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java

2006-04-05 Thread dion
Author: dion
Date: Wed Apr  5 05:26:33 2006
New Revision: 391600

URL: http://svn.apache.org/viewcvs?rev=391600&view=rev
Log:
Test toString

Modified:

jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java

Modified: 
jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java?rev=391600&r1=391599&r2=391600&view=diff
==
--- 
jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java
 (original)
+++ 
jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java
 Wed Apr  5 05:26:33 2006
@@ -852,8 +852,13 @@
 {
 JexlContext jc = JexlHelper.createContext();
 jc.getVars().put("Boolean", Boolean.class);
-assertExpression(jc, "Boolean.valueOf('true')", Boolean.TRUE);
-
+assertExpression(jc, "Boolean.valueOf('true')", Boolean.TRUE);
+}
+
+public void testToString() throws Exception {
+String code = "abcd";
+Expression expr = ExpressionFactory.createExpression(code);
+assertEquals("Bad expression value", code, expr.toString());
 }
 
 /**



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r391599 - /jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java

2006-04-05 Thread dion
Author: dion
Date: Wed Apr  5 05:21:46 2006
New Revision: 391599

URL: http://svn.apache.org/viewcvs?rev=391599&view=rev
Log:
Add postResolver test

Modified:

jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java

Modified: 
jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java?rev=391599&r1=391598&r2=391599&view=diff
==
--- 
jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java
 (original)
+++ 
jakarta/commons/proper/jexl/trunk/src/test/org/apache/commons/jexl/JexlTest.java
 Wed Apr  5 05:21:46 2006
@@ -81,7 +81,7 @@
 Object o = e.evaluate(jc);
 
 assertTrue("o not instanceof String", o instanceof String);
-assertTrue("o incorrect", o.equals(GET_METHOD_STRING));
+assertEquals("o incorrect", GET_METHOD_STRING, o);
 }
 
 /**
@@ -745,47 +745,40 @@
  * first, a simple override
  */
 
-Expression expr =
-ExpressionFactory.createExpression("foo.bar");
-
+Expression expr = ExpressionFactory.createExpression("foo.bar");
 expr.addPreResolver(new FlatResolver());
 
 JexlContext jc = JexlHelper.createContext();
-
 Foo foo = new Foo();
-
 jc.getVars().put("foo.bar", "flat value");
 jc.getVars().put("foo", foo );
 
 Object o = expr.evaluate(jc);
-
-assertEquals("flat override", o,"flat value");
+assertEquals("flat override", "flat value", o);
 
 /*
  * now, let the resolver not find it and have it drop to jexl
  */
-
-expr =
-ExpressionFactory.createExpression("foo.bar.length()");
-
+expr = ExpressionFactory.createExpression("foo.bar.length()");
 expr.addPreResolver(new FlatResolver());
-
 o = expr.evaluate(jc);
-
-assertEquals("flat override 1", o,new 
Integer(GET_METHOD_STRING.length()));
+assertEquals("flat override 1", new 
Integer(GET_METHOD_STRING.length()), o);
 
 /*
  * now, let the resolver not find it and NOT drop to jexl
  */
 
-expr =
-ExpressionFactory.createExpression("foo.bar.length()");
-
+expr = ExpressionFactory.createExpression("foo.bar.length()");
 expr.addPreResolver(new FlatResolver(false));
-
 o = expr.evaluate(jc);
-
 assertEquals("flat override 2", o, null);
+
+// now for a post resolver
+expr = ExpressionFactory.createExpression("foo.bar.baz");
+Long result = new Long(1);
+jc.getVars().put("foo.bar.baz", result);
+expr.addPostResolver(new FlatResolver());
+assertEquals("flat override", result, expr.evaluate(jc));
 
 }
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[EMAIL PROTECTED]: Project commons-jelly-tags-jsl-test (in module commons-jelly) failed

2006-04-05 Thread commons-jelly-tags-jsl development
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 commons-jelly-tags-jsl-test has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 70 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-jsl-test :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on ant exists, no need to add for property 
maven.jar.ant-optional.
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -WARNING- Overriding Maven properties: 
[/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties]
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/gump_work/build_commons-jelly_commons-jelly-tags-jsl-test.html
Work Name: build_commons-jelly_commons-jelly-tags-jsl-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 15 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/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/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-05042006.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-4/jaxen-1.1-beta-4.jar
-
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262)
[junit] at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)
[junit] at 
org.apache.commons.jelly.TagSupport.getBodyText(TagSupport.java:234)
[junit] at 
org.apache.commons.jelly.tags.core.SetTag.doTag(SetTag.java:90)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
[junit] at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)
[junit] at 
org.apache.commons.jelly.tags.jsl.TemplateTag$1.run(TemplateTag.java:160)
[junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59)
[junit] at org.dom4j.rule.Mode.applyTemplates(Mode.java:80)
[junit] at org.dom4j.rule.RuleManager$1.run(RuleManager.java:171)
[junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:102)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:91)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:78)
[junit] at org.dom4j.rule.St

[EMAIL PROTECTED]: Project commons-jelly-tags-jsl-test (in module commons-jelly) failed

2006-04-05 Thread commons-jelly-tags-jsl development
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 commons-jelly-tags-jsl-test has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 70 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-jsl-test :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on ant exists, no need to add for property 
maven.jar.ant-optional.
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -WARNING- Overriding Maven properties: 
[/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties]
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/gump_work/build_commons-jelly_commons-jelly-tags-jsl-test.html
Work Name: build_commons-jelly_commons-jelly-tags-jsl-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 15 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/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/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-05042006.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-4/jaxen-1.1-beta-4.jar
-
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262)
[junit] at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)
[junit] at 
org.apache.commons.jelly.TagSupport.getBodyText(TagSupport.java:234)
[junit] at 
org.apache.commons.jelly.tags.core.SetTag.doTag(SetTag.java:90)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
[junit] at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)
[junit] at 
org.apache.commons.jelly.tags.jsl.TemplateTag$1.run(TemplateTag.java:160)
[junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59)
[junit] at org.dom4j.rule.Mode.applyTemplates(Mode.java:80)
[junit] at org.dom4j.rule.RuleManager$1.run(RuleManager.java:171)
[junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:102)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:91)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:78)
[junit] at org.dom4j.rule.St

[EMAIL PROTECTED]: Project commons-jelly-tags-html (in module commons-jelly) failed

2006-04-05 Thread commons-jelly-tags-html development
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 commons-jelly-tags-html has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 70 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-html :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-html/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-jelly-tags-html-05042006.jar] identifier set to 
project name
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-reports
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-html/gump_work/build_commons-jelly_commons-jelly-tags-html.html
Work Name: build_commons-jelly_commons-jelly-tags-html (Type: Build)
Work ended in a state of : Failed
Elapsed: 12 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/html]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/commons-jelly-tags-jsl-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-05042006.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-4/jaxen-1.1-beta-4.jar:/usr/local/gump/packages/nekohtml-0.9.5/nekohtml.jar
-
[junit] at 
org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59)
[junit] 
[junit] 
[junit] Testcase: 
testLowerCase(org.apache.commons.jelly.tags.junit.CaseTag$1): Caused an 
ERROR
[junit] 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:40:48:
  You must define an attribute called 'test' for this tag.
[junit] org.apache.commons.jelly.MissingAttributeException: 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:40:48:
  You must define an attribute called 'test' for this tag.
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:54)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
[junit] at 
org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59)
[junit] 
[junit] 
[junit] Testcase: 
testMixedCase(org.apache.commons.jelly.tags.junit.CaseTag$1): Caused an 
ERROR
[junit] 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:47:48:
  You must define an attribute called 'test' for this tag.
[junit] org.apache.commons.jelly.MissingAttributeException: 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:47:48:
  You must define an attribute called 'test' for this tag.
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:54)

[EMAIL PROTECTED]: Project commons-jelly-tags-html (in module commons-jelly) failed

2006-04-05 Thread commons-jelly-tags-html development
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 commons-jelly-tags-html has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 70 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-html :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-html/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-jelly-tags-html-05042006.jar] identifier set to 
project name
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-reports
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-html/gump_work/build_commons-jelly_commons-jelly-tags-html.html
Work Name: build_commons-jelly_commons-jelly-tags-html (Type: Build)
Work ended in a state of : Failed
Elapsed: 12 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/html]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/commons-jelly-tags-jsl-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-05042006.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-4/jaxen-1.1-beta-4.jar:/usr/local/gump/packages/nekohtml-0.9.5/nekohtml.jar
-
[junit] at 
org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59)
[junit] 
[junit] 
[junit] Testcase: 
testLowerCase(org.apache.commons.jelly.tags.junit.CaseTag$1): Caused an 
ERROR
[junit] 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:40:48:
  You must define an attribute called 'test' for this tag.
[junit] org.apache.commons.jelly.MissingAttributeException: 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:40:48:
  You must define an attribute called 'test' for this tag.
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:54)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
[junit] at 
org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59)
[junit] 
[junit] 
[junit] Testcase: 
testMixedCase(org.apache.commons.jelly.tags.junit.CaseTag$1): Caused an 
ERROR
[junit] 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:47:48:
  You must define an attribute called 'test' for this tag.
[junit] org.apache.commons.jelly.MissingAttributeException: 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:47:48:
  You must define an attribute called 'test' for this tag.
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:54)

[EMAIL PROTECTED]: Project commons-jelly-tags-xml-test (in module commons-jelly) failed

2006-04-05 Thread commons-jelly-tags-xml development
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 commons-jelly-tags-xml-test has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 70 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-xml-test :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-xml-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -WARNING- Overriding Maven properties: 
[/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/build.properties]
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-xml-test/gump_work/build_commons-jelly_commons-jelly-tags-xml-test.html
Work Name: build_commons-jelly_commons-jelly-tags-xml-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 18 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-05042006.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-05042006.jar
-
[junit] 
[junit] 
[junit] Testcase: 
testImportResourcesFromUncompiledScript(org.apache.commons.jelly.tags.xml.TestImport):
FAILED
[junit] expected:<... xmlns="http://www.w3.org/TR/xhtml1/strict";...> but 
was:<..>
[junit] junit.framework.ComparisonFailure: expected:<... 
xmlns="http://www.w3.org/TR/xhtml1/strict";...> but was:<..>
[junit] at 
org.apache.commons.jelly.tags.xml.TestImport.testImportResourcesFromUncompiledScript(TestImport.java:77)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit] at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[junit] at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[junit] 
[junit] 
[junit] [ERROR] TEST org.apache.commons.jelly.tags.xml.TestImport FAILED
[junit] Running org.apache.commons.jelly.tags.xml.TestXMLTags
[junit] Tests run: 19, Failures: 0, Errors: 0, Time elapsed: 3.001 sec
[junit] Testsuite: org.apache.commons.jelly.tags.xml.TestXMLTags
[junit] Tests run: 19, Failures: 0, Errors: 0, Time elapsed: 3.001 sec
[junit] 
[junit] - Standard Output ---
[junit] TestXMLTags.testNamespaceReplace() text=http://apache/testNS"; xmlns="http://java/ns"; 
test:abc="testValue">http://java/ns"; xmlns="http://java/ns"; 
other:abc="testValue">http://java/ns"; 
other:abc="testValue">
[junit] http://apache/testNS"; 
xmlns="http://apache/trueNS"; test:abc="testValue" abc2="testValue" 
abc3="testValue">
[junit] http://apache/testNS"; 
xmlns="http://apache/trueNS"; test:abc="testValue" abc2="testValue" 
abc3="testValue">
[junit] -  ---
[junit] Running org.apache.commons.jelly.tags.xml.TestJelly
[junit] some text
[junit] 
[junit] The exception was: 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:104:45:
  
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:104:4

[EMAIL PROTECTED]: Project commons-jelly-tags-xml-test (in module commons-jelly) failed

2006-04-05 Thread commons-jelly-tags-xml development
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 commons-jelly-tags-xml-test has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 70 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-xml-test :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-xml-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -WARNING- Overriding Maven properties: 
[/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/build.properties]
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-xml-test/gump_work/build_commons-jelly_commons-jelly-tags-xml-test.html
Work Name: build_commons-jelly_commons-jelly-tags-xml-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 18 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-05042006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-05042006.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-05042006.jar
-
[junit] 
[junit] 
[junit] Testcase: 
testImportResourcesFromUncompiledScript(org.apache.commons.jelly.tags.xml.TestImport):
FAILED
[junit] expected:<... xmlns="http://www.w3.org/TR/xhtml1/strict";...> but 
was:<..>
[junit] junit.framework.ComparisonFailure: expected:<... 
xmlns="http://www.w3.org/TR/xhtml1/strict";...> but was:<..>
[junit] at 
org.apache.commons.jelly.tags.xml.TestImport.testImportResourcesFromUncompiledScript(TestImport.java:77)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit] at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[junit] at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[junit] 
[junit] 
[junit] [ERROR] TEST org.apache.commons.jelly.tags.xml.TestImport FAILED
[junit] Running org.apache.commons.jelly.tags.xml.TestXMLTags
[junit] Tests run: 19, Failures: 0, Errors: 0, Time elapsed: 3.001 sec
[junit] Testsuite: org.apache.commons.jelly.tags.xml.TestXMLTags
[junit] Tests run: 19, Failures: 0, Errors: 0, Time elapsed: 3.001 sec
[junit] 
[junit] - Standard Output ---
[junit] TestXMLTags.testNamespaceReplace() text=http://apache/testNS"; xmlns="http://java/ns"; 
test:abc="testValue">http://java/ns"; xmlns="http://java/ns"; 
other:abc="testValue">http://java/ns"; 
other:abc="testValue">
[junit] http://apache/testNS"; 
xmlns="http://apache/trueNS"; test:abc="testValue" abc2="testValue" 
abc3="testValue">
[junit] http://apache/testNS"; 
xmlns="http://apache/trueNS"; test:abc="testValue" abc2="testValue" 
abc3="testValue">
[junit] -  ---
[junit] Running org.apache.commons.jelly.tags.xml.TestJelly
[junit] some text
[junit] 
[junit] The exception was: 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:104:45:
  
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:104:4

svn commit: r391588 - /jakarta/commons/proper/jexl/trunk/src/java/org/apache/commons/jexl/util/introspection/MethodMap.java

2006-04-05 Thread dion
Author: dion
Date: Wed Apr  5 04:37:40 2006
New Revision: 391588

URL: http://svn.apache.org/viewcvs?rev=391588&view=rev
Log:
Javadoc cleanup

Modified:

jakarta/commons/proper/jexl/trunk/src/java/org/apache/commons/jexl/util/introspection/MethodMap.java

Modified: 
jakarta/commons/proper/jexl/trunk/src/java/org/apache/commons/jexl/util/introspection/MethodMap.java
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/jexl/trunk/src/java/org/apache/commons/jexl/util/introspection/MethodMap.java?rev=391588&r1=391587&r2=391588&view=diff
==
--- 
jakarta/commons/proper/jexl/trunk/src/java/org/apache/commons/jexl/util/introspection/MethodMap.java
 (original)
+++ 
jakarta/commons/proper/jexl/trunk/src/java/org/apache/commons/jexl/util/introspection/MethodMap.java
 Wed Apr  5 04:37:40 2006
@@ -68,7 +68,7 @@
 /**
  * Return a list of methods with the same name.
  *
- * @param key a key to the [EMAIL PROTECTED] #methodByNameMap}
+ * @param key The method name.
  * @return List list of methods
  */
 public List get(String key)



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[EMAIL PROTECTED]: Project commons-chain (in module jakarta-commons) failed

2006-04-05 Thread Stefan Bodewig
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 commons-chain has an issue affecting its community integration.
This issue affects 8 projects,
 and has been outstanding for 64 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-chain :  GoF "Chain of Responsibility" pattern
- commons-jelly-tags-quartz :  Commons Jelly
- fulcrum-quartz :  Services Framework
- myfaces :  JavaServer(tm) Faces implementation
- portals-bridges-jsf :  Support for JSR168 compliant Portlet development
- quartz :  Job Scheduler
- struts-action :  Model 2 Model-View-Controller framework for Servlets and 
JSP
- struts-tiles :  Model 2 Model-View-Controller framework for Servlets and 
JSP


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-commons/commons-chain/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-chain-05042006.jar] identifier set to project name
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-commons/commons-chain/gump_work/build_jakarta-commons_commons-chain.html
Work Name: build_jakarta-commons_commons-chain (Type: Build)
Work ended in a state of : Failed
Elapsed: 17 secs
Command Line: java -Djava.awt.headless=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
 org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only -Dfinal.name=commons-chain-05042006 -f build.xml jar 
[Working Directory: /usr/local/gump/public/workspace/jakarta-commons/chain]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/chain/target/classes:/usr/local/gump/public/workspace/jakarta-commons/chain/target/test-classes:/usr/local/gump/packages/jsf-1_1_01/lib/jsf-api.jar:/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/packages/junit3.8.1/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/digester/dist/commons-digester.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-05042006.jar:/usr/local/gump/public/workspace/portals-pluto-1.0/api/target/portlet-api-1.0.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar
-
[junit] Tests run: 10, Failures: 0, Errors: 0, Time elapsed: 0.294 sec
[junit] Tests run: 10, Failures: 0, Errors: 0, Time elapsed: 0.294 sec

[junit] Testcase: testPristine took 0.042 sec
[junit] Testcase: testReadOnly took 0.003 sec
[junit] Testcase: testReadWrite took 0.001 sec
[junit] Testcase: testWriteOnly took 0 sec
[junit] Testcase: testAttributes took 0.001 sec
[junit] Testcase: testContains took 0.001 sec
[junit] Testcase: testEquals took 0.011 sec
[junit] Testcase: testKeySet took 0.002 sec
[junit] Testcase: testPutAll took 0.001 sec
[junit] Testcase: testSeriaization took 0.053 sec
[junit] Running org.apache.commons.chain.web.ChainResourcesTestCase
[junit] Testsuite: org.apache.commons.chain.web.ChainResourcesTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.249 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.249 sec

[junit] Testcase: testGetPaths took 0.084 sec
[junit] Running 
org.apache.commons.chain.web.servlet.ServletGetLocaleCommandTestCase
[junit] Testsuite: 
org.apache.commons.chain.web.servlet.ServletGetLocaleCommandTestCase
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.229 sec
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.229 sec

[junit] Testcase: testConfigured took 0.052 sec
[junit] Testcase: testDefaut took 

[EMAIL PROTECTED]: Project commons-chain (in module jakarta-commons) failed

2006-04-05 Thread Stefan Bodewig
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 commons-chain has an issue affecting its community integration.
This issue affects 8 projects,
 and has been outstanding for 64 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-chain :  GoF "Chain of Responsibility" pattern
- commons-jelly-tags-quartz :  Commons Jelly
- fulcrum-quartz :  Services Framework
- myfaces :  JavaServer(tm) Faces implementation
- portals-bridges-jsf :  Support for JSR168 compliant Portlet development
- quartz :  Job Scheduler
- struts-action :  Model 2 Model-View-Controller framework for Servlets and 
JSP
- struts-tiles :  Model 2 Model-View-Controller framework for Servlets and 
JSP


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-commons/commons-chain/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-chain-05042006.jar] identifier set to project name
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-commons/commons-chain/gump_work/build_jakarta-commons_commons-chain.html
Work Name: build_jakarta-commons_commons-chain (Type: Build)
Work ended in a state of : Failed
Elapsed: 17 secs
Command Line: java -Djava.awt.headless=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
 org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only -Dfinal.name=commons-chain-05042006 -f build.xml jar 
[Working Directory: /usr/local/gump/public/workspace/jakarta-commons/chain]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/chain/target/classes:/usr/local/gump/public/workspace/jakarta-commons/chain/target/test-classes:/usr/local/gump/packages/jsf-1_1_01/lib/jsf-api.jar:/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/packages/junit3.8.1/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/digester/dist/commons-digester.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-05042006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-05042006.jar:/usr/local/gump/public/workspace/portals-pluto-1.0/api/target/portlet-api-1.0.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar
-
[junit] Tests run: 10, Failures: 0, Errors: 0, Time elapsed: 0.294 sec
[junit] Tests run: 10, Failures: 0, Errors: 0, Time elapsed: 0.294 sec

[junit] Testcase: testPristine took 0.042 sec
[junit] Testcase: testReadOnly took 0.003 sec
[junit] Testcase: testReadWrite took 0.001 sec
[junit] Testcase: testWriteOnly took 0 sec
[junit] Testcase: testAttributes took 0.001 sec
[junit] Testcase: testContains took 0.001 sec
[junit] Testcase: testEquals took 0.011 sec
[junit] Testcase: testKeySet took 0.002 sec
[junit] Testcase: testPutAll took 0.001 sec
[junit] Testcase: testSeriaization took 0.053 sec
[junit] Running org.apache.commons.chain.web.ChainResourcesTestCase
[junit] Testsuite: org.apache.commons.chain.web.ChainResourcesTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.249 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.249 sec

[junit] Testcase: testGetPaths took 0.084 sec
[junit] Running 
org.apache.commons.chain.web.servlet.ServletGetLocaleCommandTestCase
[junit] Testsuite: 
org.apache.commons.chain.web.servlet.ServletGetLocaleCommandTestCase
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.229 sec
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.229 sec

[junit] Testcase: testConfigured took 0.052 sec
[junit] Testcase: testDefaut took 

Re: [logging] RC on ibiblio ?

2006-04-05 Thread Simon Kitching
On Wed, 2006-04-05 at 10:05 +0200, Nicolas De Loof wrote:
> Hello,
> 
> Can someone upload commons-logging RC on Maven2 ibiblio repository ?
> It would be very cool to also upload a POM and the sources jar...

That would be a good idea. 

We should also provide a link on the downloads page or something
similar. Just today a work colleague was looking for a later version
than 1.0.4 in order to get log4j TRACE support. I told him there was an
RC out, but there was just no way for him to locate it...


By the way, there is still an outstanding discussion about whether to
add JDK14Logger back into the commons-logging-api.jar file. It was there
in the previous release. It probably shouldn't be; it's not logical.
However it does no harm as far as I can see, and the point was made that
because the current RC doesn't include it, it isn't a drop-in
replacement. 

So I'm +1 on adding JDK14Logger back to the api jar, then cutting a new
RC and uploading to ibiblio + linking from useful places. 

Alternatively, we could just make the above change then hold a release
vote. I think we've given this RC enough time for feedback.

Cheers,

Simon


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[logging] RC on ibiblio ?

2006-04-05 Thread Nicolas De Loof


Hello,

Can someone upload commons-logging RC on Maven2 ibiblio repository ?
It would be very cool to also upload a POM and the sources jar...

Nico.

This message contains information that may be privileged or confidential and is 
the property of the Capgemini Group. It is intended only for the person to whom 
it is addressed. If you are not the intended recipient,  you are not authorized 
to read, print, retain, copy, disseminate,  distribute, or use this message or 
any part thereof. If you receive this  message in error, please notify the 
sender immediately and delete all  copies of this message.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[EMAIL PROTECTED]: Project commons-daemon-native-configure (in module jakarta-commons) failed

2006-04-05 Thread Bill Barker
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 commons-daemon-native-configure has an issue affecting its community 
integration.
This issue affects 2 projects,
 and has been outstanding for 16 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-daemon-native :  Native application for daemon
- commons-daemon-native-configure :  Configure the build for daemon


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-commons/commons-daemon-native-configure/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/jakarta-commons/commons-daemon-native-configure/gump_work/buildscript_jakarta-commons_commons-daemon-native-configure.html
Work Name: buildscript_jakarta-commons_commons-daemon-native-configure (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 4 secs
Command Line: 
/usr/local/gump/public/workspace/jakarta-commons/daemon/src/native/unix/configure
 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-commons/daemon/src/native/unix]
-
*** Current host ***
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking cached host system type... ok
*** C-Language compilation tools ***
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for ranlib... ranlib
*** Host support ***
checking C flags dependant on host system type... ok
*** Java compilation tools ***
checking for sablevm... NONE
checking for kaffe... NONE
checking for javac-sablevm... NONE
NONE
configure: error: javac not found
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/jakarta-commons/commons-daemon-native-configure/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/jakarta-commons/commons-daemon-native-configure/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 2705042006, vmgump.apache.org:vmgump-public:2705042006
Gump E-mail Identifier (unique within run) #22.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[EMAIL PROTECTED]: Project commons-daemon-native-configure (in module jakarta-commons) failed

2006-04-05 Thread Bill Barker
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 commons-daemon-native-configure has an issue affecting its community 
integration.
This issue affects 2 projects,
 and has been outstanding for 16 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-daemon-native :  Native application for daemon
- commons-daemon-native-configure :  Configure the build for daemon


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-commons/commons-daemon-native-configure/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/jakarta-commons/commons-daemon-native-configure/gump_work/buildscript_jakarta-commons_commons-daemon-native-configure.html
Work Name: buildscript_jakarta-commons_commons-daemon-native-configure (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 4 secs
Command Line: 
/usr/local/gump/public/workspace/jakarta-commons/daemon/src/native/unix/configure
 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-commons/daemon/src/native/unix]
-
*** Current host ***
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking cached host system type... ok
*** C-Language compilation tools ***
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for ranlib... ranlib
*** Host support ***
checking C flags dependant on host system type... ok
*** Java compilation tools ***
checking for sablevm... NONE
checking for kaffe... NONE
checking for javac-sablevm... NONE
NONE
configure: error: javac not found
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/jakarta-commons/commons-daemon-native-configure/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/jakarta-commons/commons-daemon-native-configure/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 2705042006, vmgump.apache.org:vmgump-public:2705042006
Gump E-mail Identifier (unique within run) #22.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]