Carsten Ziegeler wrote:
It seems that we should make a 2.1.1 release soon due to some
bugs/problems.
Now, what do you think if we apply/process all patches entered
in bugzilla for 2.1.1 as well? A patch can either be applied or
closed if it's obsolete etc.
+1.
I fixed some bugs in internal forwar
> From: Joerg Heinicke
> Carsten Ziegeler wrote:
> > It seems that we should make a 2.1.1 release soon due to some
> > bugs/problems.
> >
> > Now, what do you think if we apply/process all patches entered in
> > bugzilla for 2.1.1 as well? A patch can either be applied
> or closed if
> > it
Carsten Ziegeler wrote:
It seems that we should make a 2.1.1 release soon due to some
bugs/problems.
Now, what do you think if we apply/process all patches entered
in bugzilla for 2.1.1 as well? A patch can either be applied or
closed if it's obsolete etc.
Carsten
+1 making 2.1.1 a bugfix release
Hello.
I am trying to install 2.1 on a brand new, just-opened-the-box system
and I get a build error. I'm not at all familiar with the new build
system, so I'm trying to navigate the build files myself. This looks
like a minor (classpath?) oversight of some sort, but it prevents the
default b
Vadim Gritsenko wrote:
Reinhard Pötz wrote:
IMO a bug in Cocoon 2.1 that makes a 2.1.1 necessary, doesn't it? I
think many production environments depend on external sources and many
use proxy firewalls.
Without looking into the sources: could this be a problem with the
httpclient library?
Yahoo
Reinhard Pötz wrote:
IMO a bug in Cocoon 2.1 that makes a 2.1.1 necessary, doesn't it? I
think many production environments depend on external sources and many
use proxy firewalls.
Without looking into the sources: could this be a problem with the
httpclient library?
Yahoo screenscrape example was
