[
http://issues.apache.org/jira/browse/FOR-506?page=comments#action_12317756 ]
David Crossley commented on FOR-506:
Some html validation issues ...
Re: FOR-592 - pelt and i18n clarifications
http://marc.theaimsgroup.com/?t=11231601642
Do not
[
http://issues.apache.org/jira/browse/FOR-592?page=comments#action_12317757 ]
David Crossley commented on FOR-592:
Re: FOR-592 - pelt and i18n clarifications
http://marc.theaimsgroup.com/?t=11231601642
Pelt skin not HTML 4.01 compliant
Addi a écrit :
Diwaker Gupta wrote:
The naming convention for the plugins is fine, but I think it would
be nice if users are able to declare required plugins using simpler
names like pdf, text, docbook and so on.
We can figure out what simple names exactly to use later. I just
wanted to
Anil Ramnanan wrote:
Ross Gardler wrote:
The wizard will then use this method to get the URL for each of the
plugin descriptors and processes them as you intended above.
When we change the forrest configuration system we would just need to
change the way the forrest.properties are read into
David Crossley wrote:
Anil Ramnanan wrote:
Ross Gardler wrote:
The wizard will then use this method to get the URL for each of the
plugin descriptors and processes them as you intended above.
When we change the forrest configuration system we would just need to
change the way the
[ http://issues.apache.org/jira/browse/FOR-585?page=all ]
Ross Gardler closed FOR-585:
Fix Version: 0.8-dev
Resolution: Fixed
Assign To: Ross Gardler
Forgot to close the issue
Provide full list of plugins via Activate Plugins list
Modify Activate Plugin Wizard page so that it retrieves the list of plugins
from the plugin descriptors
---
Key: FOR-598
URL: http://issues.apache.org/jira/browse/FOR-598
Ross Gardler wrote:
In other words use the fetch-plugins-descriptors task in
FORREST_HOME/main/targets/plugins.xml to retrieve the descriptors and
then process the downloaded files that can be found in
${project.temp-dir}.
I have uploaded a patch that works by reading the forrest.properties
Diwaker Gupta wrote:
On Thursday 04 August 2005 3:04 pm, Ross Gardler wrote:
How do you avoid name conflicts given that Forrest does not have a
monopoly on plugin publication?
That is what if I call a plugin foo and Joe calls his plugin foo and
then Forrest creates one called foo?
Hmm, I
David Crossley wrote:
Ross Gardler wrote:
David Crossley wrote:
Are you just talking about the stylesheet or the DTDs too?
The trouble with the DTDs is that they will make this
plugin, and our SVN trunk, very cumbersome. How many
versions of Full DocBook and Simplified DocBook will
we
Refactoring of SelectionChanged events in Eclipse actions and popups
Key: FOR-599
URL: http://issues.apache.org/jira/browse/FOR-599
Project: Forrest
Type: Improvement
Components: Tool: Eclipse
I had put a patch in for issue FOR-598 which was supposed to be appplied
instead of this. I included some more changes. I will redo the patch so
the patch for issue FOR-598 should be ignored.
Anil.
Ross Gardler (JIRA) wrote:
[ http://issues.apache.org/jira/browse/FOR-596?page=all ]
[
http://issues.apache.org/jira/browse/FOR-598?page=comments#action_12317801 ]
Ross Gardler commented on FOR-598:
--
I've applied this patch (locally), but things no longer compile, I'm not sure
if I made a mistake (as I realised too late that this patch
Google Sitemap causes stack overflow exceptions
---
Key: FOR-600
URL: http://issues.apache.org/jira/browse/FOR-600
Project: Forrest
Type: Bug
Components: Plugins (general issues)
Versions: 0.8-dev
Reporter:
[ http://issues.apache.org/jira/browse/FOR-597?page=all ]
Ross Gardler closed FOR-597:
Fix Version: 0.8-dev
Resolution: Fixed
Applied to whiteboard with minor modifications:
- added site.xml and tabs.xml page so docs can be generated
- add links
Anil Ramnanan wrote:
I had put a patch in for issue FOR-598 which was supposed to be appplied
instead of this. I included some more changes. I will redo the patch so
the patch for issue FOR-598 should be ignored.
Yeah, I noticed too late. See my comments on the other issue before
spending
Original Message
To: users@cocoon.apache.org, dev@cocoon.apache.org, [EMAIL PROTECTED]
Subject: [ANN] Eclipse Lepido, Tools for Apache Cocoon milestone 1
Eclipse Lepido, Tools for Apache Cocoon milestone 1
---
The development
Last modified time of Goggle Sitemap incorrect
--
Key: FOR-601
URL: http://issues.apache.org/jira/browse/FOR-601
Project: Forrest
Type: Bug
Versions: 0.8-dev
Reporter: Ross Gardler
Priority: Minor
The
Rasik Pandey wrote:
The Google Sitemap generated by the GoogleSitemap Plugin creates a
last modified time.
However, this is always the time that the file was generated, which
is not necessarily the
time the src was last modified.
It seems to me that this could be classified as a cocoon
19 matches
Mail list logo
