Nabble - LiquiBase - Development

New Topic: Is it possible to define a changeset programmatically?

2009-11-06T02:11:18Z

A new topic, 'Is it possible to define a changeset programmatically?', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=218.new#new

The text of the topic is shown below:

Hi,

I would like to use Liquibase for inserting master data in a JPA environment, so I have no need to define SQL statements
or using <insert> in changesets. I would prefer to define a changeset programatically, e.g. as a Java class implementing
a special interface or as a JUnit Testcase (because then I can use SpringRunner and the like to get the PersistenceContext)
This way I could use JPA for creating the data, keep the refactoring support of my IDE and use LiquiBase just for the
book keeping.
So, is something like this already supported? If not, do you think some kind of JUnit extension is easy to implement?
(would also be nice for defining prerequisites)

To make myself clear, I want to define something like this:
<changeSet id="1" author="robin">
<execute class="de/robin/InsertNewStates" />
</changeSet>

regards,

Robin.

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

New Topic: How to configure logging

2009-10-16T07:29:23Z

A new topic, 'How to configure logging', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=197.new#new

The text of the topic is shown below:

Had a look through the 2.0-RC1 code in an attempt to find out how to configure the new logging architecture. In 1.9.4 it was quite easy
to reconfigure java.util.logging to use log4j instead but now I cant really figure out how this is possible.
The LogFactory seems to use the ServiceLocator singleton to look up Logger.class so in order to reroute log messages to log4j instead I would have to implement a log4j bridge by using this interface.
But how can I make sure that the ServiceLocator uses my bridge instead of the default logger? How do I configure the ServiceLocator?

Best regards
Lars Gråmark

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

New Topic: problem with caching of lock and changelog table existing

2009-09-30T12:45:39Z

A new topic, 'problem with caching of lock and changelog table existing ', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=179.new#new

The text of the topic is shown below:

Hi,

I Run Liquibase with postgresql, where for each schema a new instanceof Liquibase is created and run with a different default-schema-name and changelog file.

liquibase then creates a lock and changelog table in each schema - which is very good for me because the schemas should be completley independent of eachother.

Today I run into a problem, which I think did not happen before because I always build the single modules(each module has one db schema), and in the context of the tests, the db-schemas are created and liquibase is run a single time.

But when running liquibase multiple times on the same vm with different default-schemas, the JdbcDatabaseSnapshotGenerator instance, which is referenced from a static instance (and thus being shared by all instances of liquibase on the same VM), caches the hasDatabaseChangeLogTable and the hasDatabaseChangeLogLockTable values. So, even if for the actual schema there is no lock table or changelog file, liquibase is informed it does exist, which ofcause does not work right.

So - I removed this fields from JdbcDatabaseSnapshotGenerator -

I searched just a bit and think that the only call to the methods that cache these values are from when initializing liquibase, and I ask myself if it make sense to cache them. Usually, liquibase will be instanciated once, and ran once, not ? so there is no point in caching these values, because they are only used once, not? and if liquibase is run more than once, maybe it *is* better to check every time - as my settings proof...

I am not sure, so I just wanted to ask (sorry for the long post) if I should commit the change ?

Cheers, Ron

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

New Topic: is CORE-476 fixed in trunk ?

2009-09-24T00:38:59Z

A new topic, 'is CORE-476 fixed in trunk ?', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=170.new#new

The text of the topic is shown below:

Hi,

I Saw that CORE-476 is set fixed. Is the fix in trunk yet ?

Cheers, Ron

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

New Topic: Adding new datatype via the ServiceLocator

2009-09-21T23:42:45Z

A new topic, 'Adding new datatype via the ServiceLocator', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=164.new#new

The text of the topic is shown below:

Hi,

I wonder what the best way is to add a new data type to Liquibase. Lets say that in the changelog XML I have columns of type DECIMAL, for Oracle these must be converted to NUMBER. I created a new class extending OracleTypeConverter overriding the getDataType(String, Boolean) method. In case I need to change a datatype for one of the supported types I override the getXXXType() method.

The class is pushed into Liquibase using the ServiceLocator.addPackageToScan(String) method. When the changelog is parsed and processed Liquibase uses my class instead of the original OracleTypeConvertor.

Is this the intended approach to extend datatypes?

Chris

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

New Topic: Liquibase doesn,t support precision

2009-09-14T05:21:30Z

A new topic, 'Liquibase doesn,t support precision', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=146.new#new

The text of the topic is shown below:

Hi Nathan.
I noticed that when I try to use CreateTable tag to create new table, I've got problem with ColumnType attribute. When ColumnType value is for example: NUMBER(10) I've got following error:

Code:
liquibase.exception.UnexpectedLiquibaseException: Type class liquibase.database.structure.type.NumberType doesn't support precision but precision was specified: NUMBER(10)
at liquibase.database.typeconversion.core.AbstractTypeConverter.getColumnType(AbstractTypeConverter.java:216)
at liquibase.sqlgenerator.core.CreateTableGenerator.generateSql(CreateTableGenerator.java:45)
at liquibase.ext.ora.splittable.SplitTableGenerator.Transition(SplitTableGenerator.java:131)
at liquibase.ext.ora.splittable.SplitTableGenerator.generateSql(SplitTableGenerator.java:35)
at liquibase.ext.ora.splittable.SplitTableGenerator.generateSql(SplitTableGenerator.java:1)
at liquibase.sqlgenerator.SqlGeneratorChain.generateSql(SqlGeneratorChain.java:29)
at liquibase.sqlgenerator.SqlGeneratorFactory.generateSql(SqlGeneratorFactory.java:119)
at liquibase.ext.ora.splittable.SplitTableChangeTest.parseAndGenerate(SplitTableChangeTest.java:113)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:71)
at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35)
at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:46)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)

Do you have any suggestion?

Tomek

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

New Topic: Should 'or precondition's be Short Circuited (aka Lazy Evaluation)?

2009-09-13T21:30:07Z

A new topic, 'Should 'or precondition's be Short Circuited (aka Lazy Evaluation)?', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=145.new#new

The text of the topic is shown below:

