-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathdesign.txt
More file actions
97 lines (69 loc) · 3.77 KB
/
design.txt
File metadata and controls
97 lines (69 loc) · 3.77 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
====
Copyright (C) 2013, Moss Computing Inc.
This file is part of nomad.
nomad is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2, or (at your option)
any later version.
nomad 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
General Public License for more details.
You should have received a copy of the GNU General Public License
along with nomad; see the file COPYING. If not, write to the
Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
02110-1301 USA.
Linking this library statically or dynamically with other modules is
making a combined work based on this library. Thus, the terms and
conditions of the GNU General Public License cover the whole
combination.
As a special exception, the copyright holders of this library give you
permission to link this library with independent modules to produce an
executable, regardless of the license terms of these independent
modules, and to copy and distribute the resulting executable under
terms of your choice, provided that you also meet, for each linked
independent module, the terms and conditions of the license of that
module. An independent module is a module which is not derived from
or based on this library. If you modify this library, you may extend
this exception to your version of the library, but you are not
obligated to do so. If you do not wish to do so, delete this
exception statement from your version.
====
COMPONENTS
api - the contract between a migration-def and nomad
core
def - defines the xml format to store information about updates.
history - defines an xml format describing what updates have been
applied to a given data set.
packager - constructs an update jar.
runner - executes updates from an update jar.
maven-plugin - the thing that lets you configure the packager to run as part
of the maven build.
prep-maven-plugin - an optional plugin that records a project's
dependencies in META-INF/classpath.xml as part of the build.
test-migration-handler - used for automated testing.
test-migration-support - used for automated testing.
test-migration-case - used for more real-world automated testing.
CONCERNS
The migration-defs.xml file references a specific version of each artifact.
It would probably make sense for the version of that artifact to be bumped
to the release version once it has been released. It might be possible to
somehow incorporate this into the release process? It might just be more
trouble than its worth.
We've talked about implementing some sort of workspace-awareness logic into
the runner such that it uses workspace/project/target/classes for its
classpath where it make sense. This also might be more trouble than its
worth.
TERMS
Migration Handler: the code/project which performs a single atomic change to
data.
Migration Def: the metdata concerning a single atomic change to data.
Migration Path: a sequence of Migration Def's which define the changes to be
applied to a particular set of data.
Migration: an operation performed by a Migration Handler according to the
appearance of a Migration Def in a Migration Path which is being applied to
a data set.
Migration History: a record of the Migrations which have been performed on a
set of data.
Migration Package: A component containing a migration-def along with all the
resource information needed to execute a migration with it.