geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Petersson (JIRA)" <j...@apache.org>
Subject [jira] Updated: (GERONIMO-2994) Apache Roller plugin
Date Mon, 03 Sep 2007 18:46:59 GMT

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

Peter Petersson updated GERONIMO-2994:
--------------------------------------

    Attachment: roller_maven_ant_task_070902_0.patch
                roller_plugin_070803.patch

Bringing Roller plugins to G v2.0.1 and roller-4.0_rc1 by adding roller_plugin_070803.patch
and roller_maven_ant_task_070902_0.patch. 

Changes I recall doing
=========================
 * Updating roller plugins from Geronimo 2.0-SNAPSHOT to Geronimo 2.0.1.
 * Changing the version schema of the plugins to <plugin module version>(-SNAPSHOT)
and adding geronimo and roller version information to the geronimo-plugin description.   

 * Removing dependency of the roller-war plugin module and updating the roller-weblogger war
by using the 4.0_rc1 version via local maven repo. See additional information on building
and installing the roller weblogger artifact below. 
 * Updating the plugins parent version accordingly (org.apache.geronimo.genesis.config/project-config/1.2)
 * Setting <property name="openjpa.QueryCompilationCache" value="false"/> I am not sure
this is needed (and it is likely a performance damper) but during my work on the roller maven
build system (jira ROL-1537) I got rid of a random exception that bugged me wile adding and
testing out the mvn jetty:run-war on roller-weblogger.war by setting it.  
 * Could not get the DatabaseInitializationGBean to work properly, switched to rollers auto
install by setting installation.type=auto in roller-custom.properties
 * Updating the geronimo-plugins.xml file to reflect the new version.
 * Updating the README file with up to date installation instructions. 
 * Some general cleanup.

 
Local maven roller-weblogger.war
================================
 For now (as long as no official roller maven artifacts are available) I found this to be
the most useful way of handling the weblogger.
 Check out the svn 4.0_rc1 tag found at https://svn.apache.org/repos/asf/roller/tags/roller_4.0_rc1/
patch it with the roller_maven_ant_task_070902_0.patch (it's a small maven patch to the ant
build included in this jira) and run 'ant mvn-install'. Observe that 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_rc1>/tools/buildtime/maven/. Some of this information can
also be fond in the README file in the plugin root.
 
Known Caveats
============= 
 * uninstall of roller plugins leaves the roller-<database>-resources files present
in geronimo/repostory and it will not be overwritten/replaced by a new one unless you manually
delete it or change the version. This can be a bit annoying and cause some confusion during
work on the plugins.       
 * maven install from root directory dose not work the first time around (from a clean local
repository) you have to install the modules one by one.


> 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_plugin.patch, roller_plugin_070717.patch, roller_plugin_070803.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.


Mime
View raw message