Reinhard Poetz wrote:
I also think that it is an *important signal to us*: 2.2 is complete,
the contracts are stable and they can't be changed
One thing to add: As Cocoon is modularized now, we can and _will_ have different
release cycles for our modules, e.g. if we think it's useful we can
hepabolu wrote:
Guys,
Thien did it again:
- he changed the masthead, making it a bit smaller and darker.
- he also added a search box and changed the color of apache cocoon to
be more prominent.
- he removed some tiles to make things look better at 800x600.
- the green blocks are now moved
On 2/7/07, Carsten Ziegeler [EMAIL PROTECTED] wrote:
...The version from trunk is used by several of us
already in production, several people have tried it out and it seems
that most of the problems have been fixed. So I really think that this
qualifies for an RC release...
Excuse the silly
Ok. In the trunk version of Spring framework, one can also use ordinary
Java (interface based) proxies, so I guess it is better to wait with
this functionality until the next minor version of Spring is released. I
turned it off in our trunk.
In Cocoon we use a call stack for handling some
Reinhard Poetz skrev:
Carsten Ziegeler wrote:
Vadim Gritsenko wrote:
RC has a meaning of release candidate, which to most people means
well tested almost production quality code. Going through recent
commits I noticed a lot of refactoring, new code, untested code, and
so on. This hardly
Hi,
On 7 Feb 2007, at 07:13, Carsten Ziegeler wrote:
I really doubt that most of the code for final releases (or rc) is
tested better than what we currently have in trunk. We do releases for
2.1.x without real tests for most of the code base. We rely on user
experience/tests. The version from
Hello,
It's little bit off-topic but my question is related to my patches I've
recently sent on JIRA. I've seen that all my patches produced by
Subclipse contain absolute path of Index: field. I think it's not
desired and these patches will cause problems to the others. Could
someone using
Andrew Savory wrote:
Hi,
Not wishing to spread FUD and rain on the parade, but ... I think 2.2
is *massively* less tested than 2.1.x. The main reason 2.1.x goes out
with not much testing is because it's been used in production by a
very large number of people. How many are actually
Hi,
What should context:// be changed to in src attribute in a block like
cocoon-forms-sample in 2.2 version (servlet service)? For example, how
should I rewrite the following statement in th cocoon-forms-sample?
map:transform src=context://samples/common/style/xsl/html/simple-
On 6 Feb 2007, at 13:06, Grzegorz Kossakowski wrote:
Jeremy Quinn napisał(a):
I think part of the problem is that I was unable to get the proper
sitemap glue working for Cocoon 2.2 as I was unable to run the
samples.
This section in the root sitemap (same mechanism in 2.1.n) is
designed
Jeremy Quinn napisał(a):
On 6 Feb 2007, at 13:06, Grzegorz Kossakowski wrote:
Jeremy Quinn napisał(a):
The point is, while using servlet-service-fw there is *no* root sitemap
handling all request. Request are handled by dispatcher servlet,
instead.
This is all news to me as I am not in a
Hi,
The dojo drag-and-drop repeater isn't working with IE (checked with IE 6
and IE 7). Both Cocoon 2.1 and 2.2 have the same problem (as expected...)
Somehow Dojo isn't capable of drag-and-drop, where tr elements are
used. The problem was reported, and I also found a sulution here [1].
Carsten Ziegeler wrote:
Andrew Savory wrote:
Hi,
Not wishing to spread FUD and rain on the parade, but ... I think 2.2
is *massively* less tested than 2.1.x. The main reason 2.1.x goes out
with not much testing is because it's been used in production by a
very large number of people.
Reinhard Poetz wrote:
What we need now is more people
who use/try it and in this sense it doesn't help to ship more milestone
releases.
Make it easy to try it and people will come.
http://cocoon.apache.org/mirror.cgi
http://cocoon.apache.org/2.2/
Contrast and compare with 2.1
Simone Gianni wrote:
Hi all,
I was playing with the profiler when I noticed the way the
ProfilingXMLPipe works. Every component is given the opportunity to
stream its sax events, they are buffered in a DOM, the DOM is then used
(to display the intermediate XML and) to stream SAX events to the
ClassCastException in Rhino when creating a continuation in a catch block
-
Key: COCOON-2006
URL: https://issues.apache.org/jira/browse/COCOON-2006
Project: Cocoon
Vadim Gritsenko wrote:
You are missing a point. It's not about a bug free version. It is about a
version which seen more than like 4 hours of testing after major surgery.
Sorry, but that's not fair. There were no code or api changes to the
core in the last weeks (apart from bug fixes). There
Vadim Gritsenko wrote:
Simone Gianni wrote:
Can someone point me to the right documentation branch where I should
update documentation?
I'd guess it should be cdocs: Profiler Block, but it is not listed on:
http://cocoon.zones.apache.org/daisy/
Not sure how easy/hard it is to add it
Vadim Gritsenko wrote:
Carsten Ziegeler wrote:
[...]
We need to get a 2.2 out; imho it is more important to have something
out after so many years than having a 115% bug free version.
You are missing a point. It's not about a bug free version. It is about
a version which seen more than
Carsten Ziegeler wrote:
[...]
Anyways, I'm a little bit clueless how to continue. Some of us say,
let's call it RC, some say no as things are missing.
Since writing more mails would take longer than releasing another series of core
milestone releases, I will release cocoon-core-2.2 as M3.
hepabolu wrote:
Awesome! Looks good ... but ... is that a page curl beside What is
Apache Cocoon ? *shudder*
I suppose it is. I think it's very well done, no tackiness about it.
What makes you shudder?
I'm not crazy about this page curl as well... Would it perhaps be better to move
both
Reinhard Poetz wrote:
Vadim Gritsenko wrote:
It is a bit
different for 2.2 though: there were no real downloadable release yet,
And maybe there will never be one. Don't know. There doesn't seem to be
much energy in this community to provide it - especially if you use
Maven 2 you don't
Hi,
On 7 Feb 2007, at 14:01, Carsten Ziegeler wrote:
Now, I will ask the open question right away: who will work on the
missing parts?
FX: TUMBLEWEED
Gosh, no rush of people to say I will! ;-)
On 7 Feb 2007, at 14:49, Reinhard Poetz wrote:
From my experience over the last months, I'd say
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
Vadim Gritsenko wrote:
It is a bit different for 2.2 though: there were no real
downloadable release yet,
And maybe there will never be one. Don't know. There doesn't seem to
be much energy in this community to provide it - especially if you
Vadim Gritsenko said the following on 7/2/07 16:11:
hepabolu wrote:
Awesome! Looks good ... but ... is that a page curl beside What is
Apache Cocoon ? *shudder*
I suppose it is. I think it's very well done, no tackiness about it.
What makes you shudder?
I'm not crazy about this page curl as
Reinhard Poetz wrote:
Carsten Ziegeler wrote:
[...]
Anyways, I'm a little bit clueless how to continue. Some of us say,
let's call it RC, some say no as things are missing.
Since writing more mails would take longer than releasing another series of
core
milestone releases, I will
Reinhard Poetz wrote:
Vadim Gritsenko wrote:
Simone Gianni wrote:
Can someone point me to the right documentation branch where I should
update documentation?
I'd guess it should be cdocs: Profiler Block, but it is not listed on:
Not sure how easy/hard it is to add it there... Reinhard?
It
Reinhard Poetz wrote:
Vadim Gritsenko wrote:
Regardless of download presence, at the very least there should be a
2.2 site set up and running.
http://cocoon.apache.org/2.2/
IMNSHO we don't have http://cocoon.apache.org/2.2/ anymore. Information
about the core will be available at
Carsten Ziegeler wrote:
Reinhard Poetz wrote:
Carsten Ziegeler wrote:
Anyways, I'm a little bit clueless how to continue. Some of us say,
let's call it RC, some say no as things are missing.
Since writing more mails would take longer than releasing another series of core
milestone releases,
[
https://issues.apache.org/jira/browse/COCOON-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reinhard Poetz reassigned COCOON-2005:
--
Assignee: Reinhard Poetz
Cocoon's build broken due to invalid parent in
[
https://issues.apache.org/jira/browse/COCOON-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reinhard Poetz closed COCOON-2005.
--
Resolution: Fixed
should work now. please crosscheck. thanks!
Cocoon's build broken due to
Reinhard Poetz wrote:
Jorg Heymans wrote:
Hi,
I've killed off the instance as obviously it can't cope with
Reinhard's recent structural refactorings. I'll see about rebuilding
in the next few weeks unless someone beats me to it.
What needs to be done for a rebuild? I would remove all
Vadim Gritsenko wrote:
Continuum was stopped because I started to flatten the POM hierarchy
in trunk. This will hopefully save me a lot of time during the release
process.
Do I understand it correctly - it should be turned off to simplify
release process? Sounds Ok to me if that's the case.
Jorg Heymans wrote:
So for me, currently, the best solution ATM for CI would be to cron
something like this:
#!/bin/bash
rm -fr ~/.m2/repository
Or:
rm -rf ~/.m2/repository/org/apache/cocoon
cd src/cocoon-trunk
svn update
mvn clean install ~/cocoon-build.log 21
if [ $? -ne 0 ]; then
Vadim Gritsenko wrote:
#!/bin/bash
rm -fr ~/.m2/repository
Or:
rm -rf ~/.m2/repository/org/apache/cocoon
possibly yes. I'm still debating the usefulness of downloading
everything new each time. It was useful back in the days where existing
poms were updated, they seem to have this
cocoon-block-deployer plugin falis to build war file
Key: COCOON-2007
URL: https://issues.apache.org/jira/browse/COCOON-2007
Project: Cocoon
Issue Type: Bug
Components: * Cocoon
[
https://issues.apache.org/jira/browse/COCOON-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Knecht updated COCOON-2007:
-
Attachment: deployer-pom.diff
patch for cocoon-block-deployer pom.xml
cocoon-block-deployer
37 matches
Mail list logo
