You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Peter Petersson (JIRA)" <ji...@apache.org> on 2007/09/18 22:27:44 UTC

[jira] Issue Comment Edited: (GERONIMO-2994) Apache Roller plugin

    [ https://issues.apache.org/jira/browse/GERONIMO-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528545 ] 

ppe edited comment on GERONIMO-2994 at 9/18/07 1:26 PM:
--------------------------------------------------------------------

Roller plugin updates for Geronimo v2.0.1

Adding roller_plugin_070918.patch and roller_maven_ant_task_070918_0.patch

Changes 
=======
 * Updating roller-weblogger from 4.0_rc1 to 4.0_rc2.
 * Updating the roller plugin artifact versions.
 * Updating README.

Adding roller-weblogger.war aftifact to local repo 
==============================================
 For now (as long as no official roller maven artifacts are available). Check out the svn 4.0_rc2 tag found at 
 https://svn.apache.org/repos/asf/roller/tags/roller_4.0_rc2/ patch it with the roller_maven_ant_task_070918_0.patch (it's 
 a small maven patch to the ant build included in this jira) and run 'ant mvn-install'. You need to download and install 
 the maven-ant-task jar from here http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-ant-tasks-2.0.7.jar and 
 place it in <roller_4.0_rc2>/tools/buildtime/maven/.
  

      was (Author: ppe):
    Roller plugin updates for Geronimo v2.0.1

Adding roller_plugin_070918.patch and roller_maven_ant_task_070918_0.patch

Changes 
=======
 * Updating roller-weblogger from 4.0_rc1 to 4.0_rc2.
 * Updating the roller plugin artifact versions.
 * Updating README.
  
> Apache Roller plugin 
> ---------------------
>
>                 Key: GERONIMO-2994
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2994
>             Project: Geronimo
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: Plugins
>    Affects Versions: 1.2
>            Reporter: Peter Petersson
>            Assignee: David Jencks
>            Priority: Minor
>         Attachments: geronimo-plugins.xml, geronimo-plugins.xml, geronimo-plugins_070602.xml, geronimo-web.xml, geronimo-web.xml, plan.xml, PluginInstallerGBean.patch, pom.xml, pom.xml, roller-custom.properties, roller-custom.properties, roller-custom.properties, roller-derbydb-plan-g1_2.xml, roller-mysql-db-plan-1-2.xml, roller070409.patch, roller12_070602.zip, roller_g20_svn_070602.patch, roller_maven_ant_task_070902_0.patch, roller_maven_ant_task_070918_0.patch, roller_plugin.patch, roller_plugin_070717.patch, roller_plugin_070803.patch, roller_plugin_070918.patch, roller_plugin_patch_070724.txt
>
>
> Have been working on getting Apache Roller running under Geronimo I finally got to the point where the roller application seems to be running smoothly in Geronimo v1.2 (current snapshot). It would be great to eventually see this application as a plugin in G so here are pointers to resources and attached plans.
> Apache Roller v3.1 Resources (soon to be released)
> Apache roller home: http://rollerweblogger.org/project/
> The bundle: http://people.apache.org/~snoopdave/apache-roller-3.1/ (until it will be available directly via roller home)
> Required jars: https://roller.dev.java.net/servlets/ProjectDocumentList?expandFolder=6959&folderID=0
> Path to database create scripts can be found in the bundle above under: apache-roller-3.1/webapp/roller/WEB-INF/dbscripts/
> I have tested with the derby database and mysql 5. 
> There is currently a issue with G v1.2 and hibernates v3.1 (used by roller 3.1) property loader that gets a
>  
> FATAL [HibernateRollerImpl] Error initializing Hibernate
> java.lang.ClassCastException: java.util.HashSet
>         at org.hibernate.util.PropertiesHelper.resolvePlaceHolders(PropertiesHelper.java:88)   
> Hibernate is expecting a String value (This issue is fixed in hibernate 3.2 with a instanceOf check)
> Fortunately David Jencks hit this problem in trunk and suggested turning off the activemq and activemq-broker modules in config.xml, to test things out, and after that everything was running smothly :).
>     

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.