Re: [pool] how about new release and incubating my composite pool implementation

[Henri Yandell]

On 2/13/06, robert burrell donkin <[EMAIL PROTECTED]> wrote:
> On Sun, 2006-02-12 at 17:35 -0500, Sandy McArthur wrote:
> > On 2/9/06, robert burrell donkin <[EMAIL PROTECTED]> wrote:
> > > i've checked the records and i can't see a software grant on record as
> > > being received. so, you'll create a archive (tar or zip) of the source
> > > which is to be donated to the ASF and create an MD5 for it. the software
> > > grant should describe the donated software and refer to the sum. the
> > > archive will be uploaded to an ASF server for the record. you'll need to
> > > fax the grant to jim.
> >
> > Fax sent 30 min ago.
>
> great :)
>
> the receipt notice hasn't been committed yet. jim last committed on the
> 10th (so there's nothing to be worried about yet). hopefully should be
> in his next batch.

When it shows; and prior to committing the code; go ahead and send an
email to [EMAIL PROTECTED], cc [EMAIL PROTECTED]; letting them know that
we're taking said code in.

Commons-CSV was a bit heavyweight compared to this, but here's what I did then:

http://mail-archives.apache.org/mod_mbox/incubator-general/200512.mbox/[EMAIL 
PROTECTED]

and for Norbert -> HTTP Components:

http://mail-archives.apache.org/mod_mbox/incubator-general/200601.mbox/[EMAIL 
PROTECTED]

Important to mention that we've voted this on.

---

Basically the Incubator is supposed to be in the process when it comes
to adding new sizeable pieces of code (such as would require a
software grant), and this is my lightweight solution to doing so. No
complaints so far.

Hen

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

Re: [jelly] Gump failures

[Dion Gillard]

Note to self and Paul:

In particular, it's ASTAddNote.unwiden(Long).

This needs to get looked at.

On 2/13/06, Dion Gillard <[EMAIL PROTECTED]> wrote:
> I'm pretty sure this has to do with recent changes in Jexl to 'narrow'
> results to make introspection easier.
>
> Before all integer results were stored in a long. Now they're stored
> as Byte, Short, Long etc.
>
> On 2/13/06, Paul Libbrecht <[EMAIL PROTECTED]> wrote:
> > But remember this is only part of the problem.
> > The jelly-test failure is related to expression-equality in jexl where:
> >
> > [junit] Expected expression: ${singleSize*2}
> > [junit] Actual expression: ${doubleSize} File:
> >
> > fails because, I think so said Dion, of primitive-types incorrect
> > comparison in jexl or jelly's packing of jexl.
> > DIdn't have the time to dive for it yet...
> >
> > paul
> >
> > Brett Porter wrote:
> > > I think this could be "solved" by setting it to use jaxen-1.1-beta-4
> > > instead. I'll try that now. If I can't get it fixed by the end of the
> > > week, I'll turn them off.
> > >
> > > I still believe that someone with spare time needs to get Jelly working
> > > with newer versions of Jaxen. Being stuck on beta-4 is not very
> > > desirable, and it appears they are never going to restore backwards
> > > compatibility as it was a deliberate breakage. I'm not that person (I
> > > have neither the xpath knowledge or spare time or need to use Jelly any
> > > more :)
> > >
> > > - Brett
> > >
> > > Bill Barker wrote:
> > >
> > >>> "Henri Yandell" <[EMAIL PROTECTED]> wrote in message
> > >>> news:[EMAIL PROTECTED]
> > >>> *ping*
> > >>>
> > >>> Waking this thread up again. While it's bad for us to go "Jelly HEAD +
> > >>> Jaxen HEAD -> can't work so turn off the build", it's much worse for
> > >>> us to let the noise continue as that switches people off of paying
> > >>> attention to the gump errors. It becomes background noise.
> > >>>
> > >> Actually, from the Gump page it's using jaxen-1.1b6 (Jaxen HEAD wasn't
> > >> building for a long time, so a lot of projects got switched to a packaged
> > >> version).
> > >>
> > >>
> > >>> Of course this might be interpreted as a feature request for gump;
> > >>> don't irritate us by repeating yourself, instead just send us a
> > >>> summary every now and then of the ones that are long term issues.
> > >>>
> > >>>
> > >> Development on Gump is sort of slow right now.  Unless somebody wants to
> > >> step up with a patch, it may not happen anytime soon ;-).
> > >>
> > >>
> > >>> Still, +1 to any idea that gets rid of the background noise.
> > >>>
> > >>>
> > >> The Jelly projects that are failing are basically the unit tests (this is
> > >> also true for tags-html, the error for tags-swing is just wierd :).  If
> > >> nobody care about the tests, you could just get rid of those s
> > >> in the jakarta-commons-jelly.xml file.
> > >>
> > >>
> > >>> Hen
> > >>>
> > >>>
> > >>
> > >>
> > >> -
> > >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> > >> For additional commands, e-mail: [EMAIL PROTECTED]
> > >>
> > >>
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> http://www.multitask.com.au/people/dion/
> "If I close my eyes it doesn't seem so dark." - SpongeBob SquarePants
>


--
http://www.multitask.com.au/people/dion/
"If I close my eyes it doesn't seem so dark." - SpongeBob SquarePants

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

Re: [all] Compile-Source-JDK and Compile-Target-JDK

[Henri Yandell]

On 2/14/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> Henri Yandell wrote:
> > However Java 1.2 and 1.3 don't run on OS X; and most Commons
> > components target those JVMs - and I thought Maven doesn't run on
> > those JVMs either.
>
> Run != target, but you'd still need them installed and all the
> appropriate fork/path settings set. Which we've been over more than once
> here :)
>
> I thought the agreement was to compile with the latest, but -target 1.3,
> and verify that there are no binary incompatibilities with earlier rt.jar's?

Entirely possible; I'm picking all this up again and probably have a
head full of confused memories and/or outdated decisions.

Hen

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

svn commit: r377640 - /jakarta/commons/proper/jexl/trunk/xdocs/changes.xml

[dion]

Author: dion
Date: Mon Feb 13 22:08:09 2006
New Revision: 377640

URL: http://svn.apache.org/viewcvs?rev=377640&view=rev
Log:
Add tests for UnaryMinus on integer and float point numbers

Modified:
jakarta/commons/proper/jexl/trunk/xdocs/changes.xml

Modified: jakarta/commons/proper/jexl/trunk/xdocs/changes.xml
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/jexl/trunk/xdocs/changes.xml?rev=377640&r1=377639&r2=377640&view=diff
==
--- jakarta/commons/proper/jexl/trunk/xdocs/changes.xml (original)
+++ jakarta/commons/proper/jexl/trunk/xdocs/changes.xml Mon Feb 13 22:08:09 2006
@@ -25,6 +25,7 @@
   
   
 
+  Unary minus was only working for integer 
values.
   Add @since tags to code so we can track 
API additions via javadoc
   Support assignment to variables
   'abc'.substring(0,1+1) is 
empty (method matching problem)



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

svn commit: r377636 - /jakarta/commons/proper/jexl/trunk/src/java/org/apache/commons/jexl/parser/ASTUnaryMinusNode.java

[dion]

Author: dion
Date: Mon Feb 13 22:04:58 2006
New Revision: 377636

URL: http://svn.apache.org/viewcvs?rev=377636&view=rev
Log:
Add support for Byte, Short, Long, Float and Double to UnaryMinus operation.
Integer was previously the only one supported.

Modified:

jakarta/commons/proper/jexl/trunk/src/java/org/apache/commons/jexl/parser/ASTUnaryMinusNode.java

Modified: 
jakarta/commons/proper/jexl/trunk/src/java/org/apache/commons/jexl/parser/ASTUnaryMinusNode.java
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/jexl/trunk/src/java/org/apache/commons/jexl/parser/ASTUnaryMinusNode.java?rev=377636&r1=377635&r2=377636&view=diff
==
--- 
jakarta/commons/proper/jexl/trunk/src/java/org/apache/commons/jexl/parser/ASTUnaryMinusNode.java
 (original)
+++ 
jakarta/commons/proper/jexl/trunk/src/java/org/apache/commons/jexl/parser/ASTUnaryMinusNode.java
 Mon Feb 13 22:04:58 2006
@@ -47,11 +47,37 @@
 {
 Object val = ((SimpleNode) jjtGetChild(0)).value(jc);
 
-if (val instanceof Integer)
+if (val instanceof Byte)
 {
-return new Integer(- ( ((Integer) val).intValue() ) );
+   byte valueAsByte = ((Byte) val).byteValue();
+return new Byte((byte) -valueAsByte);
+} 
+else if (val instanceof Short)
+{
+   short valueAsShort = ((Short) val).shortValue(); 
+return new Short((short) -valueAsShort);
+}
+else if (val instanceof Integer)
+{
+   int valueAsInt = ((Integer) val).intValue();
+return new Integer(-valueAsInt);
+}
+else if (val instanceof Long)
+{
+   long valueAsLong = ((Long) val).longValue();
+return new Long(-valueAsLong);
+}
+else if (val instanceof Float)
+{
+   float valueAsFloat = ((Float) val).floatValue(); 
+   return new Float( -valueAsFloat  );
+}
+else if (val instanceof Double)
+{
+   double valueAsDouble = ((Double) val).doubleValue();  
+   return new Double( -valueAsDouble );
 }
-throw new Exception("expression not integer valued");
+throw new Exception("expression not a number");
 }
 }
 



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

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

[dion]

Author: dion
Date: Mon Feb 13 22:03:54 2006
New Revision: 377635

URL: http://svn.apache.org/viewcvs?rev=377635&view=rev
Log:
Add tests for UnaryMinus on integer and float point numbers

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=377635&r1=377634&r2=377635&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
 Mon Feb 13 22:03:54 2006
@@ -325,6 +325,18 @@
 
 
 
+   /**
+*  test some simple mathematical calculations
+*/
+   public void testUnaryMinus()
+throws Exception
+   {
+   JexlContext jc = JexlHelper.createContext();
+   assertExpression(jc, "-3", new Integer(-3));
+   assertExpression(jc, "-3.0", new Float("-3.0"));
+   }
+
+
 /**
   *  test some simple mathematical calculations
   */



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

Re: [all] Compile-Source-JDK and Compile-Target-JDK

[Brett Porter]

Henri Yandell wrote:
> However Java 1.2 and 1.3 don't run on OS X; and most Commons
> components target those JVMs - and I thought Maven doesn't run on
> those JVMs either.

Run != target, but you'd still need them installed and all the
appropriate fork/path settings set. Which we've been over more than once
here :)

I thought the agreement was to compile with the latest, but -target 1.3,
and verify that there are no binary incompatibilities with earlier rt.jar's?

- Brett (now wondering about a Clirr extension that detects binary
incompatibility with certain JVMs).


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

Re: [jelly] Gump failures

[Henri Yandell]

Rather than stopping gump; why not just turn off these particular
tests in the build (and System out something saying they're being
skipped)?

Hen


On 2/13/06, Paul Libbrecht <[EMAIL PROTECTED]> wrote:
> But remember this is only part of the problem.
> The jelly-test failure is related to expression-equality in jexl where:
>
> [junit] Expected expression: ${singleSize*2}
> [junit] Actual expression: ${doubleSize} File:
>
> fails because, I think so said Dion, of primitive-types incorrect
> comparison in jexl or jelly's packing of jexl.
> DIdn't have the time to dive for it yet...
>
> paul
>
> Brett Porter wrote:
> > I think this could be "solved" by setting it to use jaxen-1.1-beta-4
> > instead. I'll try that now. If I can't get it fixed by the end of the
> > week, I'll turn them off.
> >
> > I still believe that someone with spare time needs to get Jelly working
> > with newer versions of Jaxen. Being stuck on beta-4 is not very
> > desirable, and it appears they are never going to restore backwards
> > compatibility as it was a deliberate breakage. I'm not that person (I
> > have neither the xpath knowledge or spare time or need to use Jelly any
> > more :)
> >
> > - Brett
> >
> > Bill Barker wrote:
> >
> >>> "Henri Yandell" <[EMAIL PROTECTED]> wrote in message
> >>> news:[EMAIL PROTECTED]
> >>> *ping*
> >>>
> >>> Waking this thread up again. While it's bad for us to go "Jelly HEAD +
> >>> Jaxen HEAD -> can't work so turn off the build", it's much worse for
> >>> us to let the noise continue as that switches people off of paying
> >>> attention to the gump errors. It becomes background noise.
> >>>
> >> Actually, from the Gump page it's using jaxen-1.1b6 (Jaxen HEAD wasn't
> >> building for a long time, so a lot of projects got switched to a packaged
> >> version).
> >>
> >>
> >>> Of course this might be interpreted as a feature request for gump;
> >>> don't irritate us by repeating yourself, instead just send us a
> >>> summary every now and then of the ones that are long term issues.
> >>>
> >>>
> >> Development on Gump is sort of slow right now.  Unless somebody wants to
> >> step up with a patch, it may not happen anytime soon ;-).
> >>
> >>
> >>> Still, +1 to any idea that gets rid of the background noise.
> >>>
> >>>
> >> The Jelly projects that are failing are basically the unit tests (this is
> >> also true for tags-html, the error for tags-swing is just wierd :).  If
> >> nobody care about the tests, you could just get rid of those s
> >> in the jakarta-commons-jelly.xml file.
> >>
> >>
> >>> Hen
> >>>
> >>>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

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

Re: [all] Compile-Source-JDK and Compile-Target-JDK

