Website Downloads Documentation Knowledgebase Wiki Issue tracker Commercial support

Changes between Daisy 2.0.1 (=revision 3952) and Daisy 2.1 (=revision 4366)

Revision 4260 (July 30, 2007)

Switching to Maven 1.1 as build tool.

Just about everything stays the same, except that the manual installation of the maven plugins is not needed anymore.

As you can see in the updated README.txt, the maven repository should now be http://repo1.maven.org/maven/ instead of http://mirrors.ibiblio.org/pub/mirrors/maven

To make the switch:

  • download & extract Maven 1.1 and
    • update the PATH environment variable to point to the new Maven
    • (not needed anymore since rev 4271) put a Xalan jar in lib/endorsed as explained in the Daisy <daisy-src>/README.txt
  • delete your ~/.maven directory
  • drop all the target directories in the Daisy source tree. Linux:
    cd <daisy-src>
    find -name target -exec rm -rf {} \;
  • build as usual (see also the README.txt)

Revision 4238 (July 27, 2007)

The ActiveMQ configuration done by daisy-repository-init was still adding the problematic poolPreparedStatements property to the database pool configuration.

So you might want to check if it occurs in your ActiveMQ configuration (<repo data dir>/conf/activemq-conf.xml) and remove it if present. It is this line:

<property name="poolPreparedStatements" value="true"/>

Revision 4263 (July 26, 2007)

The branch BRANCH_VARIABLES was merged into trunk.

To make use of the new variables functionality, you will need to run daisy-wiki-init to create a new doc/part type:

cd <daisy-src>/install/target
./daisy-wiki-init-dev

Revision 4176 (July 13, 2007)

Some changes were made to make building Daisy easier, especially with the development setup:

  • introduced the use of the "repodata dir" for development setup, so that things are consistent with the binary dist and the manual configuration work is gone
  • use different default database names for development (daisydev_repository and daisydev_activemq)
  • for the Daisy Wiki, added a "maven cocoon.download" goal to automatically download Cocoon
  • for the Daisy Wiki, moved the default location of the wikidata dir to <daisy-src>/../devwikidata to be in line with the default location of the new repodata dir

For binary dists, no special upgrade actions are required.

Changes for repository

For development setups, you will need to create a repodata dir.

If you want to keep your existing configuration files and ata, you can do this manually. Otherwise, use the daisy-repository-init-dev script as explained in the README.txt.

The default location for the repodata dir is: <daisy-src>/../devrepodata

Afterwards, you can remove your <daisy-src>/repository/server/myconfig.xml and activemq-conf.xml

Changes for the Wiki

Nothing is required, but you might align with the new defaults: comment out the cocoon.dist.home and daisywiki.data properties in your <daisy-src>/applications/daisywiki/frontend/build.properties, and follow the instructions in README.txt to build the frontend.

If you want to keep your existing wikidata dir, move it to <daisy-src>/../devwikidata

Revison 4146 (July 5, 2007)

Merged BRANCH_NEWRUNTIME into trunk.

This replaces Merlin with the new Daisy Runtime.

For development setup, no special actions are required, though you can now remove Merlin from your system.

For binary distributions, you need to create a new log4j-based logging configuration for the repository server:

copy

<daisy-src>/repository/server/src/conf/repository-log4j.properties

to

<repo data dir>/conf

and remove the logkit.xml

Revision 4025 (May 5, 2007)

genscript-plugin updated (cfr. DSY-461 -- Windows trailing backslash problem), recommended to reinstall it:

cd tools/genscript-plugin
maven plugin:install

Revision 3977 (April 18, 2007)

Changed the database schema version number to reflect the decision to call the next Daisy release 2.1 (rather than 2.0.2).

Login to MySQL:

mysql -Ddaisyrepository -udaisy -pdaisy

And then execute:

update daisy_system set propvalue = '2.1' where propname = 'schema_version';

Revision 3960 (April 16, 2007)

The GuestRepositoryProvider allows a configurable guest user. This enables users to change the guest user used for obtaining a repository instance.

Rebuild the wiki : maven clean; maven cocoon.get; maven webapp

Open <wiki.datadir>/daisy.xconf in your favourite editor.
Add these lines inside the cocoon element

<component
    class="org.outerj.daisy.frontend.GuestRepositoryProviderImpl"
    role="org.outerj.daisy.frontend.GuestRepositoryProvider"
    logger="daisy">
    <guestUser login="guest" password="guest"/>
</component>

Revision 3958 (April 13, 2007)

Introduced a new selection list type (a link-hierarchical one based on a link field pointing to the parent). This needs a new database table, created as follows.

Login to MySQL:

mysql -Ddaisyrepository -udaisy -pdaisy

And then execute:

CREATE TABLE parentlinkedsellist
(
  fieldtype_id BIGINT NOT NULL,
  whereclause LONGTEXT NOT NULL,
  filtervariants CHAR NOT NULL,
  linkfield VARCHAR (50) NOT NULL,
  FOREIGN KEY (fieldtype_id) REFERENCES field_types (id),
  UNIQUE (fieldtype_id)
) ENGINE=InnoDB;


# update schema version number
update daisy_system set propvalue = '2.0.2' where propname = 'schema_version';
Comments (0)
Advertisement

Daisy hosting, installation, support. Workshops and turnkey Daisy CMS projects. Get Daisy from its creators.

outerthought.org

Downloads provided by

SourceForge.net Logo

Open source stats