Re: [Proposal] Project Management Roles

2006-05-01 Thread Rick Tessner
On Wed, 2006-26-04 at 17:43 +1000, David Crossley wrote:

 Establish Project Management Roles for various
 well-defined tasks (see below).

I like it.  Good idea.


 Subversion Monitor
 --
 Ensure that svn:eol-style settings are appropriate.
 Ensure no line-endings issues.
 Regularly run xml-tidy.
 Regularly run java-tidy.
 
 There are already some Perl scripts and other tools in
 the committers SVN and Forrest SVN.

I'll volunteer for this.  I haven't had a lot of cycles of late, but this is
something I should be able to fit into my schedule. :)

-- 
Rick Tessner
rick at apache dot org


smime.p7s
Description: S/MIME cryptographic signature


FYI on forrest.apache.org being down

2005-04-12 Thread Rick Tessner
Hi all,

I'm attaching a note I received from Joshua Slive over at
[EMAIL PROTECTED]

I at first, incorrectly, thought that the problem with the forrest web
site was related to the Apache upgrade.  That was not the case.  It was
our problem.

See attached.

Joshua also pointed out the following:

Note it is a little hard to debug this stuff at the moment
because of the four hour delay between placing stuff on minotaur
and having it go live on ajax.  So it is best to be very careful
with the .htaccess files.

-- 
Rick Tessner
rick at apache dot org
---BeginMessage---
Rick Tessner wrote:
On Tue, 2005-04-12 at 10:29 -0400, Joshua Slive wrote:
As the subject says...
Let me know if you see any problems.

http://forrest.apache.org/
is giving a 500 Internal Server Error.  Although other sites, such as
cocoon.apache.org, seem to be fine.
Not related to the upgrade, as far as I can tell.  It was a bad regex in 
a RedirectMatch directive in the .htaccess file that was installed 
earlier today.  It appears to have been removed already on minotaur, so 
I removed it on ajax as well to get the site going again.

By the way, RedirectMatch shouldn't even be necessary for this stuff, 
since Redirect will do prefix substitution.

Joshua.
---End Message---


smime.p7s
Description: S/MIME cryptographic signature


Re: [JIRA] Closed: (FOR-450) Input plugins broken

2005-04-04 Thread Rick Tessner
On Mon, 2005-04-04 at 15:52 -0500, [EMAIL PROTECTED] wrote:

 My testing turns up not issues, so , once again, thanks for finding
 this Rick, I'd gone blind to the problem and it was driving me mad!

No worries!  Sometimes all it takes is a fresh pair of eyes. :)

-- 
Rick Tessner
rick at apache dot org


smime.p7s
Description: S/MIME cryptographic signature


Forrest 0.6.x, Cocoon and Java

2005-01-09 Thread Rick Tessner
Hi all,

I've been looking at the best way to upgrade cocoon in the
forrest_06_branch in order to address
http://issues.cocoondev.org//browse/FOR-356 (Multi-User Capability).  

The problem was a cocoon issue which has been fixed in both Cocoon
2.2-dev and Cocoon 2.1.6 (and thus Cocoon 2.1.7-dev)

Issues that I've run across

  * Current Cocoon 2.2-dev (and that used in Forrest 0.7-dev) works
only with Java 1.4.x or higher. 
  * Cocoon 2.1.6 works with Java 1.3.x and higher 
  * Cocoon 2.1.7-dev I can't get to compile with either Java 1.3.x
or 1.4.x (bombs in different places tho) so I don't know whether
it works with Forrest. :(
  * The pass-through attribute for the map:mount element in the
sitemap does not work under Cocoon 2.1.6 (may work in 2.1.7-dev,
but again I haven't been able to test this)
  * Forrest 0.6 currently uses an earlier revision of Cocoon 2.2-dev
(which was at the time compatible with Java 1.3.x) with Cocoon
2.1.5 libs.

My Preference:

  * Upgrade Cocoon in forrest_06_branch to the same Cocoon being
used in the Forrest trunk and make it clear that Java 1.4.x is
the minimum requirement for Forrest (both 0.6.x and svn trunk).
ie. Upgraded to Cocoon 2.2-dev, revision 70.
  * Upgrade the java classes in Forrest 0.6.x that were part of
o.a.cocoon to o.a.forrest to mirror what has been done in
Forrest 0.7-dev.
  * Upgrade both 0.6.1-dev and 0.7-dev to Cocoon 2.2 when it's
released.  Discussion on the cocoon dev mailing list sounds like
that could happen in the next 3-4 months.

If we go with Cocoon 2.2, it would mean that we lose Java 1.3.x
compatibility.  Then again, Java 1.3 is in the process of being EOL'd.
See http://java.sun.com/j2se/1.3/download.html .

Thoughts?  

-- 
Rick Tessner
rick at apache dot org


smime.p7s
Description: S/MIME cryptographic signature