[Henri Yandell]

On 2/13/06, Dion Gillard <[EMAIL PROTECTED]> wrote:
> On 2/14/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
> [snip]
> >
> > I thought we were supposed to use Ant because Maven can't run under
> > the JVMs we generally target (which also rules out OS X :) ).
>
> huh? Maven 1.x runs fine on OSX

However Java 1.2 and 1.3 don't run on OS X; and most Commons
components target those JVMs - and I thought Maven doesn't run on
those JVMs either.

Hen

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

Re: [all] Compile-Source-JDK and Compile-Target-JDK

[Dion Gillard]

On 2/14/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> On 2/14/06, Dion Gillard <[EMAIL PROTECTED]> wrote:
> > Which part of the email build was failing?
>
> Sorry failing was too strong - it was trying to download javamail and
> jaf and couldn't find them - so a config issue on my part (I assume
> theres a repository I could point to to get them or configure it
> locally?). As I was doing 30-40 components I just switly moved on to
> the next :-(

There's no repository available as Sun BCL forbids distribution in
this way. So it's download and place appropriately yourself
unfortunately :-(

--
http://www.multitask.com.au/people/dion/
"If I close my eyes it doesn't seem so dark." - SpongeBob SquarePants

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

Re: [all] Compile-Source-JDK and Compile-Target-JDK

[Niall Pemberton]

On 2/14/06, Dion Gillard <[EMAIL PROTECTED]> wrote:
> Which part of the email build was failing?

Sorry failing was too strong - it was trying to download javamail and
jaf and couldn't find them - so a config issue on my part (I assume
theres a repository I could point to to get them or configure it
locally?). As I was doing 30-40 components I just switly moved on to
the next :-(

Niall

> It's built fine for me lately
>
> On 2/14/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> > OK I've done this for active components in "proper" and "sandbox".
> > Couldn't test email and modler because their builds failed.
> >
> > Also exec and openpgp only have maven2 build files. I downloaded
> > maven2 and got as far as working out how to add manifest entries - but
> > I couldn't work out how to refernece the compile plugin configuration
> > - so I've left the JDK bits commented out in the sandbox's pom.xml:
> >
> >http://tinyurl.com/737qc
> >
> > Any maven2 experts feel free to jump in :-)
> >
> > I also added a bit to the release docs - as per Robert's suggestion.
> >
> > Niall
> >
> > On 2/10/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> > > I just added "Compile-Source-JDK"  and "Compile-Target-JDK" attributes to
> > > the validator jar's manifest file (the manifest spec says unknown 
> > > attributes
> > > are ignored) to show the setting of  maven's "maven.compile.source" and
> > > "maven.compile.target" attributes which the jar was created with.
> > >
> > > http://svn.apache.org/viewcvs?rev=376748&view=rev
> > >
> > > I think its a good idea to give people "comfort" over the JDK version used
> > > to build a release. If no-one objects I will modify the rest of the 
> > > commons
> > > components to do the same.
> > >
> > > Niall
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> http://www.multitask.com.au/people/dion/
> "If I close my eyes it doesn't seem so dark." - SpongeBob SquarePants
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

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

Re: [all] Compile-Source-JDK and Compile-Target-JDK

[Dion Gillard]

On 2/14/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
[snip]
>
> I thought we were supposed to use Ant because Maven can't run under
> the JVMs we generally target (which also rules out OS X :) ).

huh? Maven 1.x runs fine on OSX

--
http://www.multitask.com.au/people/dion/
"If I close my eyes it doesn't seem so dark." - SpongeBob SquarePants

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

Re: [all] Compile-Source-JDK and Compile-Target-JDK

[Dion Gillard]

Which part of the email build was failing?

It's built fine for me lately

On 2/14/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> OK I've done this for active components in "proper" and "sandbox".
> Couldn't test email and modler because their builds failed.
>
> Also exec and openpgp only have maven2 build files. I downloaded
> maven2 and got as far as working out how to add manifest entries - but
> I couldn't work out how to refernece the compile plugin configuration
> - so I've left the JDK bits commented out in the sandbox's pom.xml:
>
>http://tinyurl.com/737qc
>
> Any maven2 experts feel free to jump in :-)
>
> I also added a bit to the release docs - as per Robert's suggestion.
>
> Niall
>
> On 2/10/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> > I just added "Compile-Source-JDK"  and "Compile-Target-JDK" attributes to
> > the validator jar's manifest file (the manifest spec says unknown attributes
> > are ignored) to show the setting of  maven's "maven.compile.source" and
> > "maven.compile.target" attributes which the jar was created with.
> >
> > http://svn.apache.org/viewcvs?rev=376748&view=rev
> >
> > I think its a good idea to give people "comfort" over the JDK version used
> > to build a release. If no-one objects I will modify the rest of the commons
> > components to do the same.
> >
> > Niall
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
http://www.multitask.com.au/people/dion/
"If I close my eyes it doesn't seem so dark." - SpongeBob SquarePants

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

Re: [net] FTP ListingFunctionalTest no longer works

[Jeffrey D. Brekke]

I'll look into this.  If so I'll see if I can find another one to poke at.

Steve Cohen wrote:
We have some functional tests for commons-net, which depend on 
connecting to ftp sites and putting them through their paces.  (These 
tests are excluded from Gump, for obvious reasons).  Some of the tests 
depend on being able to access a vms ftp server at h71000.www7.hp.com.  
This ftp server no longer seems to accept connections (or it may just be 
a temporary glitch tonight).  I believe Jeff Brekke wrote this test.  
Jeff, would you happen to know if this site has moved and if so, update 
the test?  Thanks.


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



--
=
Jeffrey D. Brekke   [EMAIL PROTECTED]
Wisconsin,  USA [EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.bloglines.com/blog/jbrekke   [EMAIL PROTECTED]


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

Re: [all] Compile-Source-JDK and Compile-Target-JDK

[Henri Yandell]

On 2/13/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> On 2/13/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> >
> > On 2/14/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> > > On 2/13/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> > > >
> > > > OK I've done this for active components in "proper" and "sandbox".
> > > > Couldn't test email and modler because their builds failed.
> > >
> > >
> > > You only changed things for the Maven builds, right?  The nightlies
> > (which
> > > use Ant) won't reflect this.  (For the record, the Commons nightlies are
> > > compiled with JDK 1.4.2).
> >
> > Yes. I assume that most components are using maven for creating
> > releases. Is it an issue that they don't - or would there be an issue
> > if they did?
>
>
> It would be an issue if they did *not* use Maven ... the Ant build does not
> add these two attributes to the manifest.  I suspect you are correct,
> though, about most people using Maven for release builds ... but we should
> probably say something to that effect in the packaging instructions.

I thought we were supposed to use Ant because Maven can't run under
the JVMs we generally target (which also rules out OS X :) ).

Hen

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

[net] FTP ListingFunctionalTest no longer works

[Steve Cohen]

We have some functional tests for commons-net, which depend on
connecting to ftp sites and putting them through their paces.  (These
tests are excluded from Gump, for obvious reasons).  Some of the tests
depend on being able to access a vms ftp server at h71000.www7.hp.com.
This ftp server no longer seems to accept connections (or it may just be
a temporary glitch tonight).  I believe Jeff Brekke wrote this test.
Jeff, would you happen to know if this site has moved and if so, update
the test?  Thanks.


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

[net] FTP ListingFunctionalTest no longer works

[Steve Cohen]

We have some functional tests for commons-net, which depend on 
connecting to ftp sites and putting them through their paces.  (These 
tests are excluded from Gump, for obvious reasons).  Some of the tests 
depend on being able to access a vms ftp server at h71000.www7.hp.com.  
This ftp server no longer seems to accept connections (or it may just be 
a temporary glitch tonight).  I believe Jeff Brekke wrote this test.  
Jeff, would you happen to know if this site has moved and if so, update 
the test?  Thanks.


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

svn commit: r377587 - in /jakarta/commons/proper/net/trunk/src: java/org/apache/commons/net/ftp/parser/UnixFTPEntryParser.java test/org/apache/commons/net/ftp/parser/UnixFTPEntryParserTest.java

[scohen]

Author: scohen
Date: Mon Feb 13 18:48:43 2006
New Revision: 377587

URL: http://svn.apache.org/viewcvs?rev=377587&view=rev
Log:
Patch by David D. Kilzer.  bug 38634.  Fix problem with group names with spaces 
in them
(allowed by Windows, and therefore Cygwin).

Modified:

jakarta/commons/proper/net/trunk/src/java/org/apache/commons/net/ftp/parser/UnixFTPEntryParser.java

jakarta/commons/proper/net/trunk/src/test/org/apache/commons/net/ftp/parser/UnixFTPEntryParserTest.java

Modified: 
jakarta/commons/proper/net/trunk/src/java/org/apache/commons/net/ftp/parser/UnixFTPEntryParser.java
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/net/trunk/src/java/org/apache/commons/net/ftp/parser/UnixFTPEntryParser.java?rev=377587&r1=377586&r2=377587&view=diff
==
--- 
jakarta/commons/proper/net/trunk/src/java/org/apache/commons/net/ftp/parser/UnixFTPEntryParser.java
 (original)
+++ 
jakarta/commons/proper/net/trunk/src/java/org/apache/commons/net/ftp/parser/UnixFTPEntryParser.java
 Mon Feb 13 18:48:43 2006
@@ -89,7 +89,7 @@
 
+"(((r|-)(w|-)([xsStTL-]))((r|-)(w|-)([xsStTL-]))((r|-)(w|-)([xsStTL-])))\\+?\\s+"
 + "(\\d+)\\s+"
 + "(\\S+)\\s+"
-+ "(?:(\\S+)\\s+)?"
++ "(?:(\\S+(?:\\s\\S+)*)\\s+)?"
 + "(\\d+)\\s+"
 
 /*

Modified: 
jakarta/commons/proper/net/trunk/src/test/org/apache/commons/net/ftp/parser/UnixFTPEntryParserTest.java
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/net/trunk/src/test/org/apache/commons/net/ftp/parser/UnixFTPEntryParserTest.java?rev=377587&r1=377586&r2=377587&view=diff
==
--- 
jakarta/commons/proper/net/trunk/src/test/org/apache/commons/net/ftp/parser/UnixFTPEntryParserTest.java
 (original)
+++ 
jakarta/commons/proper/net/trunk/src/test/org/apache/commons/net/ftp/parser/UnixFTPEntryParserTest.java
 Mon Feb 13 18:48:43 2006
@@ -36,7 +36,7 @@
"drwxr-xr-x   2 root root 4096 Aug 36  2001 
zztpp",
"-rw-r--r--   1 14   staff   80284 Aug 22  
zxJDBC-1.2.3.tar.gz",
"-rw-r--r--   1 14   staff  119:26 Aug 22  2000 
zxJDBC-1.2.3.zip",
-   "-rw-r--r--   1 ftp  no group83853 Jan 22  2001 
zxJDBC-1.2.4.tar.gz",
+   /*"-rw-r--r--   1 ftp  no group83853 Jan 22  
2001 zxJDBC-1.2.4.tar.gz",*/
"-rw-r--r--   1ftp   nogroup126552 Jan 22  2001 
zxJDBC-1.2.4.zip",
"-rw-r--r--   1 root root   190144 2001-04-27 
zxJDBC-2.0.1b1.zip",
"-rw-r--r--   1 root root   111325 Apr -7 18:79 
zxJDBC-2.0.1b1.tar.gz" };
@@ -70,7 +70,9 @@
"-rwsr-sr--   1 500  500 0 Mar 25 0:23 
testSuidExec2",
"drwxrwx---+ 23 500 5000 Jan 10 13:09 testACL",
"-rw-r--r--   1 13518644 May 25 12:12 std",
-"lrwxrwxrwx   1 neeme neeme 23 Mar  2 18:06 macros -> 
./../../global/macros/."
+"lrwxrwxrwx   1 neeme neeme 23 Mar  2 18:06 macros -> 
./../../global/macros/.",
+   "-rw-r--r--   1 ftp  group with spaces in it as 
allowed in cygwin see bug 38634   83853 Jan 22  2001 zxJDBC-1.2.4.tar.gz"
+
 
};
 