Should orpreconditions be short circuited?

As it is, you cannot have pre-conditions like "only run if this table is missing OR, if it exists, check that it contains a particular record".

e.g.

Code:
<precondition>
<or>
<not>
<tableExists tableName="some_table"/>
</not>
<sqlCheck expectedResult="0">
SELECT MAX(id)
FROM some_table
</sqlCheck>
</or>
</precondition>

However, if orprecondition's were short-circuit and evaluated in the order that they appear, then once one condition evaluates to true, you do not need to continue evaluating other conditions in the or block.

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

New Topic: Looking for help with liquibase maven config

2009-09-13T17:15:18Z

A new topic, 'Looking for help with liquibase maven config', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=144.new#new

The text of the topic is shown below:

I'm trying to get maven to run fully so I can release beta3, but when I run the mvn package command, I get the error:

Code:
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) org.liquibase:liquibase-core:test-jar:tests:2.0-SNAPSHOT

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=org.liquibase -DartifactId=liquibase-core -Dversion=2.0-SNAPSHOT -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.liquibase -DartifactId=liquibase-core -Dversion=2.0-SNAPSHOT -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

Path to dependency:
1) org.liquibase:liquibase-core-jvm:jar:2.0-SNAPSHOT
2) org.liquibase:liquibase-core:test-jar:tests:2.0-SNAPSHOT

----------
1 required artifact is missing.

for artifact:
org.liquibase:liquibase-core-jvm:jar:2.0-SNAPSHOT

Any maven experts know what I am doing wrong? You should be able to see the error if you build core trunk

Nathan

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

New Topic: Submit a patch for SpringLiquibase

2009-09-07T03:41:03Z

A new topic, 'Submit a patch for SpringLiquibase', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=139.new#new

The text of the topic is shown below:

Hi,

I Just tried to submit a patch to SpringLiquibase via Jira and noticed I could not open a JIRA Issue without choosing a resolution, which is kind of funny, because the issue has no resolution.

Here is the text for the issue:

Quote
Hi, I attach a patch to the SpringLiquibase class-

I Changed SpringLiquibase to enable subclassing and manipulating the Database object before instanciating Liquibase - specifically I need it in order to specify a default schema before proceeding, but maybe someone else needs it also...

So one can now subclass the SpringLiquibase been and manipulate the Database before creating the Liquibase object itself...

Cheers, Ron

and the patch is also attached here.

Cheers, Ron

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

New Topic: Release 2.0

2009-08-10T07:02:08Z

A new topic, 'Release 2.0', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=113.new#new

The text of the topic is shown below:

Hi,
I was just wondering... When is Liquibase 2.0 going to be final? Are there any dates yet?
Thanks, Karl

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

New Topic: Nested tags (sub-tags)

2009-08-04T01:37:28Z

A new topic, 'Nested tags (sub-tags)', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=100.new#new

The text of the topic is shown below:

Hi,

Is it possible to create nested tags (sub-tags) as LiquiBase extension?

I have got problem with this kind of tags. LiquiBase can't recognise nested tags.

For example, my tag's schema:

Code:
<xsd:element name="mergeTables">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="Update" maxOccurs="1"/>
<xsd:element ref="Insert" maxOccurs="1"/>
</xsd:sequence>
<xsd:attribute name="onCondition" type="xsd:string" use="required"/>
<xsd:attribute name="targetTableName" type="xsd:string" use="required"/>
<xsd:attribute name="targetSchemaName" type="xsd:string"/>
<xsd:attribute name="sourceSchemaName" type="xsd:string" use="required"/>
<xsd:attribute name="sourceTableName" type="xsd:string"/>
</xsd:complexType>
</xsd:element>

<xsd:element name="Update">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="column" minOccurs="1"/>
</xsd:sequence>
<xsd:attribute name="updateCondition" type="xsd:string"/>
<xsd:attribute name="deleteCondition" type="xsd:string"/>
</xsd:complexType>
</xsd:element>

<xsd:element name="Insert">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="column" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="insertCondition" type="xsd:string"/>
</xsd:complexType>
</xsd:element>

dalt

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

New Topic: Column Exists Precondition is Slow

2009-08-03T10:42:03Z

A new topic, 'Column Exists Precondition is Slow', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=98.new#new

The text of the topic is shown below:

The columnExists precondition takes about 5 seconds to run on our database. We have about 80 tables and 800+ columns.

Its building up the entire DatabaseSnapshot in a liquibase object before using the generic liquibase calls in each precondition.
I added a patch for mysql databases that does a sql call into the information_schema space. This takes milleseconds to run. (see attached).

Alternatively, the generated DatabaseSnapshot object could be cached until a database modification is done in a changeset, but I didn't see a quick way to do that.

The tableExists, foreignKeyExists, indexExists, viewExists, etc could stand to have a similar improvement.

