vtk_module(vtkCommonDataModel
  DEPENDS
    vtkCommonSystem
    vtkCommonMath
    vtkCommonMisc
    vtkCommonTransforms
  PRIVATE_DEPENDS
    vtksys
  TEST_DEPENDS
    vtkTestingCore
    vtkTestingRendering
    vtkInteractionStyle
    vtkCommonExecutionModel
    vtkFiltersGeneric
    vtkFiltersModeling
    vtkIOGeometry
    vtkIOLegacy
    vtkIOXML
    vtkTestingGenericBridge
    vtkRendering${VTK_RENDERING_BACKEND}
  KIT
    vtkCommon
  )

vtk_module(vtkCommonDataModel
  GROUPS
    StandAlone
  DEPENDS
    vtkCommonSystem
    vtkCommonMath
    vtkCommonMisc
    vtkCommonTransforms
  PRIVATE_DEPENDS
    vtksys
  TEST_DEPENDS
    vtkTestingCore
    vtkTestingRendering
    vtkInteractionStyle
    vtkCommonExecutionModel
    vtkFiltersGeneric
    vtkFiltersModeling
    vtkIOGeometry
    vtkIOLegacy
    vtkIOXML
    vtkTestingGenericBridge
    vtkRendering${VTK_RENDERING_BACKEND}
  KIT
    vtkCommon
  )

Add DataModel to StandAlone group.
Add DataModel to StandAlone group.

This make it easier to build editions which just include DataModel and
dependencies. DataModel module gets included in a "StandAlone" build of
VTK since several other modules in the StandAlone group depend on
DataModel. However, if the edition only has DataModel (and none of the
other modules that depend on it), it doesn't get enabled by default.
Given our definition of "StandAlone" module, DataModule should indeed be
a part of it. Hence, adding it to that group.
