Changes between Version 2 and Version 3 of geotools-packaging


Ignore:
Timestamp:
08/19/14 07:11:29 (11 years ago)
Author:
jlarouche
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TabularUnified geotools-packaging

    v2 v3  
    1 = GeoTools packaging =
     1= !GeoTools packaging =
    22
    3 Packaging GeoTools requires a lot of dependencies, many of them that are not up to date, are not maven compatible or simply are not packaged.
     3Packaging !GeoTools requires a lot of dependencies, many of them that are not up to date, are not maven compatible or simply are not packaged.
    44
    55=== What we need to package ===
    … …  
    9797
    9898
    99  == GeoTools Module Packaging ==
     99 == !GeoTools Module Packaging ==
    100100
    101 Since building GeoTools actually creates many .jar which are all GeoTools module which can be used independently, we can also package them separately.
     101Since building !GeoTools actually creates many .jar which are all !GeoTools module which can be used independently, we can also package them separately.
    102102
    103103Using Maven-Debian-Helper, not much needs to be done. Every module has its own pom.xml. They use a parent pom.xml where some dependencies version are set so you might have to look into it and set them in the module's pom.xml.
    … …  
    105105With that done, running mh_make should work fine.
    106106
    107 The point of packaging modules individually was to try to get just enough to be able to build GeoServer and because apps don't necessarily need the 100+ GeoTools lib to work. 
     107The point of packaging modules individually was to try to get just enough to be able to build GeoServer and because apps don't necessarily need the 100+ !GeoTools lib to work.