@@ -202,13 +204,13 @@
public void testParseFieldsOnFile() throws Exception {
FTPFile f = getParser()
.parseFTPEntry(
-   "-rwxr-xr-x   2 user group  
   50 Mar  2 15:13 zxbox");
+   "-rwxr-xr-x   2 user my 
group 50050 Mar  2 15:13 zxbox");
assertNotNull("Could not parse entry.", f);
assertTrue("Should have been a file.", f.isFile());
checkPermissions(f);
assertEquals(2, f.getHardLinkCount());
assertEquals("user", f.getUser());
-   assertEquals("group", f.getGroup());
+   assertEquals("my group 500", f.getGroup());
assertEquals("zxbox", f.getName());
assertEquals(50L, f.getSize());
 



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

Re: [all] Compile-Source-JDK and Compile-Target-JDK

[Niall Pemberton]

On 2/14/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> On 2/13/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> >
> > On 2/14/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> > > On 2/13/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> > > >
> > > > OK I've done this for active components in "proper" and "sandbox".
> > > > Couldn't test email and modler because their builds failed.
> > >
> > >
> > > You only changed things for the Maven builds, right?  The nightlies
> > (which
> > > use Ant) won't reflect this.  (For the record, the Commons nightlies are
> > > compiled with JDK 1.4.2).
> >
> > Yes. I assume that most components are using maven for creating
> > releases. Is it an issue that they don't - or would there be an issue
> > if they did?
>
>
> It would be an issue if they did *not* use Maven ... the Ant build does not
> add these two attributes to the manifest.  I suspect you are correct,
> though, about most people using Maven for release builds ... but we should
> probably say something to that effect in the packaging instructions.

I can do that - packaging instructions that is (ant builds would be
more effort than the quick maven cut and paste). I assume you mean the
"release guidelines" pages on commons:

  http://jakarta.apache.org/commons/releases/index.html

If it was somewhere else you were thinking of then let me know.

Niall

> Craig
>
>
> Niall
> >
> > > Craig
> > >
> > > Also exec and openpgp only have maven2 build files. I downloaded
> > > > maven2 and got as far as working out how to add manifest entries - but
> > > > I couldn't work out how to refernece the compile plugin configuration
> > > > - so I've left the JDK bits commented out in the sandbox's pom.xml:
> > > >
> > > >http://tinyurl.com/737qc
> > > >
> > > > Any maven2 experts feel free to jump in :-)
> > > >
> > > > I also added a bit to the release docs - as per Robert's suggestion.
> > > >
> > > > Niall
> > > >
> > > > On 2/10/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> > > > > I just added "Compile-Source-JDK"  and "Compile-Target-JDK"
> > attributes
> > > > to
> > > > > the validator jar's manifest file (the manifest spec says unknown
> > > > attributes
> > > > > are ignored) to show the setting of  maven's "maven.compile.source"
> > and
> > > > > "maven.compile.target" attributes which the jar was created with.
> > > > >
> > > > > http://svn.apache.org/viewcvs?rev=376748&view=rev
> > > > >
> > > > > I think its a good idea to give people "comfort" over the JDK
> > version
> > > > used
> > > > > to build a release. If no-one objects I will modify the rest of the
> > > > commons
> > > > > components to do the same.
> > > > >
> > > > > Niall

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

Re: [all] Compile-Source-JDK and Compile-Target-JDK

[Craig McClanahan]

On 2/13/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
>
> On 2/14/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> > On 2/13/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> > >
> > > OK I've done this for active components in "proper" and "sandbox".
> > > Couldn't test email and modler because their builds failed.
> >
> >
> > You only changed things for the Maven builds, right?  The nightlies
> (which
> > use Ant) won't reflect this.  (For the record, the Commons nightlies are
> > compiled with JDK 1.4.2).
>
> Yes. I assume that most components are using maven for creating
> releases. Is it an issue that they don't - or would there be an issue
> if they did?


It would be an issue if they did *not* use Maven ... the Ant build does not
add these two attributes to the manifest.  I suspect you are correct,
though, about most people using Maven for release builds ... but we should
probably say something to that effect in the packaging instructions.

Craig


Niall
>
> > Craig
> >
> > Also exec and openpgp only have maven2 build files. I downloaded
> > > maven2 and got as far as working out how to add manifest entries - but
> > > I couldn't work out how to refernece the compile plugin configuration
> > > - so I've left the JDK bits commented out in the sandbox's pom.xml:
> > >
> > >http://tinyurl.com/737qc
> > >
> > > Any maven2 experts feel free to jump in :-)
> > >
> > > I also added a bit to the release docs - as per Robert's suggestion.
> > >
> > > Niall
> > >
> > > On 2/10/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> > > > I just added "Compile-Source-JDK"  and "Compile-Target-JDK"
> attributes
> > > to
> > > > the validator jar's manifest file (the manifest spec says unknown
> > > attributes
> > > > are ignored) to show the setting of  maven's "maven.compile.source"
> and
> > > > "maven.compile.target" attributes which the jar was created with.
> > > >
> > > > http://svn.apache.org/viewcvs?rev=376748&view=rev
> > > >
> > > > I think its a good idea to give people "comfort" over the JDK
> version
> > > used
> > > > to build a release. If no-one objects I will modify the rest of the
> > > commons
> > > > components to do the same.
> > > >
> > > > Niall
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

DO NOT REPLY [Bug 38634] - [net] UnixFTPEntryParser fails to parse Cygwin proftpd output when group names contain spaces

[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=38634





--- Additional Comments From [EMAIL PROTECTED]  2006-02-14 03:15 ---
Thanks, that's a good patch.  I had my doubts it would pass the JUnit tests, but
except for a test that specifically disallowed spaces in group names (which I
can no longer see a good reason for), it passes all existing tests plus a couple
more I ginned up.  I will commit this soon.

-- 
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: [all] Compile-Source-JDK and Compile-Target-JDK

[Niall Pemberton]

On 2/12/06, robert burrell donkin <[EMAIL PROTECTED]> wrote:
>
> sounds like a good idea :)
>
> any chance of adding a few words to the release documentation?

I added three references to it

Two of them are here (the other earlier in the "Check Class File
Format" section):

http://jakarta.apache.org/commons/releases/prepare.html#checkjarmanifest
http://jakarta.apache.org/commons/releases/prepare.html#classfileformat

Niall

> - robert
>

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

Re: [all] Compile-Source-JDK and Compile-Target-JDK

[Niall Pemberton]

On 2/14/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> On 2/13/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> >
> > OK I've done this for active components in "proper" and "sandbox".
> > Couldn't test email and modler because their builds failed.
>
>
> You only changed things for the Maven builds, right?  The nightlies (which
> use Ant) won't reflect this.  (For the record, the Commons nightlies are
> compiled with JDK 1.4.2).

Yes. I assume that most components are using maven for creating
releases. Is it an issue that they don't - or would there be an issue
if they did?

Niall

> Craig
>
> Also exec and openpgp only have maven2 build files. I downloaded
> > maven2 and got as far as working out how to add manifest entries - but
> > I couldn't work out how to refernece the compile plugin configuration
> > - so I've left the JDK bits commented out in the sandbox's pom.xml:
> >
> >http://tinyurl.com/737qc
> >
> > Any maven2 experts feel free to jump in :-)
> >
> > I also added a bit to the release docs - as per Robert's suggestion.
> >
> > Niall
> >
> > On 2/10/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> > > I just added "Compile-Source-JDK"  and "Compile-Target-JDK" attributes
> > to
> > > the validator jar's manifest file (the manifest spec says unknown
> > attributes
> > > are ignored) to show the setting of  maven's "maven.compile.source" and
> > > "maven.compile.target" attributes which the jar was created with.
> > >
> > > http://svn.apache.org/viewcvs?rev=376748&view=rev
> > >
> > > I think its a good idea to give people "comfort" over the JDK version
> > used
> > > to build a release. If no-one objects I will modify the rest of the
> > commons
> > > components to do the same.
> > >
> > > Niall
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>

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

Re: [all] Compile-Source-JDK and Compile-Target-JDK

[Craig McClanahan]

On 2/13/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
>
> OK I've done this for active components in "proper" and "sandbox".
> Couldn't test email and modler because their builds failed.


You only changed things for the Maven builds, right?  The nightlies (which
use Ant) won't reflect this.  (For the record, the Commons nightlies are
compiled with JDK 1.4.2).

Craig

Also exec and openpgp only have maven2 build files. I downloaded
> maven2 and got as far as working out how to add manifest entries - but
> I couldn't work out how to refernece the compile plugin configuration
> - so I've left the JDK bits commented out in the sandbox's pom.xml:
>
>http://tinyurl.com/737qc
>
> Any maven2 experts feel free to jump in :-)
>
> I also added a bit to the release docs - as per Robert's suggestion.
>
> Niall
>
> On 2/10/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> > I just added "Compile-Source-JDK"  and "Compile-Target-JDK" attributes
> to
> > the validator jar's manifest file (the manifest spec says unknown
> attributes
> > are ignored) to show the setting of  maven's "maven.compile.source" and
> > "maven.compile.target" attributes which the jar was created with.
> >
> > http://svn.apache.org/viewcvs?rev=376748&view=rev
> >
> > I think its a good idea to give people "comfort" over the JDK version
> used
> > to build a release. If no-one objects I will modify the rest of the
> commons
> > components to do the same.
> >
> > Niall
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [all] Compile-Source-JDK and Compile-Target-JDK

[Niall Pemberton]

OK I've done this for active components in "proper" and "sandbox".
Couldn't test email and modler because their builds failed.

Also exec and openpgp only have maven2 build files. I downloaded
maven2 and got as far as working out how to add manifest entries - but
I couldn't work out how to refernece the compile plugin configuration
- so I've left the JDK bits commented out in the sandbox's pom.xml:

   http://tinyurl.com/737qc

Any maven2 experts feel free to jump in :-)

I also added a bit to the release docs - as per Robert's suggestion.

Niall

On 2/10/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> I just added "Compile-Source-JDK"  and "Compile-Target-JDK" attributes to
> the validator jar's manifest file (the manifest spec says unknown attributes
> are ignored) to show the setting of  maven's "maven.compile.source" and
> "maven.compile.target" attributes which the jar was created with.
>
> http://svn.apache.org/viewcvs?rev=376748&view=rev
>
> I think its a good idea to give people "comfort" over the JDK version used
> to build a release. If no-one objects I will modify the rest of the commons
> components to do the same.
>
> Niall

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

Re: [logging] r375631 - systemClassloaderTried patch

[Simon Kitching]

On Mon, 2006-02-13 at 22:33 +, robert burrell donkin wrote:
> On Mon, 2006-02-13 at 14:21 +1300, Simon Kitching wrote:
> > Hi Robert,
> > 
> > I've had a look at this patch and it doesn't seem quite right to me.
> 
> i had the same feeling :)
> 
> but that might just be the specifications being unintuitive again...
> 
> > Presumably this is to handle the case where the system classloader is
> > not in the chain leading from base classloader to boot classloader. This
> > is a rather odd situation, but I guess that in the new principle of "try
> > everything before failing" we could have a go with that when all else
> > fails.
> 
> not quite
> 
> this patch is intended to address allowed variability in the classloader
> class implementation noted in the javadocs for ClassLoader#getParent. it
> is possible that some JRE implementations "may use null to represent the
> bootstrap class loader. This method will return null in such
> implementations if this class loader's parent is the bootstrap class
> loader."  
> 
> the term bootstrap classloader is difficult. i suspect that this javadoc
> is prior to the introduction of boot, extension and system classloaders.
> i elected to assume that using the system classloader would usually be
> good enough (providing that recursive loops are avoided) since i don't
> know of any cross-JRE way of accessing the boot classloader. (if anyone
> knows, please jump in :)

I would interpret this differently. I think "bootstrap class loader" is
the same thing as "boot classloader", which is indeed represented by
"null" in the Sun JVM. A classloader for which getParent returns null is
a child of the boot classloader.

Classes in the boot classloader can be accessed via
  ClassLoader loader = null;
  Class.forName(className, true, loader);
By passing null as the loader to use, the boot classloader is used. This
is exactly what the code in method createLogFromClass is already doing;
because null is tested for only at the end of the loop, an attempt is
made to use the null (boot) classloader already.

In early JVMs, I believe ClassLoader.getSystemClassLoader returns null,
ie the "system" and "boot" classloaders are the same. I believe that
some embedded JVMs do the same thing, even if they support java > 1.1

Am I mistaken in thinking "bootstrap classloader" and "boot classloader"
are the same thing?

> 
> but it seems like a lot of complex code to address a risk something this
> obscure...
> 
> > However this is currently hooked in to fire when parentCL is null, ie
> > *before* we try the bootloader. I believe that in simple JVMs the
> > bootloader IS also the system classloader. So I think it would be better
> > as:
> > 
> > final ClassLoader systemCL = ClassLoader.getSystemClassLoader();
> > boolean systemCLTried = false;
> > for(;;) {
> >   // checks as currently done
> > 
> >   if (currentCL == systemCL) {
> > // the CL we just tested was the systemCL
> > systemCLTried = true;
> >   }
> > 
> >   if (currentCL == null) {
> > if (systemCLTried == true) {
> >   break;
> > }
> > 
> > // We've walked up the CL tree, but never visited the systemCL.
> > // Before giving up, let's try walking up from the system CL too..
> > currentCL = systemCL;
> >   } else {
> > currentCL = currentCL.getParent();
> >   }
> > }
> > 
> > Thoughts?
> 
> this seems like a better formulation with equivalent effect.

Almost the same. However the above code effectively "inserts" the system
classloader only *after* trying the logic with the null classloader. The
recently committed patch inserts it *before* trying the null loader, and
never tries the null loader at all.

> 
> i'd be equally happy to revert and go with just a dianostic message for
> now, though.

Lets do that then. The situation where the system classloader is not in
the chain from TCCL to boot is possible, but very weird. 

Cheers,

Simon



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

svn commit: r377559 - in /jakarta/commons: sandbox/compress/trunk/ sandbox/csv/trunk/ sandbox/i18n/trunk/ sandbox/id/trunk/ sandbox/javaflow/trunk/ sandbox/pipeline/trunk/ sandbox/proxy/trunk/ sandbox

[niallp]

Author: niallp
Date: Mon Feb 13 17:17:27 2006
New Revision: 377559

URL: http://svn.apache.org/viewcvs?rev=377559&view=rev
Log:
Modify maven build to add two non-standard attributes to the jar's manifest 
file to indicate the values of "maven.compile.source" and 
"maven.compile.target". Also modify the build to include an 
"Implementation-Vendor-Id" of "org.apache" in the jar's manifest.

The two non-standard entires created in the manifest file will look something 
like the following:

X-Compile-Source-JDK: 1.3
X-Compile-Target-JDK: 1.3

