Re: [RESULT] [VOTE] Move Apache Cocoon into the Apache Attic

[Gabriel Gruber]

>> Can you explain why you didn't via https://github.com/apache/cocoon ?

Hmm, good question actually. I wasn’t aware that the PR functionality was 
actually really used to add enhancements to the project and I always felt a 
little bit lost with the formal/administrative rules to get patches to the 
project, without being an official committer.

Anyway I would be willing to add all necessary changes to make cocoon 
compatible with spring 5+ in a PR

Cheerio,
Gabriel


From: Torsten Curdt 
Date: Wednesday, 11. September 2024 at 10:59
To: dev@cocoon.apache.org 
Subject: Re: [RESULT] [VOTE] Move Apache Cocoon into the Apache Attic
It is sad, to let such a powerful project die. Having said that, we are using 
it still in production and trying to apply security patches on our own fork to 
make it compatible with newer versions of spring and java.

If the project would continue on github, I can just stress again that I would 
be very happy to participate and share all our patches.

Can you explain why you didn't via https://github.com/apache/cocoon ?

Just trying to understand whether github would really make a difference.

While I am still +1 for the attic (because I don't see anyone working on Cocoon 
in any form),
it feels a little sad if there are individually maintained forks that could as 
well be part of the project.

cheers,
Torsten

Re: [RESULT] [VOTE] Move Apache Cocoon into the Apache Attic

[Torsten Curdt]

> It is sad, to let such a powerful project die. Having said that, we are
> using it still in production and trying to apply security patches on our
> own fork to make it compatible with newer versions of spring and java.
>
> If the project would continue on github, I can just stress again that I
> would be very happy to participate and share all our patches.
>

Can you explain why you didn't via https://github.com/apache/cocoon ?

Just trying to understand whether github would really make a difference.

While I am still +1 for the attic (because I don't see anyone working on
Cocoon in any form),
it feels a little sad if there are individually maintained forks that could
as well be part of the project.

cheers,
Torsten

Re: [RESULT] [VOTE] Move Apache Cocoon into the Apache Attic

[Gabriel Gruber]

Hello,

first of all thanks to Chris and his honesty to declare that the needed power 
and energy is just not enough to continue with the project.

It is sad, to let such a powerful project die. Having said that, we are using 
it still in production and trying to apply security patches on our own fork to 
make it compatible with newer versions of spring and java.

If the project would continue on github, I can just stress again that I would 
be very happy to participate and share all our patches.

Anyway, thank you all for your effort and maybe someone should try to just 
quickly describe what it practically means for cocoon. (documentation, 
soucecode, releases, jira project)

There is a page describing the general process

https://attic.apache.org/#:~:text=The%20Apache%20Attic%20was%20created,Attic%20Project%20%5B...%5D

Thanks
Gabriel

From: Rich Bowen 
Sent: Tuesday, September 10, 2024 7:04:47 PM
To: dev@cocoon.apache.org 
Subject: Re: [RESULT] [VOTE] Move Apache Cocoon into the Apache Attic



On 2024/08/29 15:12:33 Cédric Damioli wrote:
> Hi Chris,
>
> I saw in the last board's meeting notes than Rich wanted to pursue
> another roll call. Am I wrong here ?
> That's why I didn't vote on this thread in the first place.

Yeah, sorry to make this confusing. That was not my intent. The vote for attic 
seems to be pretty definitive, and I don't wish to interfere with the will of 
the project. I'd only ask that you be sure to announce it loudly on your 
dev/user lists, so that it doesn't come as a surprise.

--Rich

Re: [RESULT] [VOTE] Move Apache Cocoon into the Apache Attic

[Rich Bowen]

On 2024/08/29 15:12:33 Cédric Damioli wrote:
> Hi Chris,
> 
> I saw in the last board's meeting notes than Rich wanted to pursue 
> another roll call. Am I wrong here ?
> That's why I didn't vote on this thread in the first place.

Yeah, sorry to make this confusing. That was not my intent. The vote for attic 
seems to be pretty definitive, and I don't wish to interfere with the will of 
the project. I'd only ask that you be sure to announce it loudly on your 
dev/user lists, so that it doesn't come as a surprise.

--Rich

Re: [RESULT] [VOTE] Move Apache Cocoon into the Apache Attic

[Cédric Damioli]

Hi Chris,

I saw in the last board's meeting notes than Rich wanted to pursue 
another roll call. Am I wrong here ?

That's why I didn't vote on this thread in the first place.

I'm also sad to act the end of this great project but as you said, it's 
probably time to let it go ...


Cédric


Le 29/08/2024 à 13:02, Christofer Dutz a écrit :


So, the vote passes with 4 binding +1 votes and no other votes.

I guess the next step would be for the PMC Chair do add an attic 
resolution to the next month’s board agenda.


Apache Cocoon was the one project that brought me to Apache, even if 
it took a lng long time for me to really get involved.


It’s a little sad to see it go, but I guess there’s a time for 
everything and the time for XML has long time passed.


Thanks to all of you.

Chris

*Von: *Jörg Heinicke 
*Datum: *Donnerstag, 22. August 2024 um 09:52
*An: *dev@cocoon.apache.org 
*Betreff: *Re: [VOTE] Move Apache Cocoon into the Apache Attic

+1

Joerg

PS: I already gave my +1 two days ago, but my message might be stuck
somewhere.


On 20.08.24 11:39, Christofer Dutz wrote:
> Hi all,
>
> given that there is not enough remaining activity in the Apache Cocoon
> project, we would like to start a vote on moving Apache Cocoon into the
> Apache Attic.
>
> Please vote:
>
>   * +1 if you are in favor
>   * 0 if you are indifferent about it
>   * -1 if you are not in favor, but please provide reasoning
>
> I think given the low activity here, we should keep the vote open for a
> full week.
>
> Chris
>

Re: [VOTE] Move Apache Cocoon into the Apache Attic

[Jörg Heinicke]

+1

Joerg

PS: I already gave my +1 two days ago, but my message might be stuck
somewhere.


On 20.08.24 11:39, Christofer Dutz wrote:

Hi all,

given that there is not enough remaining activity in the Apache Cocoon
project, we would like to start a vote on moving Apache Cocoon into the
Apache Attic.

Please vote:

  * +1 if you are in favor
  * 0 if you are indifferent about it
  * -1 if you are not in favor, but please provide reasoning

I think given the low activity here, we should keep the vote open for a
full week.

Chris

Re: [VOTE] Move Apache Cocoon into the Apache Attic

[Jörg Heinicke]

+1

Regards,
Joerg

On 20.08.24 11:39, Christofer Dutz wrote:

Hi all,

given that there is not enough remaining activity in the Apache Cocoon
project, we would like to start a vote on moving Apache Cocoon into the
Apache Attic.

Please vote:

  * +1 if you are in favor
  * 0 if you are indifferent about it
  * -1 if you are not in favor, but please provide reasoning

I think given the low activity here, we should keep the vote open for a
full week.

Chris

Re: [VOTE] Move Apache Cocoon into the Apache Attic

[Francesco Chicchiriccò]

On 20/08/24 11:39, Christofer Dutz wrote:


Hi all,

given that there is not enough remaining activity in the Apache Cocoon project, 
we would like to start a vote on moving Apache Cocoon into the Apache Attic.

Please vote:

  * +1 if you are in favor
  * 0 if you are indifferent about it
  * -1 if you are not in favor, but please provide reasoning

I think given the low activity here, we should keep the vote open for a full 
week.


+1
Regards.

--
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/

Re: [VOTE] Move Apache Cocoon into the Apache Attic

[Torsten Curdt]

+1 sad but about time


 given that there is not enough remaining activity in the Apache Cocoon
> project, we would like to start a vote on moving Apache Cocoon into the
> Apache Attic.
>
>
>
> Please vote:
>
>- +1 if you are in favor
>- 0 if you are indifferent about it
>- -1 if you are not in favor, but please provide reasoning
>
>
>
> I think given the low activity here, we should keep the vote open for a
> full week.
>
>
>
> Chris
>

Re: [DISCUSS] Move Apache Cocoon to the attic?

[Cédric Damioli]

Hi,

IMHO, we tried last year to impulse some energy here, with a release, 
with more discussions than in the previous 8 years, but I think the 
conclusion is now pretty clear : still some interest, still some 
production users, but not enough to run an Apache-hosted community.

So moving to the Attic makes sense.

Cédric

Le 05/08/2024 à 14:38, Christofer Dutz a écrit :


Hi all,

even if I initially had plans for doing some experiments with Apache 
PLC4X and Apache Cocoon, I have come to the conclusion that this 
interest doesn’t seem to be shared by anyone who could possibly use 
the things I would be trying. Also am I currently struggling to avoid 
completely burning out. I would therefore like to revoke my raised hand.


I simply don’t have the energy to try and re-initialize a community 
around a project who’s core technologies are perceived old-falchioned 
(Even if I don’t see it that way)


I think we therefore should reinitiate the discussion on moving Apache 
Cocoon into the attic.


The Attic doesn’t have to be a dead end. If I or anyone else happen to 
find some fresh energy-batteries in the future, it has happened 
several times, that a project can be re-booted in the future.


I would therefore be in strong favor for moving Apache Cocoon into the 
Attic. I don’t think we would need a “last release”, as we just 
recently did that.


Chris

Re: [DISCUSS] Move Apache Cocoon to the attic?

[Torsten Curdt]

Even with people saying they would like to contribute nothing has happened
- in months. (no criticism)
As I said before - I think moving to the attic makes sense.
It would better reflect reality.

cheers,
Torsten

Re: Next steps?

[Gabriel Gruber]

+1

Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: Torsten Curdt 
Sent: Saturday, May 11, 2024 9:34:13 PM
To: dev@cocoon.apache.org 
Subject: Re: Next steps?



So, if I don’t hear anything else within the next 72h, I’ll initiate the Git 
migration.

+1

+1

 Torsten

Re: Next steps?

[Torsten Curdt]

> So, if I don’t hear anything else within the next 72h, I’ll initiate the
>> Git migration.
>>
>>
> +1
>

+1

 Torsten

>

Re: Next steps?

[Peter Hunsberger]

On Sat, May 11, 2024 at 12:18 PM Christofer Dutz 
wrote:

> So, as this project is so low-volume … I think I’ll do what I did with
> similar projects.
>
>
>
> So, if I don’t hear anything else within the next 72h, I’ll initiate the
> Git migration.
>
>
+1

>
>
> Chris
>
>
>
>
>
>
>
> *Von: *Christofer Dutz 
> *Datum: *Samstag, 11. Mai 2024 um 19:12
> *An: *dev@cocoon.apache.org 
> *Betreff: *Next steps?
>
> Hi all,
>
>
>
> So, it’s been a while and I think we were waiting for the results of the
> survey.
>
>
>
> Not quite sure what we agreed upon what the next steps were.
>
>
>
> So far, I think one of the first steps I recall was a formal migration to
> using Git as a primary SCM.
>
> If that’s the case I would volunteer to do that.
>
>
>
>
>
> Chris
>

Re: AW: Developer Survey Results

[Torsten Curdt]

>
> During the past years, I always felt it was somehow my duty as chair to
> write reports, ensure someone answers to incoming requests, etc...
> So yes it is formally a simple secretarial role, but as a someone only
> involved in a now-retired-version (2.1), I think it'd be good for the
> project that the chair is actually involved in the current live branch.
>
> So good news if you're willing to take the hat :)
>

+1 to all of that

Re: AW: Developer Survey Results

[Cédric Damioli]

During the past years, I always felt it was somehow my duty as chair to 
write reports, ensure someone answers to incoming requests, etc...
So yes it is formally a simple secretarial role, but as a someone only 
involved in a now-retired-version (2.1), I think it'd be good for the 
project that the chair is actually involved in the current live branch.


So good news if you're willing to take the hat :)

My 2 cents,
Cédric

Le 29/02/2024 à 16:48, Christofer Dutz a écrit :


Hi all,

Admittedly the Chair position is a simple secretarial role.

So, if this is the problem nobody wants to take on … I’d be willing to 
do that paperwork for a while.


Chris

*Von: *Torsten Curdt 
*Datum: *Donnerstag, 29. Februar 2024 um 01:19
*An: *dev@cocoon.apache.org 
*Betreff: *Developer Survey Results

The Developer survey is now open for 9 days.

We have received 10 responses.
5 were from PMC members.

Here are the results

https://app.edkimo.com/results/ewevipve

My takeaways:


- 7 disagree to retire
- only 10 responses is discouraging
- but 6 say they can make time and imagine to continue work on Cocoon
- I really hope the person that can imagine to be PMC chair will step 
forward
- 2.1 is still the most widely used version (and I am curious how this 
can be merged into a single path forward)



cheers,
Torsten

Re: [IMPORTANT] Developer Survey on the State of Cocoon

[Torsten Curdt]

> So, what’s the status of this?
> I haven’t started the Git migration as I thought it might make more sense
> to wait for the end of this.
>

I tried to wait as long as possible - but there ain't more responses coming
in I guess.

Let me send the results...

>

Re: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

[Torsten Curdt]

> I guess as there were no objections, I’ll go forward with this.
>

+1

Re: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

[Gabriel Gruber]

Going to github would make things a lot easier. Who could do that?
Gabriel

Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: Jörg Heinicke 
Sent: Sunday, January 28, 2024 4:37:25 PM
To: dev@cocoon.apache.org 
Subject: Re: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

I'd also rather go with porting to Git as next step.

Besides, this seems a necessary prerequisite to revive the community
since it reduces the hurdle to get people involved.

Jörg

On 23.01.24 17:54, Christofer Dutz wrote:
> Possibly worth discussing if it’s easier to port to Git and do that then
> … or if better done in SVN … I guess the final discussion Git vs. SVN
> still needs to formally be done, right?
>
> Chris
>
> *Von: *Cédric Damioli 
> *Datum: *Dienstag, 23. Januar 2024 um 17:30
> *An: *dev@cocoon.apache.org 
> *Betreff: *Re: AW: AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x
>
> +1
>
> Cédric
>
> Le 23/01/2024 à 17:25, Christofer Dutz a écrit :
>
> Yeah … I also think that possibly making them read-only (and
> additionally prefixing them with a “retired/” prefix should be enough.
>
> Chris

Re: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

[Jörg Heinicke]

I'd also rather go with porting to Git as next step.

Besides, this seems a necessary prerequisite to revive the community
since it reduces the hurdle to get people involved.

Jörg

On 23.01.24 17:54, Christofer Dutz wrote:

Possibly worth discussing if it’s easier to port to Git and do that then
… or if better done in SVN … I guess the final discussion Git vs. SVN
still needs to formally be done, right?

Chris

*Von: *Cédric Damioli 
*Datum: *Dienstag, 23. Januar 2024 um 17:30
*An: *dev@cocoon.apache.org 
*Betreff: *Re: AW: AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

+1

Cédric

Le 23/01/2024 à 17:25, Christofer Dutz a écrit :

Yeah … I also think that possibly making them read-only (and
additionally prefixing them with a “retired/” prefix should be enough.

Chris

Re: AW: AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

[Cédric Damioli]

+1

Cédric

Le 23/01/2024 à 17:25, Christofer Dutz a écrit :


Yeah … I also think that possibly making them read-only (and 
additionally prefixing them with a “retired/” prefix should be enough.


Chris

*Von: *Cédric Damioli 
*Datum: *Freitag, 12. Januar 2024 um 20:48
*An: *dev@cocoon.apache.org 
*Betreff: *Re: AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

Why should retired branches be deleted ?
Shouldn't they instead be somehow put in read-only state but kept 
available for anyone needing them ?


My 2 cents,
Cédric

Le 09/01/2024 à 14:40, Christofer Dutz a écrit :

So, I guess the deletion of the “retired” branches should probably
be done by a PMC member.

I’m happy to help with migrating 2.3.x to git as soon as the old
stuff is buried, if the project wants this to happen.

Chris

*Von: *Christofer Dutz 
<mailto:christofer.d...@c-ware.de>
*Datum: *Montag, 18. Dezember 2023 um 20:25
*An: *dev@cocoon.apache.org 
<mailto:dev@cocoon.apache.org>
*Betreff: *AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

How about a Mexican style funeral party at Community Over Code? ;-)

Cocoon 2.1 was such a big part of my early IT carreer …

Chris

*Von: *Cédric Damioli 
<mailto:cdami...@apache.org>
*Datum: *Montag, 18. Dezember 2023 um 19:40
*An: *dev@cocoon.apache.org 
<mailto:dev@cocoon.apache.org>
*Betreff: *[RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

The vote is now over and successful with 4 binding +1 and no -1 :

  * Francesco Chicchiriccò
  * Peter Hunsberger
  * Jörg Heinicke
  * Cédric Damioli

The PMC is now tasked to do what is needed to effectively retire
2.1/3.0.

As discussed before, it's now time for volunteers to step up to do
whatever is needed to actively maintain a now-refocused Cocoon
project (migration to Git, dependencies upgrades, ...).

Farewell, good old 2.1 :)

Regards,
Cédric

Le 13/12/2023 à 15:00, Cédric Damioli a écrit :

Hi,

Following and according to last weeks' discussions, it seems
that the general consensus would be to retire 2.1 (too old to
be maintained) and 3.0 (too alpha to be maintained), and keep
2.x around for now.

If I try to summarize what have been said, refocusing on a
single product would give the project a chance to 1) provide a
clear upgrade path to existing 2.1 users and 2) gather renewed
interest.
For the still many existing 2.1 users, this would give a clear
signal that it's time to consider other options.

It's now time to formally vote:

[ ] +1 accept (retire and officially stop the maintenance of
2.1/3.0 branches, only keeping 2.x)
[ ] -1 reject (explanation required)

A minimum of 3 binding +1 votes and more binding +1 than
binding -1 are required to pass.
This vote will be open for at least 72 hours.

Best regards,
Cédric

Re: AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

[Cédric Damioli]

Why should retired branches be deleted ?
Shouldn't they instead be somehow put in read-only state but kept 
available for anyone needing them ?


My 2 cents,
Cédric

Le 09/01/2024 à 14:40, Christofer Dutz a écrit :


So, I guess the deletion of the “retired” branches should probably be 
done by a PMC member.