(I haven't looked at the 2.0 branch yet to see if this overall problem is solved)

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

New Topic: Add Primary Key - extension tag

2009-08-03T02:44:16Z

A new topic, 'Add Primary Key - extension tag', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=97.new#new

The text of the topic is shown below:

Hi,

I have been creating some extension for Oracle DB, most of all new specialised tags (not defined in LiquideBase, for example CREATE TRIGGER and DROP TRIGGER for Oracle). Everything work fine until I added tag ADD PRIMARY KEY which is defined in LiquideBase (I wanted to extend this tag by adding attributes: DEFERRABLE and INITIALLYDEFERRED).

What's my problem?

Code:
<databaseChangeLog
xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
xmlns:ora="http://www.liquibase.org/xml/ns/dbchangelog-ext"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog ../../../../../java/liquibase/ext/ora/xml/dbchangelog-2.0.xsd
http://www.liquibase.org/xml/ns/dbchangelog-ext ../../../../../java/liquibase/ext/ora/xml/dbchangelog-ext.xsd">

<changeSet id="2" author="author01">




<addPrimaryKey tableName="AddPrimaryKeyTest" columnNames="id" />
</changeSet>

In this case ADD PRIMARY KEY should be created by rules from LiquiBase, but classes from extension are used (package liquibase.ext.ora.addprimarykey;)

I suppose that it doesn't work because classes names in LiquiBase and my extension are same (but package is different!). Because of that, classes from extensin override classes from LiquiBase and tag <addPrimaryKey tableName="AddPrimaryKeyTest" columnNames="id" /> is maintained by extension classes.

Is there any way I should follow? Do I have to rename my tag and classes names?

dalt

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

New Topic: Wondering about SVN...

2009-07-21T16:55:00Z

A new topic, 'Wondering about SVN...', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=87.new#new

The text of the topic is shown below:

Hi Nathan,
I was just browsing the SVN repository as I finally found some time to work on the addition of an M2 MOJO for dbDoc mentioned in CORE-49 and I noticed that you've updated the jira to go into LB 2.0 so I'm just confirming that 2.0 is now trunk. I'd hate to do the work in the wrong tree ;)

On a different (but related) note, I noticed a TRY-M2 branch... would this happen to be a proof-of-concept branch that the migration to M2 would be taking place in? If so, I would love to contribute to this effort as all of my projects are being built with M2 these days. Let me know if you would like some help in this arena as I have some time to contribute.

Thanks!
-Ryan

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------

_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

New Topic: change log file is not generated by 'updateDatabase' ant task

2009-07-09T08:10:07Z

A new topic, 'change log file is not generated by 'updateDatabase' ant task', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=73.new#new

The text of the topic is shown below:

Hi,
In our project we are using 'Build and Deployment Automation (BDA)' tool for building and deployment of the project. The BDA uses liquibase for database versioning (liquibase-1.9.3.jar). When the 'updateDatabase' ant task is executed through BDA tool the change log file is not getting generated. In other projects the BDA is working fine. After searching through web found that hibernate jar should be in classpath : http://mrdkl.wordpress.com/2008/06/27/fun-with-liquibase/.
I cross checked the classpath and updated so that it will contain hibernate jar. Bust still no change log file is getting generated.

Please help us to find out what configuration we are missing.

~vijay

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

New Topic: Problem building/testing 1.9.x branch: failing tests

2009-07-08T10:26:47Z

A new topic, 'Problem building/testing 1.9.x branch: failing tests', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=71.new#new

The text of the topic is shown below:

Hi,

I have been using Liquibase for about a year now, but this is the first time I've tried to build it. I am also new to svn, so that doesn't help. I am a fairly old hand at ant and java.

I'm building and running tests, and I'm encountering some failures and errors.

I grabbed what I think is the 1.9.x branch using this command:
svn co http://liquibase.jira.com/svn/CORE/branches/1_9 liquibase_BR_1_9

Then I navigated into the liquibase_BR_1_9/core/src directory and built using this command:
ant

Then I built and ran the tests using this command:
ant test

With the results that I got 1 failure and 7 errors.

liquibase.LiquibaseTest failed with Code:
junit.framework.AssertionFailedError: expected:<14> but was:<15>
at liquibase.LiquibaseTest.getImplementedDatabases(LiquibaseTest.java:76)
. I looked at the code, and DatabaseFactory is creating 15 Databases, but the LiquibaseTest is asserting against 14.

liquibase.change.AddColumnChangeTest is erroring out in the sybaseNull, sybaseNotNull, and sybaseConstraintsNull tests.
Code:
[junit] Testcase: sybaseNull(liquibase.change.AddColumnChangeTest): Caused an ERROR
[junit] null expected:<...TER TABLE [TAB] ADD [NEWCOL] TYP NULL> but was:<...TER TABLE [TAB] ADD [[NEWCOL]] TYP NULL>
[junit] at liquibase.change.AddColumnChangeTest.sybaseNull(AddColumnChangeTest.java:218)
[junit]
[junit]
[junit] Testcase: sybaseNotNull(liquibase.change.AddColumnChangeTest): Caused an ERROR
[junit] null expected:<...TER TABLE [TAB] ADD [NEWCOL] TYP NOT NULL> but was:<...TER TABLE [TAB] ADD [[NEWCOL]] TYP NOT NULL>
[junit] at liquibase.change.AddColumnChangeTest.sybaseNotNull(AddColumnChangeTest.java:237)
[junit]
[junit]
[junit] Testcase: sybaseConstraintsNull(liquibase.change.AddColumnChangeTest): Caused an ERROR
[junit] null expected:<...TER TABLE [TAB] ADD [NEWCOL] TYP NULL> but was:<...TER TABLE [TAB] ADD [[NEWCOL]] TYP NULL>
[junit] at liquibase.change.AddColumnChangeTest.sybaseConstraintsNull(AddColumnChangeTest.java:257)

liquibase.change.ModifyColumnChangeTest is erroring out in the generateStatement and generateFullStatementForMysql tests.
Code:
[junit] Testcase: generateStatement(liquibase.change.ModifyColumnChangeTest): Caused an ERROR
[junit] null expected:<..._NAME MODIFY ( NAME [integer](3) )> but was:<..._NAME MODIFY ( NAME [INT](3) )>
[junit] at liquibase.change.ModifyColumnChangeTest.generateStatement(ModifyColumnChangeTest.java:44)
[junit]
[junit]
[junit] Testcase: generateFullStatementForMysql(liquibase.change.ModifyColumnChangeTest): Caused an ERROR
[junit] null expected:<...NAME` MODIFY `NAME` [integer](3) NOT NULL DEFAULT...> but was:<...NAME` MODIFY `NAME` [INT](3) NOT NULL DEFAULT...>
[junit] at liquibase.change.ModifyColumnChangeTest.generateFullStatementForMysql(ModifyColumnChangeTest.java:85)

liquibase.database.H2DatabaseTest errors out in the escapeTableName_noSchema and escapeTableName_withSchema tests.
Code:
[junit] Testcase: escapeTableName_noSchema(liquibase.database.H2DatabaseTest): Caused an ERROR
[junit] null expected:<[`tableName`]> but was:<[tableName]>
[junit] at liquibase.database.H2DatabaseTest.escapeTableName_noSchema(H2DatabaseTest.java:73)
[junit]
[junit]
[junit] Testcase: escapeTableName_withSchema(liquibase.database.H2DatabaseTest): Caused an ERROR
[junit] null expected:<[`schemaName`.`tableName`]> but was:<[schemaName.tableName]>
[junit] at liquibase.database.H2DatabaseTest.escapeTableName_withSchema(H2DatabaseTest.java:79)

JAVA_HOME points to JDK 1.5 (I usually build with JDK 6 but Liquibase seems to want 1.5.)

Ant is 1.7.0.

I'm building on cygwin under Windows XP.

Do these test cases currently pass for other people? If so, then it's something in my environment that I need to fix, or maybe I'm grabbing the code wrong or building it wrong. But looking at the first one, I'm not so sure it's me. I thought it might be leftovers from a previous version of Liquibase, but I've cleared out my CLASSPATH.

Is the official daily build junit results posted online somewhere?

thanks for any help,
shoover

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

New Topic: Sybase support not correct

2009-07-03T03:01:31Z

A new topic, 'Sybase support not correct', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=66.new#new

The text of the topic is shown below:

Hi,

I am using generating sybase db statements using liquibase jar.
For generated statements look like:
CREATE TABLE [AA774] (ID INT IDENTITY NOT NULL, V1 INT NULL, CONSTRAINT [PKCN_AA774] PRIMARY KEY (ID))
(Class used to generate this statement is CreateTableStatement)

CREATE UNIQUE INDEX [X1_AA774] ON [AA774](V1)
(Class used to generate this statement is CreateTableStatement)

DROP INDEX [AA774].[X1_AA774]
(Class used to generate this statement is DropIndexStatement)

DROP VIEW [V_AA774]
(Class used to generate this statement is DropViewStatement)

ALTER TABLE [AA774] ADD F4 INT NULL
(Class used to generate this statement is AddColumnStatement)

CREATE VIEW [V_AA774] AS SELECT * FROM AA774
(Class used to generate this statement is CreateViewStatement)

All the above statemens use square brackets around the table/view/constraint name. This does not work in Sybase.
Is there any fix coming for this in the next version of liquibase?

Also there is another problem here, for SybaseDatabase.getIntType() gives "INT", it should be NUMERIC.

Regards,
Usha.

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------

_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

SQL Parsing

2009-06-29T09:54:49Z

My understanding is that currently SQL in LiquiBase within the <SQL/> tags is parsed into statements and then executed without translation. I do something similar in GarinDriver and see this as an area where we can share technology.

Often vendors have slightly different SQL syntax rules so a good universal parser is hard to implement. For example MySQL uses java style string encoding while other vendors use SQL99 style (O''Brian vs. O\'Brian). The MySQL guys also support # style comments in addition to the SQL99 -- and /* */ styles.

I am not sure how robust the current LiquiBase parser is. My initial guess from looking at the code and reading some issues on your forum/jira is that it will have trouble with many of the more complex scripts especially the ones with comments and semis in strange places.

The garin.parse package currently handles all the complex SQL that I can find from MySQL including all weird comment rules. I wrote this package after looking around and not finding any similar package in the open source community.

My parser framework uses an approach where each parse mode is a separate object and as such it is hopefully easy to extend and/or use.

If LiquiBase would like, you are free to embed my parsing package in the main liquibase code (it is eclipse public licence code). For me the benefit is that it would provide more testing of the package and help find weird scripts that I might not otherwise come across. When we find weird but legal scripts we can add them to the test case and I think it should be fairly easy to adapt my parser to handle some pretty wacky rules if needed.

The current test case for my parse package is here:
http://code.google.com/p/garindriver/source/browse/trunk/GarinDriver/tst/src/garin/standard/TestParser.java

The test case works on some sample files (also in SVN). The sample file for MySQL testing is fairly complex but still parses correctly.
http://code.google.com/p/garindriver/source/browse/trunk/GarinDriver/tst/parse/mySQL.sql

Let me know if you decide to use the package and/or if you already have a similar package and/or find a better one.

New Topic: Implementing a SQL/DDL deployment script model as a JDBC driver

2009-06-23T18:54:36Z

A new topic, 'Implementing a SQL/DDL deployment script model as a JDBC driver', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=59.new#new

The text of the topic is shown below:

Hello All,

I happened across LiquiBase as I was recently doing some Google searching. It looks like an interesting project and I would like to get involved at the user level or at the developer level.

In any case, I recently created an opensource project that has some similarities to LiquiBase.
http://code.google.com/p/garindriver/

My project is similar to LiquiBase in some respects but a took a different approach. GarinDriver is a much smaller project (dev team of 1). Most of the code was a weekend project (last weekend). The approach, I took was to integrate the system for running the deployment scripts into the JDBC driver layer. By integrating the deployment of scripts into the JDBC driver my system ensures that client's can never access the database until it is properly initialized (i.e. the JDBC url used by the client describes a minimal database level and internally the GarinDriver can promote the database to the proper level by running required members from a stack of scripts using a databased tracking table to coordinate script running). The GarinDriver contract with scripts is basically run once. When a client connects through the driver it checks it's stack of scripts vs. the database tracking table and runs only the scripts needed to move the database forward. The GarinDriver is really a wrapper around a backend jdbc driver and as such the GarinDriver focus is on the script stack with all real work handed off to the backend jdbc driver. It seems like a different approach then LiquiBase and there is a possibility that the concept could be merged into LiquiBase.

>From my understanding the LiquiBase concept is similar but also includes a set of tools to create a stack of deployment scripts and a way to organize running such scripts. What I really like is that LiquiBase seems to have a database vendor neutral way of describing DDL changes (and possibly a vendor neutral way of describing data loads).

Does LiquiBase provide a JDBC driver wrapper concept similar to GarinDriver?
Do members of the LiquiBase community think that JDBC driver integration concept provides value?
Is LiquiBase interested in the idea of integration with the GarinDriver concept?

-Mark
http://markfarnsworth.wordpress.com

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------

_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

Re: encoding attribute in LoadData as List in Schema

2009-06-14T22:02:17Z

That would be a good idea. Could you create an issue for it at liquibase.jira.com?

Nathan

________________________________

From: Marc Logemann [mailto:li@...]
Sent: Sat 6/13/2009 3:34 AM
To: liquibase-devel@...
Subject: [Liquibase-devel] encoding attribute in LoadData as List in Schema

Hi,

wouldnt it make sense to supply the Liquibase schema with a lists of
encodings for the LoadData task? The encodings are quite "stable" and
this way, people dont have to lookup the java encoding name in the
javadocs and could just use auto-complete in their IDE.

---
regards
Marc Logemann
http://www.logemann.org <http://www.logemann.org/>
http://www.logentis.de <http://www.logentis.de/>

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

winmail.dat (5K) Download Attachment

encoding attribute in LoadData as List in Schema

2009-06-13T01:34:15Z

Hi,

wouldnt it make sense to supply the Liquibase schema with a lists of
encodings for the LoadData task? The encodings are quite "stable" and
this way, people dont have to lookup the java encoding name in the
javadocs and could just use auto-complete in their IDE.

---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

New Topic: ChangeLog Chain Example required

2009-06-12T23:29:45Z

A new topic, 'ChangeLog Chain Example required', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=47.new#new

The text of the topic is shown below:

Hi Nathan,
I'm exploring you changes, you made for adding fine tuning sql generation through SqlGeneratorChain facility.
And already run into situation, where it might to be applied.

Running java-dbtest against MSSQL 2000 getting the error (see at the end of post)
The server supports only to the following
[ ON DELETE { CASCADE | NO ACTION } ]
[ ON UPDATE { CASCADE | NO ACTION } ]

By RESTRICT I think the clauses ON DELETE/ON UPDATE must be omitted.

Give some ideas, how sql generation may be customized to this case

Thanks.

liquibase.exception.MigrationFailedException: Migration failed for change set liquibase-test3201895695241807216.xml::1244876788296-49::otaranenko (generated):
Reason: liquibase.exception.JDBCException: Error executing SQL ALTER TABLE [liquibase].[address] ADD CONSTRAINT [FK_ADDRESS_STATE] FOREIGN KEY ([state]) REFERENCES [liquibase].[state]([id]) ON UPDATE RESTRICT ON DELETE RESTRICT:
Caused By: Error executing SQL ALTER TABLE [liquibase].[address] ADD CONSTRAINT [FK_ADDRESS_STATE] FOREIGN KEY ([state]) REFERENCES [liquibase].[state]([id]) ON UPDATE RESTRICT ON DELETE RESTRICT:
Caused By: Incorrect syntax near the keyword 'RESTRICT'.
at liquibase.changelog.ChangeSet.execute(ChangeSet.java:234)
at liquibase.changelog.visitor.UpdateVisitor.visit(UpdateVisitor.java:26)
at liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:39)
at liquibase.Liquibase.update(Liquibase.java:113)
at liquibase.dbtest.AbstractSimpleChangeLogRunnerTest.testRerunDiffChangeLog(AbstractSimpleChangeLogRunnerTest.java:298)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at junit.framework.TestCase.runTest(TestCase.java:164)
at junit.framework.TestCase.runBare(TestCase.java:130)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:120)
at junit.framework.TestSuite.runTest(TestSuite.java:228)
at junit.framework.TestSuite.run(TestSuite.java:223)
at org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:35)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:46)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: liquibase.exception.JDBCException: Error executing SQL ALTER TABLE [liquibase].[address] ADD CONSTRAINT [FK_ADDRESS_STATE] FOREIGN KEY ([state]) REFERENCES [liquibase].[state]([id]) ON UPDATE RESTRICT ON DELETE RESTRICT
at liquibase.executor.DefaultExecutor.execute(DefaultExecutor.java:59)
at liquibase.executor.DefaultExecutor.execute(DefaultExecutor.java:89)
at liquibase.database.AbstractDatabase.execute(AbstractDatabase.java:1443)
at liquibase.database.AbstractDatabase.executeStatements(AbstractDatabase.java:1430)
at liquibase.changelog.ChangeSet.execute(ChangeSet.java:210)
... 23 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near the keyword 'RESTRICT'.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
at com.microsoft.sqlserver.jdbc.IOBuffer.processPackets(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.sendExecute(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecute(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(Unknown Source)
at liquibase.executor.DefaultExecutor$1ExecuteStatementCallback.doInStatement(DefaultExecutor.java:80)
at liquibase.executor.DefaultExecutor.execute(DefaultExecutor.java:52)
... 27 more

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

Re: just want to say hello

2009-06-03T15:07:50Z

Welcome Marc, and thanks for the help with the DB2 iSeries.

Nathan

-----Original Message-----
From: Marc Logemann [mailto:li@...]
Sent: Wednesday, June 03, 2009 3:55 PM
To: liquibase-devel@...
Subject: [Liquibase-devel] just want to say hello

Hi,

just wanted to say hello. My name is Marc Logemann from Osnabrueck,
Germany, i am 35 years and i am developing java for about 10 years. I
will contribute to the project in the future and started to include
better support for DB2 for IBM i Systems (iSeries, AS400). I am
looking forward to get in contact to the other developers of Liquibase
and hope we have some fun together, because thats what OSS projects
shoud also be: Fun to develop software with other guys.

---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de

------------------------------------------------------------------------
------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the
latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

just want to say hello

2009-06-03T13:55:29Z

Hi,

just wanted to say hello. My name is Marc Logemann from Osnabrueck,
Germany, i am 35 years and i am developing java for about 10 years. I
will contribute to the project in the future and started to include
better support for DB2 for IBM i Systems (iSeries, AS400). I am
looking forward to get in contact to the other developers of Liquibase
and hope we have some fun together, because thats what OSS projects
shoud also be: Fun to develop software with other guys.

---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de

------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

Re: New Topic: maillist vs. Forum and commits(and translation)

2009-06-02T23:18:56Z

Because I am following 20+ other projects. With email distribution lists it all turns up in one place, with a single login and its something I can monitor daily. If its in a forum I would actively have to monitor that topic, search through all its various sub forums for posts I hadn't read etc. The user interface for email is significantly better for seeing new topics and responding quickly.

Paul

----- Original Message ----
From: "Voxland, Nathan" <nvoxland@...>
To: liquibase-devel@...
Sent: Tuesday, 2 June, 2009 19:49:50
Subject: Re: [Liquibase-devel] New Topic: maillist vs. Forum and commits(and translation)

Can I ask why you prefer the mailing list over the forum?

Nathan

-----Original Message-----
From: Paul Keeble [mailto:csuml@...]
Sent: Tuesday, June 02, 2009 1:27 PM
To: liquibase-devel@...
Subject: Re: [Liquibase-devel] New Topic: maillist vs. Forum and
commits(and translation)

2) If your iffy about a patch normally you would attach to a post to the
liquibase-dev list and then a committer can check and commit it or make
comments about getting it in shape if there are problems with it. Can
you attach in the forums? If so do that or you can attach the patch to
the bug/feature request in sourceforge and then let someone know it
exists in the forum.

agree on (1) - I'm happy to get emails, but I won't be using the forums
so if liquibase switches over fully I'll not be going with it.

Paul

----- Original Message ----
From: LiquiBase Community Forum <nathan@...>
To: liquibase-devel@...
Sent: Tuesday, 2 June, 2009 18:30:46
Subject: [Liquibase-devel] New Topic: maillist vs. Forum and commits
(and translation)

A new topic, 'maillist vs. Forum and commits (and translation)', has
been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=35.new#new

The text of the topic is shown below:

Hi,

i have two issues i want to discuss.

1) I strongly recommend to stick with the dev maillist for developer
issues. I dont know of a single OSS project which handles the dev
communication via Forum. Its so much slower than maillists and the
archiving issue is non-existant for devs normally. And if you need to
find something older, you still have an archive, just not as beautiful
as in a forum. But beauty is for users....

2) Is it ok that i can commit with my newly created JIRA account into
the 1.9 branch? I hope there is some quality check before you guys build
a new 1.9.x because i really dont want to break a release with my first
commit in case i ve missed something.