This change serves two purposes:

  1) To provide comfort to users regarding JVM compatibility.
  2) Enable releases to be checked more easily for JVM compatibility.

The manifest specification indicates that "unknown" entries in the manifest 
file are ignored. These entries have been prefixed with "X-" which is a 
sometimes used "convention" for indicating non-standard entries.

See thread: http://tinyurl.com/839zh

Modified:
jakarta/commons/sandbox/compress/trunk/project.properties
jakarta/commons/sandbox/csv/trunk/project.properties
jakarta/commons/sandbox/i18n/trunk/project.properties
jakarta/commons/sandbox/id/trunk/project.properties
jakarta/commons/sandbox/javaflow/trunk/project.properties
jakarta/commons/sandbox/pipeline/trunk/project.properties
jakarta/commons/sandbox/proxy/trunk/project.properties
jakarta/commons/sandbox/scxml/trunk/project.properties
jakarta/commons/trunks-sandbox/pom.xml

Modified: jakarta/commons/sandbox/compress/trunk/project.properties
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/sandbox/compress/trunk/project.properties?rev=377559&r1=377558&r2=377559&view=diff
==
--- jakarta/commons/sandbox/compress/trunk/project.properties (original)
+++ jakarta/commons/sandbox/compress/trunk/project.properties Mon Feb 13 
17:17:27 2006
@@ -21,6 +21,12 @@
 
 maven.checkstyle.properties = checkstyle.xml
 
+# Jar Manifest Additional Attributes
+maven.jar.manifest.attributes.list=Implementation-Vendor-Id,X-Compile-Source-JDK,X-Compile-Target-JDK
+maven.jar.manifest.attribute.Implementation-Vendor-Id=org.apache
+maven.jar.manifest.attribute.X-Compile-Source-JDK=${maven.compile.source}
+maven.jar.manifest.attribute.X-Compile-Target-JDK=${maven.compile.target}
+
 # uncomment the next line to work in offline mode (no jar download & no 
linkcheck)
 #maven.mode.online=
 maven.changelog.factory=org.apache.maven.svnlib.SvnChangeLogFactory

Modified: jakarta/commons/sandbox/csv/trunk/project.properties
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/sandbox/csv/trunk/project.properties?rev=377559&r1=377558&r2=377559&view=diff
==
--- jakarta/commons/sandbox/csv/trunk/project.properties (original)
+++ jakarta/commons/sandbox/csv/trunk/project.properties Mon Feb 13 17:17:27 
2006
@@ -19,6 +19,12 @@
 maven.xdoc.developmentProcessUrl=http://jakarta.apache.org/commons/charter.html
 maven.xdoc.includeProjectDocumentation=yes
 
+# Jar Manifest Additional Attributes
+maven.jar.manifest.attributes.list=Implementation-Vendor-Id,X-Compile-Source-JDK,X-Compile-Target-JDK
+maven.jar.manifest.attribute.Implementation-Vendor-Id=org.apache
+maven.jar.manifest.attribute.X-Compile-Source-JDK=${maven.compile.source}
+maven.jar.manifest.attribute.X-Compile-Target-JDK=${maven.compile.target}
+
 maven.checkstyle.properties = checkstyle.xml
 
 # uncomment the next line to work in offline mode (no jar download & no 
linkcheck)

Modified: jakarta/commons/sandbox/i18n/trunk/project.properties
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/sandbox/i18n/trunk/project.properties?rev=377559&r1=377558&r2=377559&view=diff
==
--- jakarta/commons/sandbox/i18n/trunk/project.properties (original)
+++ jakarta/commons/sandbox/i18n/trunk/project.properties Mon Feb 13 17:17:27 
2006
@@ -15,6 +15,12 @@
 maven.javadoc.author=false
 maven.javadoc.links=http://java.sun.com/j2se/1.4.2/docs/api
 
+# Jar Manifest Additional Attributes
+maven.jar.manifest.attributes.list=Implementation-Vendor-Id,X-Compile-Source-JDK,X-Compile-Target-JDK
+maven.jar.manifest.attribute.Implementation-Vendor-Id=org.apache
+maven.jar.manifest.attribute.X-Compile-Source-JDK=${maven.compile.source}
+maven.jar.manifest.attribute.X-Compile-Target-JDK=${maven.compile.target}
+
 maven.xdoc.jsl=../commons-build/commons-site.jsl
 maven.xdoc.date=bottom
 maven.xdoc.poweredby.image=maven-feather.png

Modified: jakarta/commons/sandbox/id/trunk/project.properties
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/sandbox/id/trunk/project.properties?rev=377559&r1=377558&r2=377559&view=diff
==
--- jakarta/commons/sandbox/id/trunk/project.properties (original)
+++ jakarta/commons/sandbox/id/trunk/proj

svn commit: r377558 - in /jakarta/commons/proper: attributes/trunk/ beanutils/trunk/ betwixt/trunk/ chain/trunk/ cli/trunk/ codec/trunk/ collections/trunk/ commons-build/trunk/xdocs/releases/ configur

[niallp]

Author: niallp
Date: Mon Feb 13 17:15:14 2006
New Revision: 377558

URL: http://svn.apache.org/viewcvs?rev=377558&view=rev
Log:
Modify maven build to add two non-standard attributes to the jar's manifest 
file to indicate the values of "maven.compile.source" and 
"maven.compile.target". Also modify the build to include an 
"Implementation-Vendor-Id" of "org.apache" in the jar's manifest.

The two non-standard entires created in the manifest file will look something 
like the following:

X-Compile-Source-JDK: 1.3
X-Compile-Target-JDK: 1.3

This change serves two purposes:

  1) To provide comfort to users regarding JVM compatibility.
  2) Enable releases to be checked more easily for JVM compatibility.

The manifest specification indicates that "unknown" entries in the manifest 
file are ignored. These entries have been prefixed with "X-" which is a 
sometimes used "convention" for indicating non-standard entries.

See thread: http://tinyurl.com/839zh

Modified:
jakarta/commons/proper/attributes/trunk/project.properties
jakarta/commons/proper/beanutils/trunk/project.properties
jakarta/commons/proper/betwixt/trunk/project.properties
jakarta/commons/proper/chain/trunk/project.properties
jakarta/commons/proper/cli/trunk/project.properties
jakarta/commons/proper/codec/trunk/project.properties
jakarta/commons/proper/collections/trunk/project.properties
jakarta/commons/proper/commons-build/trunk/xdocs/releases/prepare.xml
jakarta/commons/proper/configuration/trunk/project.properties
jakarta/commons/proper/daemon/trunk/project.properties
jakarta/commons/proper/dbcp/trunk/project.properties
jakarta/commons/proper/dbutils/trunk/project.properties
jakarta/commons/proper/digester/trunk/project.properties
jakarta/commons/proper/discovery/trunk/project.properties
jakarta/commons/proper/el/trunk/project.properties
jakarta/commons/proper/email/trunk/project.properties
jakarta/commons/proper/fileupload/trunk/project.properties
jakarta/commons/proper/httpclient/trunk/project.properties
jakarta/commons/proper/io/trunk/project.properties
jakarta/commons/proper/jelly/trunk/project.properties
jakarta/commons/proper/jexl/trunk/project.properties
jakarta/commons/proper/jxpath/trunk/project.properties
jakarta/commons/proper/lang/trunk/project.properties
jakarta/commons/proper/launcher/trunk/project.properties
jakarta/commons/proper/logging/trunk/project.properties
jakarta/commons/proper/math/trunk/project.properties
jakarta/commons/proper/modeler/trunk/project.properties
jakarta/commons/proper/net/trunk/project.properties
jakarta/commons/proper/pool/trunk/project.properties
jakarta/commons/proper/primitives/trunk/project.properties
jakarta/commons/proper/resources/trunk/project.properties
jakarta/commons/proper/transaction/trunk/project.properties
jakarta/commons/proper/validator/trunk/project.properties
jakarta/commons/proper/vfs/trunk/project.properties

Modified: jakarta/commons/proper/attributes/trunk/project.properties
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/attributes/trunk/project.properties?rev=377558&r1=377557&r2=377558&view=diff
==
--- jakarta/commons/proper/attributes/trunk/project.properties (original)
+++ jakarta/commons/proper/attributes/trunk/project.properties Mon Feb 13 
17:15:14 2006
@@ -18,7 +18,19 @@
 ##
 maven.changelog.factory=org.apache.maven.svnlib.SvnChangeLogFactory
 
+##
+# Specify the JVM version.
+##
+#maven.compile.source=
+#maven.compile.target=
 
+##
+# Jar Manifest Additional Attributes
+##
+maven.jar.manifest.attributes.list=Implementation-Vendor-Id,X-Compile-Source-JDK,X-Compile-Target-JDK
+maven.jar.manifest.attribute.Implementation-Vendor-Id=org.apache
+maven.jar.manifest.attribute.X-Compile-Source-JDK=${maven.compile.source}
+maven.jar.manifest.attribute.X-Compile-Target-JDK=${maven.compile.target}
 
 ##
 # Apache Central Repository

Modified: jakarta/commons/proper/beanutils/trunk/project.properties
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/beanutils/trunk/project.properties?rev=377558&r1=377557&r2=377558&view=diff
==
--- jakarta/commons/proper/beanutils/trunk/project.properties (original)
+++ jakarta/commons/proper/beanutils/trunk/project.properties Mon Feb 13 
17:15:14 2006
@@ -19,6 +19,16 @@
 maven.xdoc.developmentProcessUrl=http://jakarta.apache.org/commons/charter.html

DO NOT REPLY [Bug 32801] - [collections] Provide maps with direct indexed access to the entries