I’m happy to help with migrating 2.3.x to git as soon as the old stuff 
is buried, if the project wants this to happen.


Chris

*Von: *Christofer Dutz 
*Datum: *Montag, 18. Dezember 2023 um 20:25
*An: *dev@cocoon.apache.org 
*Betreff: *AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

How about a Mexican style funeral party at Community Over Code? ;-)

Cocoon 2.1 was such a big part of my early IT carreer …

Chris

*Von: *Cédric Damioli 
*Datum: *Montag, 18. Dezember 2023 um 19:40
*An: *dev@cocoon.apache.org 
*Betreff: *[RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

The vote is now over and successful with 4 binding +1 and no -1 :

  * Francesco Chicchiriccò
  * Peter Hunsberger
  * Jörg Heinicke
  * Cédric Damioli

The PMC is now tasked to do what is needed to effectively retire 2.1/3.0.

As discussed before, it's now time for volunteers to step up to do 
whatever is needed to actively maintain a now-refocused Cocoon project 
(migration to Git, dependencies upgrades, ...).


Farewell, good old 2.1 :)

Regards,
Cédric

Le 13/12/2023 à 15:00, Cédric Damioli a écrit :

Hi,

Following and according to last weeks' discussions, it seems that
the general consensus would be to retire 2.1 (too old to be
maintained) and 3.0 (too alpha to be maintained), and keep 2.x
around for now.

If I try to summarize what have been said, refocusing on a single
product would give the project a chance to 1) provide a clear
upgrade path to existing 2.1 users and 2) gather renewed interest.
For the still many existing 2.1 users, this would give a clear
signal that it's time to consider other options.

It's now time to formally vote:

[ ] +1 accept (retire and officially stop the maintenance of
2.1/3.0 branches, only keeping 2.x)
[ ] -1 reject (explanation required)

A minimum of 3 binding +1 votes and more binding +1 than binding
-1 are required to pass.
This vote will be open for at least 72 hours.

Best regards,
Cédric

Re: [PR] Bump ch.qos.logback:logback-core from 1.0.9 to 1.2.13 in /jail/cocoon3 [cocoon]

[via GitHub]

dependabot[bot] commented on PR #56:
URL: https://github.com/apache/cocoon/pull/56#issuecomment-1888125064

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. If you'd rather skip all updates until the next 
major or minor version, let me know by commenting `@dependabot ignore this 
major version` or `@dependabot ignore this minor version`.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cocoon.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump ch.qos.logback:logback-classic from 1.0.9 to 1.2.13 in /jail/cocoon3 [cocoon]

[via GitHub]

dependabot[bot] commented on PR #57:
URL: https://github.com/apache/cocoon/pull/57#issuecomment-1888125059

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. If you'd rather skip all updates until the next 
major or minor version, let me know by commenting `@dependabot ignore this 
major version` or `@dependabot ignore this minor version`.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cocoon.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump ch.qos.logback:logback-core from 1.0.9 to 1.2.13 in /jail/cocoon3 [cocoon]

[via GitHub]

asfgit closed pull request #56: Bump ch.qos.logback:logback-core from 1.0.9 to 
1.2.13 in /jail/cocoon3
URL: https://github.com/apache/cocoon/pull/56


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cocoon.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump ch.qos.logback:logback-core from 1.4.5 to 1.4.12 [cocoon]

[via GitHub]

dependabot[bot] commented on PR #52:
URL: https://github.com/apache/cocoon/pull/52#issuecomment-1888125047

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. If you'd rather skip all updates until the next 
major or minor version, let me know by commenting `@dependabot ignore this 
major version` or `@dependabot ignore this minor version`.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cocoon.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump ch.qos.logback:logback-classic from 1.4.5 to 1.4.12 [cocoon]

[via GitHub]

dependabot[bot] commented on PR #54:
URL: https://github.com/apache/cocoon/pull/54#issuecomment-1888125032

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. If you'd rather skip all updates until the next 
major or minor version, let me know by commenting `@dependabot ignore this 
major version` or `@dependabot ignore this minor version`.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cocoon.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump ch.qos.logback:logback-core from 1.4.5 to 1.4.12 [cocoon]

[via GitHub]

asfgit closed pull request #52: Bump ch.qos.logback:logback-core from 1.4.5 to 
1.4.12
URL: https://github.com/apache/cocoon/pull/52


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cocoon.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump ch.qos.logback:logback-classic from 1.0.9 to 1.2.13 in /jail/cocoon3 [cocoon]

[via GitHub]

asfgit closed pull request #57: Bump ch.qos.logback:logback-classic from 1.0.9 
to 1.2.13 in /jail/cocoon3
URL: https://github.com/apache/cocoon/pull/57


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cocoon.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump ch.qos.logback:logback-classic from 1.4.5 to 1.4.12 [cocoon]

[via GitHub]

asfgit closed pull request #54: Bump ch.qos.logback:logback-classic from 1.4.5 
to 1.4.12
URL: https://github.com/apache/cocoon/pull/54


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cocoon.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [VOTE] Retire 2.1/3.0 and keep 2.x

[Cédric Damioli]

Here is my +1:

[X] +1 accept (retire and officially stop the maintenance of 2.1/3.0 
branches, only keeping 2.x)


Cédric

Le 13/12/2023 à 15:00, Cédric Damioli a écrit :

Hi,

Following and according to last weeks' discussions, it seems that the 
general consensus would be to retire 2.1 (too old to be maintained) 
and 3.0 (too alpha to be maintained), and keep 2.x around for now.


If I try to summarize what have been said, refocusing on a single 
product would give the project a chance to 1) provide a clear upgrade 
path to existing 2.1 users and 2) gather renewed interest.
For the still many existing 2.1 users, this would give a clear signal 
that it's time to consider other options.


It's now time to formally vote:

[ ] +1 accept (retire and officially stop the maintenance of 2.1/3.0 
branches, only keeping 2.x)

[ ] -1 reject (explanation required)

A minimum of 3 binding +1 votes and more binding +1 than binding -1 
are required to pass.

This vote will be open for at least 72 hours.

Best regards,
Cédric



--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org

Re: [VOTE] Retire 2.1/3.0 and keep 2.x

[Jörg Heinicke]

On 13.12.23 15:00, Cédric Damioli wrote:

Hi,


...

It's now time to formally vote:

[x] +1 accept (retire and officially stop the maintenance of 2.1/3.0
branches, only keeping 2.x)
[ ] -1 reject (explanation required)


Regards,
Jörg

Re: [VOTE] Retire 2.1/3.0 and keep 2.x

[Peter Hunsberger]

On 2023/12/13 14:00:09 Cédric Damioli wrote:
> Hi,
> 
> Following and according to last weeks' discussions, it seems that the 
> general consensus would be to retire 2.1 (too old to be maintained) and 
> 3.0 (too alpha to be maintained), and keep 2.x around for now.
> 
> If I try to summarize what have been said, refocusing on a single 
> product would give the project a chance to 1) provide a clear upgrade 
> path to existing 2.1 users and 2) gather renewed interest.
> For the still many existing 2.1 users, this would give a clear signal 
> that it's time to consider other options.
> 
> It's now time to formally vote:
> 
 [X] +1 accept (retire and officially stop the maintenance of 2.1/3.0 
> branches, only keeping 2.x)
> [ ] -1 reject (explanation required)
> 
> A minimum of 3 binding +1 votes and more binding +1 than binding -1 are 
> required to pass.
> This vote will be open for at least 72 hours.
> 

+1 to retire and officially stop the maintenance of 2.1/3.0 
 branches, only keeping 2.x

Peter Hunsberger

> Best regards,
> Cédric
> 

Re: Probably first user-question since many years ;-)

[Peter Hunsberger]

On Thu, Dec 14, 2023 at 1:51 AM Christofer Dutz 
wrote:

> Hi all,
>
>
>
> as we’re thinking of giving 2.3 another try … I’m trying to make the ideas
> I had a bit more concrete …
>
>
>
> As some of you might know, I’m working mainly in the Industrial IoT area …
> here we have loads of data in odd data-structures and in general industial
> IoT consists of converting one odd format into another odd format.
>
> Currently most use some super tricky conversion tools …. I would love to
> try setup Cocoon pipelines, that validate and transform this information.
>

Interesting, I've done industrial IoT and have considered Cocoon just for
IoT in general. I've often debated just handling binary and allowing
arbitrary data handlers in the pipeline... That was sort of where Cocoon 3
was headed but I didn't get a chance to explore it for this purpose.  If
you get somewhere with this I might be able to make time to play with it
some.


>
>
> So, my question is: Can Cocoon also be run as a pure xml pipelining
> framework that doesn’t necessarily serve Web-clients?
>
>
>
> Chris
>
>
>

Re: Probably first user-question since many years ;-)

[Cédric Damioli]

Don't know for 2.3, but in 2.1 there is an abstraction of the 
request/response model, allowing to have eg. 
CommandLineRequest/CommandLineResponse to achieve your needs.
It's actually very useful, I use it frequently to call Cocoon pipelines 
from random threads, not linked to an actual http request. I've 
developed my own BackgroundRequest/BackgroundResponse more suiting my 
needs, but the concept is the same.


Cédric

Le 14/12/2023 à 08:50, Christofer Dutz a écrit :


Hi all,

as we’re thinking of giving 2.3 another try … I’m trying to make the 
ideas I had a bit more concrete …


As some of you might know, I’m working mainly in the Industrial IoT 
area … here we have loads of data in odd data-structures and in 
general industial IoT consists of converting one odd format into 
another odd format.


Currently most use some super tricky conversion tools …. I would love 
to try setup Cocoon pipelines, that validate and transform this 
information.


So, my question is: Can Cocoon also be run as a pure xml pipelining 
framework that doesn’t necessarily serve Web-clients?


Chris



--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org

Re: [VOTE] Retire 2.1/3.0 and keep 2.x

[Francesco Chicchiriccò]

On 13/12/23 15:00, Cédric Damioli wrote:

Hi,

Following and according to last weeks' discussions, it seems that the general 
consensus would be to retire 2.1 (too old to be maintained) and 3.0 (too alpha 
to be maintained), and keep 2.x around for now.

If I try to summarize what have been said, refocusing on a single product would 
give the project a chance to 1) provide a clear upgrade path to existing 2.1 
users and 2) gather renewed interest.
For the still many existing 2.1 users, this would give a clear signal that it's 
time to consider other options.

It's now time to formally vote:

[ ] +1 accept (retire and officially stop the maintenance of 2.1/3.0 branches, 
only keeping 2.x)
[ ] -1 reject (explanation required)

A minimum of 3 binding +1 votes and more binding +1 than binding -1 are 
required to pass.
This vote will be open for at least 72 hours.


+1
Regards.

--
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/

Re: [DISCUSS] Retiring 2.1.x ? (Was: Re: Future of the Cocoon project)

[Jörg Heinicke]

I do agree and would be +1 for retiring 2.1.x as well.

If you want any traction within Cocoon project, you'll need at least
focus. And here my vote would clearly go to 2.2/ 2.3 (even though I
never adapted it myself due to the build system issues we always had
with it and despite all the fond memories of 2.1).

Regards,
Jörg

On 01.12.23 19:26, Christofer Dutz wrote:

I'd be +1 to retire 2.1.x

Even if I have fond memories of it, as it was my first major apache
project.

However it's grown quite old technically and refreshing things would be
a huge effort. Some of the jvm versions needed are no longer available
and I failed to even build it on 1.8.

Don't think it's worth the effort :-(

Chris



Gesendet von Outlook für Android <https://aka.ms/AAb9ysg>

*From:* Cédric Damioli 
*Sent:* Friday, December 1, 2023 7:06:08 PM
*To:* dev@cocoon.apache.org 
*Subject:* Re: [DISCUSS] Retiring 2.1.x ? (Was: Re: Future of the Cocoon
project)

Le 01/12/2023 à 18:13, Cédric Damioli a écrit :


We'd like to know whether you'd prefer:
[ ] retiring Cocoon 2.1.x
[ ] reviving/maintaining Cocoon 2.1.x, meaning that you volunteer to
be somehow involved



I'd vote +/-0 here ...
Definitively the toughest for me ...
I still heavily use Cocoon 2.1 core, but I recognize that it's an very
old piece of software, and that maintaining it here would demand more
and more work.

Perhaps it could be wiser to also let it go, and then fork the core
elsewhere if needed with a new build system, without all block stuff, ...
I'm curious to see what will others say about it.

Cédric

Re: [DISCUSS] Retiring 3.0 ? (Was: Re: Future of the Cocoon project)

[Jörg Heinicke]

On 01.12.23 17:41, Cédric Damioli wrote:

Hi,

First of the sub-project to be discussed, the Cocoon 3 project.
Never released, it only reached the alpha status 12 years ago.
Its goal was to provide a pure Java API on top of pipelines and sitemaps
concept, to be able to easily implements lightweight REST applications.

We'd like to know whether you'd prefer:
[ ] retiring Cocoon 3.0
[ ] reviving/maintaining Cocoon 3.0, meaning that you volunteer to be
somehow involved


+1 for retiring Cocoon 3.0. Most likely you would start from scratch
anyways if you want anything in that direction.

Regards,
Jörg


Please note that the above proposal is not a formal vote, but more like
a open poll, so that everyone could speak out.

Cédric


Le 30/11/2023 à 19:53, Cédric Damioli a écrit :

Dear Cocoon users and developers,

Sorry for crossposting here, I wanted to be sure that all involved
people were aware of the ongoing discussions.

We recently pushed a new release of Cocoon, 11 years after the
previous one. This release gathers all changes made in between as well
as two security fixes discovered last year.
The journey to roll this release out was definitively not an easy one,
and it's now time to think about what should be next for the project.

We currently officially maintain 3 branches, not compatible with each
others and having evolved differently over the years : 2.1.x, 2.2/2.3
and 3.0, and we do not have enough active developers to be able to
continue to properly and correctly maintain them.

For a project as old as Cocoon (21 years!), there may be many users
around here still using one branch or another, which could be
interested to step up, contribute and try to revive the project, or at
least some parts of it.

I will soon start 3 threads on the developers list to decide what to
do about each of the 3 branches (retiring or not), so I encourage
volunteers to bring their voices.

Best regards,
Cédric, on behalf of the Apache Cocoon PMC

Re: [PR] Bump ch.qos.logback:logback-classic from 1.0.9 to 1.3.12 in /jail/cocoon3 [cocoon]

[via GitHub]

dependabot[bot] commented on PR #55:
URL: https://github.com/apache/cocoon/pull/55#issuecomment-1841671567

   Superseded by #57.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cocoon.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump ch.qos.logback:logback-classic from 1.0.9 to 1.3.12 in /jail/cocoon3 [cocoon]

[via GitHub]

dependabot[bot] closed pull request #55: Bump ch.qos.logback:logback-classic 
from 1.0.9 to 1.3.12 in /jail/cocoon3
URL: https://github.com/apache/cocoon/pull/55


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cocoon.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump ch.qos.logback:logback-core from 1.0.9 to 1.3.12 in /jail/cocoon3 [cocoon]

[via GitHub]

dependabot[bot] commented on PR #53:
URL: https://github.com/apache/cocoon/pull/53#issuecomment-1841652123

   Superseded by #56.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cocoon.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump ch.qos.logback:logback-core from 1.0.9 to 1.3.12 in /jail/cocoon3 [cocoon]

[via GitHub]

dependabot[bot] closed pull request #53: Bump ch.qos.logback:logback-core from 
1.0.9 to 1.3.12 in /jail/cocoon3
URL: https://github.com/apache/cocoon/pull/53


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cocoon.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)

[Gabriel Gruber]

Sorry, just to clarify: [+1] on
reviving/maintaining Cocoon 2.3+, meaning that you volunteer to be somehow 
involved. Main point for us never considering C3 was that it somehow never left 
alpha state and that it did not support cocoon forms AFAIKT
Cheers, Gabriel

Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: Christofer Dutz 
Sent: Sunday, December 3, 2023 12:03:43 PM
To: dev@cocoon.apache.org 
Subject: AW: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)


Even if in the end we decide to keep 2.3.x running, we probably should go 
through the module list and retire some of the modules. I know that for some I 
couldn’t update to good versions, as the technology they use was abandoned. So, 
cutting the hair of our modules, might be necessary.



Chris







Von: Gabriel Gruber 
Datum: Samstag, 2. Dezember 2023 um 12:25
An: dev@cocoon.apache.org 
Betreff: Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)

-1 on retiring cocoon 2.3.x. It needs some more love in maintaining but it 
works even with spring 5 and java 11(for us). Would like to see it run with 
spring boot.



Migrating to github and having a fork/PR workflow could bring some Traktion on 
it's own from willing supporters/users.



What could be a valid goal would maybe to repackage cocoon with docker so that 
it can be easily used by 2.1.x users?



Cheers,

Gabriel







Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>



From: Peter Hunsberger 
Sent: Friday, December 1, 2023 9:45:24 PM
To: dev@cocoon.apache.org 
Subject: Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)







On Fri, Dec 1, 2023 at 11:00 AM Cédric Damioli 
mailto:cdami...@apache.org>> wrote:

Hi,

Second thread to discuss about Cocon 2.x branch, with the latest
release, 2.3.0, just being rolled out.
Cocoon 2.2 was initially meant to implements all stuff developed during
the 2.1 cycle on top of Spring and Maven, to drop old Avalon dependencies.

We'd like to know whether you'd prefer:
[-1 ] retiring Cocoon 2.x



[+0] reviving/maintaining Cocoon 2.x, meaning that you volunteer to be
somehow involved

Please note that the above proposal is not a formal vote, but more like
a open poll, so that everyone could speak out.

Should we continue the project and this branch particularly, there are
recent threads on this list proposing to switch to Git, to upgrade
dependencies, build system, ...

Cédric



Not sure I can really commit to helping much, other than testing releases, I 
don't see having the time to dive into the code anymore but I do still see 
people using this code base.



Peter Hunsberger



