Grzegorz Kossakowski wrote:
Reinhard Poetz pisze:
Joerg Heinicke wrote:
On 12.01.2008 21:20, [EMAIL PROTECTED] wrote:
Could it be we switched from status.xml to changes.xml? :)
yes. We had some discussion about it when I switched our doc generation to
be based on Maven 2. The only
Grzegorz Kossakowski wrote:
Carsten Ziegeler pisze:
Grzegorz Kossakowski wrote:
Grzegorz Kossakowski pisze:
Committed approx twelve hours ago and still our site is not updated.
Anyone has an idea what's going on?
Did you do an svn up on people.apache.org:/www/cocoon.apache.org ?
No, I
Grzegorz Kossakowski wrote:
Reinhard Poetz pisze:
IIRC an 'svn up' is done by a cron job automatically every hour.
Apparently, it does not work any more. Do you know who has set up this cron
job?
Sorry, no idea.
--
Reinhard PötzManaging Director, {Indoqa} GmbH
hepabolu wrote:
Reinhard, would a single version-based collection be enough to extract
the documents for a specific version or does your exporter work
differently?
No, that's not enough. There is a mapping of a collection to the URI space where
its documents get deployed to.
--
Reinhard
Joerg Heinicke wrote:
On 08.01.2008 14:45, Grzegorz Kossakowski wrote:
We were not shipping samples because samples should depend on released
artifacts, only. Anyway, I
agree that we need to find a way for distribution of our samples.
However, I wonder how we will treat them? As official
Ralph Goers wrote:
No. We could take advantage of http://maven.apache.org/ant-tasks.html to
create various ant scripts to do that. However, since I'm still not
sure what this supposed support for non-maven builds really looks like
it is hard to have a good answer to the question.
Yes,
Carsten Ziegeler wrote:
Ok, the file was deleted with r581188.
Uuups, that was me. I'm sorry :-(
I'll restored and updated the file.
Interesting that no user complained in the meantime about a missing
download page
downloading Cocoon 2.1.10 required an additional mouse click (or two)
Carsten Ziegeler wrote:
Reinhard Poetz wrote:
Carsten Ziegeler wrote:
downloading Cocoon 2.1.10 required an additional mouse click (or two)
but was still possible.
Ah, ok - how?
Go to http://cocoon.apache.org/mirror.cgi, choose any of the mirrors, select
cocoon and then you're
Grzegorz Kossakowski wrote:
Carsten Ziegeler pisze:
Grzegorz Kossakowski wrote:
Carsten Ziegeler pisze:
If you give me a link I can add it to the main page. Or if you want to
do it yourself just edit
these pages:
http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g1/1285.html
Vadim Gritsenko wrote:
On Jan 5, 2008, at 9:53 AM, hepabolu wrote:
Grzegorz Kossakowski said the following on 5/1/08 13:51:
Hi,
I added[1] FAQ-entry for the subject of much controversy among Cocoon
community. Now I wonder how to
get it published, I found old document aggregating all FAQ
Grzegorz Kossakowski wrote:
Hello,
I was working on fixing documentation publishing and I quite satisfied with
results.
:-)
Yesterday I was trying to run 'mvn site-deploy' but always run into some strange
Maven exceptions coming from Wagon (I guess that there was a release of Wagon
which
Can somebody explain the purpose of this code to me? What's the use case that
makes a second request necessary?
public InputStream getInputStream() throws IOException,
SourceException {
try {
connect();
if (servletConnection.getResponseCode() !=
Carsten Ziegeler wrote:
It seems that Daisy is not running properly:
http://cocoon.zones.apache.org/daisy/
Thanks for spotting. I've restarted the Daisy wiki server and it runs properly
again.
--
Reinhard PötzManaging Director, {Indoqa} GmbH
Carsten Ziegeler wrote:
How is this related to a final 2.2 release? Are we planning to release
2.2 soon?
Yes, I want to work on the final release in the second week of January again. I
can't say how much time I can dedicate to the release work, but I guess that we
can ship the release by
Was it me who caused these test errors?
Continuum VMBuild Server wrote:
[INFO] Building Cocoon Forms Block Implementation
[INFO]task-segment: [clean, install]
[INFO]
Grzegorz Kossakowski wrote:
[EMAIL PROTECTED] pisze:
Author: reinhard Date: Mon Dec 31 03:02:53 2007 New Revision: 607723
URL: http://svn.apache.org/viewvc?rev=607723view=rev Log: COCOON-1831 Pass
data from the parent request to the child request. This time session
handling is also included
We at Indoqa have started to think about working on a slimmed down version of
Cocoon 2.2 (Micro-Cocoon). By doing this we pursue a couple of goals:
o increase the maintainability of Cocoon
(Cocoon 2.2 is already a big improvement but still too complicated
in some areas)
o optimize
Grzegorz Kossakowski wrote:
o aspect-oriented profiling of pipelines
Could you elaborate on this? I may not know all fashionable terminology. :-)
My idea is that profiling should only be an aspect on pipeline processing. In
2.1/2.2 you have to use a different pipeline implementation for
Grzegorz Kossakowski wrote:
Ralph Goers pisze:
Use the whiteboard. The only areas of concern I have is with regard to
sub-sitemaps and resources. But I reserve judgment on that until I see what
you come up with.
Hi Ralph,
When it comes to resources, we have a replacement for that already.
Grzegorz Kossakowski wrote:
Reinhard Poetz pisze:
My idea is that profiling should only be an aspect on pipeline processing.
In 2.1/2.2 you have to use a different pipeline implementation for
profiling - I think we can do better.
Ahh, got it. If we architect API of pipelines well we
[
https://issues.apache.org/jira/browse/COCOON-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554947
]
Reinhard Poetz commented on COCOON-1831:
Thanks for the update on your patch. I had already been wondering
[
https://issues.apache.org/jira/browse/COCOON-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554665
]
Reinhard Poetz commented on COCOON-1831:
yes, I understand and agree. But Grek's and my question is why do
[
https://issues.apache.org/jira/browse/COCOON-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reinhard Poetz updated COCOON-1831:
---
Affects version (Component): Parent values: Servlet Service
Framework(10175
[
https://issues.apache.org/jira/browse/COCOON-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reinhard Poetz updated COCOON-1831:
---
Other Info: [Patch available]
Passing parameters to sub calls
Ralph Goers wrote:
Thanks for the explanation, except I'm still not clear what a
connection name is. See below for my 2 cents.
Grzegorz Kossakowski wrote:
The only problem is that we have no way to check if given URI contains
connection name or servlet
ID. Therefore the idea to add special
Grzegorz Kossakowski wrote:
Reinhard Poetz pisze:
ServletSource is only available if you use the ServletService Framework
together with Cocoon. So I think that ServletConnection should become
public API too.
We could offer two types of ServletConnections:
* RelativeServletConnection
Vadim Gritsenko wrote:
On Dec 26, 2007, at 4:01 PM, Grzegorz Kossakowski wrote:
Plus sign doesn't look naturally for me. Are there any other options?
How about
servlet:com.mycompany.project.servlet.service:!/test/foo/bar
Hmmm, I'm not perfectly happy with this solution either. In this
[
https://issues.apache.org/jira/browse/COCOON-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reinhard Poetz reassigned COCOON-1831:
--
Assignee: Reinhard Poetz (was: Grzegorz Kossakowski)
Finish blocks-fw
[
https://issues.apache.org/jira/browse/COCOON-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reinhard Poetz reassigned COCOON-2154:
--
Assignee: Reinhard Poetz
Servlet:/ protocol: Support absolute URIs
framework
Reporter: Reinhard Poetz
Using the servlet-protocol you can only define relative URIs which means that
those URIs are only valid if they are resolved in the context of a particular
servlet-service because they refer to the defines connections.
If you need globally resolveable
Grzegorz Kossakowski wrote:
Reinhard Poetz (JIRA) pisze:
Servlet:/ protocol: Support absolute URIs
-
Key: COCOON-2154 URL: https://issues.apache.org/jira/browse/COCOON-2154
Project: Cocoon Issue Type: New Feature Components: - Servlet service
framework
Joerg Heinicke wrote:
Just curious: Is there a reason for having identical TraxTransformer and
XSLTTransformer? If it is just for the name why does the one not extend
the other?
IIRC one has been springified (or is on the way to become a pojo).
--
Reinhard Pötz
Vadim Gritsenko wrote:
On Dec 19, 2007, at 11:08 AM, Reinhard Poetz wrote:
Vadim Gritsenko wrote:
Generally, making sure that 2.1 functionality is working fine in 2.2
is more critical. Once it is all there, we can finally make a beta
release.
What do you mean by beta?
It is getting
Vadim Gritsenko wrote:
On Dec 20, 2007, at 5:29 AM, Reinhard Poetz wrote:
We have already shipped snip release candiates of Cocoon 2.2. I'm a
bit puzzled why we should switch our agreed release strategy now.
I've not said a word about switching - comment was related to the
de-facto state
Unfortunatly I don't have the necessary spare time to work on Cocoon this week.
Considering holidays and a busy first week in January, probably the earliest
possible date when I can work on Cocoon more than an hour from time to time is
in the middle of January.
Except from documentation
Reinhard Poetz wrote:
Apart from that I will also work on providing packages for all released
modules.
By packages I meant official release binaries that contains the sources, the
compiled classes, the JAR, docs etc. that can be downloaded (mostly) by
non-Maven-2 users.
--
Reinhard Pötz
Felix Knecht wrote:
To who it may concern when releasing
There seems to be a problem with the sources plugin people from the
maven project run into [1]:
zitate
The -sources jar that is generated does not contain the required NOTICE
and LICENSE files. Thus, it's not releasable according to
Vadim Gritsenko wrote:
Generally, making sure that 2.1 functionality is working fine in 2.2 is
more critical. Once it is all there, we can finally make a beta release.
What do you mean by beta?
--
Reinhard PötzManaging Director, {Indoqa} GmbH
Sylvain Wallez wrote:
Reinhard Poetz wrote:
Recently I've been thinking more and more about some kind of
Micro-Cocoon[*] that consists of
o a slimmed-down sitemap language available in as an XML and as a
Java dialect
(no component declarations, no sub-sitemaps, no resources, merged
Vadim Gritsenko wrote:
On Dec 7, 2007, at 2:59 AM, Carsten Ziegeler wrote:
Vadim Gritsenko wrote:
Thanks for quick fix! btw why bean is named
org.apache.cocoon.portal.om.CopletAdapter.cocoon and not
org.apache.cocoon.portal.om.CopletAdapter/cocoon?
Good question - to be honest, I don't
Vadim Gritsenko wrote:
On Dec 7, 2007, at 9:25 AM, Reinhard Poetz wrote:
Vadim Gritsenko wrote:
On Dec 7, 2007, at 2:59 AM, Carsten Ziegeler wrote:
Vadim Gritsenko wrote:
Thanks for quick fix! btw why bean is named
org.apache.cocoon.portal.om.CopletAdapter.cocoon
Giacomo Pati wrote:
Hi all
Is there a problem upgrading the cocoon-lucene block to newest Lucene (from
1.4.3 to 2.2.0). To me
that block seems quite outdated (we use it but now it bites us with other
components building up
from Lucene 2.2.0)
If not I'll see that I can upgrade it, ok?
Fine
Honig, Job wrote:
Hi,
I am trying to port some cocoon projects to cocoon 2.2 as well as to
create a new project.
I have already stumbled upon a few problems with installation, which
were caused by inaccurate docs. Also I found typos.
I am willing to help improve the docs to avoid such
Ralph,
First I want to say, that I'm very much appreciating having this discussion with
you. Find my comments inline.
Ralph Goers wrote:
Reinhard Poetz said:
I agree with you but let me give you some reasoning that has lead to this
misture:
The problem is that developing really RESTful
Sylvain Wallez wrote:
Reinhard Poetz wrote:
snip/
For me those are the reasons why I said that I have changed the camp
and think that Stefano was right with his opinion that traditional web
frameworks would become obsolete. But, in contrast to him, I think
that Cocoon, which in some respect
Carsten Ziegeler wrote:
I might be mistaken but I have the feeling that this discussion mixes
things a little bit. Once thing is REST and another thing is javascript.
I can use/follow one of them wihtout using/following the other.
It might be true that using AJAX makes developing RESTful
Ralph Goers wrote:
Reinhard Poetz wrote:
I was referring to your Javascript argument: I certainly won't get in
your way, but I just don't believe we'll get there into browsers
evolve into something smarter than what they are today. We went
through great pains removing a ton of Javascript
Ralph Goers wrote:
Reinhard Poetz wrote:
Ralph Goers wrote:
I suppose REST is fine for some trivial applications on the web tier,
I disagree with this statement. REST is an architectural style and I'm
sure, following those principles will help you to build applications
from trivial
Ralph Goers wrote:
Reinhard Poetz wrote:
Have you visited Amazon.com or some of Google's apps recently?
Just went to Amazon. I immediately noticed that they set cookies named
session-id, session-time, and session-token. Somehow that doesn't
seem completely stateless to me.
I was referring
Ralph Goers wrote:
Carsten Ziegeler wrote:
Grzegorz Kossakowski wrote:
It may sound controversial but I think that things like information
about user locale or preferences
should be kept in URL (preferably in path part or in request
parameters). If data set is too big,
URL should contain an
Grzegorz Kossakowski wrote:
Reinhard Poetz pisze:
Carsten Ziegeler wrote:
Reinhard Poetz wrote: What happens if a sub request accesses the session?
Is an artifical one created?
The current implementation returns an unusable implementation of a session
which needs to fixed in some way.
After
[EMAIL PROTECTED] wrote:
Author: reinhard
Date: Thu Nov 29 14:06:11 2007
New Revision: 599593
URL: http://svn.apache.org/viewvc?rev=599593view=rev
Log:
- pass attributes, headers and parameters from parent request to sub request
- expand sample
Since I remember some discussions about passing
Grzegorz Kossakowski wrote:
[EMAIL PROTECTED] pisze:
Author: reinhard
Date: Thu Nov 29 14:06:11 2007
New Revision: 599593
URL: http://svn.apache.org/viewvc?rev=599593view=rev
Log:
- pass attributes, headers and parameters from parent request to sub request
- expand sample
Hi Reinhard,
I
[
https://issues.apache.org/jira/browse/COCOON-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546938
]
Reinhard Poetz commented on COCOON-1831:
I've applied the patch except the part that deals with accessing
Carsten Ziegeler wrote:
Reinhard Poetz wrote:
[EMAIL PROTECTED] wrote:
Author: reinhard
Date: Thu Nov 29 14:06:11 2007
New Revision: 599593
URL: http://svn.apache.org/viewvc?rev=599593view=rev
Log:
- pass attributes, headers and parameters from parent request to sub
request
- expand sample
Ralph Goers wrote:
Reinhard Poetz wrote:
Ralph Goers wrote:
Is the cocoon build really trying to rely on transitive dependency
verions? Very bad idea. Versions of every dependency cocoon uses
directly or indirectly should be specified in the managedDependencies.
The problem
Carsten Ziegeler wrote:
Reinhard Poetz wrote:
Since I've been running successfully two of my custom Cocoon 2.2 apps
with Spring 2.5-rc2
(http://opensource.atlassian.com/projects/spring/browse/SPR-4081), I
upgraded trunk to use Spring 2.5. Since it is aimed to be a drop-in
replacement for 2.0.x
Joerg Heinicke wrote:
On 25.11.2007 10:32 Uhr, Grzegorz Kossakowski wrote:
I'm quite reluctant to accept this patch because I believe that one
should never rely on block's
directory location
Why? It might be necessary when communicating with other systems. There
is no difference than with
Joerg Heinicke wrote:
But how to trace it back when the dependency report does not even
mention it. I wonder if I'm actually the only one with this problem?
It's probably not critical since it seems to occur only with the Eclipse
plugin and fixing the build path is easy. But it might point to
Ralph Goers wrote:
Is the cocoon build really trying to rely on transitive dependency
verions? Very bad idea. Versions of every dependency cocoon uses
directly or indirectly should be specified in the managedDependencies.
The problem is that the groupId of the Avalon framework changed and
Vadim Gritsenko wrote:
The error message on the console seems to point to an error in the
servlet service framework since it tries to reset the response despite
it already has been committed.
Yeah... This IllegalStateException - I'm not sure why it is happening,
but I also see it
Joerg Heinicke wrote:
And what can be the actual reason for the error. I grepped the code base
and did not find any reference to 'file-generator.pool-max'.
My first guess was that somebody tries to set this property but Spring doesn't
find a placeholder where this property can be applied.
Since I've been running successfully two of my custom Cocoon 2.2 apps with
Spring 2.5-rc2
(http://opensource.atlassian.com/projects/spring/browse/SPR-4081), I upgraded
trunk to use Spring 2.5. Since it is aimed to be a drop-in replacement for
2.0.x, I don't expect problems. Doing the upgrade
Daniel Fagerstrom wrote:
Now we can also think about merging Daniel's work on OSGi
(whiteboard), which requires Spring-OSGi, with trunk. Daniel, maybe
you can share your thoughts on what this would mean for trunk (build
system, required code changes, etc.) and how we can keep the
experimental
Grzegorz Kossakowski wrote:
Carsten Ziegeler pisze:
I know that this has been discussed in the past
several times ;-)
, but nevertheless do we
really think that urls like
http://cocoon.apache.org/2.2/1290_1_1.html
are suited for a top web framework of the 21st century? 1290_1_1 has
Grzegorz Kossakowski wrote:
Reinhard Poetz pisze:
We should create a seperate documentation for it and list it at the page
that contains all our blocks.
I still don't follow you here. We already released a few cocoon-databases-*
modules like: cocoon-databases-impl cocoon-databases-hsqldb
Grzegorz Kossakowski wrote:
Hello,
I would like to release first milestone of cocoon-databases-bridge module
upcoming days. I hope that
nobody objects?
It's going to be my first release so I will probably need some assistance.
Grek,
thanks for pushing on releasing another block I guess
Grzegorz Kossakowski wrote:
Reinhard Poetz pisze:
Grek,
thanks for pushing on releasing another block I guess that you don't
have a PGP key which is signed by other ASF folks. If I'm right this
means that you can't create the release artifacts yourself.
Yep. Did we forget that GT was a great
Thorsten Scherler wrote:
Hi all,
I just committed a first cocoon 2.2 block in the forrest
http://svn.apache.org/viewvc?view=revrevision=591961
The question now is how can we publish a snapshot of this block to the
maven repo?
As an Apache committer you should be able to deploy to the Maven 2
Reinhard Poetz wrote:
Vadim Gritsenko wrote:
Grzegorz Kossakowski wrote:
Vadim, have you seen our whiteboard with the list of things people
have been wondering about when it
came to deprecation?
Seen it but I would not be able to recall it.
I remember though that it was acknowledged
The Apache Cocoon Community is proud to announce the second release
candidate of Cocoon 2.2.
Apache Cocoon is a Spring-based framework (since version 2.2) built
around the concepts of separation of concerns and component-based development.
Cocoon implements these concepts around the
Thorsten Scherler wrote:
On Tue, 2007-10-30 at 12:43 +0100, Thorsten Scherler wrote:
Hi all,
I am trying to get started with cocoon 2.2 development and need to write
my own custom transformer.
Since I will start from scratch I directly want to start using Spring
instead of Avalon.
Is
Reinhard Poetz wrote:
Grzegorz Kossakowski wrote:
BTW. When can we expect new release officialy announced?
I've started to work on it together with a What's new in Cocoon 2.2
page and hope to finish it this weekend.
Could somebody help me please with proof-reading the announcment message
Jeroen Reijn wrote:
Reinhard Poetz wrote:
Reinhard Poetz wrote:
Grzegorz Kossakowski wrote:
BTW. When can we expect new release officialy announced?
I've started to work on it together with a What's new in Cocoon 2.2
page and hope to finish it this weekend.
Could somebody help me
Giacomo Pati wrote:
Reinhard Poetz wrote:
Reinhard Poetz wrote:
Grzegorz Kossakowski wrote:
BTW. When can we expect new release officialy announced?
I've started to work on it together with a What's new in Cocoon 2.2
page and hope to finish it this weekend.
Could somebody help me please
hepabolu wrote:
Reinhard Poetz said the following on 26/10/07 18:34:
Grzegorz Kossakowski wrote:
BTW. When can we expect new release officialy announced?
I've started to work on it together with a What's new in Cocoon 2.2
page and hope to finish it this weekend.
Sorry to reply so late
Grzegorz Kossakowski wrote:
BTW. When can we expect new release officialy announced?
I've started to work on it together with a What's new in Cocoon 2.2 page and
hope to finish it this weekend.
--
Reinhard PötzManaging Director, {Indoqa} GmbH
András Hatvani wrote:
Hi Joerg,
thanks for your quick reply and sorry for my delay.
On the page http://cocoon.apache.org/2.2/blocks/1204_1_1.html you wrote:
This list of blocks hasn't been released yet. Your help is more than
appreciated to make them ready for a release as Cocoon 2.2 block.
I
Philipp Zerelles wrote:
Is the reloading classloader in trunk not working currently? I checked out
trunk an hour ago and tried the first steps as described on the web page,
including the RCL setup. But the RCL somehow does not see changes to java
files I make.
does everything else work
Grzegorz Kossakowski wrote:
Reinhard Poetz pisze:
+1
Let's fix this for the final 2.2 release and work in parallel on the
springification. As soon as it is done, we branch off 2.2 and merge the
springified Cocoon back into trunk.
WDOT?
I don't agree with this. I would choose following
Reinhard Poetz wrote:
I've prepared another series of releases from trunk, see the list of all 45
artifacts below.
[...]
SUBPROJECT: COCOON CONFIGURATION
- cocoon-configuration-api-1.0.1.jar
- cocoon-spring-configurator-1.0.1.jar
SUBPROJECT
[
https://issues.apache.org/jira/browse/COCOON-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reinhard Poetz reassigned COCOON-1354:
--
Assignee: Cocoon Developers Team (was: Reinhard Poetz)
I applied the patch to trunk
Hanne Moa wrote:
I have the user hm at http://cocoon.zones.apache.org/daisy/ and would
like to do more than commenting. As in: fixing typos and other errors
and adding howtos and FAQs. On the GT it was said the thing to do was to
write here and ask for a role-change and by this mail I am doing
Vadim Gritsenko wrote:
Hi,
Ok I'm confused about AbstractLogEnabled business. Is it correct that
instead of org.apache.avalon.framework.logger.AbstractLogEnabled we
should be using org.apache.cocoon.util.AbstractLogEnabled [1]?
If yes, why there are only 2 usages of the latter and around
[EMAIL PROTECTED] wrote:
A document has been updated:
http://cocoon.zones.apache.org/daisy/documentation/1419.html
Document ID: 1419
Branch: main
Language: default
Name: Cocoon 2.2 Migration Guide (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 10/16/07 3:24:54 PM
Updated
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
For me the most important aspect in this matter is that users
shouldn't be forced to recompile their stuff if they don't want to.
I don't think this is a realistic expectation for the major (2.X is
major in our numbering scheme) release. I'd
Vadim Gritsenko wrote:
Hi,
New site has little 'home' icon in top-left corner with a link, but
regardless of link text, it always points to the same place -
http://cocoon.apache.org/, instead of home of the current module/block/etc:
http://cocoon.apache.org/2.2/blocks/ - Cocoon Blocks 2.2 -
I've prepared another series of releases from trunk, see the list of all 45
artifacts below. This time most of the modules are proposed to be released as
RC2 (release candidate 2) or RC1.
This is probably be the last release before the final release of all those
modules. For this final
The proposed release artifacts of all the modules that we vote on (see the
seperate voting thread) are available at http://people.apache.org/builds/cocoon/
The easiest way to test the artifacts is by adding a cocoon-staging profile to
your ~/.m2/settings.xml:
settings
profiles
profile
Reinhard Poetz wrote:
I've prepared another series of releases from trunk
+1
--
Reinhard PötzManaging Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer
As I announced in the RC2 voting thread, I think that it is time for the final
release of Cocoon 2.2. What issues are open that have to be resolved by then?
Here is the list of items that I've found:
- provide a migration guide (???)
- deprecation (???)
We have to deprecate everything
As promised at the GetTogether, I wrote some documentation about how our docs
can be published.
In order to make it as simple as possible, I've setup a nightly build (2am UTC)
of our docs on cocoon.zones.apache.org. The only thing that I can't do is
checking the document in into the SVN
[EMAIL PROTECTED] wrote:
Author: jheymans
Date: Thu Oct 11 01:31:56 2007
New Revision: 583731
URL: http://svn.apache.org/viewvc?rev=583731view=rev
Log:
test commit
It was me who did this commit because Jorg has stored his SVN credentials on the
zone. I deleted them.
To anybody who wants to
Daniel Fagerstrom wrote:
Reinhard Poetz skrev:
Don't get me wrong. I would love to move to Spring sooner than later
but I wonder if this wouldn't be a too big step.
Starting to think so as well.
For the moment I would propose that we fork cocoon-pipeline-components
and cocoon-sitemap
I've been working on setting up build scripts for our docs on our zone so that
we
- can create our docs and publish them to
http://cocoon.zones.apache.org/dev-docs/
- they can be easily checked in into our SVN - you only have to login to
cocoon.zone and invoke
'svn commit
Today I've been setting up some shell scripts that make it easy for everybody to
publish docs. The only problem I run into now is that if I run the site
generation, every page is changed because of the publication date.
This will cause a lot of commits that only change the publication date.
Reinhard Poetz wrote:
I've been working on setting up build scripts for our docs on our zone
so that we
- can create our docs and publish them to
http://cocoon.zones.apache.org/dev-docs/
- they can be easily checked in into our SVN - you only have to login to
cocoon.zone and invoke
[EMAIL PROTECTED] wrote:
Some suggestions for:
Cocoon 2.2 - All Sitemap Components
http://cocoon.apache.org/2.2/1347_1_1.html
1. Make names in second column into links and delete the third column.
Having a Details column wastes space and reduces usability.
USECASE: I want FileGenerator. I am
Leszek Gawron wrote:
I suggest that when Springifiing components, we just remove the Avalon
stuff.
WDYT?
+1
lovely, less work for me :)
and seriously: +1
Do we really want to springify trunk *now*? The problem is that the migration of
Cocoon 2.1 apps gets more difficult if you have to
Leszek Gawron wrote:
Reinhard Poetz wrote:
Leszek Gawron wrote:
I suggest that when Springifiing components, we just remove the Avalon
stuff.
WDYT?
+1
lovely, less work for me :)
and seriously: +1
Do we really want to springify trunk *now*? The problem is that the
migration of Cocoon
301 - 400 of 2579 matches
Mail list logo