3) I can help out translating the wiki to german if you like. What do i
need in terms of accounts?

Marc

Unsubscribe to new topics from this board by clicking here:
http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.

------------------------------------------------------------------------
------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the
latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

Re: New Topic: maillist vs. Forum and commits(and translation)

2009-06-02T11:49:50Z

Can I ask why you prefer the mailing list over the forum?

Nathan

-----Original Message-----
From: Paul Keeble [mailto:csuml@...]
Sent: Tuesday, June 02, 2009 1:27 PM
To: liquibase-devel@...
Subject: Re: [Liquibase-devel] New Topic: maillist vs. Forum and
commits(and translation)

2) If your iffy about a patch normally you would attach to a post to the
liquibase-dev list and then a committer can check and commit it or make
comments about getting it in shape if there are problems with it. Can
you attach in the forums? If so do that or you can attach the patch to
the bug/feature request in sourceforge and then let someone know it
exists in the forum.

agree on (1) - I'm happy to get emails, but I won't be using the forums
so if liquibase switches over fully I'll not be going with it.

Paul

----- Original Message ----
From: LiquiBase Community Forum <nathan@...>
To: liquibase-devel@...
Sent: Tuesday, 2 June, 2009 18:30:46
Subject: [Liquibase-devel] New Topic: maillist vs. Forum and commits
(and translation)