Le 30/11/2023 à 19:53, Cédric Damioli a écrit :
> Dear Cocoon users and developers,
>
> Sorry for crossposting here, I wanted to be sure that all involved
> people were aware of the ongoing discussions.
>
> We recently pushed a new release of Cocoon, 11 years after the
> previous one. This release gathers all changes made in between as well
> as two security fixes discovered last year.
> The journey to roll this release out was definitively not an easy one,
> and it's now time to think about what should be next for the project.
>
> We currently officially maintain 3 branches, not compatible with each
> others and having evolved differently over the years : 2.1.x, 2.2/2.3
> and 3.0, and we do not have enough active developers to be able to
> continue to properly and correctly maintain them.
>
> For a project as old as Cocoon (21 years!), there may be many users
> around here still using one branch or another, which could be
> interested to step up, contribute and try to revive the project, or at
> least some parts of it.
>
> I will soon start 3 threads on the developers list to decide what to
> do about each of the 3 branches (retiring or not), so I encourage
> volunteers to bring their voices.
>
> Best regards,
> Cédric, on behalf of the Apache Cocoon PMC
>

--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org<http://www.ametys.org>

AW: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)

[Christofer Dutz]

Even if in the end we decide to keep 2.3.x running, we probably should go 
through the module list and retire some of the modules. I know that for some I 
couldn’t update to good versions, as the technology they use was abandoned. So, 
cutting the hair of our modules, might be necessary.

Chris



Von: Gabriel Gruber 
Datum: Samstag, 2. Dezember 2023 um 12:25
An: dev@cocoon.apache.org 
Betreff: Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)
-1 on retiring cocoon 2.3.x. It needs some more love in maintaining but it 
works even with spring 5 and java 11(for us). Would like to see it run with 
spring boot.

Migrating to github and having a fork/PR workflow could bring some Traktion on 
it's own from willing supporters/users.

What could be a valid goal would maybe to repackage cocoon with docker so that 
it can be easily used by 2.1.x users?

Cheers,
Gabriel



Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: Peter Hunsberger 
Sent: Friday, December 1, 2023 9:45:24 PM
To: dev@cocoon.apache.org 
Subject: Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)



On Fri, Dec 1, 2023 at 11:00 AM Cédric Damioli 
mailto:cdami...@apache.org>> wrote:
Hi,

Second thread to discuss about Cocon 2.x branch, with the latest
release, 2.3.0, just being rolled out.
Cocoon 2.2 was initially meant to implements all stuff developed during
the 2.1 cycle on top of Spring and Maven, to drop old Avalon dependencies.

We'd like to know whether you'd prefer:
[-1 ] retiring Cocoon 2.x

[+0] reviving/maintaining Cocoon 2.x, meaning that you volunteer to be
somehow involved

Please note that the above proposal is not a formal vote, but more like
a open poll, so that everyone could speak out.

Should we continue the project and this branch particularly, there are
recent threads on this list proposing to switch to Git, to upgrade
dependencies, build system, ...

Cédric

Not sure I can really commit to helping much, other than testing releases, I 
don't see having the time to dive into the code anymore but I do still see 
people using this code base.

Peter Hunsberger

Le 30/11/2023 à 19:53, Cédric Damioli a écrit :
> Dear Cocoon users and developers,
>
> Sorry for crossposting here, I wanted to be sure that all involved
> people were aware of the ongoing discussions.
>
> We recently pushed a new release of Cocoon, 11 years after the
> previous one. This release gathers all changes made in between as well
> as two security fixes discovered last year.
> The journey to roll this release out was definitively not an easy one,
> and it's now time to think about what should be next for the project.
>
> We currently officially maintain 3 branches, not compatible with each
> others and having evolved differently over the years : 2.1.x, 2.2/2.3
> and 3.0, and we do not have enough active developers to be able to
> continue to properly and correctly maintain them.
>
> For a project as old as Cocoon (21 years!), there may be many users
> around here still using one branch or another, which could be
> interested to step up, contribute and try to revive the project, or at
> least some parts of it.
>
> I will soon start 3 threads on the developers list to decide what to
> do about each of the 3 branches (retiring or not), so I encourage
> volunteers to bring their voices.
>
> Best regards,
> Cédric, on behalf of the Apache Cocoon PMC
>

--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org<http://www.ametys.org>

Re: [DISCUSS] Retiring 3.0 ? (Was: Re: Future of the Cocoon project)

[Francesco Chicchiriccò]

On 2023/12/01 17:45:42 Francesco Chicchiriccò wrote:
> On 01/12/23 18:24, Cédric Damioli wrote:
> > Le 01/12/2023 à 17:41, Cédric Damioli a écrit :
> >> We'd like to know whether you'd prefer:
> >> [ ] retiring Cocoon 3.0
> >> [ ] reviving/maintaining Cocoon 3.0, meaning that you volunteer to be 
> >> somehow involved
> >
> > I'd vote +1 for retiring Cocoon 3.0, as during the past 10+ years, I had 
> > seen no thread, no questions about it.
> > I personally have never tried it. 
> 
> Cocoon 3.0 has been my first "serious" approach to The ASF and also where I 
> earned committership and PMC membership.
> 
> I am not pleased to admin that, but I think it is time to let it go: while 
> its ground ideas were incredibly neat at the time, they never turned into 
> mainstream, regrettably.
> 
> It has been even used by Syncope until 3.0.0-M0 [1] around Q4 2022.

Also found [2] from my archives, at a cross site with the old Hippo CMS...

> Regards.
> 
> [1] 
> https://github.com/apache/syncope/blob/syncope-3.0.0-M0/pom.xml#L1167-L1176
[2] https://hct.tirasa.net/
> -- 
> Francesco Chicchiriccò
> 
> Tirasa - Open Source Excellence
> http://www.tirasa.net/
> 
> Member at The Apache Software Foundation
> Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
> http://home.apache.org/~ilgrosso/
> 
> 

Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)

[Gabriel Gruber]

-1 on retiring cocoon 2.3.x. It needs some more love in maintaining but it 
works even with spring 5 and java 11(for us). Would like to see it run with 
spring boot.

Migrating to github and having a fork/PR workflow could bring some Traktion on 
it's own from willing supporters/users.

What could be a valid goal would maybe to repackage cocoon with docker so that 
it can be easily used by 2.1.x users?

Cheers,
Gabriel



Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: Peter Hunsberger 
Sent: Friday, December 1, 2023 9:45:24 PM
To: dev@cocoon.apache.org 
Subject: Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)



On Fri, Dec 1, 2023 at 11:00 AM Cédric Damioli 
mailto:cdami...@apache.org>> wrote:
Hi,

Second thread to discuss about Cocon 2.x branch, with the latest
release, 2.3.0, just being rolled out.
Cocoon 2.2 was initially meant to implements all stuff developed during
the 2.1 cycle on top of Spring and Maven, to drop old Avalon dependencies.

We'd like to know whether you'd prefer:
[-1 ] retiring Cocoon 2.x

[+0] reviving/maintaining Cocoon 2.x, meaning that you volunteer to be
somehow involved

Please note that the above proposal is not a formal vote, but more like
a open poll, so that everyone could speak out.

Should we continue the project and this branch particularly, there are
recent threads on this list proposing to switch to Git, to upgrade
dependencies, build system, ...

Cédric

Not sure I can really commit to helping much, other than testing releases, I 
don't see having the time to dive into the code anymore but I do still see 
people using this code base.

Peter Hunsberger

Le 30/11/2023 à 19:53, Cédric Damioli a écrit :
> Dear Cocoon users and developers,
>
> Sorry for crossposting here, I wanted to be sure that all involved
> people were aware of the ongoing discussions.
>
> We recently pushed a new release of Cocoon, 11 years after the
> previous one. This release gathers all changes made in between as well
> as two security fixes discovered last year.
> The journey to roll this release out was definitively not an easy one,
> and it's now time to think about what should be next for the project.
>
> We currently officially maintain 3 branches, not compatible with each
> others and having evolved differently over the years : 2.1.x, 2.2/2.3
> and 3.0, and we do not have enough active developers to be able to
> continue to properly and correctly maintain them.
>
> For a project as old as Cocoon (21 years!), there may be many users
> around here still using one branch or another, which could be
> interested to step up, contribute and try to revive the project, or at
> least some parts of it.
>
> I will soon start 3 threads on the developers list to decide what to
> do about each of the 3 branches (retiring or not), so I encourage
> volunteers to bring their voices.
>
> Best regards,
> Cédric, on behalf of the Apache Cocoon PMC
>

--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org<http://www.ametys.org>

Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)

[Peter Hunsberger]

On Fri, Dec 1, 2023 at 11:00 AM Cédric Damioli  wrote:

> Hi,
>
> Second thread to discuss about Cocon 2.x branch, with the latest
> release, 2.3.0, just being rolled out.
> Cocoon 2.2 was initially meant to implements all stuff developed during
> the 2.1 cycle on top of Spring and Maven, to drop old Avalon dependencies.
>
> We'd like to know whether you'd prefer:
> [-1 ] retiring Cocoon 2.x
>


> [+0] reviving/maintaining Cocoon 2.x, meaning that you volunteer to be
> somehow involved
>
> Please note that the above proposal is not a formal vote, but more like
> a open poll, so that everyone could speak out.
>
> Should we continue the project and this branch particularly, there are
> recent threads on this list proposing to switch to Git, to upgrade
> dependencies, build system, ...
>
> Cédric
>

Not sure I can really commit to helping much, other than testing releases,
I don't see having the time to dive into the code anymore but I do still
see people using this code base.

Peter Hunsberger


> Le 30/11/2023 à 19:53, Cédric Damioli a écrit :
> > Dear Cocoon users and developers,
> >
> > Sorry for crossposting here, I wanted to be sure that all involved
> > people were aware of the ongoing discussions.
> >
> > We recently pushed a new release of Cocoon, 11 years after the
> > previous one. This release gathers all changes made in between as well
> > as two security fixes discovered last year.
> > The journey to roll this release out was definitively not an easy one,
> > and it's now time to think about what should be next for the project.
> >
> > We currently officially maintain 3 branches, not compatible with each
> > others and having evolved differently over the years : 2.1.x, 2.2/2.3
> > and 3.0, and we do not have enough active developers to be able to
> > continue to properly and correctly maintain them.
> >
> > For a project as old as Cocoon (21 years!), there may be many users
> > around here still using one branch or another, which could be
> > interested to step up, contribute and try to revive the project, or at
> > least some parts of it.
> >
> > I will soon start 3 threads on the developers list to decide what to
> > do about each of the 3 branches (retiring or not), so I encourage
> > volunteers to bring their voices.
> >
> > Best regards,
> > Cédric, on behalf of the Apache Cocoon PMC
> >
>
> --
> Cédric Damioli
> CMS - Java - Open Source
> www.ametys.org
>
>

Re: [DISCUSS] Retiring 3.0 ? (Was: Re: Future of the Cocoon project)

[Peter Hunsberger]

On Fri, Dec 1, 2023 at 10:41 AM Cédric Damioli  wrote:

> Hi,
>
> First of the sub-project to be discussed, the Cocoon 3 project.
> Never released, it only reached the alpha status 12 years ago.
> Its goal was to provide a pure Java API on top of pipelines and sitemaps
> concept, to be able to easily implements lightweight REST applications.
>
> We'd like to know whether you'd prefer:

[+1 ] retiring Cocoon 3.0
>


> [ ] reviving/maintaining Cocoon 3.0, meaning that you volunteer to be
> somehow involved
>
> Please note that the above proposal is not a formal vote, but more like
> a open poll, so that everyone could speak out.
>
> Cédric
>
I too had some fun building stuff with 3.0 but I can't see a use for it any
more.

+1 to retiring it (if it's not obvious from above)

Peter Hunsberger



> Le 30/11/2023 à 19:53, Cédric Damioli a écrit :
> > Dear Cocoon users and developers,
> >
> > Sorry for crossposting here, I wanted to be sure that all involved
> > people were aware of the ongoing discussions.
> >
> > We recently pushed a new release of Cocoon, 11 years after the
> > previous one. This release gathers all changes made in between as well
> > as two security fixes discovered last year.
> > The journey to roll this release out was definitively not an easy one,
> > and it's now time to think about what should be next for the project.
> >
> > We currently officially maintain 3 branches, not compatible with each
> > others and having evolved differently over the years : 2.1.x, 2.2/2.3
> > and 3.0, and we do not have enough active developers to be able to
> > continue to properly and correctly maintain them.
> >
> > For a project as old as Cocoon (21 years!), there may be many users
> > around here still using one branch or another, which could be
> > interested to step up, contribute and try to revive the project, or at
> > least some parts of it.
> >
> > I will soon start 3 threads on the developers list to decide what to
> > do about each of the 3 branches (retiring or not), so I encourage
> > volunteers to bring their voices.
> >
> > Best regards,
> > Cédric, on behalf of the Apache Cocoon PMC
> >
>
> --
> Cédric Damioli
> CMS - Java - Open Source
> www.ametys.org
>
>

Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)

[Carlos Armando Chávez Chavarría]

In the company I work sometime ago it was created a fork from the branch 
https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X-dojo1_1


As far I remember someone at apache created that version to upgrade the 
DojoToolkit java script framework.


In our fork I worked to make it work in Java 1.8, then Java 11 and later 
in Java 17.


In our fork I worked to make it work the XSP as well in those java versions.

In our fork I have the Dojotoolkit updated to the version 1.17.2

There is some issue about the flowscript framework that in our fork 
still using the Rhino version rhino1.5r4-continuations-R26.jar but that 
branch was updated to the version s-1.6R5.jar but that version break our 
application.


I don't think there is people using that branch, we still have a active 
application using that, but the changes I made was mostly to make it run 
on newer java versions and some minor fixes.


On 1/12/23 12:27, Christofer Dutz wrote:

I'd be -1 on retiring 2.x.

I put in the work to fix things, cause I still think there's valid 
usecases for it.


I would be willing to help and try to see, if we can reinitialize a 
small community around it.


Chris

Gesendet von Outlook für Android <https://aka.ms/AAb9ysg>

*From:* Cédric Damioli 
*Sent:* Friday, December 1, 2023 6:42:08 PM
*To:* dev@cocoon.apache.org 
*Subject:* Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon 
project)



Le 01/12/2023 à 18:00, Cédric Damioli a écrit :
>
> We'd like to know whether you'd prefer:
> [ ] retiring Cocoon 2.x
> [ ] reviving/maintaining Cocoon 2.x, meaning that you volunteer to be
> somehow involved
>
I'd vote +0 for retiring 2.x, holding my thoughts until the result of
this thread.
I personally don't use it nor plan to use it, but with my PMC member hat
on, I see that there's still some interest around here.
The current PMC and committers roster is not sufficient to keep the
project alive, but with new volunteers, why not ...

Cédric


--
Saludos.
Carlos Armando Chávez Chavarría.
AG Software, S.A.

Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)

[Christofer Dutz]

I'd be -1 on retiring 2.x.

I put in the work to fix things, cause I still think there's valid usecases for 
it.

I would be willing to help and try to see, if we can reinitialize a small 
community around it.

Chris

Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: Cédric Damioli 
Sent: Friday, December 1, 2023 6:42:08 PM
To: dev@cocoon.apache.org 
Subject: Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)



Le 01/12/2023 à 18:00, Cédric Damioli a écrit :
>
> We'd like to know whether you'd prefer:
> [ ] retiring Cocoon 2.x
> [ ] reviving/maintaining Cocoon 2.x, meaning that you volunteer to be
> somehow involved
>
I'd vote +0 for retiring 2.x, holding my thoughts until the result of
this thread.
I personally don't use it nor plan to use it, but with my PMC member hat
on, I see that there's still some interest around here.
The current PMC and committers roster is not sufficient to keep the
project alive, but with new volunteers, why not ...

Cédric

Re: [DISCUSS] Retiring 2.1.x ? (Was: Re: Future of the Cocoon project)

[Christofer Dutz]

I'd be +1 to retire 2.1.x

Even if I have fond memories of it, as it was my first major apache project.

However it's grown quite old technically and refreshing things would be a huge 
effort. Some of the jvm versions needed are no longer available and I failed to 
even build it on 1.8.

Don't think it's worth the effort :-(

Chris



Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: Cédric Damioli 
Sent: Friday, December 1, 2023 7:06:08 PM
To: dev@cocoon.apache.org 
Subject: Re: [DISCUSS] Retiring 2.1.x ? (Was: Re: Future of the Cocoon project)


Le 01/12/2023 à 18:13, Cédric Damioli a écrit :
>
> We'd like to know whether you'd prefer:
> [ ] retiring Cocoon 2.1.x
> [ ] reviving/maintaining Cocoon 2.1.x, meaning that you volunteer to
> be somehow involved
>

I'd vote +/-0 here ...
Definitively the toughest for me ...
I still heavily use Cocoon 2.1 core, but I recognize that it's an very
old piece of software, and that maintaining it here would demand more
and more work.

Perhaps it could be wiser to also let it go, and then fork the core
elsewhere if needed with a new build system, without all block stuff, ...
I'm curious to see what will others say about it.

Cédric

Re: [DISCUSS] Retiring 3.0 ? (Was: Re: Future of the Cocoon project)

[Christofer Dutz]

I'd also vote +1 on retiring 3.0.
There's only little activity overall I'd opt for concentrating it instead of 
fuchsig on too many things in parallel.

Chris

Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: Francesco Chicchiriccò 
Sent: Friday, December 1, 2023 6:45:42 PM
To: dev@cocoon.apache.org 
Subject: Re: [DISCUSS] Retiring 3.0 ? (Was: Re: Future of the Cocoon project)

On 01/12/23 18:24, Cédric Damioli wrote:
> Le 01/12/2023 à 17:41, Cédric Damioli a écrit :
>> We'd like to know whether you'd prefer:
>> [ ] retiring Cocoon 3.0
>> [ ] reviving/maintaining Cocoon 3.0, meaning that you volunteer to be 
>> somehow involved
>
> I'd vote +1 for retiring Cocoon 3.0, as during the past 10+ years, I had seen 
> no thread, no questions about it.
> I personally have never tried it.

Cocoon 3.0 has been my first "serious" approach to The ASF and also where I 
earned committership and PMC membership.

I am not pleased to admin that, but I think it is time to let it go: while its 
ground ideas were incredibly neat at the time, they never turned into 
mainstream, regrettably.

It has been even used by Syncope until 3.0.0-M0 [1] around Q4 2022.

Regards.

[1] https://github.com/apache/syncope/blob/syncope-3.0.0-M0/pom.xml#L1167-L1176

--
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/

Re: [DISCUSS] Retiring 2.1.x ? (Was: Re: Future of the Cocoon project)

[Cédric Damioli]

Le 01/12/2023 à 18:13, Cédric Damioli a écrit :


We'd like to know whether you'd prefer:
[ ] retiring Cocoon 2.1.x
[ ] reviving/maintaining Cocoon 2.1.x, meaning that you volunteer to 
be somehow involved




I'd vote +/-0 here ...
Definitively the toughest for me ...
I still heavily use Cocoon 2.1 core, but I recognize that it's an very 
old piece of software, and that maintaining it here would demand more 
and more work.


Perhaps it could be wiser to also let it go, and then fork the core 
elsewhere if needed with a new build system, without all block stuff, ...

I'm curious to see what will others say about it.

Cédric

Re: [DISCUSS] Retiring 3.0 ? (Was: Re: Future of the Cocoon project)

[Francesco Chicchiriccò]

On 01/12/23 18:24, Cédric Damioli wrote:

Le 01/12/2023 à 17:41, Cédric Damioli a écrit :

We'd like to know whether you'd prefer:
[ ] retiring Cocoon 3.0
[ ] reviving/maintaining Cocoon 3.0, meaning that you volunteer to be somehow 
involved


I'd vote +1 for retiring Cocoon 3.0, as during the past 10+ years, I had seen 
no thread, no questions about it.
I personally have never tried it. 


Cocoon 3.0 has been my first "serious" approach to The ASF and also where I 
earned committership and PMC membership.

I am not pleased to admin that, but I think it is time to let it go: while its 
ground ideas were incredibly neat at the time, they never turned into 
mainstream, regrettably.

It has been even used by Syncope until 3.0.0-M0 [1] around Q4 2022.

Regards.

[1] https://github.com/apache/syncope/blob/syncope-3.0.0-M0/pom.xml#L1167-L1176

--
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/

Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)

