introduction of molecular data type for RNASeq data
segment adaptations
segment adaptations
Set license to GPL3 in plugin descriptor
Add DatabasePortabilityService; fix LIKE on Oracle

Moved here from transmartApp and added fixup for Oracle queries
involving LIKE when HibernateCriteriaBuilder is used (does not cover all
uses).
Fix patient set queries on Oracle

WHen the operator is LIKE, add ESCAPE '\' after the 2nd operand.
Revert "segment adaptations"

This reverts commit c1ae48764fa8cd5299b1a1f6b77c2a56569220e4.
Revert "segment adaptations"

This reverts commit d2109aa7dcf284d0cf0848d72c309bffce740748.
Revert "introduction of molecular data type for RNASeq data"

This reverts commit ea81261fc39ebf48d97fe1c6f72d0e819c80bb4f.
Merge branch rnaseq-revert into master
Remove and ignore web-app/
Upgrade to Grails 2.3.0
Revert "Fix patient set queries on Oracle"

This reverts commit 8a1860bd3a2518157b8f08642dc093e9801e4ff6.
Another strategy is required here.
Revert "Upgrade to Grails 2.3.0"

This reverts commit 84352f79d93810dc435c69f5e78a7282c0d526d4.
Upgrade to Grails 2.2.4; some prep for 2.3.0
DeGplInfo: replace genome_build with release_nbr

That's the column that's in transmsart-data.
Oracle support for when building patient sets

Another strategy.
Work around problem with H2 tests

For some reason, the tests stopped working. There's an exception when
the database connection is created saying the schemas being created in
the init file already exist. For reference, this is the data soure
definition:

	environments {
		test {
			dataSource {
				dbCreate = "update"
				url = "jdbc:h2:mem:testDb;MVCC=TRUE;LOCK_TIMEOUT=10000;INIT=" +
					"RUNSCRIPT FROM './h2_init.sql'"
			}
		}
	}

So I changed CREATE SCHEMA to CREATE SCHEMA IF NOT EXISTS.
I haven't gotten to the bottom of this (why it worked before, but not
now). Though I've noticed  the stack trace includes the creation of a
connection pool, so maybe there are several connections being made and
the second one finds the schemas already there when running h2_init.sql.
Maven repo for publishing is now under https
Don't export code coverage plugin