pom.xml: don't generate database scheme each time automatically.

So now after each changes in entities you should not forget to
re-generate database scheme by command `mvn -P hiberante3:hbm2ddl`

After this changes integration tests passes about 8 sec faster at my
homes laptop.

No functional changes.

Author: php-coder

pom.xml

@@ -636,7 +636,7 @@
 								<component>
 									<name>hbm2ddl</name>
 									<implementation>jpaconfiguration</implementation>
-									<outputDirectory>target/classes</outputDirectory>
+									<outputDirectory>${env.dir}/test</outputDirectory>
 								</component>
 							</components>
 							<componentProperties>
@@ -676,15 +676,6 @@
 								<version>1.0.0.GA</version>
 							</dependency>
 						</dependencies>
-						<executions>
-							<execution>
-								<id>generate-hsql-scheme</id>
-								<phase>prepare-package</phase>
-								<goals>
-									<goal>hbm2ddl</goal>
-								</goals>
-							</execution>
-						</executions>
 					</plugin>
 
 					<plugin>

src/env/test/hsql-scheme.sql

@@ -0,0 +1,52 @@
+--
+-- Generated by Maven: mvn -P test hibernate3:hbm2ddl
+--
+
+    create table suspicious_activities (
+        id integer generated by default as identity (start with 1),
+        ip varchar(15) not null,
+        occured_at timestamp not null,
+        page varchar(100) not null,
+        referer_page varchar(255) not null,
+        user_agent varchar(255) not null,
+        type_id integer not null,
+        user_id integer,
+        primary key (id)
+    );
+
+    create table suspicious_activities_types (
+        id integer generated by default as identity (start with 1),
+        name varchar(100) not null,
+        primary key (id),
+        unique (name)
+    );
+
+    create table users (
+        id integer generated by default as identity (start with 1),
+        activated_at timestamp not null,
+        email varchar(255) not null,
+        hash varchar(40) not null,
+        login varchar(15) not null,
+        name varchar(100) not null,
+        registered_at timestamp not null,
+        salt varchar(10) not null,
+        primary key (id),
+        unique (login)
+    );
+
+    create table users_activation (
+        act_key varchar(10) not null,
+        created_at timestamp not null,
+        email varchar(255) not null,
+        primary key (act_key)
+    );
+
+    alter table suspicious_activities 
+        add constraint FK35F0CA0F8D3FBEA4 
+        foreign key (user_id) 
+        references users;
+
+    alter table suspicious_activities 
+        add constraint FK35F0CA0FC005E970 
+        foreign key (type_id) 
+        references suspicious_activities_types;