[Cédric Damioli]

Le 01/12/2023 à 18:00, Cédric Damioli a écrit :


We'd like to know whether you'd prefer:
[ ] retiring Cocoon 2.x
[ ] reviving/maintaining Cocoon 2.x, meaning that you volunteer to be 
somehow involved


I'd vote +0 for retiring 2.x, holding my thoughts until the result of 
this thread.
I personally don't use it nor plan to use it, but with my PMC member hat 
on, I see that there's still some interest around here.
The current PMC and committers roster is not sufficient to keep the 
project alive, but with new volunteers, why not ...


Cédric

Re: [DISCUSS] Retiring 3.0 ? (Was: Re: Future of the Cocoon project)

[Cédric Damioli]

Le 01/12/2023 à 17:41, Cédric Damioli a écrit :



We'd like to know whether you'd prefer:
[ ] retiring Cocoon 3.0
[ ] reviving/maintaining Cocoon 3.0, meaning that you volunteer to be 
somehow involved


I'd vote +1 for retiring Cocoon 3.0, as during the past 10+ years, I had 
seen no thread, no questions about it.

I personally have never tried it.

Cédric

[DISCUSS] Retiring 2.1.x ? (Was: Re: Future of the Cocoon project)

[Cédric Damioli]

Hi,

Last thread to discuss about Cocon 2.1.x branch, with 2.1.13 released 3 
years ago.
Cocoon 2.1 has no dependencies to Maven/Spring and rely on the old 
Avalon stuff instead.
Its build system is way outdated, there's no dependency management and 
many blocks rely on obsolete/unmaintained 3rd party libs, but its core 
is still reliable.
Unfortunately, there's no easy way to migrate from Cocoon 2.1 to 2.2, 
that's why this branch still exists.


We'd like to know whether you'd prefer:
[ ] retiring Cocoon 2.1.x
[ ] reviving/maintaining Cocoon 2.1.x, meaning that you volunteer to be 
somehow involved


Please note that the above proposal is not a formal vote, but more like 
a open poll, so that everyone could speak out.


Cédric


Le 30/11/2023 à 19:53, Cédric Damioli a écrit :

Dear Cocoon users and developers,

Sorry for crossposting here, I wanted to be sure that all involved 
people were aware of the ongoing discussions.


We recently pushed a new release of Cocoon, 11 years after the 
previous one. This release gathers all changes made in between as well 
as two security fixes discovered last year.
The journey to roll this release out was definitively not an easy one, 
and it's now time to think about what should be next for the project.


We currently officially maintain 3 branches, not compatible with each 
others and having evolved differently over the years : 2.1.x, 2.2/2.3 
and 3.0, and we do not have enough active developers to be able to 
continue to properly and correctly maintain them.


For a project as old as Cocoon (21 years!), there may be many users 
around here still using one branch or another, which could be 
interested to step up, contribute and try to revive the project, or at 
least some parts of it.


I will soon start 3 threads on the developers list to decide what to 
do about each of the 3 branches (retiring or not), so I encourage 
volunteers to bring their voices.


Best regards,
Cédric, on behalf of the Apache Cocoon PMC



--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org

[DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)

[Cédric Damioli]

Hi,

Second thread to discuss about Cocon 2.x branch, with the latest 
release, 2.3.0, just being rolled out.
Cocoon 2.2 was initially meant to implements all stuff developed during 
the 2.1 cycle on top of Spring and Maven, to drop old Avalon dependencies.


We'd like to know whether you'd prefer:
[ ] retiring Cocoon 2.x
[ ] reviving/maintaining Cocoon 2.x, meaning that you volunteer to be 
somehow involved


Please note that the above proposal is not a formal vote, but more like 
a open poll, so that everyone could speak out.


Should we continue the project and this branch particularly, there are 
recent threads on this list proposing to switch to Git, to upgrade 
dependencies, build system, ...


Cédric


Le 30/11/2023 à 19:53, Cédric Damioli a écrit :

Dear Cocoon users and developers,

Sorry for crossposting here, I wanted to be sure that all involved 
people were aware of the ongoing discussions.


We recently pushed a new release of Cocoon, 11 years after the 
previous one. This release gathers all changes made in between as well 
as two security fixes discovered last year.
The journey to roll this release out was definitively not an easy one, 
and it's now time to think about what should be next for the project.


We currently officially maintain 3 branches, not compatible with each 
others and having evolved differently over the years : 2.1.x, 2.2/2.3 
and 3.0, and we do not have enough active developers to be able to 
continue to properly and correctly maintain them.


For a project as old as Cocoon (21 years!), there may be many users 
around here still using one branch or another, which could be 
interested to step up, contribute and try to revive the project, or at 
least some parts of it.


I will soon start 3 threads on the developers list to decide what to 
do about each of the 3 branches (retiring or not), so I encourage 
volunteers to bring their voices.


Best regards,
Cédric, on behalf of the Apache Cocoon PMC



--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org

[DISCUSS] Retiring 3.0 ? (Was: Re: Future of the Cocoon project)

[Cédric Damioli]

Hi,

First of the sub-project to be discussed, the Cocoon 3 project.
Never released, it only reached the alpha status 12 years ago.
Its goal was to provide a pure Java API on top of pipelines and sitemaps 
concept, to be able to easily implements lightweight REST applications.


We'd like to know whether you'd prefer:
[ ] retiring Cocoon 3.0
[ ] reviving/maintaining Cocoon 3.0, meaning that you volunteer to be 
somehow involved


Please note that the above proposal is not a formal vote, but more like 
a open poll, so that everyone could speak out.


Cédric


Le 30/11/2023 à 19:53, Cédric Damioli a écrit :

Dear Cocoon users and developers,

Sorry for crossposting here, I wanted to be sure that all involved 
people were aware of the ongoing discussions.


We recently pushed a new release of Cocoon, 11 years after the 
previous one. This release gathers all changes made in between as well 
as two security fixes discovered last year.
The journey to roll this release out was definitively not an easy one, 
and it's now time to think about what should be next for the project.


We currently officially maintain 3 branches, not compatible with each 
others and having evolved differently over the years : 2.1.x, 2.2/2.3 
and 3.0, and we do not have enough active developers to be able to 
continue to properly and correctly maintain them.


For a project as old as Cocoon (21 years!), there may be many users 
around here still using one branch or another, which could be 
interested to step up, contribute and try to revive the project, or at 
least some parts of it.


I will soon start 3 threads on the developers list to decide what to 
do about each of the 3 branches (retiring or not), so I encourage 
volunteers to bring their voices.


Best regards,
Cédric, on behalf of the Apache Cocoon PMC



--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org

Re: AW: [ANN] Apache Cocoon 2.3.0 Released

[Cédric Damioli]

There's even a @Cocoon3 account on X/Twitter, but I don't know who's behind.

Cédric

Le 28/11/2023 à 14:27, Christofer Dutz a écrit :


Anyone sharing this on LinkedIn and X?


Chris

*Von: *Cédric Damioli 
*Datum: *Dienstag, 28. November 2023 um 14:17
*An: *us...@cocoon.apache.org , 
dev@cocoon.apache.org , annou...@apache.org 


*Betreff: *[ANN] Apache Cocoon 2.3.0 Released

Apache Cocoon 2.3.0 Released
-

   The Apache Cocoon Community is proud to announce the release of
   Cocoon 2.3.0.

   Apache Cocoon is a Spring-based framework (since version 2.2 of
   Cocoon) built around the concepts of separation of concerns and
   component-based development.

   Cocoon implements these concepts around the notion of component
   pipelines, each component on the pipeline specializing on a particular
   operation.

   This release, 11 years after 2.2.0, gathers all changes made since 
then,

   along with security fixes.

   The minimum Java version was also upgraded to 1.8

Apache Cocoon 2.3.0 may be downloaded from
https://cocoon.apache.org/1284_1_1.html

For more information about Apache Cocoon, please go to
https://cocoon.apache.org





--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org

Re: Now that the release is out, what's next?

[Christofer Dutz]

I agree... 2.3.x seems to be the best option to keep.

Chris

Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: Gabriel Gruber 
Sent: Wednesday, November 22, 2023 12:32:12 AM
To: dev@cocoon.apache.org 
Subject: Re: Now that the release is out, what's next?

Maybe a docker version could be attractive for non java users, who just want to 
work with xslt Pipelines and web resources?

Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: Christofer Dutz 
Sent: Tuesday, November 21, 2023 10:55:50 PM
To: dev@cocoon.apache.org 
Subject: Re: Now that the release is out, what's next?

Well for me, the one thing at has changed since then, is that I've become a 
maven wizard  and a certified spring professional myself. Maven is my primary 
build tool and spring my primary component framework. Cocoon was just a read 
ahead of its time then.

Now I wouldn't want to touch an Ant build anymore and am happy we left the 
jakarta/avalon times behind us ;-)

Chris

Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: insigh...@gmail.com 
Sent: Tuesday, November 21, 2023 10:26:05 PM
To: dev@cocoon.apache.org 
Subject: Re: Now that the release is out, what's next?

Like Chris, I never could adapt to the build and Spring changes in Cocoon 2.2, 
and continued (until a few years ago) to develop projects from Cocoon 2.1 
(v2.1.13). I love and am still passionate about the original 2.1 framework, 
having used it since 2002. In fact, I would still be using it if not for 
security, and other, challenges with the old code.

The thing that drew me to Cocoon in the first place was the terrific pipeline 
transformer architecture: it really fit the text transforming ability of XSLT. 
It is something I greatly miss in Python.

I like the idea of using GitHub (https://github.com/apache/cocoon), as it may 
expose more people to the project. In this regard, explaining what Cocoon does, 
benefits of using it etc., might attract some passers by.

Thank you to all of you, who have, over the years, contributed and participated 
in this beautiful piece of software.

Dan

===


On 2023-11-21 6:46 a.m., Peter Hunsberger wrote:

On Tue, Nov 21, 2023 at 12:15 AM Christofer Dutz 
mailto:christofer.d...@c-ware.de>> wrote:
Well guess I haven't stated it yet: I would be willing to work on it (I've 
especially for some ideas on streaming industrial data from plc4x).

Personally I would let the pre-2.2 branch rest in peace. All is dependencies 
are so extremely old and the jdks for some are no longer available. At least I 
probably wouldn't touch it and focus on the "middle"...
 +1 !

Possibly have a look at 3.0 (haven't done that yet).

I tried using 3.0 for a project.  Some good ideas and simple enough 
implementation but I don't think there is enough there for it to be worth 
saving

Chris

Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: Cédric Damioli mailto:cdami...@apache.org>>
Sent: Monday, November 20, 2023 3:47:14 PM
To: dev@cocoon.apache.org<mailto:dev@cocoon.apache.org> 
mailto:dev@cocoon.apache.org>>
Subject: Re: Now that the release is out, what's next?

Hi,

On top of that, as a community, we now have to formally answer to the below 
question (going or not to the Attic) not only once, but three times, one time 
for each subproject we still officially maintain since more than 10 years :
 - Cocoon 2.1.x (pre-Spring, pre-Maven). Last release 2.1.13 was rolled out 3 
years ago.
 - Cocoon 2.2x (now 2.3.x). Last release these days.
 - Cocoon 3.0.x. Last release 3.0.0-alpha-3 back in 2011

Those 3 versions are not compatible with each other, are not meant as drop-in 
replacements, and have evolved differently over the years.

The community could either decide to stop the project as-is and go to the 
Attic, or start over maintaining only one or two branches.

Cédric

Le 19/11/2023 à 18:20, Christofer Dutz a écrit :

Hi folks,



So, it seems that we finally have finished the last missing steps to formally 
get the release out the door. Now I think comes a time where we should reflect 
and discuss, what should happen with the Project.



So instead of simply saying: Releasing it was such a struggle (not technically, 
but from a participation side) I wouldn’t say this project is healthy and we 
should discuss a move into the Attic.



However, I could also imagine that the changes I implemented in the build might 
encourage some folks to give it another go.



I know when I was doing projects with Cocoon as part of my day-job 20 years 
ago, Cocoon 2.2 sort of completely broke my flow. Not only my inexperience with 
Maven, but also that of Spring and the versioning scheme where all sorts of 
cocoon modules had different versions just made me give up at th

Re: Now that the release is out, what's next?

[Gabriel Gruber]

Maybe a docker version could be attractive for non java users, who just want to 
work with xslt Pipelines and web resources?

Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: Christofer Dutz 
Sent: Tuesday, November 21, 2023 10:55:50 PM
To: dev@cocoon.apache.org 
Subject: Re: Now that the release is out, what's next?

Well for me, the one thing at has changed since then, is that I've become a 
maven wizard  and a certified spring professional myself. Maven is my primary 
build tool and spring my primary component framework. Cocoon was just a read 
ahead of its time then.

Now I wouldn't want to touch an Ant build anymore and am happy we left the 
jakarta/avalon times behind us ;-)

Chris

Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: insigh...@gmail.com 
Sent: Tuesday, November 21, 2023 10:26:05 PM
To: dev@cocoon.apache.org 
Subject: Re: Now that the release is out, what's next?

Like Chris, I never could adapt to the build and Spring changes in Cocoon 2.2, 
and continued (until a few years ago) to develop projects from Cocoon 2.1 
(v2.1.13). I love and am still passionate about the original 2.1 framework, 
having used it since 2002. In fact, I would still be using it if not for 
security, and other, challenges with the old code.

The thing that drew me to Cocoon in the first place was the terrific pipeline 
transformer architecture: it really fit the text transforming ability of XSLT. 
It is something I greatly miss in Python.

I like the idea of using GitHub (https://github.com/apache/cocoon), as it may 
expose more people to the project. In this regard, explaining what Cocoon does, 
benefits of using it etc., might attract some passers by.

Thank you to all of you, who have, over the years, contributed and participated 
in this beautiful piece of software.

Dan

===


On 2023-11-21 6:46 a.m., Peter Hunsberger wrote:

On Tue, Nov 21, 2023 at 12:15 AM Christofer Dutz 
mailto:christofer.d...@c-ware.de>> wrote:
Well guess I haven't stated it yet: I would be willing to work on it (I've 
especially for some ideas on streaming industrial data from plc4x).

Personally I would let the pre-2.2 branch rest in peace. All is dependencies 
are so extremely old and the jdks for some are no longer available. At least I 
probably wouldn't touch it and focus on the "middle"...
 +1 !

Possibly have a look at 3.0 (haven't done that yet).

I tried using 3.0 for a project.  Some good ideas and simple enough 
implementation but I don't think there is enough there for it to be worth 
saving

Chris

Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: Cédric Damioli mailto:cdami...@apache.org>>
Sent: Monday, November 20, 2023 3:47:14 PM
To: dev@cocoon.apache.org<mailto:dev@cocoon.apache.org> 
mailto:dev@cocoon.apache.org>>
Subject: Re: Now that the release is out, what's next?

Hi,

On top of that, as a community, we now have to formally answer to the below 
question (going or not to the Attic) not only once, but three times, one time 
for each subproject we still officially maintain since more than 10 years :
 - Cocoon 2.1.x (pre-Spring, pre-Maven). Last release 2.1.13 was rolled out 3 
years ago.
 - Cocoon 2.2x (now 2.3.x). Last release these days.
 - Cocoon 3.0.x. Last release 3.0.0-alpha-3 back in 2011

Those 3 versions are not compatible with each other, are not meant as drop-in 
replacements, and have evolved differently over the years.

The community could either decide to stop the project as-is and go to the 
Attic, or start over maintaining only one or two branches.

Cédric

Le 19/11/2023 à 18:20, Christofer Dutz a écrit :

Hi folks,



So, it seems that we finally have finished the last missing steps to formally 
get the release out the door. Now I think comes a time where we should reflect 
and discuss, what should happen with the Project.



So instead of simply saying: Releasing it was such a struggle (not technically, 
but from a participation side) I wouldn’t say this project is healthy and we 
should discuss a move into the Attic.



However, I could also imagine that the changes I implemented in the build might 
encourage some folks to give it another go.



I know when I was doing projects with Cocoon as part of my day-job 20 years 
ago, Cocoon 2.2 sort of completely broke my flow. Not only my inexperience with 
Maven, but also that of Spring and the versioning scheme where all sorts of 
cocoon modules had different versions just made me give up at that time and 
switch to Adobe Flex ;-)



