Thanks!
- Brett
Quoting robert burrell donkin <[EMAIL PROTECTED]>:
> the util tag gump run was broken by the splitting of the beanutils
> distribution two jars. i've added the required dependency to gump.
> hopefully this should be fixed in the next run.
>
> - robert
>
> On 19 Jan 2005, at 1
the util tag gump run was broken by the splitting of the beanutils
distribution two jars. i've added the required dependency to gump.
hopefully this should be fixed in the next run.
- robert
On 19 Jan 2005, at 10:31, Brett Porter wrote:
The following taglibs are now broken. These all appear to b
Is httpclient 2.0 instantaneously disappearing when 3.0 is released?
Don't most projects think that way? There are some honorary
exceptions, but how often do you see "use 2.x instead" if users find a
bug in 1.x?
Yes, but if it is working fine, there is rarely motivation to move "just
be
On Thu, 20 Jan 2005, Brett Porter <[EMAIL PROTECTED]> wrote:
> Is httpclient 2.0 instantaneously disappearing when 3.0 is released?
Don't most projects think that way? There are some honorary
exceptions, but how often do you see "use 2.x instead" if users find a
bug in 1.x?
Moving these philos
Yes, in practice this is going to be fine, but its hardly a good
practice to introduce a stated dependency on something you're not
using.
True. But that you are going to use soon 8-)
You could upgrade the dependency to httpclient 3.0-beta.
Is httpclient 2.0 instantaneously disappearing wh
On Thu, 20 Jan 2005, Brett Porter <[EMAIL PROTECTED]> wrote:
> Stefan Bodewig wrote:
>
>>In the "httpclient needs codec now" case this really is just a place
>>where the taglib inherits a dependency on commons-codec via
>>commons-httpclient but the project.xml doesn't know this. If you
>>add this
Stefan Bodewig wrote:
In the "httpclient needs codec now" case this really is just a place
where the taglib inherits a dependency on commons-codec via
commons-httpclient but the project.xml doesn't know this. If you add
this, I don't think anything else needs to change and it should be
perfectly b
On Wed, 19 Jan 2005, Dion Gillard <[EMAIL PROTECTED]> wrote:
> Do you mean the gump build is broken, or the taglibs build in
> isolation is broken?
In the "httpclient needs codec now" case this really is just a place
where the taglib inherits a dependency on commons-codec via
commons-httpclient b
On 19 Jan 2005, at 10:31, Brett Porter wrote:
The following taglibs are now broken. These all appear to be because
newer dependencies are not backwards compatible (though I haven't
looked into it at this point)
jetty (commons-codec dependency introduced for httpclient)
util (commons-beanutils cha
I'm happy to fix the builds if they're broken using they're stated
dependencies, but as for changing the builds to keep up with HEAD of
Jetty or BSF, I don't see the point.
The latter is the case (its actually httpclient HEAD, not jetty HEAD),
so that's fair enough - I was just checking. In pa
I just updated everything and at least bsf and jetty build and test
fine. Do you mean with latest versions of the dependencies ?
paul
Le 19 janv. 05, à 11:31, Brett Porter a écrit :
The following taglibs are now broken. These all appear to be because
newer dependencies are not backwards compati
On Wed, 19 Jan 2005 21:31:47 +1100, Brett Porter <[EMAIL PROTECTED]> wrote:
> The following taglibs are now broken. These all appear to be because
> newer dependencies are not backwards compatible (though I haven't looked
> into it at this point)
> jetty (commons-codec dependency introduced for htt
The following taglibs are now broken. These all appear to be because
newer dependencies are not backwards compatible (though I haven't looked
into it at this point)
jetty (commons-codec dependency introduced for httpclient)
util (commons-beanutils changes)
bsf (bsf changes)
Does anyone have an i
13 matches
Mail list logo
