What is needed is to make the tests in the sitemap modules depend on the
tests in the pipeline module in Maven. I didn't know how to do that and
forgot to fix it. Anybody know about how to do that?
/Daniel
Reinhard Poetz skrev:
Is it difficult to fix this?
[EMAIL PROTECTED] wrote:
Online
Daniel Fagerstrom wrote:
What is needed is to make the tests in the sitemap modules depend on the
tests in the pipeline module in Maven. I didn't know how to do that and
forgot to fix it. Anybody know about how to do that?
The test classes have to be exported as a separate jar:
Reinhard Poetz wrote:
Ralph Goers wrote:
Reinhard Poetz wrote:
Yes. Then I will setup the src/changes/changes.xml files in our
modules because I guess that nobody wants to write a StatusReport
module for Maven.
As I said before this solution comes with the downside that the
description
Carsten Ziegeler skrev:
Daniel Fagerstrom wrote:
Carsten Ziegeler skrev:
I think this is possible by creating a proxy around the generator with
the special sitemap support.
Seem like a good solution.
I've tried to find out how label handling for sitemap components is
solved
Daniel Fagerstrom wrote:
After having looked at I think that the simplest solution would be to
just provide one (singleton) info bean for each component. Something like:
util:map name=org.apache.cocoon.serialization.Serializer/xml/info
entry key=mime-type value=text/xml/
entry
Daniel Fagerstrom wrote:
we could have something like:
bean id=org.apache.cocoon.blocks.sample.block1
class=org.apache.cocoon.sitemap.SitemapServlet
servlet:context mountPath=/cocoon-blocks-fw-sample1
contextPath=blockcontext:/cocoon-blocks-fw-sample/test1
Simone Gianni wrote:
Carsten Ziegeler wrote:
So far, I've only seen people using labels for debugging pipelines which
is really not what it was intended for (I think we should provide a
better alternative for debugging pipelines anyway). If it would be me,
we could forget about views
Reinhard Poetz skrev:
Daniel Fagerstrom wrote:
we could have something like:
bean id=org.apache.cocoon.blocks.sample.block1
class=org.apache.cocoon.sitemap.SitemapServlet
servlet:context mountPath=/cocoon-blocks-fw-sample1
Reinhard Poetz wrote:
Reinhard Poetz wrote:
Ralph Goers wrote:
What do you mean by mixed content?
e.g. ordered lists -- ollifoo/lilibar/ol
I looked into the sources of the Maven report generation mechanism
and AFAICT this API makes it difficult (impossible?) to provide
support for it.
Stupid question: I created a new document for the Spring Configurator.
How and where can I add this to our Daisy navigation?
Thanks
Carsten
--
Carsten Ziegeler - Chief Architect
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Unsynchronized access to HashMap in ResourceReader
--
Key: COCOON-1977
URL: https://issues.apache.org/jira/browse/COCOON-1977
Project: Cocoon
Issue Type: Bug
Components: * Cocoon
Carsten Ziegeler wrote:
Stupid question: I created a new document for the Spring Configurator.
How and where can I add this to our Daisy navigation?
http://cocoon.zones.apache.org/daisy/cdocs/g4/g1/1223.html explains what needs
to be done to create the documentation for a new module. As I'm
Reinhard Poetz wrote:
Carsten Ziegeler wrote:
Stupid question: I created a new document for the Spring Configurator.
How and where can I add this to our Daisy navigation?
http://cocoon.zones.apache.org/daisy/cdocs/g4/g1/1223.html explains what
needs
to be done to create the documentation
Carsten Ziegeler wrote:
Reinhard Poetz wrote:
Carsten Ziegeler wrote:
Stupid question: I created a new document for the Spring Configurator.
How and where can I add this to our Daisy navigation?
http://cocoon.zones.apache.org/daisy/cdocs/g4/g1/1223.html explains what needs
to be done to
[
https://issues.apache.org/jira/browse/COCOON-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Heinicke updated COCOON-1977:
--
Affects Version/s: 2.2-dev (Current SVN)
I'm wondering what this caching does buy us at all?
[
https://issues.apache.org/jira/browse/COCOON-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Heinicke reassigned COCOON-1977:
-
Assignee: Jörg Heinicke
Unsynchronized access to HashMap in ResourceReader
[
https://issues.apache.org/jira/browse/COCOON-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Heinicke closed COCOON-1977.
-
Resolution: Fixed
Fix Version/s: 2.2-dev (Current SVN)
2.1.11-dev
On 05.01.2007 00:21, Jörg Heinicke (JIRA) wrote:
Resolution: Fixed
Fix Version/s: 2.2-dev (Current SVN)
2.1.11-dev (current SVN)
I wonder how we manage those versions. It seems to be quite strange:
Issues fixed in 2.1.9:
[
https://issues.apache.org/jira/browse/COCOON-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Heinicke updated COCOON-1622:
--
Fix Version/s: (was: 2.1.10)
[PATCH] SendMailTransformer and HTML body
[
https://issues.apache.org/jira/browse/COCOON-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Heinicke updated COCOON-1665:
--
Component/s: * Cocoon Core
Fix Version/s: (was: 2.1.10)
Test release against JVM
[
https://issues.apache.org/jira/browse/COCOON-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Heinicke updated COCOON-1667:
--
Fix Version/s: (was: 2.1.10)
Generation of documentation
---
[
https://issues.apache.org/jira/browse/COCOON-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Heinicke updated COCOON-1976:
--
Fix Version/s: (was: 2.1.10)
2.1.11-dev (Current SVN)
[
https://issues.apache.org/jira/browse/COCOON-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Heinicke updated COCOON-1977:
--
Fix Version/s: (was: 2.1.10)
2.1.11-dev (Current SVN)
[
https://issues.apache.org/jira/browse/COCOON-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Heinicke reopened COCOON-476:
--
[PATCH] No-cache enhancement for ResourceReader component
[
https://issues.apache.org/jira/browse/COCOON-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Heinicke updated COCOON-1520:
--
Fix Version/s: (was: 2.1.9)
Database / avalon problems
--
[
https://issues.apache.org/jira/browse/COCOON-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Heinicke closed COCOON-476.
Resolution: Fixed
[PATCH] No-cache enhancement for ResourceReader component
[
https://issues.apache.org/jira/browse/COCOON-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Heinicke updated COCOON-1865:
--
Fix Version/s: (was: 2.1.10)
Affects Version/s: (was: 2.1.10)
[
https://issues.apache.org/jira/browse/COCOON-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Heinicke updated COCOON-1666:
--
Fix Version/s: (was: 2.1.8)
Affects Version/s: (was: 2.1.8)
[
https://issues.apache.org/jira/browse/COCOON-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Heinicke updated COCOON-1576:
--
Fix Version/s: (was: 2.1.8)
Cocoon 2.1.7 does not compile - in mysterious circumstances
On Jan 3, 2007, at 4:27 AM, Carsten Ziegeler wrote:
Daniel Fagerstrom wrote:
You get the wrong version of DOM, see
http://osdir.com/ml/dev@cocoon.apache.org/msg48088.html, for some
hints.
You can either use JDK 1.5 or put xml-apis, xalan, xerces into your
endorsed directory.
Works
On 04.01.2007 22:13, Jörg Heinicke (JIRA) wrote:
Jörg Heinicke updated COCOON-1977:
--
Affects Version/s: 2.2-dev (Current SVN)
I'm wondering what this caching does buy us at all? Can somebody
tell in which cases the reader is really faster? From what I
[...]
Then, can somebody add to cocoon-webapp/pom.xml:
dependency
groupIdorg.apache.cocoon/groupId
artifactIdcocoon-core-additional-sample/artifactId
version1.0.0-SNAPSHOT/version
/dependency
thx,
—ml—
The modules samples are broken...
1) For the jxpath modules, an exception is thrown:
org.apache.commons.jxpath.JXPathException: Cannot access
property:
rg.apache.cocoon.environment.wrapper.RequestWrapper.attributeNames; No
read method
2) For the rest, the Accessor/Value table displays
Joerg Heinicke wrote:
How it must be handled:
1. As soon as a bug gets fixed the Current SVN version MUST be removed
from Affects versions. As it is already fixed having it there is also
no longer correct.
2. The X.Y.Z-dev version must be renamed to X.Y.Z after a release and a
new entry
34 matches
Mail list logo