Now (15 years later) Maven and Spring have evolved and with the cleanups in the 
build, it should be a lot simpler to work with Cocoon and with all modules 
sharing the same version, also this should be a lot simpler.



So, I would like to ask you folks:

  *   Should we

Re: Now that the release is out, what's next?

[Gabriel Gruber]

Hi all,

In regards to Cédric's question about which project should go to the attic and 
which ones should stay alive, my vote clearly goes to the Cocoon 2.3.x stuff, 
as it is using mainstream build technology and base container infrastructure, 
while still containing all of the original cocoon ideas. C3 is nice, but 
incomplete in comparison to C22.

I think it is worth moving the new C2.3 baseline to github and trying a 
community restart.

WDYT?

Gabriel




Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: Christofer Dutz 
Sent: Tuesday, November 21, 2023 10:55:50 PM
To: dev@cocoon.apache.org 
Subject: Re: Now that the release is out, what's next?

Well for me, the one thing at has changed since then, is that I've become a 
maven wizard  and a certified spring professional myself. Maven is my primary 
build tool and spring my primary component framework. Cocoon was just a read 
ahead of its time then.

Now I wouldn't want to touch an Ant build anymore and am happy we left the 
jakarta/avalon times behind us ;-)

Chris

Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: insigh...@gmail.com 
Sent: Tuesday, November 21, 2023 10:26:05 PM
To: dev@cocoon.apache.org 
Subject: Re: Now that the release is out, what's next?

Like Chris, I never could adapt to the build and Spring changes in Cocoon 2.2, 
and continued (until a few years ago) to develop projects from Cocoon 2.1 
(v2.1.13). I love and am still passionate about the original 2.1 framework, 
having used it since 2002. In fact, I would still be using it if not for 
security, and other, challenges with the old code.

The thing that drew me to Cocoon in the first place was the terrific pipeline 
transformer architecture: it really fit the text transforming ability of XSLT. 
It is something I greatly miss in Python.

I like the idea of using GitHub (https://github.com/apache/cocoon), as it may 
expose more people to the project. In this regard, explaining what Cocoon does, 
benefits of using it etc., might attract some passers by.

Thank you to all of you, who have, over the years, contributed and participated 
in this beautiful piece of software.

Dan

===


On 2023-11-21 6:46 a.m., Peter Hunsberger wrote:

On Tue, Nov 21, 2023 at 12:15 AM Christofer Dutz 
mailto:christofer.d...@c-ware.de>> wrote:
Well guess I haven't stated it yet: I would be willing to work on it (I've 
especially for some ideas on streaming industrial data from plc4x).

Personally I would let the pre-2.2 branch rest in peace. All is dependencies 
are so extremely old and the jdks for some are no longer available. At least I 
probably wouldn't touch it and focus on the "middle"...
 +1 !

Possibly have a look at 3.0 (haven't done that yet).

I tried using 3.0 for a project.  Some good ideas and simple enough 
implementation but I don't think there is enough there for it to be worth 
saving

Chris

Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: Cédric Damioli mailto:cdami...@apache.org>>
Sent: Monday, November 20, 2023 3:47:14 PM
To: dev@cocoon.apache.org<mailto:dev@cocoon.apache.org> 
mailto:dev@cocoon.apache.org>>
Subject: Re: Now that the release is out, what's next?

Hi,

On top of that, as a community, we now have to formally answer to the below 
question (going or not to the Attic) not only once, but three times, one time 
for each subproject we still officially maintain since more than 10 years :
 - Cocoon 2.1.x (pre-Spring, pre-Maven). Last release 2.1.13 was rolled out 3 
years ago.
 - Cocoon 2.2x (now 2.3.x). Last release these days.
 - Cocoon 3.0.x. Last release 3.0.0-alpha-3 back in 2011

Those 3 versions are not compatible with each other, are not meant as drop-in 
replacements, and have evolved differently over the years.

The community could either decide to stop the project as-is and go to the 
Attic, or start over maintaining only one or two branches.

Cédric

Le 19/11/2023 à 18:20, Christofer Dutz a écrit :

Hi folks,



So, it seems that we finally have finished the last missing steps to formally 
get the release out the door. Now I think comes a time where we should reflect 
and discuss, what should happen with the Project.



So instead of simply saying: Releasing it was such a struggle (not technically, 
but from a participation side) I wouldn’t say this project is healthy and we 
should discuss a move into the Attic.



However, I could also imagine that the changes I implemented in the build might 
encourage some folks to give it another go.



I know when I was doing projects with Cocoon as part of my day-job 20 years 
ago, Cocoon 2.2 sort of completely broke my flow. Not only my inexperience with 
Maven, but also that of Spring and the versioning scheme where all sorts of 
cocoon modules had different

Re: Now that the release is out, what's next?

[Christofer Dutz]

Well for me, the one thing at has changed since then, is that I've become a 
maven wizard  and a certified spring professional myself. Maven is my primary 
build tool and spring my primary component framework. Cocoon was just a read 
ahead of its time then.

Now I wouldn't want to touch an Ant build anymore and am happy we left the 
jakarta/avalon times behind us ;-)

Chris

Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: insigh...@gmail.com 
Sent: Tuesday, November 21, 2023 10:26:05 PM
To: dev@cocoon.apache.org 
Subject: Re: Now that the release is out, what's next?

Like Chris, I never could adapt to the build and Spring changes in Cocoon 2.2, 
and continued (until a few years ago) to develop projects from Cocoon 2.1 
(v2.1.13). I love and am still passionate about the original 2.1 framework, 
having used it since 2002. In fact, I would still be using it if not for 
security, and other, challenges with the old code.

The thing that drew me to Cocoon in the first place was the terrific pipeline 
transformer architecture: it really fit the text transforming ability of XSLT. 
It is something I greatly miss in Python.

I like the idea of using GitHub (https://github.com/apache/cocoon), as it may 
expose more people to the project. In this regard, explaining what Cocoon does, 
benefits of using it etc., might attract some passers by.

Thank you to all of you, who have, over the years, contributed and participated 
in this beautiful piece of software.

Dan

===


On 2023-11-21 6:46 a.m., Peter Hunsberger wrote:

On Tue, Nov 21, 2023 at 12:15 AM Christofer Dutz 
mailto:christofer.d...@c-ware.de>> wrote:
Well guess I haven't stated it yet: I would be willing to work on it (I've 
especially for some ideas on streaming industrial data from plc4x).

Personally I would let the pre-2.2 branch rest in peace. All is dependencies 
are so extremely old and the jdks for some are no longer available. At least I 
probably wouldn't touch it and focus on the "middle"...
 +1 !

Possibly have a look at 3.0 (haven't done that yet).

I tried using 3.0 for a project.  Some good ideas and simple enough 
implementation but I don't think there is enough there for it to be worth 
saving

Chris

Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: Cédric Damioli mailto:cdami...@apache.org>>
Sent: Monday, November 20, 2023 3:47:14 PM
To: dev@cocoon.apache.org<mailto:dev@cocoon.apache.org> 
mailto:dev@cocoon.apache.org>>
Subject: Re: Now that the release is out, what's next?

Hi,

On top of that, as a community, we now have to formally answer to the below 
question (going or not to the Attic) not only once, but three times, one time 
for each subproject we still officially maintain since more than 10 years :
 - Cocoon 2.1.x (pre-Spring, pre-Maven). Last release 2.1.13 was rolled out 3 
years ago.
 - Cocoon 2.2x (now 2.3.x). Last release these days.
 - Cocoon 3.0.x. Last release 3.0.0-alpha-3 back in 2011

Those 3 versions are not compatible with each other, are not meant as drop-in 
replacements, and have evolved differently over the years.

The community could either decide to stop the project as-is and go to the 
Attic, or start over maintaining only one or two branches.

Cédric

Le 19/11/2023 à 18:20, Christofer Dutz a écrit :

Hi folks,



So, it seems that we finally have finished the last missing steps to formally 
get the release out the door. Now I think comes a time where we should reflect 
and discuss, what should happen with the Project.



So instead of simply saying: Releasing it was such a struggle (not technically, 
but from a participation side) I wouldn’t say this project is healthy and we 
should discuss a move into the Attic.



However, I could also imagine that the changes I implemented in the build might 
encourage some folks to give it another go.



I know when I was doing projects with Cocoon as part of my day-job 20 years 
ago, Cocoon 2.2 sort of completely broke my flow. Not only my inexperience with 
Maven, but also that of Spring and the versioning scheme where all sorts of 
cocoon modules had different versions just made me give up at that time and 
switch to Adobe Flex ;-)



Now (15 years later) Maven and Spring have evolved and with the cleanups in the 
build, it should be a lot simpler to work with Cocoon and with all modules 
sharing the same version, also this should be a lot simpler.



So, I would like to ask you folks:

  *   Should we aim directly for the Attic?
  *   Does anyone want to revive the project? (I’m intentionally not only 
addressing committers and PMC members, but also people wanting to keep the 
project alive)





Chris


--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org<http://www.ametys.org>

Re: Now that the release is out, what's next?

[insigh...@gmail.com]

Like Chris, I never could adapt to the build and Spring changes in 
Cocoon 2.2, and continued (until a few years ago) to develop projects 
from Cocoon 2.1 (v2.1.13). I love and am still passionate about the 
original 2.1 framework, having used it since 2002. In fact, I would 
still be using it if not for security, and other, challenges with the 
old code.


The thing that drew me to Cocoon in the first place was the terrific 
pipeline transformer architecture: it really fit the text transforming 
ability of XSLT. It is something I greatly miss in Python.


I like the idea of using GitHub (https://github.com/apache/cocoon), as 
it may expose more people to the project. In this regard, explaining 
what Cocoon does, benefits of using it etc., might attract some passers by.


Thank you to all of you, who have, over the years, contributed and 
participated in this beautiful piece of software.


Dan

===


On 2023-11-21 6:46 a.m., Peter Hunsberger wrote:


On Tue, Nov 21, 2023 at 12:15 AM Christofer Dutz 
 wrote:


Well guess I haven't stated it yet: I would be willing to work on
it (I've especially for some ideas on streaming industrial data
from plc4x).

Personally I would let the pre-2.2 branch rest in peace. All is
dependencies are so extremely old and the jdks for some are no
longer available. At least I probably wouldn't touch it and focus
on the "middle"...

 +1 !

Possibly have a look at 3.0 (haven't done that yet).


I tried using 3.0 for a project.  Some good ideas and simple enough 
implementation but I don't think there is enough there for it to be 
worth saving



Chris

Gesendet von Outlook für Android <https://aka.ms/AAb9ysg>

*From:* Cédric Damioli 
*Sent:* Monday, November 20, 2023 3:47:14 PM
*To:* dev@cocoon.apache.org 
*Subject:* Re: Now that the release is out, what's next?
Hi,

On top of that, as a community, we now have to formally answer to
the below question (going or not to the Attic) not only once, but
three times, one time for each subproject we still officially
maintain since more than 10 years :
 - Cocoon 2.1.x (pre-Spring, pre-Maven). Last release 2.1.13 was
rolled out 3 years ago.
 - Cocoon 2.2x (now 2.3.x). Last release these days.
 - Cocoon 3.0.x. Last release 3.0.0-alpha-3 back in 2011

Those 3 versions are not compatible with each other, are not meant
as drop-in replacements, and have evolved differently over the years.

The community could either decide to stop the project as-is and go
to the Attic, or start over maintaining only one or two branches.

Cédric

Le 19/11/2023 à 18:20, Christofer Dutz a écrit :


Hi folks,

So, it seems that we finally have finished the last missing steps
to formally get the release out the door. Now I think comes a
time where we should reflect and discuss, what should happen with
the Project.

So instead of simply saying: Releasing it was such a struggle
(not technically, but from a participation side) I wouldn’t say
this project is healthy and we should discuss a move into the Attic.

However, I could also imagine that the changes I implemented in
the build might encourage some folks to give it another go.

I know when I was doing projects with Cocoon as part of my
day-job 20 years ago, Cocoon 2.2 sort of completely broke my
flow. Not only my inexperience with Maven, but also that of
Spring and the versioning scheme where all sorts of cocoon
modules had different versions just made me give up at that time
and switch to Adobe Flex ;-)

Now (15 years later) Maven and Spring have evolved and with the
cleanups in the build, it should be a lot simpler to work with
Cocoon and with all modules sharing the same version, also this
should be a lot simpler.

So, I would like to ask you folks:

  * Should we aim directly for the Attic?
  * Does anyone want to revive the project? (I’m intentionally
not only addressing committers and PMC members, but also
people wanting to keep the project alive)

Chris



-- 
Cédric Damioli

CMS - Java - Open Source
www.ametys.org  <http://www.ametys.org>

Re: Now that the release is out, what's next?

[Peter Hunsberger]

On Tue, Nov 21, 2023 at 12:15 AM Christofer Dutz 
wrote:

> Well guess I haven't stated it yet: I would be willing to work on it (I've
> especially for some ideas on streaming industrial data from plc4x).
>
> Personally I would let the pre-2.2 branch rest in peace. All is
> dependencies are so extremely old and the jdks for some are no longer
> available. At least I probably wouldn't touch it and focus on the
> "middle"...
>
 +1 !


> Possibly have a look at 3.0 (haven't done that yet).
>

I tried using 3.0 for a project.  Some good ideas and simple enough
implementation but I don't think there is enough there for it to be worth
saving

>
> Chris
>
> Gesendet von Outlook für Android <https://aka.ms/AAb9ysg>
> --
> *From:* Cédric Damioli 
> *Sent:* Monday, November 20, 2023 3:47:14 PM
> *To:* dev@cocoon.apache.org 
> *Subject:* Re: Now that the release is out, what's next?
>
> Hi,
>
> On top of that, as a community, we now have to formally answer to the
> below question (going or not to the Attic) not only once, but three times,
> one time for each subproject we still officially maintain since more than
> 10 years :
>  - Cocoon 2.1.x (pre-Spring, pre-Maven). Last release 2.1.13 was rolled
> out 3 years ago.
>  - Cocoon 2.2x (now 2.3.x). Last release these days.
>  - Cocoon 3.0.x. Last release 3.0.0-alpha-3 back in 2011
>
> Those 3 versions are not compatible with each other, are not meant as
> drop-in replacements, and have evolved differently over the years.
>
> The community could either decide to stop the project as-is and go to the
> Attic, or start over maintaining only one or two branches.
>
> Cédric
>
> Le 19/11/2023 à 18:20, Christofer Dutz a écrit :
>
> Hi folks,
>
>
>
> So, it seems that we finally have finished the last missing steps to
> formally get the release out the door. Now I think comes a time where we
> should reflect and discuss, what should happen with the Project.
>
>
>
> So instead of simply saying: Releasing it was such a struggle (not
> technically, but from a participation side) I wouldn’t say this project is
> healthy and we should discuss a move into the Attic.
>
>
>
> However, I could also imagine that the changes I implemented in the build
> might encourage some folks to give it another go.
>
>
>
> I know when I was doing projects with Cocoon as part of my day-job 20
> years ago, Cocoon 2.2 sort of completely broke my flow. Not only my
> inexperience with Maven, but also that of Spring and the versioning scheme
> where all sorts of cocoon modules had different versions just made me give
> up at that time and switch to Adobe Flex ;-)
>
>
>
> Now (15 years later) Maven and Spring have evolved and with the cleanups
> in the build, it should be a lot simpler to work with Cocoon and with all
> modules sharing the same version, also this should be a lot simpler.
>
>
>
> So, I would like to ask you folks:
>
>- Should we aim directly for the Attic?
>- Does anyone want to revive the project? (I’m intentionally not only
>addressing committers and PMC members, but also people wanting to keep the
>project alive)
>
>
>
>
>
> Chris
>
>
> --
> Cédric Damioli
> CMS - Java - Open Sourcewww.ametys.org
>
>

Re: Now that the release is out, what's next?

[Christofer Dutz]

Well guess I haven't stated it yet: I would be willing to work on it (I've 
especially for some ideas on streaming industrial data from plc4x).

Personally I would let the pre-2.2 branch rest in peace. All is dependencies 
are so extremely old and the jdks for some are no longer available. At least I 
probably wouldn't touch it and focus on the "middle"... Possibly have a look at 
3.0 (haven't done that yet).

Chris

Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: Cédric Damioli 
Sent: Monday, November 20, 2023 3:47:14 PM
To: dev@cocoon.apache.org 
Subject: Re: Now that the release is out, what's next?

Hi,

On top of that, as a community, we now have to formally answer to the below 
question (going or not to the Attic) not only once, but three times, one time 
for each subproject we still officially maintain since more than 10 years :
 - Cocoon 2.1.x (pre-Spring, pre-Maven). Last release 2.1.13 was rolled out 3 
years ago.
 - Cocoon 2.2x (now 2.3.x). Last release these days.
 - Cocoon 3.0.x. Last release 3.0.0-alpha-3 back in 2011

Those 3 versions are not compatible with each other, are not meant as drop-in 
replacements, and have evolved differently over the years.

The community could either decide to stop the project as-is and go to the 
Attic, or start over maintaining only one or two branches.

Cédric

Le 19/11/2023 à 18:20, Christofer Dutz a écrit :

Hi folks,



So, it seems that we finally have finished the last missing steps to formally 
get the release out the door. Now I think comes a time where we should reflect 
and discuss, what should happen with the Project.



So instead of simply saying: Releasing it was such a struggle (not technically, 
but from a participation side) I wouldn’t say this project is healthy and we 
should discuss a move into the Attic.



However, I could also imagine that the changes I implemented in the build might 
encourage some folks to give it another go.



I know when I was doing projects with Cocoon as part of my day-job 20 years 
ago, Cocoon 2.2 sort of completely broke my flow. Not only my inexperience with 
Maven, but also that of Spring and the versioning scheme where all sorts of 
cocoon modules had different versions just made me give up at that time and 
switch to Adobe Flex ;-)



Now (15 years later) Maven and Spring have evolved and with the cleanups in the 
build, it should be a lot simpler to work with Cocoon and with all modules 
sharing the same version, also this should be a lot simpler.



