Grails CMS “Weceem” version 0.1 Released

Posted by: on Apr 2, 2009 | 6 Comments

Well it took a lot longer than we hoped for various reasons, but the “stake in the ground” 0.1 release of the open source grails CMS called “Weceem” is now available.

Details are available here

The release has known issues and we have lots of plans already for 0.2 and 0.3 releases, including complete back-end UI rewrite in 0.2. This release really is just to put it out there and get us on the road to future releases now that the app is hosting its own website at www.weceem.org

Thanks to the jCatalog AG team – Stephan Albers, July Antonicheva, Sergei Shushkevich and other contributors such as Glen Smith who have all been working on the app on and off for quite some time. An internal project that has morphed into an open source project which will see continued development

6 Comments

  1. Roshan Shrestha
    April 3, 2009

    Congratulation! I will download the source and study it to learn from it.

    “Note that Grails 1.1 is not currently supported due to issues with GORM in Grails 1.1″

    May I know these issues, or better yet, could you list these issues on the download page of Weceem?

    Reply
  2. noknok
    April 15, 2009

    I will follow up Weceem and try to spread it to others Groovy & Grails dev.

    Cheers.

    Reply
  3. Michael Marth
    June 29, 2009

    Hi Marc,

    just came across weceem – looks interesting. I wonder if you had a look at using JCR for the storage. That should give you most (all?) of the features on your list for free. There is also an experimental Grails plugin.

    Cheers
    Michael

    Reply
  4. Marc Palmer
    July 2, 2009

    Michael – thanks, yes we are very aware of JCR. However we wanted a pure Grails lightweight solution.

    Reply
  5. Chris Latimer
    September 7, 2009

    A friendly heads up: it appears that the link on this post ‘Details are available here’ is not working correctly. Maybe a redirect(uri:’x') where a redirect(url:’x') should be? Just a guess based on the duplicated ‘weceem’ in the url string.

    Reply
    • Marc Palmer
      September 7, 2009

      Hi Chris – thanks for that.

      The problem is just that the URL scheme completely changed between Weceem 0.1 and 0.2 :)

      Fixed the link.

      Reply

Leave a Reply