| Newsgroups |
gmane.text.xml.cocoon.devel |
| Message-ID |
<[email protected]> |
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
>