[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=32801





--- Additional Comments From [EMAIL PROTECTED]  2006-02-13 23:48 ---
(In reply to comment #0)
[SNIP]
> I created a sorted map, which uses array as a backend storage. I borrowed some
> internal implementation ideas from java.util.ArrayList, java.util.TreeMap and
> org.apache.commons.collections.map.AbstractHashedMap and LinkedMap.
> See attachment.
> I hope you will find the idea useful.

ugh... borrowing from java.util reads like IP issues to me.  I can see that this
might be useful to implement from scratch.  Probably not too hard to clone
ListOrderedMap -> IndexedSortedMap (probably not extend as things like put(int,
Object, Object) would violate the SortedMap contract); search for proper index
on insertion...

-- 
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]

svn commit: r377522 - /jakarta/commons/proper/logging/trunk/xdocs/troubleshooting.xml

[rdonkin]

Author: rdonkin
Date: Mon Feb 13 14:47:45 2006
New Revision: 377522

URL: http://svn.apache.org/viewcvs?rev=377522&view=rev
Log:
Fixed typo. Thanks to Simon Kitching.

Modified:
jakarta/commons/proper/logging/trunk/xdocs/troubleshooting.xml

Modified: jakarta/commons/proper/logging/trunk/xdocs/troubleshooting.xml
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/logging/trunk/xdocs/troubleshooting.xml?rev=377522&r1=377521&r2=377522&view=diff
==
--- jakarta/commons/proper/logging/trunk/xdocs/troubleshooting.xml (original)
+++ jakarta/commons/proper/logging/trunk/xdocs/troubleshooting.xml Mon Feb 13 
14:47:45 2006
@@ -75,7 +75,7 @@
 
   
 OIDs are intended to be used to cross-reference. They allow particular 
instances of classloaders
-and JCL classes to be tracked in different context's. This plays a vital role 
in building
+and JCL classes to be tracked in different contexts. This plays a vital role 
in building
 up the understanding of the classloader environment required to diagnose JCL 
problems. 

 



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

Re: [collections] Collections 3.2/4.0

[Stephen Colebourne]

Stephen Colebourne wrote:

Plan for collections 3.2

Agree contents
(notably, I'd like to remove BoundedBuffer)
Task complete. We'll include BoundedBuffer. I'd just like a little more 
javadoc, James?



Check bugs

Bugzilla shows no outstanding bugs that we can fix.


Build and release in single jar format

Any objections to this? Its well overdue.

Stephen

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

DO NOT REPLY [Bug 37473] - [collections] Implement a BoundedBuffer class

[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=37473





--- Additional Comments From [EMAIL PROTECTED]  2006-02-13 23:39 ---
James, can you add javadoc to explain what a zero or less timeout means. Also
can you add code to validate the max size parameter. Then, you can close this
call...

-- 
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]

svn commit: r377517 - in /jakarta/commons/proper/collections/trunk/src: java/org/apache/commons/collections/buffer/BoundedBuffer.java test/org/apache/commons/collections/buffer/TestAll.java test/org/a

[scolebourne]

Author: scolebourne
Date: Mon Feb 13 14:38:20 2006
New Revision: 377517

URL: http://svn.apache.org/viewcvs?rev=377517&view=rev
Log:
Implement BoundedCollection, Add javadoc
rfe 37473

Modified:

jakarta/commons/proper/collections/trunk/src/java/org/apache/commons/collections/buffer/BoundedBuffer.java
   (contents, props changed)

jakarta/commons/proper/collections/trunk/src/test/org/apache/commons/collections/buffer/TestAll.java

jakarta/commons/proper/collections/trunk/src/test/org/apache/commons/collections/buffer/TestBoundedBuffer.java

Modified: 
jakarta/commons/proper/collections/trunk/src/java/org/apache/commons/collections/buffer/BoundedBuffer.java
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/collections/trunk/src/java/org/apache/commons/collections/buffer/BoundedBuffer.java?rev=377517&r1=377516&r2=377517&view=diff
==
--- 
jakarta/commons/proper/collections/trunk/src/java/org/apache/commons/collections/buffer/BoundedBuffer.java
 (original)
+++ 
jakarta/commons/proper/collections/trunk/src/java/org/apache/commons/collections/buffer/BoundedBuffer.java
 Mon Feb 13 14:38:20 2006
@@ -1,5 +1,5 @@
 /*
- *  Copyright 2005 The Apache Software Foundation
+ *  Copyright 2005-2006 The Apache Software Foundation
  *
  *  Licensed under the Apache License, Version 2.0 (the "License");
  *  you may not use this file except in compliance with the License.
@@ -15,24 +15,33 @@
  */
 package org.apache.commons.collections.buffer;
 
-import org.apache.commons.collections.Buffer;
-import org.apache.commons.collections.BufferOverflowException;
-import org.apache.commons.collections.BufferUnderflowException;
-import org.apache.commons.collections.iterators.AbstractIteratorDecorator;
-
 import java.io.PrintWriter;
 import java.io.StringWriter;
 import java.util.Collection;
 import java.util.Iterator;
 
+import org.apache.commons.collections.BoundedCollection;
+import org.apache.commons.collections.Buffer;
+import org.apache.commons.collections.BufferOverflowException;
+import org.apache.commons.collections.BufferUnderflowException;
+import org.apache.commons.collections.iterators.AbstractIteratorDecorator;
+
 /**
- * A wrapper class for buffers which makes them bounded.
+ * Decorates another Buffer to ensure a fixed maximum size.
+ * 
+ * Note: This class should only be used if you need to add bounded
+ * behaviour to another buffer. If you just want a bounded buffer then
+ * you should use [EMAIL PROTECTED] BoundedFifoBuffer} or [EMAIL PROTECTED] 
CircularFifoBuffer}.
+ * 
+ * The decoration methods allow you to specify a timeout value, which
+ * causes the add methods to wait for up to the specified wait period.
  *
  * @author James Carman
- * @version $Revision: $ $Date: $
+ * @author Stephen Colebourne
+ * @version $Revision$ $Date$
  * @since Commons Collections 3.2
  */
-public class BoundedBuffer extends SynchronizedBuffer {
+public class BoundedBuffer extends SynchronizedBuffer implements 
BoundedCollection {
 
 /** The serialization version. */
 private static final long serialVersionUID = 1536432911093974264L;
@@ -132,6 +141,14 @@
 throw new BufferOverflowException("Timeout expired");
 }
 }
+}
+
+public boolean isFull() {
+return (collection.size() == maxSize());
+}
+
+public int maxSize() {
+return maximumSize;
 }
 
 //---

Propchange: 
jakarta/commons/proper/collections/trunk/src/java/org/apache/commons/collections/buffer/BoundedBuffer.java
--
--- svn:keywords (original)
+++ svn:keywords Mon Feb 13 14:38:20 2006
@@ -1 +1 @@
-Id
+Date Author Id Revision HeadURL

Modified: 
jakarta/commons/proper/collections/trunk/src/test/org/apache/commons/collections/buffer/TestAll.java
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/collections/trunk/src/test/org/apache/commons/collections/buffer/TestAll.java?rev=377517&r1=377516&r2=377517&view=diff
==
--- 
jakarta/commons/proper/collections/trunk/src/test/org/apache/commons/collections/buffer/TestAll.java
 (original)
+++ 
jakarta/commons/proper/collections/trunk/src/test/org/apache/commons/collections/buffer/TestAll.java
 Mon Feb 13 14:38:20 2006
@@ -1,5 +1,5 @@
 /*
- *  Copyright 2003-2004 The Apache Software Foundation
+ *  Copyright 2003-2004,2006 The Apache Software Foundation
  *
  *  Licensed under the Apache License, Version 2.0 (the "License");
  *  you may not use this file except in compliance with the License.
@@ -48,6 +48,7 @@
 suite.addTest(TestUnboundedFifoBuffer.suite());
 
 suite.addTest(TestBlockingBuffer.suite());
+suite.addTest(TestBoundedBuffer.suite());
 suite.addTest(TestPredicatedBuffer.suite());
 

DO NOT REPLY [Bug 38459] - [scxml] JUnit tests for SCXML

[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=38459





--- Additional Comments From [EMAIL PROTECTED]  2006-02-13 23:30 ---
Peter - Due to the larger scope of your comment #13, I've responded via the 
dev mailing list. You can find the post here:

http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=113986940520399&w=2

I think you're subscribed to the dev list (if not, please do, to catch such 
broader discussions).


-- 
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: [logging] r375631 - systemClassloaderTried patch

[robert burrell donkin]

On Mon, 2006-02-13 at 14:21 +1300, Simon Kitching wrote:
> Hi Robert,
> 
> I've had a look at this patch and it doesn't seem quite right to me.

i had the same feeling :)

but that might just be the specifications being unintuitive again...

> Presumably this is to handle the case where the system classloader is
> not in the chain leading from base classloader to boot classloader. This
> is a rather odd situation, but I guess that in the new principle of "try
> everything before failing" we could have a go with that when all else
> fails.

not quite

this patch is intended to address allowed variability in the classloader
class implementation noted in the javadocs for ClassLoader#getParent. it
is possible that some JRE implementations "may use null to represent the
bootstrap class loader. This method will return null in such
implementations if this class loader's parent is the bootstrap class
loader."  

the term bootstrap classloader is difficult. i suspect that this javadoc
is prior to the introduction of boot, extension and system classloaders.
i elected to assume that using the system classloader would usually be
good enough (providing that recursive loops are avoided) since i don't
know of any cross-JRE way of accessing the boot classloader. (if anyone
knows, please jump in :)

but it seems like a lot of complex code to address a risk something this
obscure...

> However this is currently hooked in to fire when parentCL is null, ie
> *before* we try the bootloader. I believe that in simple JVMs the
> bootloader IS also the system classloader. So I think it would be better
> as:
> 
> final ClassLoader systemCL = ClassLoader.getSystemClassLoader();
> boolean systemCLTried = false;
> for(;;) {
>   // checks as currently done
> 
>   if (currentCL == systemCL) {
> // the CL we just tested was the systemCL
> systemCLTried = true;
>   }
> 
>   if (currentCL == null) {
> if (systemCLTried == true) {
>   break;
> }
> 
> // We've walked up the CL tree, but never visited the systemCL.
> // Before giving up, let's try walking up from the system CL too..
> currentCL = systemCL;
>   } else {
> currentCL = currentCL.getParent();
>   }
> }
> 
> Thoughts?

this seems like a better formulation with equivalent effect.

i'd be equally happy to revert and go with just a dianostic message for
now, though.

- robert


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

Re: DO NOT REPLY [Bug 37979] - [collections] [PATCH] PredicateUtils.allPredicate() should not throw if 1 or 0 predicates

[Matt Benson]

--- [EMAIL PROTECTED] wrote:
[SNIP]
> 
> 
> --- Additional Comments From
> [EMAIL PROTECTED]  2006-02-13 23:14 ---
> Patch applied, thanks

thanks back, + thanks for the extra comments.  :)

-Matt


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

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

[SCXML] Status, todos (Was: [Bug 38459])

[Rahul Akolkar]

On 2/12/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:


Peter-

I am moving this to the dev list since your comment involves much more
than issue 38459 [1], and its probably useful to do a quick review of
the status of [scxml] here, rather than in Bugzilla.


>
> --- Additional Comments From [EMAIL PROTECTED]  2006-02-12 20:04 ---
> Rahul,
>
> What else needs to be tested, or what is the priority of testing you would 
> like
> done on this?


Thanks to the numerous test you've written over the last couple of
weeks, I think we are in fair shape as indicated by cobertura, most of
the classes which are doing poorly in terms of test coverage are in
the environment and test packages, which (one or more may apply):

1) Are harder to test as they possibly need a suite of
environment-specific mock objects
2) Have been tested indirectly via the usecases
3) Are simple environment specific wrappers or adapters that can scale
to visual inspection
4) Are command-line testing classes where it makes little sense to
write JUnit tests

For now, I was planning on focusing a bit more on tests that exercise
executions of state machines, for example:

a) Enhancing the couple of SCXMLExecutor tests for the microwave
samples -- see methods checkMicrowave{01,02}Sample() [2] -- to do much
more (add "time", "door_open", "door_close", "turn_on", "turn_off"
events and expected outcomes in various permutations)
b) Adding a few "stress tests" for the SCXMLExecutor class (along the
lines of comment #8 [3] for bug 38459).
c) Adding more "sample" SCXML documents, think of any state machine --
here is one suggestion we should author anyway [4] -- and write up a
test case that executes the document (ofcourse, with multiple
differing sequences of events and outcomes).


>  I was going to continue testing SCXMLSerializer, but if I
> remember correctly, you said that was going away or was being replaced by
> Digester.


By betwixt, possibly. But you're right, I wouldn't recommend spending
your cycles there for now.


>  Aside from testing, what are other features you would like people to
> work on?
>


Not meaning to sound clichéd, but for any Apache project, the short
answer always is - whatever takes your fancy.

With that disclaimer, the two "features" that are high priority are:

i) Tim O'Brien's suggestion of using betwixt [5] for SCXML IO. We
don't have to use betwixt, as long as we can explain why we aren't
using it ;-) And towards that end, this exploration needs to be done.

ii) Documentation. For example, issues 38274 [4], 38275 [6] and 38276
[7] need to be resolved and this wiki FAQ page [8] needs to be
populated. And then some more, if we get to that point ;-) I'll take
care of the questions on the wiki shortly, which might even give us
what we need for the web pages mentioned in issues 382{75,76}. A big
help would be to just proof-read (grammar, spelling) and do a
technical review of the Javadocs for the component [9]. Javadocs need
to be:
 * correct
 * concise
 * understandable and meaningful (to a benchmark Java developer that
uses Commons libraries)
 * adequately cross-referenced (for example, using @see tags)
Javadocs patches are therefore, welcome. Patches to the xdocs [10] are
also good help.

IMO, addressing these makes us ready to attempt sandbox graduation
again (the first vote, about a month ago, was unsuccessful). Anything
else beyond the two points above is a freebie at this point since
sandbox graduation is now overdue, in my strictly personal opinion.

Thanks for your interest, and for asking. Please feel free to add any
things that you'd like to see done.

-Rahul

[1]  http://issues.apache.org/bugzilla/show_bug.cgi?id=38459
[2]  
http://svn.apache.org/viewcvs.cgi/jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/SCXMLExecutorTest.java?view=markup
[3]  http://issues.apache.org/bugzilla/show_bug.cgi?id=38459#c8
[4]  http://issues.apache.org/bugzilla/show_bug.cgi?id=38274
[5]  http://jakarta.apache.org/commons/betwixt/
[6]  http://issues.apache.org/bugzilla/show_bug.cgi?id=38275
[7]  http://issues.apache.org/bugzilla/show_bug.cgi?id=38276
[8]  http://wiki.apache.org/jakarta-commons/SCXML/SCXMLFaq
[9]  http://jakarta.apache.org/commons/sandbox/scxml/apidocs/index.html
[10] 
http://svn.apache.org/viewcvs.cgi/jakarta/commons/sandbox/scxml/trunk/xdocs/


> Peter
>

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

DO NOT REPLY [Bug 37979] - [collections] [PATCH] PredicateUtils.allPredicate() should not throw if 1 or 0 predicates

[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=37979


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED




--- Additional Comments From [EMAIL PROTECTED]  2006-02-13 23:14 ---
Patch applied, thanks

-- 
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]

svn commit: r377508 - in /jakarta/commons/proper/collections/trunk: ./ src/java/org/apache/commons/collections/ src/java/org/apache/commons/collections/functors/ src/test/org/apache/commons/collection

[scolebourne]

Author: scolebourne
Date: Mon Feb 13 14:12:33 2006
New Revision: 377508

URL: http://svn.apache.org/viewcvs?rev=377508&view=rev
Log:
All/Any/One/None Predicate - allow construction with zero or one predicates
rfe 37979, implemented by Matt Benson

Modified:
jakarta/commons/proper/collections/trunk/RELEASE-NOTES.html

jakarta/commons/proper/collections/trunk/src/java/org/apache/commons/collections/PredicateUtils.java

jakarta/commons/proper/collections/trunk/src/java/org/apache/commons/collections/functors/AllPredicate.java

jakarta/commons/proper/collections/trunk/src/java/org/apache/commons/collections/functors/AnyPredicate.java

jakarta/commons/proper/collections/trunk/src/java/org/apache/commons/collections/functors/FunctorUtils.java

jakarta/commons/proper/collections/trunk/src/java/org/apache/commons/collections/functors/NonePredicate.java

jakarta/commons/proper/collections/trunk/src/java/org/apache/commons/collections/functors/OnePredicate.java

jakarta/commons/proper/collections/trunk/src/test/org/apache/commons/collections/TestPredicateUtils.java

Modified: jakarta/commons/proper/collections/trunk/RELEASE-NOTES.html
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/collections/trunk/RELEASE-NOTES.html?rev=377508&r1=377507&r2=377508&view=diff
==
--- jakarta/commons/proper/collections/trunk/RELEASE-NOTES.html (original)
+++ jakarta/commons/proper/collections/trunk/RELEASE-NOTES.html Mon Feb 13 
14:12:33 2006
@@ -80,6 +80,7 @@
 ListOrderedMap - additional method, put(int,Object,Object)
 PriorityBuffer - now Serializable [36163]
 IfClosure - add single argument constructor [38495]
+All/Any/One/None Predicate - allow construction with zero or one 
predicates [37979]
 
 
 BUG FIXES

Modified: 
jakarta/commons/proper/collections/trunk/src/java/org/apache/commons/collections/PredicateUtils.java
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/collections/trunk/src/java/org/apache/commons/collections/PredicateUtils.java?rev=377508&r1=377507&r2=377508&view=diff
==
--- 
jakarta/commons/proper/collections/trunk/src/java/org/apache/commons/collections/PredicateUtils.java
 (original)
+++ 
jakarta/commons/proper/collections/trunk/src/java/org/apache/commons/collections/PredicateUtils.java
 Mon Feb 13 14:12:33 2006
@@ -1,5 +1,5 @@
 /*
- *  Copyright 2002-2004 The Apache Software Foundation
+ *  Copyright 2002-2004,2006 The Apache Software Foundation
  *
  *  Licensed under the Apache License, Version 2.0 (the "License");
  *  you may not use this file except in compliance with the License.
@@ -264,13 +264,13 @@
 /**
  * Create a new Predicate that returns true only if all of the specified
  * predicates are true.
+ * If the array of predicates is empty, then this predicate returns true.
  * 
  * @see org.apache.commons.collections.functors.AllPredicate
  * 
  * @param predicates  an array of predicates to check, may not be null
  * @return the all predicate
  * @throws IllegalArgumentException if the predicates array is null
- * @throws IllegalArgumentException if the predicates array has less than 
2 elements
  * @throws IllegalArgumentException if any predicate in the array is null
  */
 public static Predicate allPredicate(Predicate[] predicates) {
@@ -280,13 +280,13 @@
 /**
  * Create a new Predicate that returns true only if all of the specified
  * predicates are true. The predicates are checked in iterator order.
+ * If the collection of predicates is empty, then this predicate returns 
true.
  * 
  * @see org.apache.commons.collections.functors.AllPredicate
  * 
  * @param predicates  a collection of predicates to check, may not be null
  * @return the all predicate
  * @throws IllegalArgumentException if the predicates collection is null
- * @throws IllegalArgumentException if the predicates collection has less 
than 2 elements
  * @throws IllegalArgumentException if any predicate in the collection is 
null
  */
 public static Predicate allPredicate(Collection predicates) {
@@ -311,13 +311,13 @@
 /**
  * Create a new Predicate that returns true if any of the specified
  * predicates are true.
+ * If the array of predicates is empty, then this predicate returns false.
  * 
  * @see org.apache.commons.collections.functors.AnyPredicate
  * 
  * @param predicates  an array of predicates to check, may not be null
  * @return the any predicate
  * @throws IllegalArgumentException if the predicates array is null
- * @throws IllegalArgumentException if the predicates array has less than 
2 elements
  * @throws IllegalArgumentException if any predicate in the array is null
  */
 public static Predicate anyPredicate(Predicate[] predicates) {
@@ -327,

Re: [pool] how about new release and incubating my composite pool implementation

[robert burrell donkin]

On Sun, 2006-02-12 at 17:35 -0500, Sandy McArthur wrote:
> On 2/9/06, robert burrell donkin <[EMAIL PROTECTED]> wrote:
> > i've checked the records and i can't see a software grant on record as
> > being received. so, you'll create a archive (tar or zip) of the source
> > which is to be donated to the ASF and create an MD5 for it. the software
> > grant should describe the donated software and refer to the sum. the
> > archive will be uploaded to an ASF server for the record. you'll need to
> > fax the grant to jim.
> 
> Fax sent 30 min ago.

great :)

the receipt notice hasn't been committed yet. jim last committed on the
10th (so there's nothing to be worried about yet). hopefully should be
in his next batch.

- robert


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

Re: [cli] Moving forward

[Michael Heuer]

Stephen Colebourne wrote:

> Henri Yandell wrote:
> > On the compatibility interface; I'd rather just drop it and spend that
> > effort on migration documentation. Does raise the question of whether
> > the cli2 package name ever becomes cli. Having it as cli2 does avoid
> > any surprises; things flat out won't work.
>
> Or [commons-commandline], a completely 'new' commons project.

+1

   michael


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

DO NOT REPLY [Bug 37484] - [logging] call to getClassLoader() in LogFactoryImpl not checked for null

[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=37484





--- Additional Comments From [EMAIL PROTECTED]  2006-02-13 22:46 ---
Sadly, there are no silver bullets.

It's very easy to complain but much more difficult to understand the problem in
detail. So, I should probably thank you know for being one of the tiny minority
who step up and help :)

JCL is incredibly widely used. This makes things very difficult. The issue for
JCL is (and has always been) that the J2EE classloading specifications are 
broken.

Static binding has it's own limitations. It also has it's own issues. The vast
majority of problems experienced by users are caused by having JCL jars in
different classloaders they are not aware of. Static binding will not solve this
problem.

Dynamic binding addresses application isolation in well behaved containers in a
fashion that is impossible for compile time static binding. Application
isolation should be possible by using byte code engineering to perform static
binding but that has it's own set of issues.

So, no silver bullets but maybe we can make things a little less painful...

-- 
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: [cli] Moving forward

[Stephen Colebourne]

Henri Yandell wrote:

On the compatibility interface; I'd rather just drop it and spend that
effort on migration documentation. Does raise the question of whether
the cli2 package name ever becomes cli. Having it as cli2 does avoid
any surprises; things flat out won't work.


Or [commons-commandline], a completely 'new' commons project.

Stephen

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

DO NOT REPLY [Bug 37979] - [collections] [PATCH] PredicateUtils.allPredicate() should not throw if 1 or 0 predicates

[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=37979


[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|[collections]   |[collections] [PATCH]
   |PredicateUtils.allPredicate(|PredicateUtils.allPredicate(
   |) should not throw if 1 or 0|) should not throw if 1 or 0
   |predicates  |predicates




--- Additional Comments From [EMAIL PROTECTED]  2006-02-13 19:02 ---
Patch added so this bug can either be fixed or rejected.  :)

-- 
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]

DO NOT REPLY [Bug 38634] - [net] UnixFTPEntryParser fails to parse Cygwin proftpd output when group names contain spaces

[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=38634





--- Additional Comments From [EMAIL PROTECTED]  2006-02-13 19:02 ---
Created an attachment (id=17679)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=17679&action=view)
Patch v1

This patch fixes the parsing issue for me with proftpd on Cygwin.  The group
name is recognized as "Domain Users" and all other fields appear to be
populated correctly.


-- 
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]

DO NOT REPLY [Bug 37979] - [collections] PredicateUtils.allPredicate() should not throw if 1 or 0 predicates

[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=37979





--- Additional Comments From [EMAIL PROTECTED]  2006-02-13 19:02 ---
Created an attachment (id=17678)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=17678&action=view)
patch to implement proposed changes


-- 
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]

DO NOT REPLY [Bug 38633] - [daemon] When changing UID in jsvc on fedora core 4, warning occurs: find_vma failed

[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=38633


[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|When changing UID in jsvc on|[daemon] When changing UID
   |fedora core 4, warning  |in jsvc on fedora core 4,
   |occurs: find_vma failed |warning occurs: find_vma
   ||failed




-- 
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]

DO NOT REPLY [Bug 38634] - [net] UnixFTPEntryParser fails to parse Cygwin proftpd output when group names contain spaces

[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=38634


[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|UnixFTPEntryParser fails to |[net] UnixFTPEntryParser
   |parse Cygwin proftpd output |fails to parse Cygwin
   |when group names contain|proftpd output when group
   |spaces  |names contain spaces




-- 
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]

DO NOT REPLY [Bug 38634] - UnixFTPEntryParser fails to parse Cygwin proftpd output when group names contain spaces

[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=38634





--- Additional Comments From [EMAIL PROTECTED]  2006-02-13 18:48 ---
Note that this issue was found on commons-net-1.4.1.


-- 
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]

DO NOT REPLY [Bug 38634] New: - UnixFTPEntryParser fails to parse Cygwin proftpd output when group names contain spaces

[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=38634

   Summary: UnixFTPEntryParser fails to parse Cygwin proftpd output
when group names contain spaces
   Product: Commons
   Version: unspecified
  Platform: PC
OS/Version: Windows XP
Status: NEW
  Severity: normal
  Priority: P2
 Component: Net
AssignedTo: commons-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]


Running proftpd under Cygwin on Windows XP reports itself as UNIX-type server
using the "system" command:

ftp> system
215 UNIX Type: L8

Unfortunately Windows allows spaces in group names, so UnixFTPEntryParser fails
to parse directory output like the following:

ftp> dir
200 PORT command successful
150 Opening ASCII mode data connection for file list
-rw-r--r--   1 dkilzer  Domain Users0 Feb 13 17:20 foo.001
-rw-r--r--   1 dkilzer  Domain Users0 Feb 13 17:35 foo.002
226 Transfer complete.

The expected behavior is that it will find two files listed.

The actual behavior is that it reports no files in the directory.

-- 
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]

DO NOT REPLY [Bug 38633] New: - When changing UID in jsvc on fedora core 4, warning occurs: find_vma failed

[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=38633

   Summary: When changing UID in jsvc on fedora core 4, warning
occurs: find_vma failed
   Product: Commons
   Version: unspecified
  Platform: PC
OS/Version: Linux
Status: NEW
  Keywords: ErrorMessage
  Severity: normal
  Priority: P2
 Component: Daemon
AssignedTo: commons-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]


Greetings List.

I have searched a lot for information about this Warning I am getting when I
start up tomcat by using jsvc on my Fedora Core 4 platform, but I have not been
able to find anything that helped me solve my problem. So now I am reporting it
here.

I am using the Tomcat5.sh script supplied in the native folder.

I have tried 2 different scenarios:

1. running jsvc with "-user tomcat"
2. ommitting the -user option entirely (running it as root)

In scenario 1 I get the warning:
"Java HotSpot(TM) Server VM warning: Can't detect initial thread stack location
- find_vma failed"   (same message if I use the Client VM).

I do not get this warning in scenario 2.

If I use the script "catalina.sh" as the user tomcat I can start up the
webserver fine without warnings (though not on port 80 naturally).

System is Fedora Cora 4
Tomcat is the the apache-tomcat-5.5.15.tar.gz
JDK/JRE is Suns jdk 1.5.0_06 for linux (rpm distribution)
(note I dont have any other java distributions installed, so fedora RPM name
clashes is not an issue)

-- 
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]

DO NOT REPLY [Bug 37979] - [collections] PredicateUtils.allPredicate() should not throw if 1 or 0 predicates

[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=37979


[EMAIL PROTECTED] changed:

   What|Removed |Added

Version|3.2 |3.1




--- Additional Comments From [EMAIL PROTECTED]  2006-02-13 18:04 ---
Of course, the workaround is to use the predicate classes' constructors
directly.  Also marking this as against 3.1 .

-- 
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]

DO NOT REPLY [Bug 36397] - [configuration] Conditional directives in property files

[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=36397


[EMAIL PROTECTED] changed:

   What|Removed |Added

   Keywords||PatchAvailable
Summary|[configuration][PATCH]  |[configuration] Conditional
   |conditional directives in   |directives in property files
   |property files  |




-- 
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]

DO NOT REPLY [Bug 37979] - [collections] PredicateUtils.allPredicate() should not throw if 1 or 0 predicates

[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=37979


[EMAIL PROTECTED] changed:

   What|Removed |Added

   Severity|normal  |enhancement




--- Additional Comments From [EMAIL PROTECTED]  2006-02-13 17:25 ---
Since the limitations are documented on the classes e.g.
org.apache.commons.collections.functors.AllPredicate I would call this an RFE. 
Semantics at work; I tend to agree with most of the logic presented here,
however, and with the assertion that since exceptions are currently thrown these
changes would effectively be BC.

-- 
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]

DO NOT REPLY [Bug 37608] - [collections] Implement an IndexTransformer Class

[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=37608


[EMAIL PROTECTED] changed:

   What|Removed |Added

   Severity|normal  |enhancement
Version|3.2 |3.1




--- Additional Comments From [EMAIL PROTECTED]  2006-02-13 17:15 ---
I call this an enhancement, and change to 3.1 since 3.2 is unreleased.

-- 
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]

DO NOT REPLY [Bug 37473] - [collections] Implement a BoundedBuffer class

[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=37473


[EMAIL PROTECTED] changed:

   What|Removed |Added

   Severity|normal  |enhancement




--- Additional Comments From [EMAIL PROTECTED]  2006-02-13 17:12 ---
You guys are currently arguing about this one, so the issue is still "open." 
For my non-binding 2c I don't see the harm in allowing the wrapper to remain;
any efficiency issues could be noted in the javadoc.  But either way I would
call it an enhancement rather than a "normal" severity bug.

-- 
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: [cli] Moving forward

[sebb]

The repository also contains a version of Avalon Excalibur CLI (as
used in JMeter).

There were some bugs in the Avalon code, and there did not seem to be
any likelihood of any fixes, so we imported the source into JMeter,
and fixed the bugs (and test cases).

Just in case someone else might find it useful, the code was copied to
the CLI repository - see:
http://issues.apache.org/bugzilla/show_bug.cgi?id=34672 for the
contribution.

It would be nice if there could be a release of this - we could import
the jar and drop the source from JMeter.

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

[Jakarta-commons Wiki] Update of "VfsFaq" by MarioIvankovits

[Apache Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jakarta-commons Wiki" 
for change notification.

The following page has been changed by MarioIvankovits:
http://wiki.apache.org/jakarta-commons/VfsFaq

--
  FileObject fo = VFS.getManager().resolveFile("ftp://host/path_to/file.txt";, 
opts);
  }}}
  
+ == How to use the org.apache.commons.vfs.FileSelector or 
org.apache.commons.vfs.FileFilter ==
+ 
+ The FileFilter can be used to mimic the java.io.FileFilter interface.
+ 
+ {{{
+ FileFilter ff = new FileFilter()
+ {
+ public boolean accept(FileSelectInfo fileInfo)
+ {
+ FileObject fo = fileInfo.getFile();
+ return fo.getName().getBaseName().startsWith("ABC-");
+ }
+   
+ };
+ VFS.getManager().resolveFile("/base/folder").findFiles(new 
FileFilterSelector(ff));
+ }}}
+ 
+ You should consider using the more VFS native 
org.apache.commons.vfs.FileSelector interface as this allows you to 
automatically traverse recursive.
+ 
+ Available FileSelectors:
+  * AllFileSelector - select all files
+  * FileDepthSelector - select files at a given depth range
+  * FileTypeSelector - select files by type (file, folder)
+ 
+ So the following will be the same as above, but will scan the whole tree 
starting at the base folder.
+ 
+ {{{
+ FileSelector ff = new FileSelector()
+ {
+ public boolean includeFile(FileSelectInfo fileInfo) throws Exception
+ {
+ FileObject fo = fileInfo.getFile();
+ return fo.getName().getBaseName().startsWith("ABC-");
+ }
+ 
+ public boolean traverseDescendents(FileSelectInfo fileInfo) throws 
Exception
+ {
+ return true;
+ } 
+ };
+ VFS.getManager().resolveFile("/base/folder").findFiles(ff);
+ }}}
+ 

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

Re: [cli] Moving forward

[Henri Yandell]

On 2/13/06, Torsten Curdt <[EMAIL PROTECTED]> wrote:
> >
> > This is a tough question. There has already been a release of CLI
> > which did
> > not include the CLI2 API, and there are doubtless users of CLI out
> > there who
> > will not be interested in migrating to the CLI2.
>
> for sure
>
> >
> > However, CLI2 has the idea of argument validators, and I think
> > that's quite a
> > handy feature of the API.
>
> yepp +1
>
> >
> >> We do need to agree that cli2 is the way forward, comparing the APIs
> >> to see if it feels better is one of my todo's. What do the rest of
> >> you
> >> think? Martin/James/anyone else?
> >
> > I think you're right, we do need to compare the two APIs to make a
> > rational
> > decision. Maybe there's some scope for maintaining the current CLI
> > API while
> > merging in some of the nice validation stuff from CLI2? Whatever
> > the choice,
> > we should at least maintain a compatibility interface with this API
> > so that
> > users only have to change their code if they want to use the nice
> > parts of
> > CLI2.
>
> TBH cli1 has lived for sooo long without further releases
> why not only put it into bug fix mode and other than that
> move forward. The old jars won't go away.

+1. If we branch off a 1.x branch; it'll be releasable if people
clamour. Plus we can keep applying patches when applied; however there
will be a whole bunch of bugs that will just get marked as WONTFIX
beause the solution is to rewrite cli1.

On the compatibility interface; I'd rather just drop it and spend that
effort on migration documentation. Does raise the question of whether
the cli2 package name ever becomes cli. Having it as cli2 does avoid
any surprises; things flat out won't work.

Hen

-
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

[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 54 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.4/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-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/dynabean/target/commons-jelly-tags-dynabean-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-13022006.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] Feb 13, 2006 4:49:58 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

[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 54 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.4/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-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/dynabean/target/commons-jelly-tags-dynabean-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-13022006.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] Feb 13, 2006 4:49:58 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-jsl-test (in module commons-jelly) failed

[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 54 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: 16 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl]
CLASSPATH: 
/opt/jdk1.4/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-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-13022006.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:58)
[junit] at org.dom4j.rule.Mode.applyTemplates(Mode.java:79)
[junit] at org.dom4j.rule.RuleManager$1.run(RuleManager.java:171)
[junit] at org.dom4j.rule.Mode.fireRule(Mode.java:58)
[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

[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 54 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: 16 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl]
CLASSPATH: 
/opt/jdk1.4/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-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-13022006.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:58)
[junit] at org.dom4j.rule.Mode.applyTemplates(Mode.java:79)
[junit] at org.dom4j.rule.RuleManager$1.run(RuleManager.java:171)
[junit] at org.dom4j.rule.Mode.fireRule(Mode.java:58)
[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

[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 54 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-13022006.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.4/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-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/commons-jelly-tags-jsl-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-13022006.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

[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 54 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-13022006.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.4/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-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/commons-jelly-tags-jsl-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-13022006.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-latka (in module jakarta-commons) failed

[Ted Husted]

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-latka has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 19 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-latka :  Functional Testing Suite


Full details are available at:

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

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-latka.jar] identifier set to project name
 -DEBUG- Dependency on jaxen exists, no need to add for property jaxen.jar.
 -INFO- Made directory 
[/usr/local/gump/public/workspace/jakarta-commons/latka/target/classes]
 -INFO- Made directory 
[/usr/local/gump/public/workspace/jakarta-commons/latka/target/test-classes]
 -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-latka/gump_work/build_jakarta-commons_commons-latka.html
Work Name: build_jakarta-commons_commons-latka (Type: Build)
Work ended in a state of : Failed
Elapsed: 8 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:/usr/local/gump/public/workspace/xml-xalan/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar
 org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only 
-Djaxen.jar=/usr/local/gump/public/workspace/jaxen/target/jaxen-13022006.jar 
dist 
[Working Directory: /usr/local/gump/public/workspace/jakarta-commons/latka]
CLASSPATH: 
/opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/latka/target/classes:/usr/local/gump/public/workspace/jakarta-commons/latka/target/test-classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/jakarta-commons/httpclient/dist/commons-httpclient.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/codec/dist/commons-codec-13022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-13022006.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-13022006.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13022006.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-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-13022006.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-13022006.jar
-
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.725 sec
[junit] - Standard Output ---
[junit] log4j:INFO Using URL 
[file:/x1/gump/public/workspace/jakarta-commons/latka/target/classes/log4j.properties]
 for automatic log4j configuration of repository named [default].
[junit] ESE

[junit] [message] boo1

[junit] http://example.net:80/
[junit]   REQUEST ERROR (-1 millis)
[junit] java.net.ConnectException: Connection refused

[junit] [message] boo2

[junit] http://example.org:80/
[junit]   REQUEST SKIPPED (-1 millis)

[junit] [message] boo3

[junit] http://example.net:80/
[junit]   REQUEST ERROR (-1 millis)
[junit] java.net.ConnectException: Connection refused


[junit] SUITE FAILED
[juni

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

[Ted Husted]

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-latka has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 19 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-latka :  Functional Testing Suite


Full details are available at:

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

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-latka.jar] identifier set to project name
 -DEBUG- Dependency on jaxen exists, no need to add for property jaxen.jar.
 -INFO- Made directory 
[/usr/local/gump/public/workspace/jakarta-commons/latka/target/classes]
 -INFO- Made directory 
[/usr/local/gump/public/workspace/jakarta-commons/latka/target/test-classes]
 -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-latka/gump_work/build_jakarta-commons_commons-latka.html
Work Name: build_jakarta-commons_commons-latka (Type: Build)
Work ended in a state of : Failed
Elapsed: 8 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:/usr/local/gump/public/workspace/xml-xalan/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar
 org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only 
-Djaxen.jar=/usr/local/gump/public/workspace/jaxen/target/jaxen-13022006.jar 
dist 
[Working Directory: /usr/local/gump/public/workspace/jakarta-commons/latka]
CLASSPATH: 
/opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/latka/target/classes:/usr/local/gump/public/workspace/jakarta-commons/latka/target/test-classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/jakarta-commons/httpclient/dist/commons-httpclient.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/codec/dist/commons-codec-13022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-13022006.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-13022006.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13022006.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-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-13022006.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-13022006.jar
-
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.725 sec
[junit] - Standard Output ---
[junit] log4j:INFO Using URL 
[file:/x1/gump/public/workspace/jakarta-commons/latka/target/classes/log4j.properties]
 for automatic log4j configuration of repository named [default].
[junit] ESE

[junit] [message] boo1

[junit] http://example.net:80/
[junit]   REQUEST ERROR (-1 millis)
[junit] java.net.ConnectException: Connection refused

[junit] [message] boo2

[junit] http://example.org:80/
[junit]   REQUEST SKIPPED (-1 millis)

[junit] [message] boo3

[junit] http://example.net:80/
[junit]   REQUEST ERROR (-1 millis)
[junit] java.net.ConnectException: Connection refused


[junit] SUITE FAILED
[juni

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

[JellySwing 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-swing has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 54 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-swing :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-swing/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-swing-13022006.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/swing/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/target/test-reports
 -WARNING- No directory 
[/usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/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-swing/gump_work/build_commons-jelly_commons-jelly-tags-swing.html
Work Name: build_commons-jelly_commons-jelly-tags-swing (Type: Build)
Work ended in a state of : Failed
Elapsed: 3 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing]
CLASSPATH: 
/opt/jdk1.4/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-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/target/commons-jelly-tags-define-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/interaction/target/commons-jelly-tags-interaction-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-13022006.jar:/usr/local/gump/public/workspace/jline/release/jline.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
-
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at 
org.apache.commons.jelly.JellyContext.getTagLibrary(JellyContext.java:432)
at 
org.apache.maven.jelly.MavenJellyContext.getTagLibrary(MavenJellyContext.java:171)
at 
org.apache.commons.jelly.parser.XMLParser.createTag(XMLParser.java:1033)
at 
org.apache.commons.jelly.parser.XMLParser.startElement(XMLParser.java:647)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown 
Source)
at 
org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
at 
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
 Source)
at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown 
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)

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

[JellySwing 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-swing has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 54 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-swing :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-swing/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-swing-13022006.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/swing/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/target/test-reports
 -WARNING- No directory 
[/usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/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-swing/gump_work/build_commons-jelly_commons-jelly-tags-swing.html
Work Name: build_commons-jelly_commons-jelly-tags-swing (Type: Build)
Work ended in a state of : Failed
Elapsed: 3 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing]
CLASSPATH: 
/opt/jdk1.4/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-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/target/commons-jelly-tags-define-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/interaction/target/commons-jelly-tags-interaction-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-13022006.jar:/usr/local/gump/public/workspace/jline/release/jline.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
-
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at 
org.apache.commons.jelly.JellyContext.getTagLibrary(JellyContext.java:432)
at 
org.apache.maven.jelly.MavenJellyContext.getTagLibrary(MavenJellyContext.java:171)
at 
org.apache.commons.jelly.parser.XMLParser.createTag(XMLParser.java:1033)
at 
org.apache.commons.jelly.parser.XMLParser.startElement(XMLParser.java:647)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown 
Source)
at 
org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
at 
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
 Source)
