Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [udig-dev] lowagie.itext dependency for GeoScript

Sounds good frank, any time we can use Orbit we should make that play.

We can add the additional geotools dependencies to GeoTools CQ, first lets update the spreadsheet.

The chat with Sharon, reiterated a bunch of the same ground we covered with Wayne (example discussion is only needed for exempt and workswith dependencies). Let me check my notes ...

Her priorities are:
1) anything that is Piggyback (I think that is with using Orbit is) or DIff gets done first
Jody
2) Go over our initial code contribution questions (she and wayne were both clear that we can contribute the code now, the remaining issues/clarifications just been to be accomplished before we publish a release)
3) Getting through GeoTools (I will check back after I have answered her questions with the GeoTools PMC)

Sorry my notes are not very good, we got distracted a few times looking at things like GeoScript.

One thing I did get was this magical search query:

https://dev.eclipse.org/ipzilla/buglist.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&component=locationtech.technology.udig&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=component&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=substring&product=locationtech&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=locationtech&value-1-1-0=locationtech.technology.udig&value0-0-0=&order=bugs.bug_severity%2Cbugs.short_desc%2Cbugs.bug_severity%2Cbugs.target_milestone%20desc%2Cbugs.priority%20asc%2Cbugs.bug_id%20asc&query_based_on=

It basically says where we are at, and is worth a bookmark.


On Sat, Aug 17, 2013 at 5:39 AM, Frank Gasdorf <fgdrf@xxxxxxxxxxxxxxxxxxxxx> wrote:
I reviewed the dependency-tree for the libs bundle and have seen, that we have a dependency from geoscript to lowagie.itext.

[INFO] +- org.geoscript:geoscript-groovy:jar:1.1-SNAPSHOT:compile
[INFO] |  +- org.geotools:gt-geojson:jar:9.0-M0:compile
[INFO] |  |  \- com.googlecode.json-simple:json-simple:jar:1.1:compile
[INFO] |  +- org.geotools:gt-gtopo30:jar:9.0-M0:compile
[INFO] |  +- org.geotools:gt-imagepyramid:jar:9.0-M0:compile
[INFO] |  +- org.jaitools:jt-jiffleop:jar:0.2.0:compile
[INFO] |  +- org.json:json:jar:20090211:compile
[INFO] |  \- com.lowagie:itext:jar:2.1.7:compile

Because of already approved CQ for itext 2.1.7 (https://dev.eclipse.org/ipzilla/show_bug.cgi?id=7477) we can and included this bundle already from orbit repository.

I like to suggest to exclude com.lowagie.itext from pom-libs, update the manifest and classpath files (in addition to build.properties) and import packages in version 2.1.7 (resolved from bundle from CQ 3475)

I assume the geoscript would work like expected. 

Otherwise I guess we have to create an other CQ for transitive dependencies for GeoScript. 

@Jody: Any hints from your side after the call with Sharon? Whats your feeling about it?

- Frank



_______________________________________________
udig-dev mailing list
udig-dev@xxxxxxxxxxxxxxxx
https://locationtech.org/mailman/listinfo/udig-dev



Back to the top