So, I would like to ask you folks:

  *   Should we aim directly for the Attic?
  *   Does anyone want to revive the project? (I’m intentionally not only 
addressing committers and PMC members, but also people wanting to keep the 
project alive)





Chris


--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org<http://www.ametys.org>

Re: [DISCUSS] Switching to GIt?

[Cédric Damioli]

I know my answer will be sort of chicken-egg issue, but I'd like to be 
sure that there is enough manpower to revive and/or continue to maintain 
the project, before putting efforts to move to Git.


My 2 cents,

Cédric

Le 20/11/2023 à 15:43, Christofer Dutz a écrit :


Hi all,

I know that we currently have a mirror of the SVN in Github, however 
still the root repository is SVN, I would like to propose switching to 
using Git as the main repo.


This would allow us to start using the normal GitHub Pull-Request 
workflow and possibly make it a lot easier for new contributors to 
contribute.


Also, would I propose to start using GitHub Actions, GitHub Issues and 
GitHub discussions as in other projects this has proven to lower the 
barriers for new contributors (And it avoids the Jira account 
approving nightmare). With the changes in the messaging defaults, that 
I recently deployed, mirroring GitHub activity to the dev-list should 
allow everyone to participate.


What do the others think?

Chris

Re: Now that the release is out, what's next?

[Cédric Damioli]

Hi,

On top of that, as a community, we now have to formally answer to the 
below question (going or not to the Attic) not only once, but three 
times, one time for each subproject we still officially maintain since 
more than 10 years :
 - Cocoon 2.1.x (pre-Spring, pre-Maven). Last release 2.1.13 was rolled 
out 3 years ago.

 - Cocoon 2.2x (now 2.3.x). Last release these days.
 - Cocoon 3.0.x. Last release 3.0.0-alpha-3 back in 2011

Those 3 versions are not compatible with each other, are not meant as 
drop-in replacements, and have evolved differently over the years.


The community could either decide to stop the project as-is and go to 
the Attic, or start over maintaining only one or two branches.


Cédric

Le 19/11/2023 à 18:20, Christofer Dutz a écrit :


Hi folks,

So, it seems that we finally have finished the last missing steps to 
formally get the release out the door. Now I think comes a time where 
we should reflect and discuss, what should happen with the Project.


So instead of simply saying: Releasing it was such a struggle (not 
technically, but from a participation side) I wouldn’t say this 
project is healthy and we should discuss a move into the Attic.


However, I could also imagine that the changes I implemented in the 
build might encourage some folks to give it another go.


I know when I was doing projects with Cocoon as part of my day-job 20 
years ago, Cocoon 2.2 sort of completely broke my flow. Not only my 
inexperience with Maven, but also that of Spring and the versioning 
scheme where all sorts of cocoon modules had different versions just 
made me give up at that time and switch to Adobe Flex ;-)


Now (15 years later) Maven and Spring have evolved and with the 
cleanups in the build, it should be a lot simpler to work with Cocoon 
and with all modules sharing the same version, also this should be a 
lot simpler.


So, I would like to ask you folks:

  * Should we aim directly for the Attic?
  * Does anyone want to revive the project? (I’m intentionally not
only addressing committers and PMC members, but also people
wanting to keep the project alive)

Chris



--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org

Re: Now that the release is out, what's next?

[Peter Hunsberger]

On Mon, Nov 20, 2023 at 3:35 AM Christofer Dutz 
wrote:

> Hi Gabriel,
>
>
>
> I was more referring to the first response and I have seen loads of
> similar responses when initiating Attic discussions in the past with other
> projects. I just wanted to make it clear, that a projects livelihood is
> defined by the people giving and not the people wanting ;-)
>
>
>
> Becoming a contributor is easy. Perhaps it would make sense for us to
> formally switch to Git, because then it would be a lot simpler:
>
>- Create a fork
>- Do your changes in that fork
>- Create a PR
>- Have someone merge these changes
>- Hopefully get voted in as committer soon
>
> Perhaps switching to Git would be a good first step.
>
>
>
+1 for switching to Git

Peter Hunsberger



> Chris
>
>
>
>
>
> *Von: *Gabriel Gruber 
> *Datum: *Montag, 20. November 2023 um 10:26
> *An: *dev@cocoon.apache.org 
> *Betreff: *Re: Now that the release is out, what's next?
>
> Hello Christopher,
>
> just to make it clear. I AM willing to participate and contribute. I was
> the pushing force on the Spring 4 dependency upgrade. And meanwhile our
> cocoon 2 instance runs on spring 5 and java 11 – so I have some stuff,
> which I would love to get into the OS project again.
>
> As I said I would like to contribute further to make cocoon 2 compatible
> with state-of-the-art dependencies like java 21 and spring 6.
>
> However I need some help to become a formal contributor. Maybee you could
> help me in that?
>
> Thank you
>
> Gabriel
>
>
>
>
>
> *From: *Christofer Dutz 
> *Date: *Monday, 20. November 2023 at 10:08
> *To: *dev@cocoon.apache.org 
> *Subject: *AW: Now that the release is out, what's next?
>
> Hi all,
>
>
>
> let me mention one thing here … Open-Source is not a need-driven thing,
> that anyone is entitled to exist to solve one owns needs. It’s an
> initiative-driven thing that anyone can participate.
>
>
>
> So, if you need some open-source solution, you should consider actively
> contributing. Because if nobody contributes, then the open-source project
> will die and move into the attic.
>
>
>
> An alternative for this is that people and companies can pay someone else
> to participate in their place.
>
>
>
> But in the end, if nobody works on it, it’s going to go into the attic.
>
>
>
> I hope with my general overhaul of the build and project structure, I have
> made contributing and releasing a lot simpler, but I’m not planning on
> keeping the lights on, if I’m the only one working.
>
>
>
> Chris
>
>
>
>
>
>
>
> *Von: *Gabriel Gruber 
> *Datum: *Sonntag, 19. November 2023 um 19:55
> *An: *dev@cocoon.apache.org 
> *Betreff: *Re: Now that the release is out, what's next?
>
> Hi cocoon team,
>
>
>
> as we are still using cocoon 2.2 in PROD as base for our product, we have
> a high interest that the open source project stays alive.  Our main
> motivation here would be framework and java compatibility as well as
> security patches.
>
>
>
> Of course I am also willing to actively support and maintain. A great
> improvement would be, if the source-code could move to github.
>
>
>
> Thanks Chris for your enormous efforts to get this release through! Thanks
> to all the committers for building such a great and long lasting project.
>
>
>
> Gabriel
>
>
>
> *From: *insigh...@gmail.com 
> *Date: *Sunday, 19. November 2023 at 19:36
> *To: *dev@cocoon.apache.org 
> *Subject: *Re: Now that the release is out, what's next?
>
> I mentioned this early, the DSpace Content Management project used Cocoon
> 2.2 until version 6.4 (v7 moved to Angular JS). They integrated with Solr
> and did a bunch of other things that may be worth a look.
>
> The Cocoon interface was called xmlui (look for the subfolder), and
> available via Github:
>
> https://github.com/DSpace/DSpace/releases
>
> Source Code:
> https://github.com/DSpace/DSpace/archive/refs/tags/dspace-6.4.tar.gz
>
> Great work on continuing the Cocoon legacy!
>
> Dan
>
>
>
> On 2023-11-19 10:20 a.m., Christofer Dutz wrote:
>
> Hi folks,
>
>
>
> So, it seems that we finally have finished the last missing steps to
> formally get the release out the door. Now I think comes a time where we
> should reflect and discuss, what should happen with the Project.
>
>
>
> So instead of simply saying: Releasing it was such a struggle (not
> technically, but from a participation side) I wouldn’t say this project is
> healthy and we should discuss a move into the Attic.
>
>
>
> Howeve

Re: Now that the release is out, what's next?

[Gabriel Gruber]

Hello Christopher,
just to make it clear. I AM willing to participate and contribute. I was the 
pushing force on the Spring 4 dependency upgrade. And meanwhile our cocoon 2 
instance runs on spring 5 and java 11 – so I have some stuff, which I would 
love to get into the OS project again.
As I said I would like to contribute further to make cocoon 2 compatible with 
state-of-the-art dependencies like java 21 and spring 6.
However I need some help to become a formal contributor. Maybee you could help 
me in that?
Thank you
Gabriel


From: Christofer Dutz 
Date: Monday, 20. November 2023 at 10:08
To: dev@cocoon.apache.org 
Subject: AW: Now that the release is out, what's next?
Hi all,

let me mention one thing here … Open-Source is not a need-driven thing, that 
anyone is entitled to exist to solve one owns needs. It’s an initiative-driven 
thing that anyone can participate.

So, if you need some open-source solution, you should consider actively 
contributing. Because if nobody contributes, then the open-source project will 
die and move into the attic.

An alternative for this is that people and companies can pay someone else to 
participate in their place.

But in the end, if nobody works on it, it’s going to go into the attic.

I hope with my general overhaul of the build and project structure, I have made 
contributing and releasing a lot simpler, but I’m not planning on keeping the 
lights on, if I’m the only one working.

Chris



Von: Gabriel Gruber 
Datum: Sonntag, 19. November 2023 um 19:55
An: dev@cocoon.apache.org 
Betreff: Re: Now that the release is out, what's next?
Hi cocoon team,

as we are still using cocoon 2.2 in PROD as base for our product, we have a 
high interest that the open source project stays alive.  Our main motivation 
here would be framework and java compatibility as well as security patches.

Of course I am also willing to actively support and maintain. A great 
improvement would be, if the source-code could move to github.

Thanks Chris for your enormous efforts to get this release through! Thanks to 
all the committers for building such a great and long lasting project.

Gabriel

From: insigh...@gmail.com 
Date: Sunday, 19. November 2023 at 19:36
To: dev@cocoon.apache.org 
Subject: Re: Now that the release is out, what's next?

I mentioned this early, the DSpace Content Management project used Cocoon 2.2 
until version 6.4 (v7 moved to Angular JS). They integrated with Solr and did a 
bunch of other things that may be worth a look.

The Cocoon interface was called xmlui (look for the subfolder), and available 
via Github:

https://github.com/DSpace/DSpace/releases

Source Code: 
https://github.com/DSpace/DSpace/archive/refs/tags/dspace-6.4.tar.gz

Great work on continuing the Cocoon legacy!

Dan


On 2023-11-19 10:20 a.m., Christofer Dutz wrote:
Hi folks,

So, it seems that we finally have finished the last missing steps to formally 
get the release out the door. Now I think comes a time where we should reflect 
and discuss, what should happen with the Project.

So instead of simply saying: Releasing it was such a struggle (not technically, 
but from a participation side) I wouldn’t say this project is healthy and we 
should discuss a move into the Attic.

However, I could also imagine that the changes I implemented in the build might 
encourage some folks to give it another go.

I know when I was doing projects with Cocoon as part of my day-job 20 years 
ago, Cocoon 2.2 sort of completely broke my flow. Not only my inexperience with 
Maven, but also that of Spring and the versioning scheme where all sorts of 
cocoon modules had different versions just made me give up at that time and 
switch to Adobe Flex ;-)

Now (15 years later) Maven and Spring have evolved and with the cleanups in the 
build, it should be a lot simpler to work with Cocoon and with all modules 
sharing the same version, also this should be a lot simpler.

So, I would like to ask you folks:

  *   Should we aim directly for the Attic?
  *   Does anyone want to revive the project? (I’m intentionally not only 
addressing committers and PMC members, but also people wanting to keep the 
project alive)


Chris

Re: Now that the release is out, what's next?

[Gabriel Gruber]

Hi cocoon team,

as we are still using cocoon 2.2 in PROD as base for our product, we have a 
high interest that the open source project stays alive.  Our main motivation 
here would be framework and java compatibility as well as security patches.

Of course I am also willing to actively support and maintain. A great 
improvement would be, if the source-code could move to github.

Thanks Chris for your enormous efforts to get this release through! Thanks to 
all the committers for building such a great and long lasting project.

Gabriel

From: insigh...@gmail.com 
Date: Sunday, 19. November 2023 at 19:36
To: dev@cocoon.apache.org 
Subject: Re: Now that the release is out, what's next?

I mentioned this early, the DSpace Content Management project used Cocoon 2.2 
until version 6.4 (v7 moved to Angular JS). They integrated with Solr and did a 
bunch of other things that may be worth a look.

The Cocoon interface was called xmlui (look for the subfolder), and available 
via Github:

https://github.com/DSpace/DSpace/releases

Source Code: 
https://github.com/DSpace/DSpace/archive/refs/tags/dspace-6.4.tar.gz

Great work on continuing the Cocoon legacy!

Dan


On 2023-11-19 10:20 a.m., Christofer Dutz wrote:
Hi folks,

So, it seems that we finally have finished the last missing steps to formally 
get the release out the door. Now I think comes a time where we should reflect 
and discuss, what should happen with the Project.

So instead of simply saying: Releasing it was such a struggle (not technically, 
but from a participation side) I wouldn’t say this project is healthy and we 
should discuss a move into the Attic.

However, I could also imagine that the changes I implemented in the build might 
encourage some folks to give it another go.

I know when I was doing projects with Cocoon as part of my day-job 20 years 
ago, Cocoon 2.2 sort of completely broke my flow. Not only my inexperience with 
Maven, but also that of Spring and the versioning scheme where all sorts of 
cocoon modules had different versions just made me give up at that time and 
switch to Adobe Flex ;-)

Now (15 years later) Maven and Spring have evolved and with the cleanups in the 
build, it should be a lot simpler to work with Cocoon and with all modules 
sharing the same version, also this should be a lot simpler.

So, I would like to ask you folks:

  *   Should we aim directly for the Attic?
  *   Does anyone want to revive the project? (I’m intentionally not only 
addressing committers and PMC members, but also people wanting to keep the 
project alive)


Chris

Re: Now that the release is out, what's next?

[insigh...@gmail.com]

I mentioned this early, the DSpace Content Management project used 
Cocoon 2.2 until version 6.4 (v7 moved to Angular JS). They integrated 
with Solr and did a bunch of other things that may be worth a look.


The Cocoon interface was called xmlui (look for the subfolder), and 
available via Github:


https://github.com/DSpace/DSpace/releases

Source Code: 
https://github.com/DSpace/DSpace/archive/refs/tags/dspace-6.4.tar.gz


Great work on continuing the Cocoon legacy!

Dan


On 2023-11-19 10:20 a.m., Christofer Dutz wrote:


Hi folks,

So, it seems that we finally have finished the last missing steps to 
formally get the release out the door. Now I think comes a time where 
we should reflect and discuss, what should happen with the Project.


So instead of simply saying: Releasing it was such a struggle (not 
technically, but from a participation side) I wouldn’t say this 
project is healthy and we should discuss a move into the Attic.


However, I could also imagine that the changes I implemented in the 
build might encourage some folks to give it another go.


I know when I was doing projects with Cocoon as part of my day-job 20 
years ago, Cocoon 2.2 sort of completely broke my flow. Not only my 
inexperience with Maven, but also that of Spring and the versioning 
scheme where all sorts of cocoon modules had different versions just 
made me give up at that time and switch to Adobe Flex ;-)


Now (15 years later) Maven and Spring have evolved and with the 
cleanups in the build, it should be a lot simpler to work with Cocoon 
and with all modules sharing the same version, also this should be a 
lot simpler.


So, I would like to ask you folks:

  * Should we aim directly for the Attic?
  * Does anyone want to revive the project? (I’m intentionally not
only addressing committers and PMC members, but also people
wanting to keep the project alive)

Chris

