Antonio Gallardo (JIRA) wrote:
[
https://issues.apache.org/jira/browse/COCOON-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio Gallardo reopened COCOON-2065:
--
Patch was not applied in cocon 2.1.11-dev.
I
[
https://issues.apache.org/jira/browse/COCOON-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Knecht updated COCOON-2065:
-
Fix Version/s: (was: 2.1.11-dev (Current SVN))
Assignee: (was: Felix Knecht)
I think that I have (finally) sorted out all cases and everything
works as before.
Building the whole cocoon
MAVEN_OPTS=-Xmx256m mvn clean install -Dmaven.test.skip=true -Pallblocks
I got following error:
INFO] Building Eventcache Block Implementation
[INFO]task-segment: [clean, install]
Felix Knecht pisze:
I think that I have (finally) sorted out all cases and everything
works as before.
Building the whole cocoon
MAVEN_OPTS=-Xmx256m mvn clean install -Dmaven.test.skip=true -Pallblocks
I got following error:
snip/
Felix Knecht (JIRA) pisze:
[
https://issues.apache.org/jira/browse/COCOON-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Knecht closed COCOON-2091.
Resolution: Fixed Fix Version/s: 2.2-dev (Current SVN)
- Added xinha and
Grzegorz Kossakowski schrieb:
Felix Knecht (JIRA) pisze:
[
https://issues.apache.org/jira/browse/COCOON-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Knecht closed COCOON-2091.
Resolution: Fixed Fix Version/s: 2.2-dev
Sorry, I hit the wrong button, so former reply doesn't has any changes :-(
I haven't tested your changes but I would like to something more general.
I wonder if you have not hurried up too much with this change. Even
though Xinha is an obvious replacement for HTMLArea they are _not_ the
same
Grzegorz Kossakowski wrote:
Felix Knecht (JIRA) pisze:
[
https://issues.apache.org/jira/browse/COCOON-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Knecht closed COCOON-2091.
Resolution: Fixed Fix Version/s: 2.2-dev (Current
Reinhard Poetz schrieb:
Grzegorz Kossakowski wrote:
Felix Knecht (JIRA) pisze:
[
https://issues.apache.org/jira/browse/COCOON-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Knecht closed COCOON-2091.
Resolution: Fixed Fix
Felix Knecht wrote:
Reinhard Poetz schrieb:
Was htmlarea removed completly or is it just a styling option whether
I want to use Xinha or Htmlarea?
It's just a styling option you have (xinha instead of htmlarea) and no
real replacement has be done. You can use both at the moment, it depends
on
Then I don't see a problem (as long as Xinha resources are not loaded
from every form ... haven't had time to look into the implementation
yet).
It's more or less exactly the same implementations as for htmlarea.
Please reopen the issue if it's going wrong.
Hello,
I would like to give you a brief description of what happened in cocoon-template and cocoon-expression-language blocks/modules. All my
changes were about introducing new ObjectModel API (COCOON-2086) and switching to it in cocoon-template (COCOON-2092). As a consequence of a
switch I
Felix Knecht pisze:
Reinhard Poetz schrieb:
Grzegorz Kossakowski wrote:
Was htmlarea removed completly or is it just a styling option whether
I want to use Xinha or Htmlarea?
It's just a styling option you have (xinha instead of htmlarea) and no
real replacement has be done. You can use both
I corrected the summary and description of the issue.
Do you think it's ok this way?
[
https://issues.apache.org/jira/browse/COCOON-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Knecht updated COCOON-2091:
-
Description:
The used HTMLArea as webbased editor is no longer actively maintained [1].
Felix Knecht pisze:
I corrected the summary and description of the issue.
Do you think it's ok this way?
Yes, Felix, it's now a lot clearer. Thanks!
If you we are already in this area. What about deprecating HTMLArea? The project is not maintained any more so I think it would be very wise
If you we are already in this area. What about deprecating HTMLArea?
The project is not maintained any more so I think it would be very
wise to deprecate HTMLArea, especially when we have replacement for
it, already.
What others think about it? Do we need a vote?
Felix, could you handle
Felix Knecht wrote:
If you we are already in this area. What about deprecating HTMLArea?
The project is not maintained any more so I think it would be very
wise to deprecate HTMLArea, especially when we have replacement for
it, already.
What others think about it? Do we need a vote?
yes
Reinhard Poetz pisze:
Once we had a deprecation logger but I don't think that the
infrastructure for it is still in place.
Do you talk about client or server logger?
I think that we could create special matcher for HTMLArea resources and put a simple action (DeprecateAction?) that would
Grzegorz Kossakowski wrote:
Reinhard Poetz pisze:
Once we had a deprecation logger but I don't think that the
infrastructure for it is still in place.
Do you talk about client or server logger?
server logger. IIRC there was a log target named deprecated. Maybe Carsten
knows more.
I
Reinhard Poetz schrieb:
Grzegorz Kossakowski wrote:
Reinhard Poetz pisze:
Once we had a deprecation logger but I don't think that the
infrastructure for it is still in place.
Do you talk about client or server logger?
server logger. IIRC there was a log target named deprecated. Maybe
Reinhard Poetz schrieb:
Grzegorz Kossakowski wrote:
Reinhard Poetz pisze:
Once we had a deprecation logger but I don't think that the
infrastructure for it is still in place.
Do you talk about client or server logger?
server logger. IIRC there was a log target named deprecated. Maybe
[
https://issues.apache.org/jira/browse/COCOON-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski closed COCOON-2054.
Resolution: Fixed
Patch applied in r558726. Thanks for it, Alexander.
I tested
[
https://issues.apache.org/jira/browse/COCOON-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski closed COCOON-1991.
Resolution: Fixed
Changes has been merged with trunk long time ago and everything
Make Object Model a Spring bean
---
Key: COCOON-2095
URL: https://issues.apache.org/jira/browse/COCOON-2095
Project: Cocoon
Issue Type: Sub-task
Components: - Expression language
Affects Versions:
map:when test=servlet:servlet:/path/to/file always returns true
--
Key: COCOON-2096
URL: https://issues.apache.org/jira/browse/COCOON-2096
Project: Cocoon
Issue Type: Bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kossakowski wrote:
Felix Knecht (JIRA) pisze:
[
https://issues.apache.org/jira/browse/COCOON-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Knecht closed COCOON-2091.
Hi Felix,
You should not feel bad for that. Currently we have only 2 branches:
2.2-dev and 2.1.11-dev. The patch was applied to 2.2-dev but not to
2.1.11-dev, this is why I reopened the issue.
Best Regards,
Antonio Gallardo.
Felix Knecht escribió:
Antonio Gallardo (JIRA) wrote:
I did some more studying with jhat, and it appears that the jpegs
inside the zips are being held in memory by the cocoon cache, in the
end leading to the out of memory condition.
I used a noncaching pipeline instead, and the problem seems to go
away. However, I find it odd the cache doesnt
Antonio Gallardo wrote:
Hi Felix,
You should not feel bad for that. Currently we have only 2 branches:
2.2-dev and 2.1.11-dev. The patch was applied to 2.2-dev but not to
2.1.11-dev, this is why I reopened the issue.
I don't feel bad, the main question was if I can trust in the 'fixed'
On 24.07.2007 00:42, Felix Knecht wrote:
I don't feel bad, the main question was if I can trust in the 'fixed'
tags in jira (2.1.11-dev was marked as fixed) or if I need to check in
the code if really all (even the already marked as fixed version)
mentioned branches are fixed before closing.
31 matches
Mail list logo
