Re: svn commit: r682901 - /cocoon/trunk/tools/pom.xml

[EMAIL PROTECTED] pisze: Author: reinhard Date: Tue Aug 5 12:42:45 2008 New Revision: 682901 URL: http://svn.apache.org/viewvc?rev=682901view=rev Log: back in snapshot mode Modified: cocoon/trunk/tools/pom.xml Modified: cocoon/trunk/tools/pom.xml URL:

Re: [summary] [vote] Thorsten Scherler as new Cocoon committer

On Tue, 2008-08-05 at 12:58 +1000, David Crossley wrote: David Crossley wrote: I propose Thorsten Scherler as a new Cocoon committer and PMC member. During the time period there were no negative votes, and more than 3 positive votes. Thank you very much all of you, it is a big honor for

Re: [Vote] Jasha Joachimsthal as new Cocoon committer

Andrew Savory wrote: It's my pleasure to propose Jasha Joachimsthal as a new committer on the Apache Cocoon project. +1 from me. -David

Is it necessary to increase the development version number (SNAPSHOT) after a release?

Grzegorz Kossakowski wrote: [EMAIL PROTECTED] pisze: Author: reinhard Date: Tue Aug 5 12:42:45 2008 New Revision: 682901 URL: http://svn.apache.org/viewvc?rev=682901view=rev Log: back in snapshot mode Modified: cocoon/trunk/tools/pom.xml Modified: cocoon/trunk/tools/pom.xml URL:

Re: Is it necessary to increase the development version number (SNAPSHOT) after a release?

Reinhard Pötz pisze: yes, I was too lazy to touch nearly every POM file in our repository just to increase the version number of our parent POMs. I haven't done this for the last release either and AFAICT, no problem occurred. Hmmm, find, xargs and sed should do this work within one minute.

Re: Is it necessary to increase the development version number (SNAPSHOT) after a release?

Reinhard Pötz schrieb: Grzegorz Kossakowski wrote: [EMAIL PROTECTED] pisze: Author: reinhard Date: Tue Aug 5 12:42:45 2008 New Revision: 682901 URL: http://svn.apache.org/viewvc?rev=682901view=rev Log: back in snapshot mode Modified: cocoon/trunk/tools/pom.xml Modified:

Re: Webdav and link-rewrite

Reinhard Pötz wrote: Grzegorz Kossakowski wrote: Reinhard Pötz pisze: Grzegorz Kossakowski wrote: Reinhard Pötz pisze: I had a brief look at the link-rewrite block and think now that the migration of the LinkrewriterTransformer will be difficult because of its configuration can't be

Daisy Account

Hello, can someone please change my Daisy account (username: lukaslang) role, so that I can add block documentation. Thanks in advance, Lukas

Re: Daisy Account

Lukas Lang pisze: Hello, can someone please change my Daisy account (username: lukaslang) role, so that I can add block documentation. Added you to doc-editors role. You should be able to edit documentation. Thanks for your work Lukas. -- Grzegorz Kossakowski

[vote] Cocoon 3.0

Following the result of our recent discussion about the future of Corona, I propose Corona to become Cocoon 3. This means that any reference on Corona in source files, package names, artifact ids, group ids or anywhere else will be dropped and the standard Cocoon namespace

[vote] Release of servlet-service-impl-1.1.0, spring-configurator-2.0.0, jnet-1.0.0, block-deployment-1.0.0, cocoon-maven-plugin-1.0.0-M3

I've prepared the artifacts for the release of our four subprojects: Cocoon Servlet-Service Framework Impl 1.1.0 ~~~ The most important change is that it doesn't depend on the Cocoon source resolver any more. Custom protocols (e.g. block-context) can

Re: [vote] Cocoon 3.0

Reinhard Pötz schrieb: Following the result of our recent discussion about the future of Corona, I propose Corona to become Cocoon 3. +1 Felix

Re: [vote] Cocoon 3.0

Hi 2008/8/6 Reinhard Pötz [EMAIL PROTECTED]: Following the result of our recent discussion about the future of Corona, I propose Corona to become Cocoon 3. +1 (The king is dead, long live the king!) Andrew. -- [EMAIL PROTECTED] / [EMAIL PROTECTED] http://www.andrewsavory.com/

Re: [vote] Cocoon 3.0

Reinhard Pötz skrev: Following the result of our recent discussion about the future of Corona, I propose Corona to become Cocoon 3. This means that any reference on Corona in source files, package names, artifact ids, group ids or anywhere else will be dropped and the standard Cocoon

Re: [vote] Cocoon 3.0

On Wed, 2008-08-06 at 13:19 +0200, Reinhard Pötz wrote: Following the result of our recent discussion about the future of Corona, I propose Corona to become Cocoon 3. +1 salu2 -- Thorsten Scherler thorsten.at.apache.org Open Source Java

Re: [vote] Cocoon 3.0

+1 Carsten Reinhard Pötz wrote: Following the result of our recent discussion about the future of Corona, I propose Corona to become Cocoon 3. This means that any reference on Corona in source files, package names, artifact ids, group ids or anywhere else will be dropped and the

