https://wiki.eclipse.org/api.php?action=feedcontributions&user=Fgdrf%40users.sourceforge.net&feedformat=atomEclipsepedia - User contributions [en]2024-03-28T12:15:53ZUser contributionsMediaWiki 1.26.4https://wiki.eclipse.org/index.php?title=UDig/Release&diff=435446UDig/Release2016-08-12T19:42:21Z<p>Fgdrf@users.sourceforge.net: /* create installable artifacts */</p>
<hr />
<div><br />
== How to create a release ==<br />
<br />
=== Pre-Check ===<br />
<br />
* Are versions in <code>docs/common.py</code> set correctly ?<br />
* Is it required to have a ''What is New'' page (<code>docs/user/en/what_is_new</code>) ?<br />
* Is it neccessary to update Eclipse Help TOC (Table of content - <code>docs/user/toc.xml</code> and <code>plugins/org.locationtech.udig.help/toc.xml</code>) ?<br />
<br />
=== How to set/update versions ===<br />
<br />
mvn tycho-versions:set-version -DnewVersion=<version> -Dtycho.mode=maven -Pproduct,sdk,docs,test -Dall<br />
<br />
where `<version>` can have the following patterns:<br />
* e.g. 1.5.0 for final RELEASE<br />
* e.g. 1.6.0-SNAPSHOT for Development-Version <br />
* e.g. 1.5.0.RC1 for Release-Candiates<br />
<br />
'''NOTEs''': <br />
* Its important to build with listed profiles to update versions in all maven modules<br />
* Its required to have Major-, Minor- and Patch-Version (1.5.0 instead 1.5 to be OSGi complaint - otherwise maven build will fail)<br />
<br />
=== Release-Procedure ===<br />
==== Create a Release-Branch ====<br />
e.g. for 1.5.x Release serie create a branch from master (feature freeze) create a branch and checkout it: <br />
git checkout -b 1.5.x<br />
==== Update from Development-Version to Release(candidate) ====<br />
<br />
Just set `<version>` to prefered release version, e.g. 1.5.0 or 1.5.0.RC1<br />
<br />
==== Release-Build with maven ====<br />
Its required to have Sphinx installed to make docs auf or Restructured Text.<br />
mvn clean install -Pproduct,sdk,docs<br />
<br />
==== create installable artifacts ====<br />
Navigate into deploy folder:<br />
cd deploy<br />
<br />
To prepare update version.sh and set version for the release to package. Change the following two lines:<br />
export SERIES=1.5<br />
export VERSION=1.5.0.RC1<br />
<br />
Afterwards, start packaging with:<br />
./all.sh<br />
<br />
'''NOTE:''' To create dmg packages for Mac OSX its required to have a Mac OSX Environment<br />
<br />
=== Update next Development-Version on Release-Branch ===<br />
Set Version from 1.5.0 to 1.5.1-SNAPSHOT<br />
<br />
=== Update next Development-Version on Master-Branch ===<br />
Set Version from e.g. 1.5.0-SNAPSHOT to 1.6.0-SNAPSHOT</div>Fgdrf@users.sourceforge.nethttps://wiki.eclipse.org/index.php?title=UDig/ECE2015-Hackathon&diff=435448UDig/ECE2015-Hackathon2015-09-25T19:52:57Z<p>Fgdrf@users.sourceforge.net: </p>
<hr />
<div>== Conference ==<br />
[https://www.eclipsecon.org/europe2015/ EclipseCon Europe 2015]<br />
<br />
== Contacts ==<br />
<br />
=== Twitter ===<br />
<br />
[https://twitter.com/udiggis @udigGIS]<br />
<br />
=== Mailinglists ===<br />
* [https://www.locationtech.org/mailman/listinfo/udig-dev udig-dev]<br />
* [https://www.locationtech.org/mailman/listinfo/udig-users udig-users]<br />
<br />
== When and Where ==<br />
TBD<br />
<br />
= Ideas = <br />
* fix Unit Tests for uDig 2.0.0 based on E4<br />
* update Tutorials, both docs and Modules, to lower burdens for others<br />
* upgrade to GeoTools 14 RC <br />
* <br />
= Attendees =<br />
* Jody Garnett<br />
* Frank Gasdorf<br />
<br />
[[Category:Events]] [[Category:Hackathon]]</div>Fgdrf@users.sourceforge.nethttps://wiki.eclipse.org/index.php?title=UDig/MeetingMinutes/20150106&diff=435444UDig/MeetingMinutes/201501062015-01-16T20:07:12Z<p>Fgdrf@users.sourceforge.net: /* Meeting Minutes Jan, 16th 2015 */</p>
<hr />
<div><br />
= Meeting Minutes Jan, 16th 2015 =<br />
<br />
<br />
[[Attending]]<br />
<br />
* Andrea Antonello<br />
* Jody Garnett<br />
* Emily Gouge<br />
* Frank Gasdorf<br />
<br />
[[Agenda]]<br />
<br />
# uDig on Luna - state of the art - with Ludwig<br />
# uDig usability/stability<br />
# uDig and locationtech migration<br />
# PSC/PMC members review<br />
# Future Needs<br />
# organizational / Process<br />
# general<br />
<br />
[[Action Items]]<br />
<br />
* Next Meeting on [http://www.timeanddate.com/worldclock/fixedtime.html?msg=uDig+IRC+Meeting&iso=20150130T16&p1=37&ah=1 January, 30th 4:00PM CET] ?<br />
* Setup Contribution guide at Locationtech.org wiki, announce details at Mailinglist '''''-> Frank'''''<br />
* setup JRE with gdal native libraries (OpenJDK 1.7, gdal 1.9.X, jai) '''''-> Jody'''''<br />
* release from master (Eclipse 3.7 + geotools 11.2) --> Release Version 1.5 '''''-> Frank'''''<br />
* merge luna-branch back to master '''''-> TBD'''''<br />
* release from master (Eclipse 4.4 + geotools 11.2) --> Release Version 2.0 '''''-> TBD'''''<br />
<br />
[[Meeting Minutes]]<br />
<br />
'''1) uDig on Luna - state of the art - with Ludwig'''<br />
<br />
Emily started using luna-support branch and in the application they use a small portion of udig but haven't had any issues with those parts.<br />
<br />
Jody was able to build and walked through the basic motions. Dialog (File Dialog on Mac OSX?) worked. Jody likes to merge as soon as possible because master on Eclipse Indigo doesn't work on Mac OSX (10.9.X?) because of known SWT issues<br />
<br />
Question to Ludwig : Have you tried to integrate it? What are your impressions?<br />
<br />
Frank reports the current state:<br />
master branch is based on Eclipse 3.7 (Indigo) and has been updated to geotools 11.2, geoscript 1.3.1, and imageio-ext 1.1.10 Releases<br />
master branch was broken because of out-dated bable (language packs) update site --> got fixed at the beginning of 2015<br />
luna-support is based on Eclipse 4.4 (Luna) and recently got merged master branch and has the same dependencies<br />
both depending on gdal 1.9.2 (because of imagio-ext bindings) --> Missing gdal support with provided and shipped JRE's<br />
<br />
'''2) uDig usability/stability'''<br />
<br />
Thats the point why uDig isn't usable to run a business such as Hydrology on it. SDK is fine. It will not possible anymore to build a complete GIS application from LocationTech Infrastructure (not allowed to ship JRE and bundled runtime) makes it impossible to use it as it is.<br />
<br />
Community doesn't really know how and where to contribute. Some projects and users have a lot of fixes for known bugs and need a guiding hand..<br />
<br />
Community isn't active as needed to give support on ML<br />
<br />
'''3) uDig and locationtech migration'''<br />
<br />
Jody reports about the state of IP (intellectual property) review of uDig's dependencies such as geotools. with first geomesa, and now geogig going through the review - and cleaning up a lot of our geotools dependencies<br />
<br />
'''4) PSC/PMC members review'''<br />
Andrea has stepped down as a PSC Member - thank you for your time, major contributions and community support. Hope to welcome you back sometimes<br />
<br />
'''5) Future Needs'''<br />
<br />
omitted<br />
<br />
'''6) organizational / Process'''<br />
<br />
omitted<br />
<br />
'''7) general'''<br />
<br />
Jody offered to backport a FeatureSource fix on Geotools master to 11.x branch to get it into uDig - if required.<br />
<br />
We add this point to the agenda of next IRC Meeting.</div>Fgdrf@users.sourceforge.nethttps://wiki.eclipse.org/index.php?title=UDig/MeetingMinutes&diff=435445UDig/MeetingMinutes2015-01-16T20:05:20Z<p>Fgdrf@users.sourceforge.net: Created page with "== uDig Meeting Minutes == {{Special:PrefixIndex/{{FULLPAGENAME}}}}"</p>
<hr />
<div>== uDig Meeting Minutes ==<br />
<br />
{{Special:PrefixIndex/{{FULLPAGENAME}}}}</div>Fgdrf@users.sourceforge.nethttps://wiki.eclipse.org/index.php?title=UDig&diff=435433UDig2015-01-16T19:55:48Z<p>Fgdrf@users.sourceforge.net: /* Wiki */</p>
<hr />
<div>==Infrastructure==<br />
<br />
* project page: http://locationtech.org/projects/technology.udig <br />
* mailing list: http://locationtech.org/mailman/listinfo/udig-dev <br />
<br />
==Wiki==<br />
<br />
* [[uDig Roadmap]]<br />
* [[uDig Infrastructure Migration]]<br />
* [[uDig/MeetingMinutes|Meeting Minutes]]</div>Fgdrf@users.sourceforge.nethttps://wiki.eclipse.org/index.php?title=Upgrade_EclipseE4&diff=435441Upgrade EclipseE42014-05-22T13:24:45Z<p>Fgdrf@users.sourceforge.net: /* Updgrade to E4 */</p>
<hr />
<div>= Updgrade to E4 =<br />
<br />
As a starting point to upgrade uDig to Eclipse E4 Platform this page collects some notes to the [https://www.eclipse.org/eclipse/development/porting/4.2/incompatibilities.php incompatibilities]<br />
<br />
<br />
<br />
== Platform keyring implementation removed ==<br />
We are not managing credentials at the moment, although we have a spot in IService workflow to insert the use of a security service to look up passwords. Looks like org.eclipse.equinox.security.storage is the target.<br />
<br />
--> not applicable.<br />
<br />
== Compatibility bundles for Eclipse 1.0-2.1 removed ==<br />
We are not quite that old!<br />
<br />
== Bundle org.eclipse.help.appserver removed ==<br />
They replaced tomcat with Jetty, chances are we update some dependencies. Since we depend on org.eclipse.help it may be easy to figure out what the new dependencies are.<br />
<br />
== Update Manager bundles removed ==<br />
This was a problem when I did my accidental update - I ended up commenting out the install new plugins menu option. Careful reading shows this is only removed from the SDK, the target platform may still be able to grab them.<br />
<b>Options</b>: Migrate to P2, document use of dropins folder, or update target platform file.<br />
<br />
== Presentation API no longer functional ==<br />
We did not use this functionality (allows you to mess with look and feel).<br />
<br />
== Workbench window advisor can no longer customize window creation ==<br />
We may need to check our udig advisor, as this functionality was intended for RCP apps such as uDig. That said I am not sure we made use of these facilities (it allows you to make funny shaped windows and so forth).<br />
<br />
Notes on the E4 way: http://wiki.eclipse.org/Eclipse4/RCP#Contributing_to_the_Model<br />
<br />
== Servlet 3.0 and Jetty 8 ==<br />
not applicable.</div>Fgdrf@users.sourceforge.nethttps://wiki.eclipse.org/index.php?title=UDig_Roadmap&diff=435440UDig Roadmap2014-05-22T13:23:54Z<p>Fgdrf@users.sourceforge.net: /* uDig 2.0 Release */</p>
<hr />
<div><br />
=uDig 2 Series Roadmap=<br />
<br />
uDig 2 Series is devoted to finding the project a home (with LocationTech) and gradually factoring the project into component parts for use by Eclipse RCP developers.<br />
<br />
For our desktop users there is a lot more functionality available within easy reach:<br />
<br />
* The uDig SDK provides developers with additional features (graph analysis, geocoder search etc...) beyond that available in the desktop application.<br />
* The other great source of functionality is the additional RnD work that is happening at the library level (geopackage, additional raster formats, a host rendering improvements).<br />
<br />
Making this functionality available for our Desktop users, and our SDK developers, is a great technical direction.<br />
<br />
We also look forward to collaboration with fellow LocationTech projects as they complete incubation. This is especially important as GeoCoding technologies are developed, as this is a roadblock for those seeking to bridge between their business data and a good mapping solution.<br />
<br />
By the end of the uDig 2 Series we want to nail our reuse story for RCP developers, and earnestly collect tools and processes for our Desktop users.<br />
<br />
== uDig 2.0 Milestone 1 ==<br />
<br />
Incubation Progress:<br />
<br />
- Transition to LocationTech github<br />
- Packages changed to org.locationtech.udig<br />
<br />
Technology Progress:<br />
<br />
- Upgrade to GeoTools 11 series<br />
- Installer download of prepackaged JRE<br />
<br />
Stretch goal:<br />
<br />
- Upgrade to Eclipse 3.8 (to avoid issues on OSX)<br />
<br />
Note: This is a milestone target, pre-packaged download will be from refractions.net as we will not of completed parallel IP process yet.<br />
<br />
== uDig 2.0 Release ==<br />
<br />
Incubation Progress:<br />
<br />
- Submission of all dependencies for IP review<br />
<br />
Technology progress:<br />
<br />
- n/a<br />
<br />
Stretch goal:<br />
<br />
- Reduce code to minimum in active use<br />
- [[upgrade_EclipseE4|Upgrade to Eclipse 4.x]] for a new look and feel (given community interest)<br />
<br />
=uDig 3 Series=<br />
<br />
What does the future of uDig look like beyond 2.0? The uDig Platform has a strong integration story, and is fully capable of integration with other toolkits and rendering chains beyond our core use of GeoTools. We would like to take advantage of this independence and take a role similar to OpenLayers for web mapping, acting as a single "clearing house" framework allowing teams to leverage spatial data using their choice of spatial toolkit, scripting language, and even geometry representation.<br />
<br />
== Toolkit Independence ==<br />
<br />
The uDig architecture makes heavy use of the Eclipse IAdaptable approach to problem solving. This allows the core framework to remain stable, while gradually being taught (through plugins) how to work with additional GeoSpatial toolkits.<br />
<br />
GeoTools Example (available in uDig 2 series):<br />
<br />
if( resolve.canResolve( FeatureSource.class ) ){<br />
FeatureSource source = resolve.resolve( FeatureSource.class, progressMonitor );<br />
FeatureCollection features = source.getFeatures();<br />
...<br />
}<br />
<br />
Because we know we are working with external resources, the uDig IResolve class makes use of a progress monitor to track any work involved in establishing an initial connection.<br />
<br />
This is the same example adapted for the light-weight Jeo project:<br />
<br />
if( resolve.canResolve( VectorDataset.class ) ){<br />
VectorDataset dataset = resolve.resolve( VectorDataset.class, progressMonitor );<br />
Cursor<Feature> features = dataset.cursor( new Query() );<br />
...<br />
}<br />
<br />
uDig offers similar independence with respect to its rendering engine, out of the box support for the GeoTools rendering engine is available. Our business customers already write custom renderers to directly draw their business objects smoothly and efficiently.<br />
<br />
=Road Map FAQ=<br />
<br />
==Q: When will uDig upgrade from Eclipse 3.7==<br />
<br />
There is strong community demand to upgrade to Eclipse 4.<br />
<br />
The development team is occupied with the transition to LocationTech, if you know any other developers interested in this work we would be pleased to work with them.<br />
<br />
==Q: When are you going to have a release?==<br />
<br />
We are in position to issue a milestone release at any time, based on community demand/interest.<br />
<br />
Our next official release will depend on the Eclipse Foundation IP process which is currently underway.<br />
<br />
==Q: When are you going to support Curve (or GML3, or Geography)?==<br />
<br />
We are dependent on the JTS project getting funding, with a technical direction to take on these data structures (and more importantly the math behind them).<br />
<br />
Recently the Spatial4J project has joined LocationTech offering us an implementation of Geography (i.e. geometry on the surface of a sphere). Technically the GeoTools library can be taught how to make use of Spatial4J (rather than JTS) but this integration effort remains unfunded.<br />
<br />
If you are interested several projects have been able to produce the appropriate data structures, but as a GIS application we have not been interested until they are backed up by math (allowing their use for analysis).<br />
<br />
* http://sourceforge.net/p/jts-topo-suite/code/HEAD/tree/trunk/<br />
* https://github.com/spatial4j/spatial4j<br />
* https://github.com/geotools/geotools/tree/master/modules/unsupported/geometry (port of JTS to ISO1907 data structures)<br />
* https://github.com/geotools/geotools/tree/master/spike/geometry (mash up of deegree GML data structure only approach)<br />
<br />
Technical details: JTS is an implementation of Simple Features for SQL data structures (Point, Line, Polygon). ISO19107 offers a richer set of data structures (Point, Curve, Surface, Volume) that is used by GML3. Implementing the data structures is reasonably straightforward, supplying the math to support operations requires dedication and funding.<br />
<br />
==Q: Are you going to have a 3D map?==<br />
<br />
A: Teams have added a 3D map to uDig before, and our ViewportModel can be used to drive a 3D canvas if you would like to implement one. If you check the email archives you can find that previous teams have been successful (but were unable to donate their work back to the project due to licensing restrictions). <br />
<br />
==Q: Can I read GML files?==<br />
<br />
We previously implemented this functionality, but it was withdrawn due to user-list frustration over how GML works. GML is really a choose-your-own-file-format adventure kit, where your choices are represented by a schema file making use of GML concepts and definitions. <br />
<br />
The good news is that a "two pass" solution is now available (scanning the file once to build up a pretend schema) and then a second time to import the data.<br />
<br />
==Q: Do you support WCS?==<br />
<br />
No. The WCS specification is not complete from the perspective of a client. Based on the information available in the GetCapabilities and DescribeCoverage documents you are not able to safely construct a GetCoverage request.<br />
<br />
How is this being used by other projects? I can only assume that the end-user is being asked, and thus is responsible for making some assumptions about the data being accessed.<br />
<br />
This situation has improved for WCS 2.0, making it the first WCS standard that we could recommend for implementation.</div>Fgdrf@users.sourceforge.nethttps://wiki.eclipse.org/index.php?title=UDig-tmp&diff=435437UDig-tmp2013-11-26T15:29:07Z<p>Fgdrf@users.sourceforge.net: Fgdrf@users.sourceforge.net moved page UDig-tmp to UDig over redirect</p>
<hr />
<div>#REDIRECT [[UDig]]</div>Fgdrf@users.sourceforge.net