at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown 
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)

DO NOT REPLY [Bug 36844] - [email] Embedding raw DataSource Attachments

[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=36844





--- Additional Comments From [EMAIL PROTECTED]  2006-02-13 12:58 ---
(In reply to comment #2)
> This requires an extra dependency on commons-lang which I'd prefer not to 
> have,
> if possible.
> 
> Got another simpler way of getting the cid?

You can use EmailUtils.randomAlphabetic() to get what you are looking for.


-- 
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]

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

[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 54 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: 28 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml]
CLASSPATH: 
/opt/jdk1.4/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-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-13022006.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.tags.junit.CaseTag$1.runTest(CaseTag.java:59)
[junit] 
[junit] 
[junit] Testcase: 
testSetSingleNodeAndAsString(org.apache.commons.jelly.tags.junit.CaseTag$1):
  Caused an ERROR
[junit] 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:294:81:
  You must define an attribute called 'select' for this tag.
[junit] org.apache.commons.jelly.MissingAttributeException: 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:294:81:
  You must define an attribute called 'select' for this tag.
[junit] at 
org.apache.commons.jelly.tags.xml.SetTag.doTag(SetTag.java:86)
[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: 
testSetStringLists(org.apache.commons.jelly.tags.junit.CaseTag$1):
Caused an ERROR
[junit] 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:339:82:
  You must define an attribute called 'select' for this tag.
[junit] org.apache.commons.jelly.MissingAttributeException: 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:339:82:
  You must define an attribute called 'select' for this tag.
[junit] at 
org.apache.commons.jelly.tags.xml.SetTag.doTag(SetTag.java:86)
[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: 
testEntities(org.apache.commons.jelly.tags.junit.CaseTag$1):  Caused an 
ERROR
[junit] 
file:/x1/gump/public/workspace/

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

[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 54 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: 28 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml]
CLASSPATH: 
/opt/jdk1.4/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-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13022006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-13022006.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.tags.junit.CaseTag$1.runTest(CaseTag.java:59)
[junit] 
[junit] 
[junit] Testcase: 
testSetSingleNodeAndAsString(org.apache.commons.jelly.tags.junit.CaseTag$1):
  Caused an ERROR
[junit] 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:294:81:
  You must define an attribute called 'select' for this tag.
[junit] org.apache.commons.jelly.MissingAttributeException: 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:294:81:
  You must define an attribute called 'select' for this tag.
[junit] at 
org.apache.commons.jelly.tags.xml.SetTag.doTag(SetTag.java:86)
[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: 
testSetStringLists(org.apache.commons.jelly.tags.junit.CaseTag$1):
Caused an ERROR
[junit] 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:339:82:
  You must define an attribute called 'select' for this tag.
[junit] org.apache.commons.jelly.MissingAttributeException: 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:339:82:
  You must define an attribute called 'select' for this tag.
[junit] at 
org.apache.commons.jelly.tags.xml.SetTag.doTag(SetTag.java:86)
[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: 
testEntities(org.apache.commons.jelly.tags.junit.CaseTag$1):  Caused an 
ERROR
[junit] 
file:/x1/gump/public/workspace/

DO NOT REPLY [Bug 38626] - [logging] LogFactory#getLogFactory should not look for method every time

[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=38626


[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|LogFactory#getLogFactory|[logging]
   |should not look for method  |LogFactory#getLogFactory
   |every time  |should not look for method
   ||every time




-- 
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]

DO NOT REPLY [Bug 38623] - [fileupload] Efficient upload stream reading API

[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=38623


[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|Efficient upload stream |[fileupload] Efficient
   |reading API |upload stream reading API




-- 
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]

DO NOT REPLY [Bug 38614] - [dbcp] allow to set >= 6 parameters to do non-global SSL

[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=38614


[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|allow to set >= 6 parameters|[dbcp] allow to set >= 6
   |to do non-global SSL|parameters to do non-global
   ||SSL




-- 
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]

DO NOT REPLY [Bug 38625] - [pool] GenericObjectPool currently in SVN isn't Java 1.3 compatible because of one line

[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=38625


[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|[pool] GenericObjectPool|[pool] GenericObjectPool
   |currently in SVN isn't Java |currently in SVN isn't Java
   |1.3 compatabile because of  |1.3 compatible because of
   |one line|one line




-- 
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]

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

[commons-jelly 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-test has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 54 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-test :  Commons Jelly


Full details are available at:

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

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on jakarta-servletapi-5-servlet exists, no need to add for 
property maven.jar.servletapi.
 -DEBUG- Dependency on jakarta-taglibs-standard exists, no need to add for 
property maven.jar.jstl.
 -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/build.properties]
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-test/gump_work/build_commons-jelly_commons-jelly-test.html
Work Name: build_commons-jelly_commons-jelly-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 55 secs
Command Line: maven --offline jar 
[Working Directory: /usr/local/gump/public/workspace/commons-jelly]
CLASSPATH: 
/opt/jdk1.4/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-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/discovery/dist/commons-discovery.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-13022006.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/forehead/forehead-1.0-beta-5.jar:/usr/local/gump/public/workspace/jakarta-servletapi-5/jsr154/dist/lib/servlet-api.jar:/usr/local/gump/public/workspace/jakarta-taglibs/dist/standard/lib/jstl.jar:/usr/local/gump/packages/jaxen-1.1-beta-4/jaxen-1.1-beta-4.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar
-
[junit] Expected expression: ${singleSize*2}
[junit] Actual expression: ${doubleSize} File: 
file:/x1/gump/public/workspace/commons-jelly/target/test-classes/org/apache/commons/jelly/suite.jelly
 At tag : line: 359 column: 75
[junit] org.apache.commons.jelly.JellyTagException: 
file:/x1/gump/public/workspace/commons-jelly/target/test-classes/org/apache/commons/jelly/suite.jelly:359:75:
   expected:[22] but was:[22]
[junit] Expected expression: ${singleSize*2}
[junit] Actual expression: ${doubleSize} File: 
file:/x1/gump/public/workspace/commons-jelly/target/test-classes/org/apache/commons/jelly/suite.jelly
 At tag : line: 359 column: 75
[junit] at 
org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:712)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:282)
[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] Caused by: 
org.apache.commons.jelly.tags.junit.JellyAssertionFailedError:  expected:[22] 
but was:[22]
[junit] Expected expression: ${singleSize*2}
[junit] Actual expression: ${doubleSize} File: 
file:/x1/gump/public/workspace/commons-jelly/target/test-classes/org/apache/commons/jelly/suite.jelly
 At tag : line: 359 column: 75
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:39)
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTagSupport.failNotEquals(AssertTagSupport.java:62)
[junit] at 
org.apache.commons.jelly.tags.junit.AssertEqualsTag.doTag(AssertEqualsTag.java:55)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262

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

[commons-jelly 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-test has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 54 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-test :  Commons Jelly


Full details are available at:

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

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on jakarta-servletapi-5-servlet exists, no need to add for 
property maven.jar.servletapi.
 -DEBUG- Dependency on jakarta-taglibs-standard exists, no need to add for 
property maven.jar.jstl.
 -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/build.properties]
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-test/gump_work/build_commons-jelly_commons-jelly-test.html
Work Name: build_commons-jelly_commons-jelly-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 55 secs
Command Line: maven --offline jar 
[Working Directory: /usr/local/gump/public/workspace/commons-jelly]
CLASSPATH: 
/opt/jdk1.4/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-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/discovery/dist/commons-discovery.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-13022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-13022006.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/forehead/forehead-1.0-beta-5.jar:/usr/local/gump/public/workspace/jakarta-servletapi-5/jsr154/dist/lib/servlet-api.jar:/usr/local/gump/public/workspace/jakarta-taglibs/dist/standard/lib/jstl.jar:/usr/local/gump/packages/jaxen-1.1-beta-4/jaxen-1.1-beta-4.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar
-
[junit] Expected expression: ${singleSize*2}
[junit] Actual expression: ${doubleSize} File: 
file:/x1/gump/public/workspace/commons-jelly/target/test-classes/org/apache/commons/jelly/suite.jelly
 At tag : line: 359 column: 75
[junit] org.apache.commons.jelly.JellyTagException: 
file:/x1/gump/public/workspace/commons-jelly/target/test-classes/org/apache/commons/jelly/suite.jelly:359:75:
   expected:[22] but was:[22]
[junit] Expected expression: ${singleSize*2}
[junit] Actual expression: ${doubleSize} File: 
file:/x1/gump/public/workspace/commons-jelly/target/test-classes/org/apache/commons/jelly/suite.jelly
 At tag : line: 359 column: 75
[junit] at 
org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:712)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:282)
[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] Caused by: 
org.apache.commons.jelly.tags.junit.JellyAssertionFailedError:  expected:[22] 
but was:[22]
[junit] Expected expression: ${singleSize*2}
[junit] Actual expression: ${doubleSize} File: 
file:/x1/gump/public/workspace/commons-jelly/target/test-classes/org/apache/commons/jelly/suite.jelly
 At tag : line: 359 column: 75
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:39)
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTagSupport.failNotEquals(AssertTagSupport.java:62)
[junit] at 
org.apache.commons.jelly.tags.junit.AssertEqualsTag.doTag(AssertEqualsTag.java:55)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262

DO NOT REPLY [Bug 38611] - [cli][PATCH] HelpFormatter shouldn't throw IOException

[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=38611





--- Additional Comments From [EMAIL PROTECTED]  2006-02-13 12:14 ---
Created an attachment (id=17677)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=17677&action=view)
Patch to remove throws IOException clauses

This updated patch does not change the access modifier for the method
printWrapped, but it does eliminate all mention of IOExceptions thrown by
methods of this class. I think this is definitely a worthwhile patch.

Thanks!

-- 
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]

DO NOT REPLY [Bug 38611] - [cli][PATCH] HelpFormatter shouldn't throw IOException

[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=38611


[EMAIL PROTECTED] changed:

   What|Removed |Added

  Attachment #17645|0   |1
is obsolete||




--- Additional Comments From [EMAIL PROTECTED]  2006-02-13 12:12 ---
(From update of attachment 17645)
Obsoleted by subsequent patch.


-- 
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: [jelly] Gump failures

[Dion Gillard]

I'm pretty sure this has to do with recent changes in Jexl to 'narrow'
results to make introspection easier.

Before all integer results were stored in a long. Now they're stored
as Byte, Short, Long etc.

On 2/13/06, Paul Libbrecht <[EMAIL PROTECTED]> wrote:
> But remember this is only part of the problem.
> The jelly-test failure is related to expression-equality in jexl where:
>
> [junit] Expected expression: ${singleSize*2}
> [junit] Actual expression: ${doubleSize} File:
>
> fails because, I think so said Dion, of primitive-types incorrect
> comparison in jexl or jelly's packing of jexl.
> DIdn't have the time to dive for it yet...
>
> paul
>
> Brett Porter wrote:
> > I think this could be "solved" by setting it to use jaxen-1.1-beta-4
> > instead. I'll try that now. If I can't get it fixed by the end of the
> > week, I'll turn them off.
> >
> > I still believe that someone with spare time needs to get Jelly working
> > with newer versions of Jaxen. Being stuck on beta-4 is not very
> > desirable, and it appears they are never going to restore backwards
> > compatibility as it was a deliberate breakage. I'm not that person (I
> > have neither the xpath knowledge or spare time or need to use Jelly any
> > more :)
> >
> > - Brett
> >
> > Bill Barker wrote:
> >
> >>> "Henri Yandell" <[EMAIL PROTECTED]> wrote in message
> >>> news:[EMAIL PROTECTED]
> >>> *ping*
> >>>
> >>> Waking this thread up again. While it's bad for us to go "Jelly HEAD +
> >>> Jaxen HEAD -> can't work so turn off the build", it's much worse for
> >>> us to let the noise continue as that switches people off of paying
> >>> attention to the gump errors. It becomes background noise.
> >>>
> >> Actually, from the Gump page it's using jaxen-1.1b6 (Jaxen HEAD wasn't
> >> building for a long time, so a lot of projects got switched to a packaged
> >> version).
> >>
> >>
> >>> Of course this might be interpreted as a feature request for gump;
> >>> don't irritate us by repeating yourself, instead just send us a
> >>> summary every now and then of the ones that are long term issues.
> >>>
> >>>
> >> Development on Gump is sort of slow right now.  Unless somebody wants to
> >> step up with a patch, it may not happen anytime soon ;-).
> >>
> >>
> >>> Still, +1 to any idea that gets rid of the background noise.
> >>>
> >>>
> >> The Jelly projects that are failing are basically the unit tests (this is
> >> also true for tags-html, the error for tags-swing is just wierd :).  If
> >> nobody care about the tests, you could just get rid of those s
> >> in the jakarta-commons-jelly.xml file.
> >>
> >>
> >>> Hen
> >>>
> >>>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
http://www.multitask.com.au/people/dion/
"If I close my eyes it doesn't seem so dark." - SpongeBob SquarePants

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