A new topic, 'maillist vs. Forum and commits (and translation)', has
been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=35.new#new

The text of the topic is shown below:

Hi,

i have two issues i want to discuss.

1) I strongly recommend to stick with the dev maillist for developer
issues. I dont know of a single OSS project which handles the dev
communication via Forum. Its so much slower than maillists and the
archiving issue is non-existant for devs normally. And if you need to
find something older, you still have an archive, just not as beautiful
as in a forum. But beauty is for users....

2) Is it ok that i can commit with my newly created JIRA account into
the 1.9 branch? I hope there is some quality check before you guys build
a new 1.9.x because i really dont want to break a release with my first
commit in case i ve missed something.

3) I can help out translating the wiki to german if you like. What do i
need in terms of accounts?

Marc

Unsubscribe to new topics from this board by clicking here:
http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.

------------------------------------------------------------------------
------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the
latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

Re: New Topic: maillist vs. Forum and commits(and translation)

2009-06-02T11:49:30Z

Reposting response on forum for those not subscribed:

First the easy ones:

2) It is fine to commit into the 1.9 branch. I do code review every
commit, especially from new committers and can easily roll back changes
that cause problems. We also have a set of unit and integration tests
we run before every release. The long term goal is to further improve
our test coverage, and to take advantage of crucible on
liquibase.jira.com to streamline the code review process.