Re: Is it necessary to increase the development version number (SNAPSHOT) after a release?

Reinhard Pötz wrote: yes, I was too lazy to touch nearly every POM file in our repository just to increase the version number of our parent POMs. I haven't done this for the last release either and AFAICT, no problem occurred. Does anybody know if it can cause problems if the development

Re: Is it necessary to increase the development version number (SNAPSHOT) after a release?

Carsten Ziegeler wrote: Reinhard Pötz wrote: yes, I was too lazy to touch nearly every POM file in our repository just to increase the version number of our parent POMs. I haven't done this for the last release either and AFAICT, no problem occurred. Does anybody know if it can cause

Re: Is it necessary to increase the development version number (SNAPSHOT) after a release?

Reinhard Pötz wrote: I was releasing cocoon-parent because I wanted to use the latest versions of some plugins and some dependencies (e.g. Spring). Ah yes, ok - Personally I would not change the references of all modules to the latest snapshot of the parent pom after a release. The modules

Re: Is it necessary to increase the development version number (SNAPSHOT) after a release?

Grzegorz Kossakowski wrote: Reinhard Pötz pisze: yes, I was too lazy to touch nearly every POM file in our repository just to increase the version number of our parent POMs. I haven't done this for the last release either and AFAICT, no problem occurred. Hmmm, find, xargs and sed should do

Cocoon GT 2008

Dear Devs Nearly a month ago I have asked on the user list if there is any news about the Cocoon GT in 2008. Since I did not have any response I repost my question to the dev-list. I would really appreciate to meet the community again this year. So do we will have a Cocoon GT this year? For your

RE: [vote] Cocoon 3.0

-Original Message- From: Reinhard Pötz [mailto:[EMAIL PROTECTED] Sent: woensdag 6 augustus 2008 13:20 To: dev@cocoon.apache.org Subject: [vote] Cocoon 3.0 Following the result of our recent discussion about the future of Corona, I propose Corona to become Cocoon 3. This

RE: [vote] Java 1.5 as minimal requirement for trunk

-Original Message- From: Grzegorz Kossakowski [mailto:[EMAIL PROTECTED] Sent: dinsdag 5 augustus 2008 15:08 To: Cocoon's dev mailing list Subject: [vote] Java 1.5 as minimal requirement for trunk Hello, As discussed in thread Cocoon-jms-sample requires Java = 1.5[1] there are

Re: [vote] Cocoon 3.0

On Wed, Aug 6, 2008 at 6:19 AM, Reinhard Pötz [EMAIL PROTECTED] wrote: Following the result of our recent discussion about the future of Corona, I propose Corona to become Cocoon 3. +1 Seems a little weird but I certainly don't have any better alternatives. -- Peter Hunsberger

Re: [vote] Cocoon 3.0

+1 Reinhard Pötz wrote: Following the result of our recent discussion about the future of Corona, I propose Corona to become Cocoon 3. This means that any reference on Corona in source files, package names, artifact ids, group ids or anywhere else will be dropped and the standard Cocoon

Re: Is it necessary to increase the development version number (SNAPSHOT) after a release?

Reinhard Pötz wrote: Grzegorz Kossakowski wrote: [EMAIL PROTECTED] pisze: Author: reinhard Date: Tue Aug 5 12:42:45 2008 New Revision: 682901 URL: http://svn.apache.org/viewvc?rev=682901view=rev Log: back in snapshot mode Modified: cocoon/trunk/tools/pom.xml Modified:

Re: Is it necessary to increase the development version number (SNAPSHOT) after a release?

Ralph Goers wrote I'm actually working on a fix to maven for this at the moment. It would allow you to put versionMAVEN_PARENT_VERSION/version in the pom instead of an actual version number. Don't get your hopes up though. I've been working on this for the last few weeks in the precious little

Re: [vote] Cocoon 3.0

Reinhard Pötz reinhard at apache.org writes: Following the result of our recent discussion about the future of Corona, I propose Corona to become Cocoon 3. +1 Joerg

Re: [vote] Java 1.5 as minimal requirement for trunk

Grzegorz Kossakowski grek at tuffmail.com writes: switching to Java 1.5 as minimal required version +1 Joerg

Re: Is it necessary to increase the development version number (SNAPSHOT) after a release?

It uses the relative path so you will need the parent also. Carsten Ziegeler wrote: Ralph Goers wrote I'm actually working on a fix to maven for this at the moment. It would allow you to put versionMAVEN_PARENT_VERSION/version in the pom instead of an actual version number. Don't get your

[jira] Subscription: COCOON-open-with-patch

Issue Subscription Filter: COCOON-open-with-patch (108 issues) Subscriber: cocoon Key Summary COCOON-2228 StripNameSpacesTransformer does not strip namespace prefix of attributes https://issues.apache.org/jira/browse/COCOON-2228 COCOON- Add SaxParser configuration

[GSoC] Proposal modification

Hello, after investing some time in the WebDAV block and meeting Reinhard today, none of us can spot a way to migrate this block to Spring easily and provide integration tests with embedded Jackrabbit. Migration process originally aimed at removing Slide specific dependencies. Due to lack of