You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Alex Batlin <al...@batlin.com> on 2005/09/29 08:13:35 UTC

committing a plugin

How do I go about committing plugins into SVN?

-----Original Message-----
From: David Crossley (JIRA) [mailto:jira@apache.org] 
Sent: 29 September 2005 03:56
To: dev@forrest.apache.org
Subject: [jira] Commented: (FOR-675) upgrading to commons-jxpath-1.2.jar
causes failures with linkrewriter protocols site: etc.

    [
http://issues.apache.org/jira/browse/FOR-675?page=comments#action_12330771 ]


David Crossley commented on FOR-675:
------------------------------------

I had already tried adding the "namespace-uri" parameter to the Forrest
sitemaps (see above) but that had no effect. The value was as declared in
the site-author/content/xdocs/site.xml
(http://apache.org/forrest/linkmap/1.0). I tried again today to no avail.

The sample that you enhanced in Cocoon-2.1 was the old "bookdemo". I was
using the "sitedemo" in Cocoon trunk 2.2 because that is closer to what we
have in Forrrest. Today i added a demonstration of the problem to Cocoon 2.2

You wonder why JXPath raises the issue. So did i, which is why the Bugzilla
entry mentions "Input Modules". These are used to inject the site.xml file
and JXPath is involved with Input Modules.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36810
"source that declares namespace fails JXPath/Linkrewriter/Input Modules"




> upgrading to commons-jxpath-1.2.jar causes failures with linkrewriter
protocols site: etc.
>
----------------------------------------------------------------------------
--------------
>
>          Key: FOR-675
>          URL: http://issues.apache.org/jira/browse/FOR-675
>      Project: Forrest
>         Type: Bug
>   Components: Core operations
>     Versions: 0.8-dev, 0.7
>     Reporter: David Crossley
>     Priority: Blocker
>      Fix For: 0.8-dev

>
> upgrading from commons-jxpath-20030909.jar to commons-jxpath-1.2.jar
causes failures with linkrewriter protocols site: etc. This happens in both
modes: 'forret run' and 'forrest'.

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


Re: committing a plugin

Posted by David Crossley <cr...@apache.org>.
Alex Batlin wrote:
> How do I go about committing plugins into SVN?

Not sure what you mean.

Do you have changes that you want to make to an
existing plugin?

Only Apache Forrest committers have direct write access.
Other contributers need to send a patch via the Issue
Tracker.
http://forrest.apache.org/issues.html

If you are suggesting the donation of a whole new
plugin, then please describe it on the dev mailing
list and we will see how it fits. Then ask you to
donate it via the Issue Tracker.

-David