If it gets too unwieldy, we can always go back to limited committers and
patches, but I am hoping that we can get this approach to work. It
lowers the bar to contributing code, makes the accepting submissions
process less error prone, and gives credit to contributors better.

3) If you could help with translating to German, that would be great.
You only need to create an account on the site wiki to edit pages and
create translations.

Then the bigger one:
1) You are right that you get more lag with the forum than with an email
list. It is also easier to ignore a forum than emails that come to you.
There are some things I really like about the forum, however, even for
devel lists.
a) Archives are more searchable and browsable. This is often not
as big of an issue, but there are many topics on the devel list (like
your questions on adding new database support, building, etc) that new
devels would like to be able to find easily.
b) There are some functionality such as polls, splitting topics,
etc. that would be useful

My hope was/is that we can find a good middle ground between the
features of the forum and the speed of the mailing list. Having topic
notifications go to the mailing list helps because you still get the
immediate feedback that something was posted while still keeping
discussion on the forum (unless people reply to the mailing list:) ).
Unfortunately, only the first topic post gets forwarded to the mailing
list, so you can't use it fully.

There are also RSS feeds available for each forum which does have an
every for every post, although I have noticed using google reader, there
is an hour or so delay before it shows up.

For the devel group, I want something that works best for:
a) getting people answers on the code (either from finding existing
answers or getting a response)
b) keeping people who commit from time to time engaged in the project
c) making anyone who wants to contribute to a topic feel that they
can

