Excellent, please keep the replies on the user list so folks can follow along (others will have the same questions). There are a number of blog posts covering the repo change, any tips on how to make this more visible let us know! -- Jody Garnett
On Wed, 6 May 2020 at 04:38, Daniel Boulerice <bigblackh...@gmail.com> wrote: > Jody, thanks for the prompt reply. > > I found the POM I was looking for in the systems ZIP. Thanks for the hint. > > For the short story, we build App A which depends on App B. App B is made > by another group in our large company, many time zones away. We are > hooking to the latest version of their app was drafted when GeoTools was > version 21.2 (this group does not turn around quickly and their project is > large). So GeoTools 21.2 dependencies are everywhere. So we have to bring > them in. > > Now, because of the Boundless transition you are mentioning, our code > stopped compiling so it was deemed best to place it in a more stable > location that we own. Therefore we have to hunt for little dependencies > everywhere. > > Thanks for the mirror hint also. > > > > On Tue, May 5, 2020 at 11:30 PM Jody Garnett <jody.garn...@gmail.com> > wrote: > >> Can I ask for more details please? I am going to move my reply to the >> user list also :) >> >> The unsupported modules are not ready to be distributed by geotools (they >> have not been through a review by our project management committee yet). >> >> As such the unsupported modules are not build by default, instead you can >> use maven profiles to build one you are interested in. As an example: >> >> maven clean install -Pgeojsonstore >> >> Check modules/unsupported/pom.xml >> <https://github.com/geotools/geotools/blob/21.2/modules/unsupported/pom.xml> >> for a list of available profiles. >> >> What are you building? >> - If I go to 21.2 page >> <https://sourceforge.net/projects/geotools/files/GeoTools%2021%20Releases/21.2/> >> I can see the pre-built artifacts, and geotools-21.2-project.zip >> - You can also go to the 21.2 tag >> <https://github.com/geotools/geotools/tree/21.2> in GitHub and download >> >> Keep in mind we have recently changed our maven repository so some >> changes to your local .m2/settings.xml file are required if you wish to >> build prior releases such as this. >> >> <mirrors> >> <mirror> >> <id>osgeo-release</id> >> <name>OSGeo Repository</name> >> <url>https://repo.osgeo.org/repository/release/</url> >> <mirrorOf>osgeo</mirrorOf> <!-- previously >> http://download.osgeo.org/webdav/geotools/ --> >> </mirror> >> <mirror> >> <id>geoserver-releases</id> >> <name>Boundless Repository</name> >> <url>https://repo.osgeo.org/repository/Geoserver-releases/</url> >> <mirrorOf>boundless</mirrorOf> <!-- previously >> http://repo.boundlessgeo.com/main/ --> >> </mirror> >> </mirrors> >> >> >> For details see user guide >> <https://docs.geotools.org/latest/userguide/welcome/upgrade.html#alternative-mirror-retired-repo-boundlessgeo-com> >> . >> -- >> Jody Garnett >> >> >> On Tue, 5 May 2020 at 19:55, Daniel Boulerice <bigblackh...@gmail.com> >> wrote: >> >>> We are trying to make our system run with GeoTools but it seems that >>> some unsupported.pom (21.2) file is missing from the ZIP distro. >>> >>> Where do I get that? >>> >>> Thanks Yall! >>> >>> -- >>> Daniel Boulerice >>> bigblackh...@gmail.com >>> Cel: (514) 965-2973 >>> _______________________________________________ >>> GeoTools-Devel mailing list >>> geotools-de...@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/geotools-devel >>> >> > > -- > Daniel Boulerice > bigblackh...@gmail.com > Cel: (514) 965-2973 >
_______________________________________________ GeoTools-GT2-Users mailing list GeoTools-GT2-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
