hi,
thats great news and i just tried lifting a existing
grails-1.3.7/weceem-1.0 install to grails-2.0.rc3/weceem-1.1.2 ...
what i saw was that the plugin dependencies of weceem are now mostly
declared in weceems depedencies.groovy in a plugin-dependency-dsl like
fashion. but it seems to require those exact versions, not those or above.
now on every refresh of the projects dependencies, grails wants - or
even does - downgrade plugins with versions higher than those required
by weceem.
- am i doing sth. wrong or misunderstanding anything?
- do i have to declare my projects other dependencies via buildconfig
dsl too (they are still application.properties)?
- is this a weceem specific or more a general problem?
thanks n regards,
zyro
-------- Original Message --------
Subject: [grails-user] ANN: Weceem CMS 1.1.2
From: Marc Palmer <
[hidden email]>
To:
[hidden email] Users <
[hidden email]>
Date: Wed, 14 Dec 2011 12:26:16 +0000
> Hi,
>
> We are happy to bring you release 1.1.2 of Weceem, fixing more issues and providing further compatibility with Grails 2.0 RC3 and higher.
>
> NOTE: There are important changes for those upgrading from previous releases
>
> This release includes some useful new features and refinements:
>
> * New "create-content-class" script to generate customer content types
> * Change to no longer default to uploading files to web-app's work directory
> * No need to specify available space templates unless customizing them
> * Warning at startup if file extension content negotiation is enabled
> * Fixes to the Synchronize Files feature
> * Integration with new webxml plugin for filter ordering
> * Workarounds for hibernate proxies affecting admin UI
>
> The important change for those upgrading is related to file uploads. If you have deployed Weceem but not previously set weceem.upload.dir to a file: URL
> outside of the web application's work directory, you will need to move your uploaded files during upgrade. This change is necessary due to fixes in Spring used in Grails 2 and incorrect assumptions Weceem previously had about the work directory being writable.
>
> If the above applies to you, all you need to do is move the uploaded files folder from your expanded web-apps directory to the Tomcat user's home
> directory under /weceem-uploads/.
>
> If you had no previous config setting at all for weceem.upload.dir:
>
> Move <weceem-app-work-dir>/WeceemFiles to <container-user-home>/weceem-uploads/WeceemFiles
>
> If you did set weceem.upload.dir to a simple path name (not a file: URL):
>
> Move <weceem-app-work-dir>/<dir-name> to <container-user-home>/weceem-uploads/<dir-name>
>
> The URL used to serve the files should not have changed and when you start up with the new build you should find that all links work as expected. Note however that you should make sure your servlet container is NOT running as a superuser and that you have permissions on that folder set correctly. It is strongly recommended that you do use a file: URL for your upload directory and set the permissions correctly on that instead.
>
> Kind regards,
> The Weceem Team
>
http://weceem.org>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>
http://xircles.codehaus.org/manage_email>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Locked