Re: [jelly] Gump failures

[Paul Libbrecht]

But remember this is only part of the problem.
The jelly-test failure is related to expression-equality in jexl where:

   [junit] Expected expression: ${singleSize*2}
   [junit] Actual expression: ${doubleSize} File: 

fails because, I think so said Dion, of primitive-types incorrect 
comparison in jexl or jelly's packing of jexl.

DIdn't have the time to dive for it yet...

paul

Brett Porter wrote:

I think this could be "solved" by setting it to use jaxen-1.1-beta-4
instead. I'll try that now. If I can't get it fixed by the end of the
week, I'll turn them off.

I still believe that someone with spare time needs to get Jelly working
with newer versions of Jaxen. Being stuck on beta-4 is not very
desirable, and it appears they are never going to restore backwards
compatibility as it was a deliberate breakage. I'm not that person (I
have neither the xpath knowledge or spare time or need to use Jelly any
more :)

- Brett

Bill Barker wrote:
  
"Henri Yandell" <[EMAIL PROTECTED]> wrote in message 
news:[EMAIL PROTECTED]

*ping*

Waking this thread up again. While it's bad for us to go "Jelly HEAD +
Jaxen HEAD -> can't work so turn off the build", it's much worse for
us to let the noise continue as that switches people off of paying
attention to the gump errors. It becomes background noise.
  
