Grzegorz Kossakowski wrote
>>
>>
>> + javax.servlet
>> + servlet-api
>> +
>
>
> Shouldn't this dependency had scope "provided"?
>
Good catch, yes, I fixed this in our root pom, so the scope is now
"provided" for every use in one of our modules.
Carsten
--
Carsten Z
[
https://issues.apache.org/jira/browse/COCOON-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski closed COCOON-2095.
Resolution: Fixed
The goal has been accomplished. Closing issue.
> Make Object Mo
[
https://issues.apache.org/jira/browse/COCOON-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski closed COCOON-2092.
Resolution: Fixed
The goal has been accomplished. Closing issue.
> Switch to new
Carsten Ziegeler pisze:
Hi,
while briefly looking at current 2.2 I noticed some strange
dependencies, for example cocoon-expression-api depends on another impl
and cocoon-expression-impl (being part of the core packages) depends on
a block impl.
If this is just a transient state ignore my messa
[EMAIL PROTECTED] pisze:
Author: cziegeler
Date: Tue Aug 7 11:37:04 2007
New Revision: 563610
URL: http://svn.apache.org/viewvc?view=rev&rev=563610
Log:
Add missing dependency.
Modified:
cocoon/trunk/blocks/cocoon-serializers/cocoon-serializers-charsets/pom.xml
Modified:
cocoon/trunk/blo
On Tue, 2007-08-07 at 09:46 +0200, Daniel Fagerstrom wrote:
> Unfortunately it is more complicated than that. The non-compatible
> change is that Request.getSession switches return value from
> o.a.c.environment.Session to javax.servlet.http.HttpSession and that
> Request.getCookie switch return
It should be possible to choose which ELs one wants to use and avoid
unnecessary dependencies
-
Key: COCOON-2107
URL: https://issues.apache.org/jira/browse/COCOON-2107
Carsten Ziegeler pisze:
I would also be great if the cocoon-expression-impl could be split up
into separate modules, so only if I want to use the javascript stuff I
have a dep on rhino etc.
Yes, that is on my TODO list and with current design (where ELs are just Spring beans) it's really easy t
I would also be great if the cocoon-expression-impl could be split up
into separate modules, so only if I want to use the javascript stuff I
have a dep on rhino etc.
Carsten
Carsten Ziegeler wrote:
> Hi,
>
> while briefly looking at current 2.2 I noticed some strange
> dependencies, for example
Discussions should better take place in the mailing list :)
Carsten
Grzegorz Kossakowski (JIRA) wrote:
> [
> https://issues.apache.org/jira/browse/COCOON-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518179
> ]
>
> Grzegorz Kossakowski commented on CO
Hi,
while briefly looking at current 2.2 I noticed some strange
dependencies, for example cocoon-expression-api depends on another impl
and cocoon-expression-impl (being part of the core packages) depends on
a block impl.
If this is just a transient state ignore my message, but if not this has
to
[
https://issues.apache.org/jira/browse/COCOON-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518179
]
Grzegorz Kossakowski commented on COCOON-2106:
--
If registration of wrapper is implemented that bridge w
[
https://issues.apache.org/jira/browse/COCOON-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518178
]
Kazó Csaba commented on COCOON-2106:
For the bridge implementation, see commit 553872:
http://svn.apache.org/vi
[
https://issues.apache.org/jira/browse/COCOON-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518175
]
Carsten Ziegeler commented on COCOON-2106:
--
Hmm where is this SpringToAvalonDataSourceBridge?
But apart fr
Kazó Csaba pisze:
The test should be the other way round. :)
Gosh, you are right, of course! Many thanks. :)
Fixed permanently, I hope.
--
Grzegorz Kossakowski
http://reflectingonthevicissitudes.wordpress.com/
[
https://issues.apache.org/jira/browse/COCOON-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski updated COCOON-2106:
-
Argh, I forgot that DataSourceComponent and DataSource are incompatible.
This prove
The test should be the other way round. :)
> Log:
> If context object is null do nothing in fillContext method.
>
> +if (contextObject != null)
> +//nothing to do
> +return;
Kazó Csaba pisze:
Hi Grek,
Hi,
I've spotted a small regression in the stuff you're working on (ObjectModel).
It breaks functionality, so I thought I'd make sure you
know about it.
It happens when using the PipelineUtil functions. These save the current
context object, overwrite it with the
Daniel Fagerstrom pisze:
I'm wondering why not to the FlowHelper where context bean is set up?
I meant that the code should be *called* from
AbstractInterpreter.forwardTo.
Done r562896.
I'm already moving most of the code of Template and Flow Object Model
helpers.
Being more explicit
Joerg Heinicke skrev:
On 04.08.2007 9:03 Uhr, Daniel Fagerstrom wrote:
I don't want this to collide with releasing 2.2, so I'll wait with
introducing the changes if there is any risk for that.
Can you please clarify what exactly this vote is now about?
It is about "letting our environment abt
20 matches
Mail list logo
