File Release Notes and Changelog
Release Name: 0.5.0 (Delorean)
Notes: This package contains CVS entries, please do not use it to try and update from CVS (bad idea).
Changes: Welcome to the Javalobby Community Platform v.Oh pt Five pt Oh (0.5.0) ------- -- --- --------- --------- -------- I. Introduction Welcome to the second release of the Javalobby Community Platform software. With this release, we feel that the portal package is starting to flesh itself out and become feature complete. While this release still has some bugs, there has been a significant increase in speed through the use of caching and an improved UI that makes us more compatible with different browsers and different operating systems. With this release, we have also added a basic Administration console in the web interface which should allow you to control the various modules. You should expect everything to work in the manner you expect it to (with some degree of freedom), so if it doesn't please file a bug at http://jira.jlcp.org. Major improvements to this release include a complete conversion to Hibernate, improved Links storage, webpages for viewing/adding/voting polls, a new file center module, a basic calendar, and an updated UI. In addition, there have been a great number of bugs that we filed from the first release and an evener greater number that we did not file, have all been fixed. II. Some Known Problems As we all know, nearly every piece of software has bugs. As this is a very VERY rough release, expect things to be broken and to have not all the links not work. This software should not be used for anything more than just seeing what the great Javalobby volunteers have been working on. The major thing that this release lacks in is any sort of permissions system. Because of this, you should not try to deploy it where security is important and you should most likely not try to migrate from another server. We are looking for people to write migration scripts from popular forum and portal packages, so if you're interested please volunteer at matt@javalobby.org. In addition to not having security, our forums skin will be lacking (even though the backend is updated to use Hibernate). Anyone who is interested in helping us fix that problem should contact our mailing list at jl-volunteers@mailman.javalobby.org. III. Installation Notes While we've strived to make it as easy as possible to install JLCP, this release still isn't quite as easy as we would like. There are a few steps you need to do for installation. First, the requirements: 1) JDK1.4 2) A J2EE Application Server (at least J2EE 1.3 compatible) 3) A database (MySQL, DB2, HSQL, McKoi, PostGres, etc) If you've met these requirements, then we can get on with the installation. The first step in the installation is to add a datasource in your application server. How this is done varies based on the appserver. Below, is the snippet of a data-sources.xml file from the Orion Application Server: <data-source class="com.evermind.sql.DriverManagerDataSource" name="JLCP" location="jdbc/JLCPDatasource" xa-location="jdbc/xa/JLCPXADS" ejb-location="jdbc/JLCPDatasource" connection-driver="org.gjt.mm.mysql.Driver" username="jlcp" password="nothere" url="jdbc:mysql://database.jlcp.org:3306/jlcp" inactivity-timeout="30"> </data-source> Remember to keep the location the same no matter what database you use. With the datasource completed, you then need to create a local.properties file in the same location as global.properties and add the following information (with your driver, url, and user info): # Insert the JNDI Properties? insert.jndi.properties=true # Database to use database=mysql # Database connection type. Either datasource or jdbc. database.connection.type=jdbc # JDBC Connection Information jdbc.connection.driver=com.mysql.jdbc.Driver jdbc.connection.url=jdbc:mysql://database.jlcp.org:3306/jlcp jdbc.connection.username=jlcp jdbc.connection.password=nothere With this file created, you need to run 'ant createdb'. This task will build the database for you. After the database is created, you have just one more small task before you can use the enterprise application (I know this sounds tedious, it'll get better). Reopen the local.properties file and enter the following information: # Should be set to either jndi or local session.factory.type=jndi # Tells whether to insert jndi properties in hibernate.cfg.xml and hibernate.properties insert.jndi.properties=false # If inserting jndi properties, tell whether to use app server specific or Sun FS Context # The Sun FS Context must be downloaded and installed in jre/lib/ext!!! You have been warned! # EITHER: file or appserver jndi.type=appserver # Whether to show SQL in STDOUT #show.sql=false # App server to use appserver=orion # Database to use database=mysql # Connection type #database.connection.type=jdbc # Connection Info for JDBC type #jdbc.connection.driver=org.gjt.mm.mysql.Driver #jdbc.connection.url=jdbc:mysql://localhost:3306/jlcp_new #jdbc.connection.username=jlcp #jdbc.connection.password=nothere These changes tell Hibernate what application server and database to use. You can now run 'ant ear'. The ear task will build a J2EE compatible enterprise application for you. With this file built, you can move it from jlcp.home\build\jlcp-0.1.0.ear to your application server deploy directory. If you prefer a web application, you can run 'ant war' instead and deploy jlcp.home\build\jlcp-web.war. One note: once the ear file is created, how you deploy it various according to your application server. Unfortunately, we did not have time to write documentation for every application server so I'm afraid you are on your own. If you run into a problem, please post it to http://jira.jlcp.org. In addition to this tedious method of installation, we have also created a standalone JBoss + JLCP + McKoi package that just requires you to unzip and run the JBoss executable. You can grab that from http://sourceforge.net/project/showfiles.php?group_id=63350, just look for the standalone 0.5.0 (Delorean) release. IV. Conclusion Enjoy what we have so far, and please feel free to post bugs to our JIRA server at http://jira.jlcp.org. We also love getting feedback on our mailing list at jl-volunteers@mailman.javalobby.org. You'll need to send a mail to jl-volunteers-request@mailman.javalobby.org with the subject 'subscribe' to join the list. Help us improve this first in Java community software! The 1.0 release is expected around the time of JavaOne (middle of June), but be on the lookout for several beta releases between now and then displaying the added security features and sneak peeks at our polished modules. We don't expect the database to change any time soon, so upgrading to the point releases should be a fairly painless process. - The JLCP Team 04/08/03 http://www.jlcp.org