Actually, from the Gump page it's using jaxen-1.1b6 (Jaxen HEAD wasn't 
building for a long time, so a lot of projects got switched to a packaged 
version).




Of course this might be interpreted as a feature request for gump;
don't irritate us by repeating yourself, instead just send us a
summary every now and then of the ones that are long term issues.

  
Development on Gump is sort of slow right now.  Unless somebody wants to 
step up with a patch, it may not happen anytime soon ;-).




Still, +1 to any idea that gets rid of the background noise.

  
The Jelly projects that are failing are basically the unit tests (this is 
also true for tags-html, the error for tags-swing is just wierd :).  If 
nobody care about the tests, you could just get rid of those s 
in the jakarta-commons-jelly.xml file.




Hen

  



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




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

  



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

RE: Re: [id] Composite identifiers

[Jörg Schaible]

Jörg Schaible wrote on Monday, February 06, 2006 9:07 PM:

> Hi Phil,
> 
> Phil Steitz wrote:
> 
>> I just committed a first cut at a CompositeIdentifierGenerator along
>> the lines of what we have discussed.  To replace the prefix
>> generators with this, we either have to modify the factories or
>> introduce a ConstantIdentifierGenerator.   If others (Michael?) have
>> better / different ideas on how to handle this, I am happy to review
>> patches or replace this implementation.
> 
> Looks fine. I've added the missing minLength/maxLength
> implementations and made it serializable. I would add a
> ConstantIdentifierGenerator. 

What about adding adding a method to StringIdentifierGenerator to deal with 
StringBuffers?

StringBuffer nextIdentifier(StringBuffer buffer);

The implementation should append the next identifier to the buffer and return 
it. This would make the concatenation more efficient and may be also useful for 
other use cases where the returned id is added to a String.

- Jörg

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