My focus for the past few months and for the next few months is around
building the liquibase community, and how the contributer community
communicates is a huge part of that. Adding the forum is an iteration
toward that goal, if it does not make sense to keep it, I am not against
dropping the devel forum in favor of the mailing list. If there are
other options that you think would be better, let me know. I have toyed
with the idea of an IRC channel or two as well, but I do not think the
community is large enough to support that yet.

Nathan

-----Original Message-----
From: Paul Keeble [mailto:csuml@...]
Sent: Tuesday, June 02, 2009 1:27 PM
To: liquibase-devel@...
Subject: Re: [Liquibase-devel] New Topic: maillist vs. Forum and
commits(and translation)

2) If your iffy about a patch normally you would attach to a post to the
liquibase-dev list and then a committer can check and commit it or make
comments about getting it in shape if there are problems with it. Can
you attach in the forums? If so do that or you can attach the patch to
the bug/feature request in sourceforge and then let someone know it
exists in the forum.

agree on (1) - I'm happy to get emails, but I won't be using the forums
so if liquibase switches over fully I'll not be going with it.

Paul

----- Original Message ----
From: LiquiBase Community Forum <nathan@...>
To: liquibase-devel@...
Sent: Tuesday, 2 June, 2009 18:30:46
Subject: [Liquibase-devel] New Topic: maillist vs. Forum and commits
(and translation)

A new topic, 'maillist vs. Forum and commits (and translation)', has
been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=35.new#new

The text of the topic is shown below:

Hi,

i have two issues i want to discuss.

1) I strongly recommend to stick with the dev maillist for developer
issues. I dont know of a single OSS project which handles the dev
communication via Forum. Its so much slower than maillists and the
archiving issue is non-existant for devs normally. And if you need to
find something older, you still have an archive, just not as beautiful
as in a forum. But beauty is for users....

2) Is it ok that i can commit with my newly created JIRA account into
the 1.9 branch? I hope there is some quality check before you guys build
a new 1.9.x because i really dont want to break a release with my first
commit in case i ve missed something.

3) I can help out translating the wiki to german if you like. What do i
need in terms of accounts?

Marc

Unsubscribe to new topics from this board by clicking here:
http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.

------------------------------------------------------------------------
------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the
latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

Re: New Topic: maillist vs. Forum and commits (and translation)

2009-06-02T11:27:13Z

2) If your iffy about a patch normally you would attach to a post to the liquibase-dev list and then a committer can check and commit it or make comments about getting it in shape if there are problems with it. Can you attach in the forums? If so do that or you can attach the patch to the bug/feature request in sourceforge and then let someone know it exists in the forum.

agree on (1) - I'm happy to get emails, but I won't be using the forums so if liquibase switches over fully I'll not be going with it.

Paul

----- Original Message ----
From: LiquiBase Community Forum <nathan@...>
To: liquibase-devel@...
Sent: Tuesday, 2 June, 2009 18:30:46
Subject: [Liquibase-devel] New Topic: maillist vs. Forum and commits (and translation)

A new topic, 'maillist vs. Forum and commits (and translation)', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=35.new#new

The text of the topic is shown below:

Hi,

i have two issues i want to discuss.

1) I strongly recommend to stick with the dev maillist for developer issues. I dont know of a single OSS project which handles the dev communication via Forum. Its so much slower than maillists and the archiving issue is non-existant for devs normally. And if you need to find something older, you still have an archive, just not as beautiful as in a forum. But beauty is for users....

2) Is it ok that i can commit with my newly created JIRA account into the 1.9 branch? I hope there is some quality check before you guys build a new 1.9.x because i really dont want to break a release with my first commit in case i ve missed something.

3) I can help out translating the wiki to german if you like. What do i need in terms of accounts?

Marc

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.

------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

New Topic: maillist vs. Forum and commits (and translation)

2009-06-02T10:30:46Z

A new topic, 'maillist vs. Forum and commits (and translation)', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=35.new#new

The text of the topic is shown below:

Hi,

i have two issues i want to discuss.

1) I strongly recommend to stick with the dev maillist for developer issues. I dont know of a single OSS project which handles the dev communication via Forum. Its so much slower than maillists and the archiving issue is non-existant for devs normally. And if you need to find something older, you still have an archive, just not as beautiful as in a forum. But beauty is for users....

2) Is it ok that i can commit with my newly created JIRA account into the 1.9 branch? I hope there is some quality check before you guys build a new 1.9.x because i really dont want to break a release with my first commit in case i ve missed something.

3) I can help out translating the wiki to german if you like. What do i need in terms of accounts?

Marc

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

New Topic: Patch: Make liquibase work with cygwin

2009-04-30T19:09:35Z

A new topic, 'Patch: Make liquibase work with cygwin', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=11.new#new

The text of the topic is shown below:

Hi.

Tried to add this to JIRA, but got "You cannot create new issues at this time, as the user limit for JIRA has been exceeded. Please contact your JIRA administrators for further assistance." when trying to create a new issue. FAIL.

Attached is a small patch to the liquibase shell script to make it work under cygwin on Windows, as well as under Linux/UNIX/POSIX as it does now.

E.

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations
Conference from O'Reilly Media. Velocity features a full day of
expert-led, hands-on workshops and two days of sessions from industry
leaders in dedicated Performance & Operations tracks. Use code vel09scf
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

New Topic: I'm thinking the next release will be 2.0, no 1.4 support.

2009-04-29T23:04:11Z

A new topic, 'I'm thinking the next release will be 2.0, no 1.4 support.', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=10.new#new

The text of the topic is shown below:

I am feeling like the refactoring I am doing in trunk is enough to push us to 2.0, especially since I have been finding that using 1.5 constructs and methods will keep the codebase simpler.

My current plan is to continue on trunk toward a 2.0 release that will be significantly cleaned up internally, but should impact end users as little as possible. I've toyed with the idea of making .xsd changes and don't think that will be worth doing for the pain that could cause. I am thinking the checksum generation will change, but that is another post...

