Ralph Goers wrote:
Reinhard Poetz wrote:
If we use the dependency management section in our root pom, what will
happen when we release one of our modules? Is the version information
used and added to the or is the fallback to the parent's
pom depdencyManagement section still considered?
The r
Jorg Heymans wrote:
Reinhard Poetz wrote:
I'm asking because I don't understand who the customers of creating a
section in Cocoon are? Is it the Cocoon project
alone or also all projects that use Cocoon?
AFAICT dependencyManagement does not come into play unless you're
inheriting from th
Reinhard Poetz wrote:
If we use the dependency management section in our root pom, what will
happen when we release one of our modules? Is the version information
used and added to the or is the fallback to the parent's
pom depdencyManagement section still considered?
The root pom should also
Reinhard Poetz wrote:
I'm asking because I don't understand who the customers of creating a
section in Cocoon are? Is it the Cocoon project
alone or also all projects that use Cocoon?
AFAICT dependencyManagement does not come into play unless you're
inheriting from the pom that declares it,
Alexander Klimetschek napisał(a):
Grzegorz Kossakowski schrieb:
You mentioned that you play with Dojo. I have some troubles with
fixing upload progress sample from Forms. I guess it's
clearly client side issue but I cannot debug relevant code snippet
(it does not appear in Firebug) and I'm real
Grzegorz Kossakowski schrieb:
I hope to commit some basic (without caching implemented) code within days. It
took me quite a long time to clarify
whole idea...
Great!
You mentioned that you play with Dojo. I have some troubles with fixing upload
progress sample from Forms. I guess it's
clea
[
https://issues.apache.org/jira/browse/COCOON-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski closed COCOON-1992.
Resolution: Fixed
All resources from Ajax block are loaded directly. The task is f
[
https://issues.apache.org/jira/browse/COCOON-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski closed COCOON-2026.
Resolution: Fixed
"resource://" scheme is used only once in all Forms samples so I
[
https://issues.apache.org/jira/browse/COCOON-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski closed COCOON-1993.
Resolution: Fixed
All resources are loaded directly so the task is accomplished.
Alexander Klimetschek wrote:
Reinhard Poetz schrieb:
After thinking more about this, I believe that one main distinction is
that cocoon-rcl creates an environment which is used at development
time. Alex' solution is used in production too, IIUC.
It's actually not that important to have reload
Alexander Klimetschek napisał(a):
> Great, I'd love to have a postable source. How far are you? I could help
> you in testing it next week, when I have our webapp running with Cocoon
> trunk (going from dojo 0.3.1 to 0.4.1 is quite some work...).
> Specifically I want to reuse lots of styling pipel
Reinhard Poetz schrieb:
After thinking more about this, I believe that one main distinction is
that cocoon-rcl creates an environment which is used at development
time. Alex' solution is used in production too, IIUC.
It's actually not that important to have reloading for the shielded
servlets
Alexander Klimetschek napisał(a):
>
> I find the wiki much more easier to find/use than the daisy
> documentation, eg. I have a full text search - although most of its
> content is quite old. No one outside of the developer mailinglist knows
> about the cocoon.zones.apache.org website and the dais
Daniel Fagerstrom schrieb:
You are supposed to be able to use the ShieldingServletService,
http://svn.apache.org/repos/asf/cocoon/trunk/core/cocoon-servlet-service/cocoon-servlet-service-components/src/main/java/org/apache/cocoon/servletservice/shielding/ShieldingServletService.java,
with a or
[
https://issues.apache.org/jira/browse/COCOON-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski closed COCOON-2039.
Resolution: Fixed
Comitted in r527070.
> Port changes made in r477161 to trunk
>
Ich werde ab 10.04.2007 nicht im Büro sein. Ich kehre zurück am
12.04.2007.
Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.
In dringenden Fällen wenden Sie sich bitte an meinen Kollegen
Sascha-Matthias Kulawik:
E-Mail: [EMAIL PROTECTED]
Tel.: 05162 / 9815 32
Mit freundlichen Grüße
Reinhard Poetz schrieb:
Daniel Fagerstrom wrote:
Becoming even vaguer: could such a shielding classloader interceptor
somehow use the reloading classloader from cocoon-rcl?
TBH, I have no idea ATM, but I will look into Alex' work when I make
cocoon-rcl ready for a release.
FYI: The Shieldin
Ralph Goers wrote:
Given the number of projects in Cocoon I'm sure it is.
Just for grins run mvn -P allblocks dependency:analyze. It will take a
while but has tons of useful output.
As an example, I've shown part of it below. You can see that
commons-logging 1.1 is used as a transitive depe
Given the number of projects in Cocoon I'm sure it is.
Just for grins run mvn -P allblocks dependency:analyze. It will take a
while but has tons of useful output.
As an example, I've shown part of it below. You can see that
commons-logging 1.1 is used as a transitive dependency for XML while
19 matches
Mail list logo
