rks.
Why not bring exactly this back to the upstream project and join
forces in maintaining it?
Chris
*Von: *Cédric Damioli
*Datum: *Donnerstag, 12. September 2024 um 19:31
*An: *dev@cocoon.apache.org
*Betreff: *Re: [RESULT] [VOTE] Move Apache Cocoon into the Apache Attic
Hi,
Sadly
exactly this back to the upstream project and join
forces in maintaining it?
Chris
*Von: *Cédric Damioli
*Datum: *Donnerstag, 12. September 2024 um 19:31
*An: *dev@cocoon.apache.org
*Betreff: *Re: [RESULT] [VOTE] Move Apache Cocoon into the Apache Attic
Hi,
Sadly, there's not enough
ith 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 u
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: [RE
> 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
>
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
> anot
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
t 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
+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 Att
+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 indifferen
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
+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 ar
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
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
+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
mig
> So, if I don’t hear anything else within the next 72h, I’ll initiate the
>> Git migration.
>>
>>
> +1
>
+1
Torsten
>
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: *Christo
>
> 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
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
> 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...
>
> I guess as there were no objections, I’ll go forward with this.
>
+1
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
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
@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
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
on, 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
on, 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
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 t
on, 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
on, 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
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 comme
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 t
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 co
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
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
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 wh
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
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 reque
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,
nt:* 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/m
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 lightweigh
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.
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 abov
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.
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 t
<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 pr
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
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
>
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 ou
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 o
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 easi
det 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
ka.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 p
.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: Fu
hiriccò
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
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
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 pa
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 perso
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,
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 p
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
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
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.
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,
o: 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. C
nt: 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
uch 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:
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
ood 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
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 off
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 cur
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
*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 for
nntag, 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
her
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 wo
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
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: R
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
Here is my +1
Checked on macOS, JDK 17.
-David
>
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
- 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 :
Apac
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]
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
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 JD
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?
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
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 unsubscrib
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
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.
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
on, 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
on, 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
on, 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
on, 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
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éd
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
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:1
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 signat
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, buil
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 s
1 - 100 of 39629 matches
Mail list logo