I created a /branches/1_9 branch to continue maintenance of the the 1.9 codeline. This will keep a version with no end-user changes required, and will continue to support java 1.4.

I'm really happy with how the refactoring is coming along. I think we are going to end up with a much cleaner and more flexible product.

Thoughts?

Nathan

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations
Conference from O'Reilly Media. Velocity features a full day of
expert-led, hands-on workshops and two days of sessions from industry
leaders in dedicated Performance & Operations tracks. Use code vel09scf
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

New Topic: Subversion moved to liquibase.jira.com

2009-04-29T22:56:11Z

A new topic, 'Subversion moved to liquibase.jira.com', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=9.new#new

The text of the topic is shown below:

To take advantage of the nicer Fisheye and to allow us to use Crucible for code reviews, I had to move the subversion repository to liquibase.jira.com.

All the history transferred over correctly, but all development going forward should be done against the new repository. If you have the code checked out from sourceforge, please re-check it out from the new location: http://liquibase.jira.com/svn/CORE/trunk.

Also, commit permissions were not transferred over, so you will need to create a new account in order to commit. You can still check out in read-only mode anonymously, but you will need an account to write. I would like to experiment with having more people commit directly now that we have access to Crucible for reviewing code. I think it will be easier than funneling patches through me and give contributers the credit they deserve. I am not sure exactly how the write permissions work, so if someone would volunteer to do a little testing of if/when they can commit (anonymously, then after creating an account) please let me know.

As an added bonus, the new svn repository is significantly faster than the one at sourceforge.

Nathan

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations
Conference from O'Reilly Media. Velocity features a full day of
expert-led, hands-on workshops and two days of sessions from industry
leaders in dedicated Performance & Operations tracks. Use code vel09scf
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

New Topic: Liquibase-devel list will get copies of "development" forum posts

2009-04-29T22:05:14Z

A new topic, 'Liquibase-devel list will get copies of "development" forum posts', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=7.new#new

More topics may be posted, but you won't receive more email notifications until you return to the board and read some of them.

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=2.0

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations
Conference from O'Reilly Media. Velocity features a full day of
expert-led, hands-on workshops and two days of sessions from industry
leaders in dedicated Performance & Operations tracks. Use code vel09scf
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

Welcome to LiquiBase Community Forum

2009-04-29T20:11:40Z

You are now registered with an account at LiquiBase Community Forum, liquibase-devel!

Your account's username is liquibase-devel and its password is l1qu1Bas3.

You may change your password after you login by going to your profile, or by visiting this page after you login:

http://liquibase.org/forum/index.php?action=profile

Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations
Conference from O'Reilly Media. Velocity features a full day of
expert-led, hands-on workshops and two days of sessions from industry
leaders in dedicated Performance & Operations tracks. Use code vel09scf
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

Re: Packaging for Ubuntu, missing copyright information

2009-04-29T05:03:05Z

Its common to have it on all files, I don't know about any strict
requirement for it to be so with the lgpl. There is an eclipse plugin
that makes it easy to add it to all files:
http://jautodoc.sourceforge.net/

Ben

Paul Keeble wrote:

> Liquibase has a licence file as part of its code base but it should probably exist at the very top of the code base on trunk as well. Is it really necessary to copy the header to every single source file?
>
> Paul
>
>
> ----- Original Message ----
> From: Maia Kozheva <sikon@...>
> To: liquibase-devel@...
> Sent: Wednesday, 29 April, 2009 2:44:42
> Subject: [Liquibase-devel] Packaging for Ubuntu, missing copyright information
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Greetings!
>
> I'm packaging the liquibase library for Ubuntu. Unfortunately, it lacks
> copyright headers in .java files and information about upstream authors.
>
> As explained in the text of the LGPL (lgpl.txt), to make this software suitable
> for inclusion in a free software distribution, you need to add headers like this
> to the .java files included in the source tarball:
>
> /*
> Copyright (C) <year> <name of author>
>
> This library is free software; you can redistribute it and/or
> modify it under the terms of the GNU Lesser General Public
> License as published by the Free Software Foundation; either
> version 2.1 of the License, or (at your option) any later version.
>
> This library is distributed in the hope that it will be useful,
> but WITHOUT ANY WARRANTY; without even the implied warranty of
> MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
> Lesser General Public License for more details.
>
> You should have received a copy of the GNU Lesser General Public
> License along with this library; if not, write to the Free Software
> Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA
> */
>
> Ideally, such a header should appear in build.xml as well.
>
> I would appreciate if you could release an updated source tarball with modified
> source files ASAP.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkn3sQoACgkQGSKqQPshyAqk5QCePwATwBVuhUc8XX6ybnf/Cbo6
> O5cAoLflnRvEvsB9Tu1U2z5g7BPVbHHr
> =JkWa
> -----END PGP SIGNATURE-----
>
> ------------------------------------------------------------------------------
> Register Now & Save for Velocity, the Web Performance & Operations
> Conference from O'Reilly Media. Velocity features a full day of
> expert-led, hands-on workshops and two days of sessions from industry
> leaders in dedicated Performance & Operations tracks. Use code vel09scf
> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
> _______________________________________________
> Liquibase-devel mailing list
> Liquibase-devel@...
> https://lists.sourceforge.net/lists/listinfo/liquibase-devel
>
>
>
>
>
> ------------------------------------------------------------------------------
> Register Now & Save for Velocity, the Web Performance & Operations
> Conference from O'Reilly Media. Velocity features a full day of
> expert-led, hands-on workshops and two days of sessions from industry
> leaders in dedicated Performance & Operations tracks. Use code vel09scf
> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
> _______________________________________________
> Liquibase-devel mailing list
> Liquibase-devel@...
> https://lists.sourceforge.net/lists/listinfo/liquibase-devel
>

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations
Conference from O'Reilly Media. Velocity features a full day of
expert-led, hands-on workshops and two days of sessions from industry
leaders in dedicated Performance & Operations tracks. Use code vel09scf
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel