Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in
Toggle navigation
Menu
Open sidebar
Michal Balážia
GaitRecognition
Commits
6b4584d7
Commit
6b4584d7
authored
Nov 07, 2016
by
Michal Balazia
Browse files
excluded files
parent
d780d773
Changes
5
Hide whitespace changes
Inline
Side-by-side
.gitignore
deleted
100644 → 0
View file @
d780d773
/dist/
\ No newline at end of file
build.xml
deleted
100644 → 0
View file @
d780d773
<?xml version="1.0" encoding="UTF-8"?>
<!-- You may freely edit this file. See commented blocks below for -->
<!-- some examples of how to customize the build. -->
<!-- (If you delete it and reopen the project it will be recreated.) -->
<!-- By default, only the Clean and Build commands use this build script. -->
<!-- Commands such as Run, Debug, and Test only use this build script if -->
<!-- the Compile on Save feature is turned off for the project. -->
<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
<!-- in the project's Project Properties dialog box.-->
<project
name=
"GaitRecognition"
default=
"default"
basedir=
"."
>
<description>
Builds, tests, and runs the project GaitRecognition.
</description>
<import
file=
"nbproject/build-impl.xml"
/>
<!--
There exist several targets which are by default empty and which can be
used for execution of your tasks. These targets are usually executed
before and after some main targets. They are:
-pre-init: called before initialization of project properties
-post-init: called after initialization of project properties
-pre-compile: called before javac compilation
-post-compile: called after javac compilation
-pre-compile-single: called before javac compilation of single file
-post-compile-single: called after javac compilation of single file
-pre-compile-test: called before javac compilation of JUnit tests
-post-compile-test: called after javac compilation of JUnit tests
-pre-compile-test-single: called before javac compilation of single JUnit test
-post-compile-test-single: called after javac compilation of single JUunit test
-pre-jar: called before JAR building
-post-jar: called after JAR building
-post-clean: called after cleaning build products
(Targets beginning with '-' are not intended to be called on their own.)
Example of inserting an obfuscator after compilation could look like this:
<target name="-post-compile">
<obfuscate>
<fileset dir="${build.classes.dir}"/>
</obfuscate>
</target>
For list of available properties check the imported
nbproject/build-impl.xml file.
Another way to customize the build is by overriding existing main targets.
The targets of interest are:
-init-macrodef-javac: defines macro for javac compilation
-init-macrodef-junit: defines macro for junit execution
-init-macrodef-debug: defines macro for class debugging
-init-macrodef-java: defines macro for class execution
-do-jar: JAR building
run: execution of project
-javadoc-build: Javadoc generation
test-report: JUnit report generation
An example of overriding the target for project execution could look like this:
<target name="run" depends="GaitRecognition-impl.jar">
<exec dir="bin" executable="launcher.exe">
<arg file="${dist.jar}"/>
</exec>
</target>
Notice that the overridden target depends on the jar target and not only on
the compile target as the regular run target does. Again, for a list of available
properties which you can use, check the target you are overriding in the
nbproject/build-impl.xml file.
-->
</project>
catalog.xml
deleted
100644 → 0
View file @
d780d773
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<catalog
xmlns=
"urn:oasis:names:tc:entity:xmlns:xml:catalog"
prefer=
"system"
>
<nextCatalog
catalog=
"nbproject/private/retriever/catalog.xml"
/>
</catalog>
\ No newline at end of file
config/applicationContext.xml
deleted
100644 → 0
View file @
d780d773
<?xml version="1.0" encoding="UTF-8"?>
<beans
xmlns=
"http://www.springframework.org/schema/beans"
xmlns:xsi=
"http://www.w3.org/2001/XMLSchema-instance"
xmlns:aop=
"http://www.springframework.org/schema/aop"
xmlns:tx=
"http://www.springframework.org/schema/tx"
xsi:schemaLocation=
"http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
http://www.springframework.org/schema/tx
http://www.springframework.org/schema/tx/spring-tx-3.0.xsd
http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.0.xsd"
>
<bean
id=
"dataSource"
class=
"org.postgresql.ds.PGPoolingDataSource"
>
<property
name=
"user"
value=
"gait"
/>
<property
name=
"password"
value=
"kuba"
/>
<property
name=
"portNumber"
value=
"5432"
/>
<!--<property name="serverName" value="andromeda.fi.muni.cz" />-->
<property
name=
"serverName"
value=
"localhost"
/>
<property
name=
"databaseName"
value=
"postgres"
/>
</bean>
<bean
id=
"sessionFactory"
class=
"org.springframework.orm.hibernate4.LocalSessionFactoryBean"
>
<property
name=
"dataSource"
ref=
"dataSource"
/>
<property
name=
"packagesToScan"
value=
"gait.domain"
/>
<property
name=
"hibernateProperties"
>
<props>
<prop
key=
"hibernate.dialect"
>
org.hibernate.dialect.PostgreSQLDialect
</prop>
<prop
key=
"hibernate.show_sql"
>
false
</prop>
<prop
key=
"hibernate.format_sql"
>
true
</prop>
<prop
key=
"hibernate.use_sql_comments"
>
true
</prop>
<prop
key=
"hibernate.default_schema"
>
gait
</prop>
<prop
key=
"hibernate.id.new_generator_mappings"
>
true
</prop>
</props>
</property>
</bean>
<bean
id=
"transactionManager"
class=
"org.springframework.orm.hibernate4.HibernateTransactionManager"
>
<property
name=
"sessionFactory"
ref=
"sessionFactory"
/>
</bean>
<tx:annotation-driven
transaction-manager=
"transactionManager"
/>
<bean
id=
"commonDao"
class=
"gait.dao.hibernate.HibernateCommonDao"
>
<constructor-arg
ref=
"sessionFactory"
/>
</bean>
<bean
id=
"print"
class=
"gait.SequentialWorker"
>
<constructor-arg>
<list>
<bean
class=
"gait.worker.Print"
/>
</list>
</constructor-arg>
</bean>
<bean
id=
"sp"
class=
"gait.SequentialWorker"
>
<constructor-arg>
<list>
<bean
class=
"gait.worker.bundle.SimpleWalkCycle150Bundle"
>
<property
name=
"commonDao"
ref=
"commonDao"
/>
</bean>
</list>
</constructor-arg>
</bean>
<bean
id=
"dispatcherDatabase"
class=
"DispatcherQuadrangle"
>
<property
name=
"batchName"
value=
"isvc_db"
/>
<property
name=
"commonDao"
ref=
"commonDao"
/>
</bean>
<bean
id=
"dispatcherQuerySet"
class=
"DispatcherQuadrangle"
>
<property
name=
"batchName"
value=
"isvc_query"
/>
<property
name=
"commonDao"
ref=
"commonDao"
/>
</bean>
</beans>
\ No newline at end of file
manifest.mf
deleted
100644 → 0
View file @
d780d773
Manifest-Version: 1.0
X-COMMENT: Main-Class will be added automatically by build
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment