[
https://issues.apache.org/jira/browse/DDLUTILS-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mansour Al Akeel updated DDLUTILS-281:
--------------------------------------
Summary: Separate the code and reduce dependencies (was: Serate the code
and reduce dependencies)
> Separate the code and reduce dependencies
> -----------------------------------------
>
> Key: DDLUTILS-281
> URL: https://issues.apache.org/jira/browse/DDLUTILS-281
> Project: DdlUtils
> Issue Type: Improvement
> Components: Ant Tasks, Core (No specific database)
> Reporter: Mansour Al Akeel
> Assignee: Thomas Dudziak
> Labels: ant, maven
> Fix For: 1.3
>
> Original Estimate: 144h
> Remaining Estimate: 144h
>
> This task is composed of additional tasks.
> Currently, the code base is tied to ANT. ddlutils can be used outside of ant.
> Here are some senarios that I can think of, where it can be with or without
> Apache ANT:
> 1- DB migration. flyway is another tool for db migration.
> 2- Unit testing, where we need to create and populate data for testing.
> 3- importing seeds / initial data into any system. Either from a build
> system (ANT, Maven .. etc), or during system startup.
> 4- DB backup ?? may be ?
> I am considering separating the code base into fewer components. A separate
> JIRA task will be created for each:
> 1- ddlutils (core), contains only the java classes for working with the DB.
> 2- ant tasks: contains the interface between ANT and ddlutils core.
> 3- maven tasks: this is not implemented, but can be easily added.
> Each of these components, can be a separate maven project:
> ddlutils:
> --> core
> --> ant-task
> --> ddlutil-maven-plugin
> additional plugin can be added.
> Will add a reference for each subtask.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