Re: [VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/

[Christofer Dutz]

I'll do that as soon as I'm back from my business trip.

Chris

Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: David Crossley 
Sent: Wednesday, November 15, 2023 3:57:44 AM
To: dev@cocoon.apache.org 
Cc: Cocoon PMC List 
Subject: Re: [VOTE] Apache Cocoon 2.3.0 RC2 
https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/

Our KEYS file is at https://dist.apache.org/repos/dist/release/cocoon/KEYS

Chris, please add yours to that one, rather than "replacing" it
as is indicated in your temporary KEYS file.

And extensive gratitude to you for taking on this task.

-David

On Sun, Oct 29, 2023 at 09:01:12PM +, Christofer Dutz wrote:
> Here’s the KEYS file … there wasn’t any, so I initialized it with my key.
>
> https://dist.apache.org/repos/dist/dev/cocoon/KEYS
>
> Chris
>
> Von: Christofer Dutz 
> Datum: Sonntag, 29. Oktober 2023 um 21:09
> An: dev@cocoon.apache.org 
> Cc: Cocoon PMC List 
> Betreff: Re: [VOTE] Apache Cocoon 2.3.0 RC2 
> https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/
> I added my key to the KEYS file in the svn repo one level up..
>
> Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>
> 
> From: Peter Hunsberger 
> Sent: Sunday, October 29, 2023 6:16:02 PM
> To: dev@cocoon.apache.org 
> Cc: Cocoon PMC List 
> Subject: Re: [VOTE] Apache Cocoon 2.3.0 RC2 
> https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/
>
> Everything looks good except I can't check the signature, I get "No public 
> key" from gpg.  I believe I need a copy of your public key to import?
>
> Peter Hunsberger
>
>
> On Sun, Oct 29, 2023 at 6:55 AM Christofer Dutz 
> mailto:christofer.d...@c-ware.de>> wrote:
>
> Apache Cocoon 2.3.0 has been staged under [2] and it’s time to vote
>
> on accepting it for release. All Maven artifacts are available under [1].
>
> Voting will be open for 72hr.
>
>
>
> A minimum of 3 binding +1 votes and more binding +1 than binding -1
>
> are required to pass.
>
>
>
> Release tag: 
> https://svn.apache.org/viewvc/cocoon/tags/cocoon-2.3/cocoon/cocoon-2.3.0/
>
> Director revision of the tag: 1913422
>
>
>
> Per [3] "Before voting +1 PMC members are required to download
>
> the signed source code package, compile it as provided, and test
>
> the resulting executable on their own platform, along with also
>
> verifying that the package meets the requirements of the ASF policy
>
> on releases."
>
>
>
> You can achieve the above by following the guide of a fellow Apache project 
> [4].
>
>
>
> [ ]  +1 accept (indicate what you validated - e.g. performed the non-RM items 
> in [4])
>
> [ ]  -1 reject (explanation required)
>
>
>
>
>
> [1] https://repository.apache.org/content/repositories/orgapachecocoon-1007
>
> [2] https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/
>
> [3] https://www.apache.org/dev/release.html#approving-a-release
>
> [4] 
> https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
>
>

Re: [VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/

[David Crossley]

Our KEYS file is at https://dist.apache.org/repos/dist/release/cocoon/KEYS

Chris, please add yours to that one, rather than "replacing" it
as is indicated in your temporary KEYS file.

And extensive gratitude to you for taking on this task.

-David

On Sun, Oct 29, 2023 at 09:01:12PM +, Christofer Dutz wrote:
> Here’s the KEYS file … there wasn’t any, so I initialized it with my key.
> 
> https://dist.apache.org/repos/dist/dev/cocoon/KEYS
> 
> Chris
> 
> Von: Christofer Dutz 
> Datum: Sonntag, 29. Oktober 2023 um 21:09
> An: dev@cocoon.apache.org 
> Cc: Cocoon PMC List 
> Betreff: Re: [VOTE] Apache Cocoon 2.3.0 RC2 
> https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/
> I added my key to the KEYS file in the svn repo one level up..
> 
> Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>
> 
> From: Peter Hunsberger 
> Sent: Sunday, October 29, 2023 6:16:02 PM
> To: dev@cocoon.apache.org 
> Cc: Cocoon PMC List 
> Subject: Re: [VOTE] Apache Cocoon 2.3.0 RC2 
> https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/
> 
> Everything looks good except I can't check the signature, I get "No public 
> key" from gpg.  I believe I need a copy of your public key to import?
> 
> Peter Hunsberger
> 
> 
> On Sun, Oct 29, 2023 at 6:55 AM Christofer Dutz 
> mailto:christofer.d...@c-ware.de>> wrote:
> 
> Apache Cocoon 2.3.0 has been staged under [2] and it’s time to vote
> 
> on accepting it for release. All Maven artifacts are available under [1].
> 
> Voting will be open for 72hr.
> 
> 
> 
> A minimum of 3 binding +1 votes and more binding +1 than binding -1
> 
> are required to pass.
> 
> 
> 
> Release tag: 
> https://svn.apache.org/viewvc/cocoon/tags/cocoon-2.3/cocoon/cocoon-2.3.0/
> 
> Director revision of the tag: 1913422
> 
> 
> 
> Per [3] "Before voting +1 PMC members are required to download
> 
> the signed source code package, compile it as provided, and test
> 
> the resulting executable on their own platform, along with also
> 
> verifying that the package meets the requirements of the ASF policy
> 
> on releases."
> 
> 
> 
> You can achieve the above by following the guide of a fellow Apache project 
> [4].
> 
> 
> 
> [ ]  +1 accept (indicate what you validated - e.g. performed the non-RM items 
> in [4])
> 
> [ ]  -1 reject (explanation required)
> 
> 
> 
> 
> 
> [1] https://repository.apache.org/content/repositories/orgapachecocoon-1007
> 
> [2] https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/
> 
> [3] https://www.apache.org/dev/release.html#approving-a-release
> 
> [4] 
> https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
> 
> 

Re: [VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/

[David Crossley]

Here is my +1

Checked on macOS, JDK 17.

-David
> 

Re: [VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/

[Francesco Chicchiriccò]

Here is my +1.
Download and build checked on Linux, JDK 17.

Sorry it took so long.
Regards.

On 2023/10/29 11:55:14 Christofer Dutz wrote:
> Apache Cocoon 2.3.0 has been staged under [2] and it’s time to vote
> on accepting it for release. All Maven artifacts are available under [1].
> Voting will be open for 72hr.
> 
> A minimum of 3 binding +1 votes and more binding +1 than binding -1
> are required to pass.
> 
> Release tag: 
> https://svn.apache.org/viewvc/cocoon/tags/cocoon-2.3/cocoon/cocoon-2.3.0/
> Director revision of the tag: 1913422
> 
> Per [3] "Before voting +1 PMC members are required to download
> the signed source code package, compile it as provided, and test
> the resulting executable on their own platform, along with also
> verifying that the package meets the requirements of the ASF policy
> on releases."
> 
> You can achieve the above by following the guide of a fellow Apache project 
> [4].
> 
> [ ]  +1 accept (indicate what you validated - e.g. performed the non-RM items 
> in [4])
> [ ]  -1 reject (explanation required)
> 
> 
> [1] https://repository.apache.org/content/repositories/orgapachecocoon-1007
> [2] https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/
> [3] https://www.apache.org/dev/release.html#approving-a-release
> [4] 
> https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
> 
> 

Re: [VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/

[Cédric Damioli]

 - signature ok
 - checksum ok
 - Build ok (Windows, java 17)
 - Jetty launch ok
 - A few samples tested ok (I've not tested all samples, nor I am able 
to test this RC in a real world app, I don't use any Cocoon 2.2)


Here's my +1

Cédric


Le 29/10/2023 à 12:55, Christofer Dutz a écrit :


Apache Cocoon 2.3.0 has been staged under [2] and it’s time to vote

on accepting it for release. All Maven artifacts are available under [1].

Voting will be open for 72hr.

A minimum of 3 binding +1 votes and more binding +1 than binding -1

are required to pass.

Release 
tag:https://svn.apache.org/viewvc/cocoon/tags/cocoon-2.3/cocoon/cocoon-2.3.0/ 



Director revision of the tag: 1913422

Per [3] "Before voting +1 PMC members are required to download

the signed source code package, compile it as provided, and test

the resulting executable on their own platform, along with also

verifying that the package meets the requirements of the ASF policy

on releases."

You can achieve the above by following the guide of a fellow Apache 
project [4].


[ ]  +1 accept (indicate what you validated - e.g. performed the 
non-RM items in [4])


[ ]  -1 reject (explanation required)





--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org

Re: [VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/

[Christofer Dutz]

I added my key to the KEYS file in the svn repo one level up..

Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: Peter Hunsberger 
Sent: Sunday, October 29, 2023 6:16:02 PM
To: dev@cocoon.apache.org 
Cc: Cocoon PMC List 
Subject: Re: [VOTE] Apache Cocoon 2.3.0 RC2 
https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/

Everything looks good except I can't check the signature, I get "No public key" 
from gpg.  I believe I need a copy of your public key to import?

Peter Hunsberger


On Sun, Oct 29, 2023 at 6:55 AM Christofer Dutz 
mailto:christofer.d...@c-ware.de>> wrote:

Apache Cocoon 2.3.0 has been staged under [2] and it’s time to vote

on accepting it for release. All Maven artifacts are available under [1].

Voting will be open for 72hr.



A minimum of 3 binding +1 votes and more binding +1 than binding -1

are required to pass.



Release tag: 
https://svn.apache.org/viewvc/cocoon/tags/cocoon-2.3/cocoon/cocoon-2.3.0/

Director revision of the tag: 1913422



Per [3] "Before voting +1 PMC members are required to download

the signed source code package, compile it as provided, and test

the resulting executable on their own platform, along with also

verifying that the package meets the requirements of the ASF policy

on releases."



You can achieve the above by following the guide of a fellow Apache project [4].



[ ]  +1 accept (indicate what you validated - e.g. performed the non-RM items 
in [4])

[ ]  -1 reject (explanation required)





[1] https://repository.apache.org/content/repositories/orgapachecocoon-1007

[2] https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/

[3] https://www.apache.org/dev/release.html#approving-a-release

[4] 
https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release

Re: [VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/

[Peter Hunsberger]

Everything looks good except I can't check the signature, I get "No public
key" from gpg.  I believe I need a copy of your public key to import?

Peter Hunsberger


On Sun, Oct 29, 2023 at 6:55 AM Christofer Dutz 
wrote:

> Apache Cocoon 2.3.0 has been staged under [2] and it’s time to vote
>
> on accepting it for release. All Maven artifacts are available under [1].
>
> Voting will be open for 72hr.
>
>
>
> A minimum of 3 binding +1 votes and more binding +1 than binding -1
>
> are required to pass.
>
>
>
> Release tag:
> https://svn.apache.org/viewvc/cocoon/tags/cocoon-2.3/cocoon/cocoon-2.3.0/
>
> Director revision of the tag: 1913422
>
>
>
> Per [3] "Before voting +1 PMC members are required to download
>
> the signed source code package, compile it as provided, and test
>
> the resulting executable on their own platform, along with also
>
> verifying that the package meets the requirements of the ASF policy
>
> on releases."
>
>
>
> You can achieve the above by following the guide of a fellow Apache
> project [4].
>
>
>
> [ ]  +1 accept (indicate what you validated - e.g. performed the non-RM
> items in [4])
>
> [ ]  -1 reject (explanation required)
>
>
>
>
>
> [1]
> https://repository.apache.org/content/repositories/orgapachecocoon-1007
>
> [2] https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/
>
> [3] https://www.apache.org/dev/release.html#approving-a-release
>
> [4]
> https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
>
>
>

Re: [VOTE] Apache Cocoon 2.3.0 RC1

[Cédric Damioli]

Hi Christofer,

First of all, many thanks for the huge work you made so far for helping 
us finally rolling out a release.


Which is the target JVM for this release ?
On my Windows laptop, I can't compile with JDK 8, due to external 
dependencies being only JDK11+
And I also can't compile with JDK11+, due to XSP block complaining that 
it can't find tools.jar


Cédric

Le 24/10/2023 à 20:50, Christofer Dutz a écrit :


Apache Cocoon 2.3.0 has been staged under [2] and it’s time to vote

on accepting it for release. All Maven artifacts are available under [1].

Voting will be open for 72hr.

A minimum of 3 binding +1 votes and more binding +1 than binding -1

are required to pass.

Release tag: 
https://svn.apache.org/viewvc/cocoon/tags/cocoon-2.3/cocoon/cocoon-2.3.0/


Director revision of the tag: 1913280

Per [3] "Before voting +1 PMC members are required to download

the signed source code package, compile it as provided, and test

the resulting executable on their own platform, along with also

verifying that the package meets the requirements of the ASF policy

on releases."

You can achieve the above by following the guide of a fellow Apache 
project [4].


[ ]  +1 accept (indicate what you validated - e.g. performed the 
non-RM items in [4])


[ ]  -1 reject (explanation required)

[1] 
https://repository.apache.org/content/repositories/orgapachecocoon-1006 



[2] https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc1/ 



[3] https://www.apache.org/dev/release.html#approving-a-release 



[4] 
https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release 





--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org

Re: [VOTE] Apache Cocoon 2.3.0 RC1

[Gabriel Gruber]

Hi,

great we move finally to a new release :-) Thanks Christopher for taking care 
of it. I was wondering if there was a github clone of the repo, where the 
commits can be traced to give some feedback. We also are still cocoon 2.2 users 
and I helped with the spring migration (3->4) some years ago  on trunk. However 
in our own product last year we even moved to spring 5 and so I justed wanted 
to check, if that is an option too.

Thanks a lot for your efforts
Gabriel Gruber

Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

From: insigh...@gmail.com 
Sent: Tuesday, October 24, 2023 10:17:05 PM
To: dev@cocoon.apache.org 
Subject: Re: [VOTE] Apache Cocoon 2.3.0 RC1


Great work everyone on the Cocoon updates. To that end, was wondering if you 
are aware of the updates DSpace.org team/users did to their own Cocoon 2.2 
architecture?

DSpace v6 was the major version using Cocoon 2.2 (they have since moved to 
Angular JS)

Might be worth a look to see if some of that work can be ported into 2.3?

Dan


On 2023-10-24 12:50 p.m., Christofer Dutz wrote:

Apache Cocoon 2.3.0 has been staged under [2] and it’s time to vote

on accepting it for release. All Maven artifacts are available under [1].

Voting will be open for 72hr.



A minimum of 3 binding +1 votes and more binding +1 than binding -1

are required to pass.



Release tag: 
https://svn.apache.org/viewvc/cocoon/tags/cocoon-2.3/cocoon/cocoon-2.3.0/

Director revision of the tag: 1913280



Per [3] "Before voting +1 PMC members are required to download

the signed source code package, compile it as provided, and test

the resulting executable on their own platform, along with also

verifying that the package meets the requirements of the ASF policy

on releases."



You can achieve the above by following the guide of a fellow Apache project [4].



[ ]  +1 accept (indicate what you validated - e.g. performed the non-RM items 
in [4])

[ ]  -1 reject (explanation required)





[1] https://repository.apache.org/content/repositories/orgapachecocoon-1006

[2] https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc1/

[3] https://www.apache.org/dev/release.html#approving-a-release

[4] 
https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release

Re: [VOTE] Apache Cocoon 2.3.0 RC1

[insigh...@gmail.com]

Great work everyone on the Cocoon updates. To that end, was wondering if 
you are aware of the updates DSpace.org team/users did to their own 
Cocoon 2.2 architecture?


DSpace v6 was the major version using Cocoon 2.2 (they have since moved 
to Angular JS)


Might be worth a look to see if some of that work can be ported into 2.3?

Dan


On 2023-10-24 12:50 p.m., Christofer Dutz wrote:


Apache Cocoon 2.3.0 has been staged under [2] and it’s time to vote

on accepting it for release. All Maven artifacts are available under [1].

Voting will be open for 72hr.

A minimum of 3 binding +1 votes and more binding +1 than binding -1

are required to pass.

Release tag: 
https://svn.apache.org/viewvc/cocoon/tags/cocoon-2.3/cocoon/cocoon-2.3.0/


Director revision of the tag: 1913280

Per [3] "Before voting +1 PMC members are required to download

the signed source code package, compile it as provided, and test

the resulting executable on their own platform, along with also

verifying that the package meets the requirements of the ASF policy

on releases."

You can achieve the above by following the guide of a fellow Apache 
project [4].


[ ]  +1 accept (indicate what you validated - e.g. performed the 
non-RM items in [4])


[ ]  -1 reject (explanation required)

[1] 
https://repository.apache.org/content/repositories/orgapachecocoon-1006 



[2] https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc1/ 



[3] https://www.apache.org/dev/release.html#approving-a-release 



[4] 
https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release 

Re: [PR] Bump xalan:xalan from 2.7.2 to 2.7.3 [cocoon]

[via GitHub]

asfgit closed pull request #49: Bump xalan:xalan from 2.7.2 to 2.7.3
URL: https://github.com/apache/cocoon/pull/49


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cocoon.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump org.springframework:spring-core from 4.3.30.RELEASE to 5.2.24.RELEASE [cocoon]

[via GitHub]

asfgit closed pull request #51: Bump org.springframework:spring-core from 
4.3.30.RELEASE to 5.2.24.RELEASE
URL: https://github.com/apache/cocoon/pull/51


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cocoon.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump org.mortbay.jetty:jetty from 6.1.14 to 6.1.23 [cocoon]

[via GitHub]

asfgit closed pull request #50: Bump org.mortbay.jetty:jetty from 6.1.14 to 
6.1.23
URL: https://github.com/apache/cocoon/pull/50


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cocoon.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump org.apache.poi:poi from 3.2-FINAL to 4.1.1 [cocoon]

[via GitHub]

asfgit closed pull request #48: Bump org.apache.poi:poi from 3.2-FINAL to 4.1.1
URL: https://github.com/apache/cocoon/pull/48


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cocoon.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump xalan:xalan from 2.7.2 to 2.7.3 [cocoon]

[via GitHub]

dependabot[bot] commented on PR #49:
URL: https://github.com/apache/cocoon/pull/49#issuecomment-160626

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. If you'd rather skip all updates until the next 
major or minor version, let me know by commenting `@dependabot ignore this 
major version` or `@dependabot ignore this minor version`.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cocoon.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump org.springframework:spring-core from 4.3.30.RELEASE to 5.2.24.RELEASE [cocoon]

[via GitHub]

dependabot[bot] commented on PR #51:
URL: https://github.com/apache/cocoon/pull/51#issuecomment-160610

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. If you'd rather skip all updates until the next 
major or minor version, let me know by commenting `@dependabot ignore this 
major version` or `@dependabot ignore this minor version`.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cocoon.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump org.mortbay.jetty:jetty from 6.1.14 to 6.1.23 [cocoon]

[via GitHub]

dependabot[bot] commented on PR #50:
URL: https://github.com/apache/cocoon/pull/50#issuecomment-160589

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. If you'd rather skip all updates until the next 
major or minor version, let me know by commenting `@dependabot ignore this 
major version` or `@dependabot ignore this minor version`.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cocoon.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump org.apache.poi:poi from 3.2-FINAL to 4.1.1 [cocoon]

[via GitHub]

dependabot[bot] commented on PR #48:
URL: https://github.com/apache/cocoon/pull/48#issuecomment-160550

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. If you'd rather skip all updates until the next 
major or minor version, let me know by commenting `@dependabot ignore this 
major version` or `@dependabot ignore this minor version`.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cocoon.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: svn commit: r1878905 - /cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/generation/StreamGenerator.java

[Cédric Damioli]

Hi Antonio,

Welcome back :)

I think I get what you mean.
The purpose of this commit was explicitly to NOT use the configured 
Excalibur's SAXParser, due to security reason. But we certainly could 
implement it otherwise by declaring another specific poolable SAXFactory 
in the cocoon.xconf


Cédric


Le 02/11/2021 à 05:33, Antonio Gallardo a écrit :

Hi all,

It has been long time since I wrote an email in a Cocoon mail list. 
First I want to say hello to all my cocoon fellows.


I am writing, because reviewing this commit, I see we are moving apart 
from the cocoon pools that allows us to control how many instances of 
a given components are being created. Please see my comments between 
lines below.


Best Regards,

Antonio Gallardo.

El 16/6/20 a las 17:04, cdami...@apache.org escribió:

Author: cdamioli
Date: Tue Jun 16 23:04:30 2020
New Revision: 1878905

URL: http://svn.apache.org/viewvc?rev=1878905&view=rev
Log:
Make StreamGenerator more robust

Modified:
cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/generation/StreamGenerator.java

Modified: 
cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/generation/StreamGenerator.java
URL: 
http://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/generation/StreamGenerator.java?rev=1878905&r1=1878904&r2=1878905&view=diff
== 

--- 
cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/generation/StreamGenerator.java 
(original)
+++ 
cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/generation/StreamGenerator.java 
Tue Jun 16 23:04:30 2020

@@ -16,6 +16,16 @@
   */
  package org.apache.cocoon.generation;
  +import java.io.IOException;
+import java.io.InputStreamReader;
+import java.io.Reader;
+import java.io.StringReader;
+
+import javax.servlet.http.HttpServletRequest;
+import javax.xml.parsers.SAXParser;
+import javax.xml.parsers.SAXParserFactory;
+
+import org.apache.avalon.framework.activity.Initializable;
  import org.apache.cocoon.ProcessingException;
  import org.apache.cocoon.ResourceNotFoundException;
  import org.apache.cocoon.environment.ObjectModelHelper;
@@ -23,16 +33,11 @@ import org.apache.cocoon.environment.Req
  import org.apache.cocoon.environment.http.HttpEnvironment;
  import org.apache.cocoon.servlet.multipart.Part;
  import org.apache.cocoon.util.PostInputStream;
-import org.apache.excalibur.xml.sax.SAXParser;
+import org.xml.sax.ErrorHandler;
  import org.xml.sax.InputSource;
  import org.xml.sax.SAXException;
-
-import javax.servlet.http.HttpServletRequest;
-
-import java.io.IOException;
-import java.io.InputStreamReader;
-import java.io.Reader;
-import java.io.StringReader;
+import org.xml.sax.SAXParseException;
+import org.xml.sax.XMLReader;
    /**
   * @cocoon.sitemap.component.documentation
@@ -64,7 +69,7 @@ import java.io.StringReader;
   * @author mailto:kinga_dziembow...@hp.com";>Kinga 
Dziembowski

   * @version CVS $Id$
   */
-public class StreamGenerator extends ServiceableGenerator
+public class StreamGenerator extends ServiceableGenerator implements 
Initializable

  {
    /** The parameter holding the name associated with the xml 
data  **/

@@ -73,6 +78,9 @@ public class StreamGenerator extends Ser
  /** The input source */
  private InputSource inputSource;
  +    // don't use Excalibur's SAXParser to prevent XXE injection
+    private SAXParserFactory factory;
+
  /**
   * Recycle this component.
   * All instance variables are set to null.
@@ -81,13 +89,20 @@ public class StreamGenerator extends Ser
  super.recycle();
  this.inputSource = null;
  }
+
+    public void initialize() throws Exception {
+    factory = SAXParserFactory.newInstance();
+    factory.setNamespaceAware(true);
+    factory.setXIncludeAware(false);
+ 
factory.setFeature("http://xml.org/sax/features/external-general-entities";, 
false);
+ 
factory.setFeature("http://xml.org/sax/features/external-parameter-entities";, 
false);

+    }
    /**
   * Generate XML data out of request InputStream.
   */
  public void generate()
  throws IOException, SAXException, ProcessingException {
-    SAXParser parser = null;
  int len = 0;
  String contentType = null;
  @@ -149,9 +164,16 @@ public class StreamGenerator extends Ser
  String charset =  getCharacterEncoding(request, 
contentType) ;

  if( charset != null) {
  this.inputSource.setEncoding(charset);
-    }
-    parser = (SAXParser)this.manager.lookup(SAXParser.ROLE);
-    parser.parse(this.inputSource, super.xmlConsumer);



The above lines removes the part that was controlled by Cocoon. The 
manager allowed to defined how many instances of the Parser can be 
created. Very useful to handle how much memory the webapp will use.


Please see the place in cocoon.xconf when we define the parsers:
http://svn.apache.org/viewvc/

Re: [VOTE] Release Cocoon 2.1.13

[Torsten Curdt]

Ah, OK. Better!

gpg: Signature made Fr 17 Jul 20:05:16 2020 CEST
gpg:using RSA key F9E031E290C9797C7F4CC02576ABEF9A6CDA1E88
gpg: Good signature from "Cédric Damioli (CODE SIGNING KEY) <
cdami...@apache.org>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the
owner.

That said - we probably need to get your key some trust.
Someone close by for a quick key signing party? :)
But I don't believe that's a blocker.

I didn't find the time to get an old JDK and run and build the release.
But from the sources/diffs the release looks good.
So I am giving my +1

If SOME OTHER PEOPLE want to have a look at it ;)

  svn diff -r {2013-03-20}:{2020-08-01}
https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/
  svn log -r {2013-03-20}:{2020-08-01} --diff
https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/

Thanks Cédric!

On Mon, Jul 20, 2020 at 11:32 AM Cédric Damioli  wrote:

> Hi Torsten,
>
> I actually added my code signing key in
> https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/KEYS
>
> I wasn't aware of https://downloads.apache.org/cocoon/KEYS. I'll add my
> key to this file when uploading release artifacts.
>
> Is it ok for you ?
>
> Cédric
>
>
> Le 19/07/2020 à 19:18, Torsten Curdt a écrit :
>
> I did a
>
>   gpg --import KEYS.txt
>
> just to make sure, but I am still getting
>
>   gpg --verify cocoon-2.1.13-src.tar.gz.asc cocoon-2.1.13-src.tar.gz
>   gpg: Signature made Fr 17 Jul 20:05:16 2020 CEST
>   gpg:using RSA key
> F9E031E290C9797C7F4CC02576ABEF9A6CDA1E88
>   gpg: Can't check signature: No public key
>
> Is your key maybe missing from https://downloads.apache.org/cocoon/KEYS
>
> cheers,
> Torsten
>
> On Sat, Jul 18, 2020 at 7:08 AM Francesco Chicchiriccò <
> ilgro...@apache.org> wrote:
>
>> On 17/07/20 20:40, Cédric Damioli wrote:
>> > Hi,
>> >
>> > More than 7 years after the 2.1.12 release, I'm glad to propose to
>> release Apache Cocoon 2.1.13 !
>> >
>> > Proposed releases artifacts are located at
>> https://dist.apache.org/repos/dist/dev/cocoon/
>> >
>> > Please check the files, verify checksums, build and run samples, and
>> cast your votes.
>>
>> +1
>> Thanks Cédric!
>>
>> Regards.
>>
>> --
>> Francesco Chicchiriccò
>>
>> Tirasa - Open Source Excellence
>> http://www.tirasa.net/
>>
>> Member at The Apache Software Foundation
>> Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
>> http://home.apache.org/~ilgrosso/
>>
>>
> --
> Cédric Damioli
> CMS - Java - Open Sourcewww.ametys.org
>
>

Re: [VOTE] Release Cocoon 2.1.13

[Cédric Damioli]

Hi Torsten,

I actually added my code signing key in 
https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/KEYS


I wasn't aware of https://downloads.apache.org/cocoon/KEYS. I'll add my 
key to this file when uploading release artifacts.


Is it ok for you ?

Cédric


Le 19/07/2020 à 19:18, Torsten Curdt a écrit :

I did a

  gpg --import KEYS.txt

just to make sure, but I am still getting

  gpg --verify cocoon-2.1.13-src.tar.gz.asc cocoon-2.1.13-src.tar.gz
  gpg: Signature made Fr 17 Jul 20:05:16 2020 CEST
  gpg:                using RSA key 
F9E031E290C9797C7F4CC02576ABEF9A6CDA1E88

  gpg: Can't check signature: No public key

Is your key maybe missing from https://downloads.apache.org/cocoon/KEYS

cheers,
Torsten

On Sat, Jul 18, 2020 at 7:08 AM Francesco Chicchiriccò 
mailto:ilgro...@apache.org>> wrote:


On 17/07/20 20:40, Cédric Damioli wrote:
> Hi,
>
> More than 7 years after the 2.1.12 release, I'm glad to propose
to release Apache Cocoon 2.1.13 !
>
> Proposed releases artifacts are located at
https://dist.apache.org/repos/dist/dev/cocoon/
>
> Please check the files, verify checksums, build and run samples,
and cast your votes.

+1
Thanks Cédric!

Regards.

-- 
Francesco Chicchiriccò


Tirasa - Open Source Excellence
http://www.tirasa.net/

Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/



--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org

Re: [VOTE] Release Cocoon 2.1.13

[Torsten Curdt]

I did a

  gpg --import KEYS.txt

just to make sure, but I am still getting

  gpg --verify cocoon-2.1.13-src.tar.gz.asc cocoon-2.1.13-src.tar.gz
  gpg: Signature made Fr 17 Jul 20:05:16 2020 CEST
  gpg:using RSA key F9E031E290C9797C7F4CC02576ABEF9A6CDA1E88
  gpg: Can't check signature: No public key

Is your key maybe missing from https://downloads.apache.org/cocoon/KEYS

cheers,
Torsten

On Sat, Jul 18, 2020 at 7:08 AM Francesco Chicchiriccò 
wrote:

> On 17/07/20 20:40, Cédric Damioli wrote:
> > Hi,
> >
> > More than 7 years after the 2.1.12 release, I'm glad to propose to
> release Apache Cocoon 2.1.13 !
> >
> > Proposed releases artifacts are located at
> https://dist.apache.org/repos/dist/dev/cocoon/
> >
> > Please check the files, verify checksums, build and run samples, and
> cast your votes.
>
> +1
> Thanks Cédric!
>
> Regards.
>
> --
> Francesco Chicchiriccò
>
> Tirasa - Open Source Excellence
> http://www.tirasa.net/
>
> Member at The Apache Software Foundation
> Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
> http://home.apache.org/~ilgrosso/
>
>

Re: [VOTE] Release Cocoon 2.1.13

[Francesco Chicchiriccò]

On 17/07/20 20:40, Cédric Damioli wrote:
> Hi,
>
> More than 7 years after the 2.1.12 release, I'm glad to propose to release 
> Apache Cocoon 2.1.13 !
>
> Proposed releases artifacts are located at 
> https://dist.apache.org/repos/dist/dev/cocoon/
>
> Please check the files, verify checksums, build and run samples, and cast 
> your votes.

+1
Thanks Cédric!

Regards.

-- 
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/

Re: Fwd: Cocoon 2.1.X - Build # 141 - Still Failing

[Francesco Chicchiriccò]

On 25/06/20 19:52, Cédric Damioli wrote:
> Le 24/06/2020 à 10:52, Francesco Chicchiriccò a écrit :
>> On 24/06/20 09:42, Cédric Damioli wrote:
>>> Le 24/06/2020 à 08:57, Francesco Chicchiriccò a écrit :
 On 23/06/20 23:20, Cédric Damioli wrote:
> 
>
>
 Maybe we could do as you suggest - e.g. restore the previous 
 xalan-2.7.2.jar and strip out the indicated classes - but also renaming it 
 somehow, e.g. xalan-2.7.2-cocoon-2.1.13.jar and adding some explanation in 
 lib/jars.xml about how we obtained this JAR from official Xalan's JAR.

 Does it sound reasonable?
>>> +1 with your proposal
>> Glad to hear this, please go on.
>>
> Committed.
> Could you check that the build is ok on your side ? 

I can confirm it works like a charm - and Jenkins agrees:

https://builds.apache.org/view/A-D/view/Cocoon/job/Cocoon%202.1.X/143/

Good job!
Regards.

-- 
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/

Re: Fwd: Cocoon 2.1.X - Build # 141 - Still Failing

[Cédric Damioli]

Le 24/06/2020 à 10:52, Francesco Chicchiriccò a écrit :

On 24/06/20 09:42, Cédric Damioli wrote:

Le 24/06/2020 à 08:57, Francesco Chicchiriccò a écrit :

On 23/06/20 23:20, Cédric Damioli wrote:





Maybe we could do as you suggest - e.g. restore the previous xalan-2.7.2.jar 
and strip out the indicated classes - but also renaming it somehow, e.g. 
xalan-2.7.2-cocoon-2.1.13.jar and adding some explanation in lib/jars.xml about 
how we obtained this JAR from official Xalan's JAR.

Does it sound reasonable?

+1 with your proposal

Glad to hear this, please go on.


Committed.
Could you check that the build is ok on your side ?

Regards,
Cédric

Re: Fwd: Cocoon 2.1.X - Build # 141 - Still Failing

[Francesco Chicchiriccò]

On 24/06/20 09:42, Cédric Damioli wrote:
> Le 24/06/2020 à 08:57, Francesco Chicchiriccò a écrit :
>> On 23/06/20 23:20, Cédric Damioli wrote:
>>> 
>>>
>>>>> Why not, but are we sure that we won't have regressions due to downgrade 
>>>>> of jakarta-regexp (the xalan bundled version is 1.2 AFAIU) ?
>>>>>
>>>>>   From a design POV, I find it quite strange to rely on an XSLT lib (ie 
>>>>> Xalan) to provide regexp processing.
>>>>> Could it be better to remove org.apache.bcel and org.apache.regexp from 
>>>>> the xalan jar and keep the existing librairies ?
>>>>> I suppose that was how it has been done previously for xalan-2.7.1
>>>> It seems you are quite right.
>>>>
>>>> I took cocoon-2.1.12-deps.tar.gz from
>>>>
>>>> http://cocoon.apache.org/mirror.html
>>>>
>>>> then extracted
>>>>
>>>> lib/endorsed/xalan-2.7.1.jar
>>>>
>>>> and found that it is *not the same* you can download from Maven Central 
>>>> under
>>>>
>>>> https://repo1.maven.org/maven2/xalan/xalan/2.7.1/xalan-2.7.1.jar
>>>>
>>>> but that it matches the one you can download from
>>>>
>>>> http://archive.apache.org/dist/xalan/xalan-j/binaries/xalan-j_2_7_1-bin-2jars.zip
>>>>
>>>> because it does not contain any org.apache.bcel.* nor any 
>>>> org.apache.regexp.* class.
>>>>
>>>> So I went ahead and replaced the current
>>>>
>>>> lib/endorsed/xalan-2.7.2.jar
>>>>
>>>> in the source tree with the one contained in
>>>>
>>>> http://archive.apache.org/dist/xalan/xalan-j/binaries/xalan-j_2_7_2-bin-2jars.zip
>>>>
>>>> and all went out smoothly.
>>>>
>>>> Problem solved :-)
>>>> Regards.
>>>>
>>> It can't be that easy :)
>>> The xalan-2.7.2 you just uploaded does not contains xsltc, whereas the 
>>> previous xalan-2.7.1 did contain it.
>>> And the xsltc.jar comes bundled with cled and regexp.
>>>
>>> But you're completely right, it seems we did not have an official xalan jar.
>>>
>>> My suggestion, to preserve legacy behaviour, is to remove 
>>> org.apache.(bcel|regexp).* from the full xalan jar.
>>>
>>> What do you think ?
>> Well, in this era of reproducible builds, taking another project's dist 
>> artifact, mangle it and include it our own sources looks a bit... weird.
>>
>> At least, the current file comes actually unchanged from Xalan's release 
>> artifact.
> I totally agree. But the Cocoon 2.1.x build system was made in a 
> pre-(ivy|maven) era and I think we don't want to take the time to re-engineer 
> it.

100% agree of course :-)

>> Maybe we could do as you suggest - e.g. restore the previous xalan-2.7.2.jar 
>> and strip out the indicated classes - but also renaming it somehow, e.g. 
>> xalan-2.7.2-cocoon-2.1.13.jar and adding some explanation in lib/jars.xml 
>> about how we obtained this JAR from official Xalan's JAR.
>>
>> Does it sound reasonable?
> +1 with your proposal

Glad to hear this, please go on.

Regards.

-- 
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/

Re: Fwd: Cocoon 2.1.X - Build # 141 - Still Failing

[Cédric Damioli]

Le 24/06/2020 à 08:57, Francesco Chicchiriccò a écrit :

On 23/06/20 23:20, Cédric Damioli wrote:




Why not, but are we sure that we won't have regressions due to downgrade of 
jakarta-regexp (the xalan bundled version is 1.2 AFAIU) ?

  From a design POV, I find it quite strange to rely on an XSLT lib (ie Xalan) 
to provide regexp processing.
Could it be better to remove org.apache.bcel and org.apache.regexp from the 
xalan jar and keep the existing librairies ?
I suppose that was how it has been done previously for xalan-2.7.1

It seems you are quite right.

I took cocoon-2.1.12-deps.tar.gz from

http://cocoon.apache.org/mirror.html

then extracted

lib/endorsed/xalan-2.7.1.jar

and found that it is *not the same* you can download from Maven Central under

https://repo1.maven.org/maven2/xalan/xalan/2.7.1/xalan-2.7.1.jar

but that it matches the one you can download from

http://archive.apache.org/dist/xalan/xalan-j/binaries/xalan-j_2_7_1-bin-2jars.zip

because it does not contain any org.apache.bcel.* nor any org.apache.regexp.* 
class.

So I went ahead and replaced the current

lib/endorsed/xalan-2.7.2.jar

in the source tree with the one contained in

http://archive.apache.org/dist/xalan/xalan-j/binaries/xalan-j_2_7_2-bin-2jars.zip

and all went out smoothly.

Problem solved :-)
Regards.


It can't be that easy :)
The xalan-2.7.2 you just uploaded does not contains xsltc, whereas the previous 
xalan-2.7.1 did contain it.
And the xsltc.jar comes bundled with cled and regexp.

But you're completely right, it seems we did not have an official xalan jar.

My suggestion, to preserve legacy behaviour, is to remove 
org.apache.(bcel|regexp).* from the full xalan jar.

What do you think ?

Well, in this era of reproducible builds, taking another project's dist 
artifact, mangle it and include it our own sources looks a bit... weird.

At least, the current file comes actually unchanged from Xalan's release 
artifact.
I totally agree. But the Cocoon 2.1.x build system was made in a 
pre-(ivy|maven) era and I think we don't want to take the time to 
re-engineer it.


Maybe we could do as you suggest - e.g. restore the previous xalan-2.7.2.jar 
and strip out the indicated classes - but also renaming it somehow, e.g. 
xalan-2.7.2-cocoon-2.1.13.jar and adding some explanation in lib/jars.xml about 
how we obtained this JAR from official Xalan's JAR.

Does it sound reasonable?


+1 with your proposal

Regards,
Cédric