ActiveMQ on SWiK

Ramesh Parthasarathy's Blog: GlassFish V2 and ActiveMQ 4.1

Mon, 18 Aug 2008 22:08:21 -0700

Ramesh Parthasarathy's Blog: GlassFish V2 and ActiveMQ 4.1

Thu, 07 Aug 2008 14:03:40 -0700

JMS Destination

SLP v2.0.0 Released

Thu, 07 Aug 2008 11:02:22 -0700

News Item edited by Alan D. Cabrera

It is a rewrite of SLP 1.0.x, hence 2.x is not API compatible with 1.x, but the API should be cleaner and more deployment scenarios are supported.

The online documentation has been already updated.

Most notables new features are:

Support for JDK 5 enum and generics.
Support for embeddable ServiceAgent, to be started in-VM with the service provider
Support for standalone ServiceAgentServer, to be deployed as standalone on a host
Support for thread-less, non-listening ServiceAgentClient and UserAgentClient
Interoperable with OpenSLP 1.2.1 and the upcoming 2.0 (for the implemented messages)
Richer Javadocs.

Sub-task

LIVETRIBE-40 - JavaDocs for org.livetribe.slp.api

Bug

LIVETRIBE-56 - OSGi headers need to be fixed
LIVETRIBE-57 - ServiceAgent server must not renew service registrations
LIVETRIBE-61 - AbstractServer is not thread safe

Improvement

LIVETRIBE-17 - Ability to statically specify DirectoryAgents in [User|Service]Agents
LIVETRIBE-32 - JavaDocs for the API classes
LIVETRIBE-54 - Convert SLP 2.0 to use slf4j
LIVETRIBE-55 - Javadocs for SLP 2.0
LIVETRIBE-58 - Allow ServiceAgentClient to connect to a configurable address
LIVETRIBE-60 - Allow ServiceAgentClient to use a list of directory agents

New Feature

LIVETRIBE-7 - Need JavaBean events for SLP events
LIVETRIBE-31 - Implement a lightweight UserAgent
LIVETRIBE-53 - Constructors without Settings parameter

View Online

Jikes RVM 3.0.0 released

Thu, 07 Aug 2008 10:02:23 -0700

News Item edited by Ian Rogers

We're very happy to announce the release of Jikes RVM version 3.0.0.

The road towards 3.0 began just about two years ago and a large number of people, both on the core team and from our user community at large, have contributed to making it a success. Thank You!

The release is available for download at http://downloads.sourceforge.net/jikesrvm/jikesrvm-3.0.0.tar.bz2

The detailed release notes for major changes since 2.9.3 can be found below or in JIRA (http://jira.codehaus.org/browse/RVM/fixforversion/13530),
but we'd like to highlight some of the larger themes that went into the 3.0 release (many of which have already been released in the 2.9.x releases we've made along the way).
** Normalization of source code and build process
*** Complete rewrite of the build/test systems to use ant.
*** Jikes RVM can be developed in Eclipse using the JDT
*** Extensive restructuring of package structure
*** Removal of VM_ and OPT_ prefixes from all source files.
** Increased system stability and performance
*** A new continuous testing system (http://jikesrvm.anu.edu.au/cattrack)
*** Concerted stability and performance drives
** Java 5 support
*** Support for Java 5 language features
*** Use of Java 5 language features throughout the code base

Detailed list (89 issues closed in the 3 months since 2.9.3)

** New Feature

[RVM-358] - Initial support for Apache Harmony class library
[RVM-480] - Spec JVM 2008 regression test
[RVM-534] - MMTk Test harness
[RVM-540] - Implement java.lang.Compiler
[RVM-591] - Support for jdocs.com javadoc
[RVM-592] - Checks on creating ObjectReferences

** Improvement

[RVM-72] - NonMoving annotations for classes instances of which should be allocated to the immortal heap
[RVM-273] - Remove VM_ prefix from all VM classes
[RVM-275] - Remove VMOpt prefix from opt compiler classes that go into bootimage
[RVM-282] - Make dumpVirtualMachine more defensive
[RVM-329] - Specialize IA32 assembler for lister vs. non-lister
[RVM-333] - Annotations used for VM Pragmas (NoInline, Uninterruptible, etc) probably should not be as closed linked to classloaders
[RVM-445] - Clean up handling of JTOC
[RVM-449] - Handle instanceof and checkcast in ShortArray scalar replacer
[RVM-477] - Gather new compiler DNA
[RVM-501] - BuildWithAllClasses is (practically) unused
[RVM-502] - Dead code elimination of pure calls
[RVM-505] - Eliminate calls to VM_Class.getClass..FromStackFrame when stack frame is determinable
[RVM-508] - Have hash map where entries are completely immutable saving references from boot image root set
[RVM-510] - Create top level common directory to make it easier to split out and share useful components from rvm and MMTk
[RVM-511] - Split out MMTk option processing support
[RVM-512] - Experiment with freezing bucket array in VM_HashMap/VM_HashSet
[RVM-513] - Large arrays in boot image cause memory leak
[RVM-525] - Upgrade to GNU classpath 0.97.2
[RVM-537] - Implement inline mustImplementInterface sequence for invokeinterface in baseline compilers
[RVM-538] - Inline checkcast/instanceof sequences in baseline compiler for simple cases
[RVM-572] - Remove OSR_ and BC_ prefixes from OnStackReplacement code
[RVM-593] - Extra checks on references being traced in rvm
[RVM-603] - Improve intel baseline prologue/epilogue/call by use push/pop instead of mov [sp]
[RVM-594] - Naming of MM_Interface

** Bug

[RVM-46] - CaffieneMark failures on AIX/PPC
[RVM-47] - DaCapo regressions on AIX/PPC
[RVM-58] - Linker errors under AIX/ppc
[RVM-105] - sysNetSelect doesnt seem to be avoiding the syswrap select
[RVM-187] - VM_OptGenericMapIterator: findGCMapIndex failed
[RVM-221] - Specialized scanning broken on ppc64-aix?
[RVM-234] - Annotation issues: not implemented via proxy classes, support for serialization
[RVM-269] - unresolved invokeinterface on <null> should force classloading before rasiing NPE

[RVM-271] - Timeouts for stress are not correct
[RVM-303] - Cannot modify accessible final instance fields
[RVM-325] - Spec JVM 98 jack failing with OOMs
[RVM-327] - Performance degredation in IA32 assembler
[RVM-332] - Eclipse 3.2 fails to run on the RVM
[RVM-369] - PPC32-OSX - Crash in GC when a stack contains native frames
[RVM-372] - Integer overflow in sysNanoTime
[RVM-423] - Fop performance strangeness
[RVM-442] - All poisoned tests fail PPC 32
[RVM-454] - The sub-test TestAnnotationInheritance of the basic tests is excluded until it can be fixed
[RVM-458] - Poisoned bit test highlights JNI problem
[RVM-469] - Fix IA32 assembler to use Address instead of Offset for absolute addressing
[RVM-482] - Crash when running Production_Opt0_perf portion of compiler-dna test run
[RVM-483] - Conditionalize fsqrt generation on PowerPC
[RVM-492] - Dumping empty stack kills VM
[RVM-493] - VM_Annotation.readValue doesn't use the correct classloader
[RVM-494] - Conversion between type descriptors, class names, and file names in VM_Atom behaves inconsistently
[RVM-495] - Crash during first major GC on PPC64 tests when running with -X:processors=2
[RVM-497] - New scan boot image assertion failing poisoned tests
[RVM-499] - Overflowing JTOC during DaCapo eclipse run on PPC64 AIX
[RVM-500] - No such field error: TreeMap$SubMap.minKey
[RVM-504] - Increase time out on DaCapo eclipse for rvmppclnx64
[RVM-506] - The field last in VM_HashMap and VM_HashSet is only ever set to null
[RVM-514] - Pure on mathMagic breaks dacapo sunflow
[RVM-521] - Freshly checked out r14346 fails to build with an uninterruptible violation
[RVM-526] - GNU Classpath build: paths too long in check_jni.sh
[RVM-527] - Harmony doesn't build 32bit libraries as necessary for x86_64 build
[RVM-529] - Implement reflection API for Harmony
[RVM-531] - Boot image stack size too small
[RVM-541] - gc stress failures
[RVM-542] - Incorrect encoding of inner class native method names
[RVM-543] - Invoking JNI_OnLoad of unrelated libraries when loading a library with no JNI_OnLoad
[RVM-544] - Class argument in NewObject ignored
[RVM-547] - Building the boot image with the opt compiler and Harmony fails
[RVM-550] - Implementation of isZero magic in PPC baseline compiler can overflow expression stack and corrupt stack frame
[RVM-571] - BigDecimal Pure annotations causes crash on SPECjbb2005 for FullAdaptiveMarkSweep
[RVM-582] - Fix all javadoc "syntax" errors
[RVM-583] - Incorrect rounding on simplified integer divide
[RVM-585] - RVM Identity HashMap doesn't use identity hashCode.. only identity.equals
[RVM-587] - IdentityHashMaps in the bootimage
[RVM-588] - Assertion failure in BC2IR for primitive array load
[RVM-597] - Array index out of bounds in BC2IR generation context
[RVM-598] - Increase use of unpreemptible
[RVM-599] - New poisoned test failures on x86
[RVM-608] - Object replacement ignores finalizer methods

** Task and Sub-Task

[RVM-37] - Doccument the command line options
[RVM-42] - Build/Test infrastructiure to compute compiler DNA
[RVM-490] - Null Pointer Exception in gnu.xml.transform.ParameterNode.clone
[RVM-518] - Change build logic so that the VM prefix on a class name does not control inclusion in the bootimage
[RVM-519] - Rename classes currently with VM_ prefix that will be confusing without it
[RVM-520] - Update userguide to remove VM_ (and OPT_) prefix globally.

View Online

Jikes RVM 3.0.0 released

Thu, 07 Aug 2008 08:02:24 -0700

News Item added by David Grove

We're very happy to announce the release of Jikes RVM version 3.0.0.

The road towards 3.0 began just about two years ago and a large number of people, both on the core team and from our user community at large, have contributed to making it a success. T
hank You!

The release is available for download at http://downloads.sourceforge.net/jikesrvm/jikesrvm-3.0.0.tar.bz2

Detailed list (89 issues closed in the 3 months since 2.9.3)

** New Feature

[RVM-358] - Initial support for Apache Harmony class library
[RVM-480] - Spec JVM 2008 regression test
[RVM-534] - MMTk Test harness
[RVM-540] - Implement java.lang.Compiler
[RVM-591] - Support for jdocs.com javadoc
[RVM-592] - Checks on creating ObjectReferences

** Improvement

[RVM-72] - NonMoving annotations for classes instances of which should be allocated to the immortal heap
[RVM-273] - Remove VM_ prefix from all VM classes
[RVM-275] - Remove VMOpt prefix from opt compiler classes that go into bootimage
[RVM-282] - Make dumpVirtualMachine more defensive
[RVM-329] - Specialize IA32 assembler for lister vs. non-lister
[RVM-333] - Annotations used for VM Pragmas (NoInline, Uninterruptible, etc) probably should not be as closed linked to classloaders
[RVM-445] - Clean up handling of JTOC
[RVM-449] - Handle instanceof and checkcast in ShortArray scalar replacer
[RVM-477] - Gather new compiler DNA
[RVM-501] - BuildWithAllClasses is (practically) unused
[RVM-502] - Dead code elimination of pure calls
[RVM-505] - Eliminate calls to VM_Class.getClass..FromStackFrame when stack frame is determinable
[RVM-508] - Have hash map where entries are completely immutable saving references from boot image root set
[RVM-510] - Create top level common directory to make it easier to split out and share useful components from rvm and MMTk
[RVM-511] - Split out MMTk option processing support
[RVM-512] - Experiment with freezing bucket array in VM_HashMap/VM_HashSet
[RVM-513] - Large arrays in boot image cause memory leak
[RVM-525] - Upgrade to GNU classpath 0.97.2
[RVM-537] - Implement inline mustImplementInterface sequence for invokeinterface in baseline compilers
[RVM-538] - Inline checkcast/instanceof sequences in baseline compiler for simple cases
[RVM-572] - Remove OSR_ and BC_ prefixes from OnStackReplacement code
[RVM-593] - Extra checks on references being traced in rvm
[RVM-603] - Improve intel baseline prologue/epilogue/call by use push/pop instead of mov [sp]
[RVM-594] - Naming of MM_Interface

** Bug

[RVM-46] - CaffieneMark failures on AIX/PPC
[RVM-47] - DaCapo regressions on AIX/PPC
[RVM-58] - Linker errors under AIX/ppc
[RVM-105] - sysNetSelect doesnt seem to be avoiding the syswrap select
[RVM-187] - VM_OptGenericMapIterator: findGCMapIndex failed
[RVM-221] - Specialized scanning broken on ppc64-aix?
[RVM-234] - Annotation issues: not implemented via proxy classes, support for serialization
[RVM-269] - unresolved invokeinterface on <null> should force classloading before rasiing NPE
[RVM-271] - Timeouts for stress are not correct
[RVM-303] - Cannot modify accessible final instance fields
[RVM-325] - Spec JVM 98 jack failing with OOMs
[RVM-327] - Performance degredation in IA32 assembler
[RVM-332] - Eclipse 3.2 fails to run on the RVM
[RVM-369] - PPC32-OSX - Crash in GC when a stack contains native frames
[RVM-372] - Integer overflow in sysNanoTime
[RVM-423] - Fop performance strangeness
[RVM-442] - All poisoned tests fail PPC 32
[RVM-454] - The sub-test TestAnnotationInheritance of the basic tests is excluded until it can be fixed
[RVM-458] - Poisoned bit test highlights JNI problem
[RVM-469] - Fix IA32 assembler to use Address instead of Offset for absolute addressing
[RVM-482] - Crash when running Production_Opt0_perf portion of compiler-dna test run
[RVM-483] - Conditionalize fsqrt generation on PowerPC
[RVM-492] - Dumping empty stack kills VM
[RVM-493] - VM_Annotation.readValue doesn't use the correct classloader
[RVM-494] - Conversion between type descriptors, class names, and file names in VM_Atom behaves inconsistently
[RVM-495] - Crash during first major GC on PPC64 tests when running with -X:processors=2
[RVM-497] - New scan boot image assertion failing poisoned tests
[RVM-499] - Overflowing JTOC during DaCapo eclipse run on PPC64 AIX
[RVM-500] - No such field error: TreeMap$SubMap.minKey
[RVM-504] - Increase time out on DaCapo eclipse for rvmppclnx64
[RVM-506] - The field last in VM_HashMap and VM_HashSet is only ever set to null
[RVM-514] - Pure on mathMagic breaks dacapo sunflow
[RVM-521] - Freshly checked out r14346 fails to build with an uninterruptible violation
[RVM-526] - GNU Classpath build: paths too long in check_jni.sh
[RVM-527] - Harmony doesn't build 32bit libraries as necessary for x86_64 build
[RVM-529] - Implement reflection API for Harmony
[RVM-531] - Boot image stack size too small
[RVM-541] - gc stress failures
[RVM-542] - Incorrect encoding of inner class native method names
[RVM-543] - Invoking JNI_OnLoad of unrelated libraries when loading a library with no JNI_OnLoad
[RVM-544] - Class argument in NewObject ignored
[RVM-547] - Building the boot image with the opt compiler and Harmony fails
[RVM-550] - Implementation of isZero magic in PPC baseline compiler can overflow expression stack and corrupt stack frame
[RVM-571] - BigDecimal Pure annotations causes crash on SPECjbb2005 for FullAdaptiveMarkSweep
[RVM-582] - Fix all javadoc "syntax" errors
[RVM-583] - Incorrect rounding on simplified integer divide
[RVM-585] - RVM Identity HashMap doesn't use identity hashCode.. only identity.equals
[RVM-587] - IdentityHashMaps in the bootimage
[RVM-588] - Assertion failure in BC2IR for primitive array load
[RVM-597] - Array index out of bounds in BC2IR generation context
[RVM-598] - Increase use of unpreemptible
[RVM-599] - New poisoned test failures on x86
[RVM-608] - Object replacement ignores finalizer methods

** Task and Sub-Task

[RVM-37] - Doccument the command line options
[RVM-42] - Build/Test infrastructiure to compute compiler DNA
[RVM-490] - Null Pointer Exception in gnu.xml.transform.ParameterNode.clone
[RVM-518] - Change build logic so that the VM prefix on a class name does not control inclusion in the bootimage
[RVM-519] - Rename classes currently with VM_ prefix that will be confusing without it
[RVM-520] - Update userguide to remove VM_ (and OPT_) prefix globally.

View Online

GeoTools OSGeo Graduation Links

Wed, 06 Aug 2008 15:02:16 -0700

News Item added by jgarnett

As mentioned in the 2.5-M3 release anouncement yesterday - GeoTools has finally graduated from the OSGeo incubation process.

Here are a couple of news links from around the web:

Thanks again to everyone who helped out.

View Online

PackJacket, a GUI for IzPack

Tue, 05 Aug 2008 11:02:10 -0700

News Item added by Julien Ponge

I am pleased to forward the announcement of a new project called PackJacket which is hosted at Sourceforge and that was created by Manodasan Wignarajah and Amandeep Grewal.

PackJacket is a GUI frontend to the IzPack project. It is built with Java Swing and creates an installer for your application. The installers which are created by this program are cross-platform and multi-language. You can use the GUI to create installer fit to your needs.

The PackJacket project is looking for feedback as this is only their first release. PackJacket is published under the terms of the GPLv3 license.

View Online

2.5-M3 Released

Mon, 04 Aug 2008 20:02:09 -0700

News Item added by jgarnett

The GeoTools 2.5-M3 milestone release is available for download:

http://geotools.codehaus.org/2.5-M3

The GeoTools 2.5 series has been updated to use Java 5, and has undergone many improvements. This release is centred around making a new Feature model available. The new feature model is based on formal GeoAPI interfaces and allows the library to work complex data structures.

Thanks to everyone who provided feedback on our new Feature model. This release contains several usability improvements based on your feedback; thanks also go out to Andrea who spent some time with a profiler to minimize the performance cost associated with this change.

There are no further API chances planned for the 2.5.x series; we have started formal branch and are treating this as a stable branch. Both the GeoServer and uDig projects have successfully migrated, you should make your migration plans now; we expect a a release candidate as soon as GeoServer passes a few more CITE tests.

Features from 2.5-M3:

OSGeo gradudation! All the headers have changed and we now track license use on a module by module basis
Usability and Performance improvements to the Feature
FeatureCollection no longer implements SimpleFeature or Collection; removal associated implementation classes such as ResourceCollection

Features from 2.5-M2:

JAXB bindings for the metadata module (ie support for ISO 19139 documents)
FeatureAccess super class for DataStore, allowing data access using ISO

Features from 2.5-M1:

Change over to GeoAPI SimpleFeature
Support GetGMLObject
Preview of new Swing Widgets (and a warm welcome to Eclesia)

Features from 2.5-M0:

Online User Guide
Java 5
Improved CRSAuthorityFactory implementations available for Java Enterprise Edition users
ISO 19107 Geometry implementation available as a supported module
DB2 returns to supported status
ArcSDE returns to supported status
GeometryBuilder utility class
A new GPX DataStore

Release Notes:

http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10270&styleName=Html&version=14259

For more information please visit:

If you are new to GeoTools please consider this release as a good starting point, although the 2.4.x remains the stable branch we have no planned API changes and user documentation available for the 2.5.x series.

Enjoy,
The GeoTools Community

View Online

IRC Logs August 4th

Mon, 04 Aug 2008 11:01:55 -0700

News Item added by jgarnett

0) what is up
1) chat

Action Items:
0) 2.5-M4 tag created; to be released this week
1) 2.4.x to be released this week for GeoServer
2) 2.2.x to be released (pending one bug fix) for uDig
3) SE patch to arrive this week Eclesia will send email

jgarnett* good morning
jgarnett I am still wonder if the meeting time is now .. or in an hour
vheurteaux hello jgarnett it's now
joined #geotools
jgarnett oh okay
jgarnett Morning Eclesia, aaime etc...
jgarnett let us start the meeting
Eclesia hi jgarnett
jgarnett (we are on holiday's here in Canada; so attendance from Refractions will be light)
aaime ops right it's Monday
jgarnett agenda topics
jgarnett aaime I feel a bit thrown around on the 2.4.x release schedule; can I ask you for an update in todays meeting?
aaime I have no topics for the meeting, the only topic I need an update for was sent to the ml
jgarnett looking for it ...
jgarnett what was it on?
jgarnett A WHERE 1=1 ?
jgarnett okay I can respond to that email.
aaime jgarnett, yes, that one
jgarnett gabriel is one of the people that can test arcsde; I should also be able to run tests for you. No idea about DB2; you can start by emailing the module maintainer directly.
jgarnett okay well let us start with the traditional 0) what is up
jgarnett this should be a short meeting.
desruisseaux Martin: metadata
Eclesia jsorel : playing with xml apis
aaime fixing bugs and plaing with the new GeoServer UI
jgarnett jgarnett - kicking off several new uDig based projects (the teams will have some exposure to this email list); wps project is wrapping up this week; looking into a gdal2gt bridge for MITAB support; hooking up the coveragetools in udig; adding some processing to imagemoasic with Emily
simboss jgarnett: wow
simboss
simboss simboss: netcdf
groldan geoserver 2.0 ui
jgarnett thinking; so if so many people are doing geoserver 2.0 ui; what is left on the 1.7 train? I ask because I would like an answer for the "GeoTools 2.5.0 when" questions on the user list.
aaime next rc is not scheduled this week afaik
aaime or at least not soon
jgarnett I see
aaime and the blockers in 1.7.0-rc1 need Justin attention
jgarnett well I would like to have a clue; since we kind of owe the OGC a press release
jgarnett and it would be nice if that included some associated software.
jgarnett was anyone able to go back and tag 2.5.x ?
jgarnett to reflect the release geoserver made last week?
jgarnett Martin started a thread about 2.5-M3 ...
aaime not sure, what I'm sure of is that someone noted the revision
aaime I wasn't involved in the release process other than doing CITE tests
jgarnett So do I ask dwins?
desruisseaux Basically I was just looking for a tag before to remove metadata annotations.
desruisseaux I was not looking for a real 2.5-M3 release.
jgarnett And I am looking to get a release in maven; for the user list.
aaime jgarnett, the release in geoserver was made by bmmpxf
aaime if he did not ask anybody to tag
aaime nobody did
groldan hmmm pity
aaime we have the revision number, we can add the tag at any point
jgarnett aaime if you could do so; I can release the tag today.
jgarnett (and can we please try and be a bit more clear next release cycle )
aaime why do you want to release the tag?
jgarnett Martin does that meet your needs?
aaime jgarnett, I cannot be clear for other people, just clear for myself
jgarnett because I care about geotools as a project; and we have users asking for the release...
jgarnett okay I will try and be more clear next release cycle; I thought I was working well with dwins
jgarnett and then he said "we are releasing a beta now" and everything went sideways for me...
aaime jgarnett, I said bmmpxf did the release
aaime he's the one doing the gs releases now
jgarnett true; dwins was just kind enough to tell me what had happened
jgarnett from my perspective I had set aside work and volunteer time to help get the geotools release out; and then I lost contact with who was doing what on the geoserver side.
groldan mike is eating, lets wait for him to get back and I can ask him for the rev number and do the tagging
jgarnett ie we wanted to try getting CITE tests to pass from a branch; and then we were going to release.
jgarnett cool; if someone can send me the -revision or create a tag; I can stumble through the release process today.
jgarnett (I would still like to confirm that this meets martin's needs?)
aaime jgarnett, we cannot pass cite due to a number of issues that require Justin attention
jgarnett okay
jgarnett I will release this as a 2.5-M3 then.
acuster it meets M's needs
aaime about the release of 1.6.5, I was going to do it, but Chris told me to delay it so...
jgarnett okay
jgarnett when you do get an idea let me know
aaime he said mid week next week thought
jgarnett hrm; should I bother to pass that on to the user list?
aaime so we could try to release 1.6.5 in a couple of days
aaime (I asked last week)
jgarnett ah
jgarnett so we should make a 2.4.x release this week then?
aaime jgarnett, you can, but there's no way I have time to fix more 2.4.x bugs
jgarnett Do you need anything for that ...
aaime apparently so
aaime nothing really
jgarnett cool.
acuster GeoServer 1.7.0-beta2 (July 30, 2008) ..... This release is based on Geotools 2.5.x (revision 31101).
jgarnett thanks ...
CIA-35 groldan * r31127 /tags/2.5-M3/: tagging 2.5.x from rev #31101
groldan jgarnett: tagged http://svn.geotools.org/tags/2.5-M3 from 2.5.x at rev #31101
jgarnett oh darn ... I am in the same boat as everyone else
jgarnett I hate to "cry wolf" but we are at the stage of making press releases for uDig 1.1.0
jgarnett so chances are I need to make a 2.2.x release this week
jgarnett we have one remaining bug fix to sort out; charset support in shapefiles.
aaime which has been fixed in 2.4.x I believe
jgarnett It has; although doing some research I found that the DBF actually contains the info
aaime at least I rember making sure that GEoServer could display layers in
aaime norvegian, chinese and arab
aaime and that info can usually be trusted, right?
jgarnett yes; that was my first thought as well. The korean uDig developers already hardcoded their locale in; I am trying to actually fix the problem so they can use the uDig 1.1.0 release.
jgarnett well I don't know how many programs use the DBF correcty; so we can still keep our connection parameter as an override.
jgarnett but when i went looking I found a list of bug reports on the topic
jgarnett (users complaining that the DBF header settings were ignored)
aaime I see
jgarnett A couple more updates; Martin I was able to use the system properties to let uDig work with epsg-hsql.
aaime ah right, did you find where GeoServer sets its own?
jgarnett So hacking on referencing can return to a low priority for both of us ... not ideal but you may relax knowning I am not going to launch into the referencing codebase this week.
desruisseaux Thanks for the info Jody
jgarnett I did not find out; I had to look at the "Axis Issue" page I am not sure I got all the settings but it is enough to reduce the panic.
jgarnett It also points out that some of our Hints cannot be "global"
desruisseaux Yes, this is what Andrea said last week. I don't know why.
jgarnett Or at the very least referencing has some fun issues to sort out with respect to hints.
aaime jgarnett, for the record: http://svn.codehaus.org/geoserver/trunk/geoserver/web/src/main/java/org/geoserver/GeoserverInitStartupListener.java
aaime we tried to use hints only but it did not work so we had to go back to system properties
jgarnett Thanks Andrea; looks like I missed a few - that is the answer I was trying to ask these last couple weeks
aaime sorry, I noticed it once but it was too late, and then I forgot
groldan aaime: btw, that one does look like it should go in main, not in web?
aaime why, it's a startup listener
aaime web container dependedent
jgarnett martin I am pretty sure I know how to approach the bug hunt; but we can leave this until we are both more sane?
aaime you did not want filters in main, you want listeners now?
groldan thought it was spring dependent
aaime nope, that one has to be absoluted the very first thign that runs
aaime when spring starts up it's already too late
desruisseaux Jody, yes it would be fine to wait a bit. I will let peoples know when I will be back on referencing hacking?
groldan ok
jgarnett Eclesia how goes your SLD work? On uDig trunk we would love to write our Style pages using StyleVisitors etc today.
aaime those properties must be set before any crs is requested
jgarnett Since we are writing them anyways; if we had your patch applied on 2.6.x we would not have to rewrite them later.
Eclesia well with everything going around I was wiating a bit for the patch
jgarnett I thought of updating SLDParser (the DOM one) to be an SEParser
jgarnett but noticed that we do not have a GML3 DOM parser etc...
jgarnett so I figured that creating more along those lines would make me tired; and thought I should check in with what you were doing?
Eclesia I can send you the patch if that's what you mean ?
jgarnett Eclesia I am not interested in checking out a patch on volunteer time
jgarnett I am interested in working with you on trunk; but I don't know your timing.
Eclesia is lost
jgarnett I am just letting you know that the timing is pretty good from the uDig standpoing.
Eclesia on what do you want to work with me ?
jgarnett ie if you commit we will be able to give you timely feedback on the new style interfaces.
jgarnett we will be writing code using style visitor
jgarnett (rather than set methods)
jgarnett to update stuff.
Eclesia ok so if I apply the patch this week does that suit you ?
jgarnett We would like a couple days warning;
jgarnett but yes; we are on trunk in order to work with you on this
Eclesia when do you want me to apply it then ?
jgarnett we have a deliverable thursday
jgarnett so either early in the week (say today?)
jgarnett or thursday.
jgarnett I would not mind an overview of what your patch includes?
jgarnett I am assuming the getools style interfaces will extend the geoapi ones
Eclesia I cant today, but tomorrow I guess it's possible
jgarnett (I tried this myself and only ran into conflicts where ENUMS had been introduced)
Eclesia the patch makes the GT style interface extends the geoapi ones, and it fix the gt style implementations
jgarnett sweet.
Eclesia all methods (old ones and new ones) are still here
jgarnett Did you wade through all my email to geoapi on the subject. We seemed to only have a few areas left to talk about.
Eclesia but the streamingrenderer breaks a bit when It comes on FeatureTypeNames that where replaced from string to Name objects
Eclesia so there will be some fixes to do
jgarnett understood
jgarnett StreamingRenderer is easier to understand with the ResourceCollection stuff removed.
Eclesia so I apply tomorrow ?
Eclesia will you have time to fix before thrusday ?
jgarnett Eclesia we have a teams of developers working on turnk
jgarnett so you should not be applying broken code?
jgarnett do you need help getting something working?
Eclesia It's not broken, test failures
jgarnett (aside: Graphic.graphicalSymbols() is order dependent ie List)
jgarnett hrm
Eclesia I cant fix the streaming renderer
jgarnett okay understood; so yeah send me an email before you commit and we can tag team that one.
jgarnett Is there a time when we are both working?
Eclesia for me it's at the end of the day
jgarnett okay so when you are ready please send an email; and set a time
Eclesia 17H to 18H
jgarnett I think that is it for the meeting time slot.
jgarnett Anything else or should I post the logs.
Eclesia jgarnett: a solution would be taht I send you the patch, and you can commit it when you think the streamingRenderer is fixed ?
Eclesia this way you can do it when you wish and we wont break the build
jgarnett I hear you
jgarnett I am weighing my volunteer time today vs you interecting with the geotools community in the normal manner.
jgarnett Is there another way to help you debug streaming renderer?
jgarnett And is your patch current; ie streaming renderer has changed over the last two weeks.
jgarnett nope I think you better set a time and commit
Eclesia I've been maitaining this patch for more then a month on my free time ...
jgarnett I don't want to set a precedent of accepting large patches; not when you have commit access.
jgarnett what I can do is help you clean up streaming renderer; and we do appoogize for taking so long to get 2.5.x out of the way ... thanks for maintaining the patch.
jgarnett So what time do you want to do this Eclesia; tomorrow?
jgarnett Now?
Eclesia I cant do it know
Eclesia the patch is at work (I'm at home)
jgarnett
Eclesia now*
jgarnett How about tomorrow? You mentioned a time up above; but I have not figured out when that is for me
Eclesia meeting startes a 18H, so one hour before
acuster what time is it for you right now jody?
acuster its 19:42 here
acuster so 17:00 is 2:42 ago
Eclesia 17h to 18h is fine
jgarnett okay sounds great
jgarnett can you send an email; with that time slot; and the appropriate dire warning for people working on turnk.
jgarnett tunk - silly typo
jgarnett Is that okay?
Eclesia ok
jgarnett cool thanks for the meeting everyone.

View Online

Release of IzPack Maven Plugin 1.0-alpha-1

Sun, 03 Aug 2008 08:01:57 -0700

News Item added by Julien Ponge

Our developer Dan Tran has just released the IzPack Maven Plugin version 1.0-alpha-1.

The plugin allows users to build their installers using IzPack, the Maven way.

The plugin is available from Maven Central at http://repo1.maven.org/maven2/org/codehaus/izpack while the plugin site is hosted at http://izpack.codehaus.org/izpack-maven-plugin.

Do not hesitate to report issues to Dan!

View Online

2.2-M1 released

Mon, 28 Jul 2008 16:58:41 -0700

News Item edited by jgarnett

The GeoAPI 2.2-M1 milestone release has been deployed to our maven repository.

This tag contains some interesting work:

Initial round of org.opengis.style interfaces based on the latest OGC and ISO portrayal specifications
Some feedback on our new feature model after several months testing
- Feature now has a getIdentifier() method allowing access to the same FeatureId used by the org.opengis.filter package.
- use of getDescriptor methods (rather than getAttribute methods) for ComplexAttribute

Thanks to everyone who helped out and provided feedback.

View Online

IRC Logs July 28th

Mon, 28 Jul 2008 11:58:56 -0700

News Item added by jgarnett

Agenda topics:

SE 1.1 and SLD 1.1 chat
Wwhat is up
2.5.x branch

jgarnett desruisseuax ping? I was wondering if you had any thoughts about epsg-hsql use?
desruisseaux Hello Jody
desruisseaux I don't know why it doesn't find it. I was hopping to produce a dump of registered factories, but I'm unable to remember where is the program doing that.
desruisseaux We had a JIRA task for that with screenshot and usage instructions... I searched for it half-an-hour and didn't found it.
jgarnett I placed it in the geotools user guide
jgarnett I can make a dump of the factories for you.
jgarnett (and can send that on to email)
jgarnett however I think the design of the factory lookup / hints is incorrect.
jgarnett ie global hints are interferring with your ability to look up the epsg-hsql authority; so you never find it in order to wrap it ...
jgarnett here is the tool
jgarnett http://docs.codehaus.org/display/GEOTDOC/1+Referencing+Configuration+and+Tool
Eclesia hi
jgarnett morning
jgarnett we should start the meeting?
jgarnett floor open to agenda topics...
jgarnett martin I am sad about the referencing stuff; I don't feel I have enough information to use up meeting time talking about it.
desruisseaux You have been much better than me for finding back the informations Jody . It was not far finally.
desruisseaux Could you send me a screenshot of the factories tree please? And also a list of all global hints
desruisseaux (there is a tools for dumping global hints as well - trying to remember...)
desruisseaux I think a copy and paste of System.out.println(GeoTools.getGlobalHints()) should be okay.
jgarnett okay I will take that to email (since I don't have enough information to talk about it during the meeting; you did get my earlier emails so you know that global hints are breaking the referencing module)
jgarnett I can make a bug report for that and we can track progress there.
jgarnett emily / Eclesia did you want to grab an agenda topic to talk about SLDParser and/or SE 1.1 ?
jgarnett I was also going to ask gabriel / dwins about the release train
Eclesia I still have no answer for SLD interface in geoapi so I can't really say
jgarnett dwins your code freeze email looked like it was held up in a moderation queue for a while? Hopefully you can clarify this meeting?
jgarnett I am not sure I understand "no answer for SLD interfaces" in geoapi? what do you mean ...
Eclesia For me it's first geoAPI then GeoTools
jgarnett well both have to happen at once; they feed into each other ... I did give you a very solid code review last week
jgarnett (using the geotools implementation to find questions about the geoapi interfaces)

dwins doesn't remember sending an email that got held up in a moderation queue
jgarnett I was supposed to be monitoring the email list while gabriel was away; I let one of your email messages loose over the weekend
Eclesia (I'm just making the secretary work to build up the interfaces of OGC SLD in geoapi, I also have a look at GT sld class to see what could go wrong)
jgarnett okay I understand now; I just read your email on the geoapi list. Thus far you have done Symbology Encoding 1.1 I guess? And now you are looking at the SLD 1.1 interfaces?
Eclesia yes
Eclesia and they are done
jgarnett got it; so you have the SLD 1.1 interfaces available for geoapi; and you would like to commit them for review etc. That sounds okay; but I can reply to your email ...
jgarnett did you want to grab an agenda topic to talk about a) your plans for 2.6.x and b) SLDParser stuff with Emily?
Eclesia I just want to know if someone at refraction is going to make an SLD1.1 parser, I seen you work on styles and sld
jgarnett Eclesia we cannot make an SLD 1.1 parser until there is code (and a renderer to make use of it).
jgarnett We have no paid work in hand that requires SLD 1.1
jgarnett (indeed for udig we would probably just stick to the SE 1.1 work; SLD is more of interest to #geoserver developers
Eclesia ok so I dont any agenda item ^^
jgarnett that said we know the DOM based SLDParser
jgarnett and we need to know your plans for supporting SE 1.1 and SLD 1.1
jgarnett (ie this is planning; we don't do work you need for free; and we also don't start work without talking to you first ...)
Eclesia for SE1.1 GT is going to have a patch in 2.6.x
jgarnett cool
Eclesia and for SLD1.1 I still dont know what will be in GT
aaime GeoServer people has no sponsoring on using SE 1.1 and SLD 1.1 either, actually we don't implement any WMS standard that could use them
jgarnett well to put anything into geotools we got to keep the big picture in mind
jgarnett so someone better have plans for a parser
jgarnett (or we are not taking good care of the library)
jgarnett I do agree that SLD 1.1 is pretty useless...
jgarnett (note we have now talked about this so much we should of grabbed an agenda item)
jgarnett aaime does #geoserver have any plans for SE 1.1 or SLD 1.1 ?
Eclesia there's no t enormous difference with SLD1.0 now that we have SE1.1
aaime none
aaime no one ever requested we support it
aaime and wms 1.1.1 is based on sld 1.0
jgarnett what is based on sld 1.1 ?
jgarnett WMS 1.3 or something?
aaime maybe wms 1.3, but I actually never seen that citation
jgarnett Eclesia I am interested in SE 1.1 for uDig.
jgarnett Based on review I don't think updating the SLDParser would be that bad
Eclesia streaming can handle Se1.1 ?
jgarnett so when you get there please talk to us and perhaps we can collaborate.
aaime of course not
aaime or can it?
jgarnett the SLDParser is dom based; the GTXML (ie streaming parser) only has binding for SLD 1.0.
Eclesia I dont now, perhaps just like me, there is a patch waiting somewhere ^^
jgarnett I think everyone has their cards on the table; SE 1.1 is new work.
aaime Eclesia, did you update SLDStyleFactory to handle the extra features se 1.1 has?
jgarnett and we either need enthusiasm (or a customer) to get it done.
Eclesia aaime: no
aaime also, classification functions should be supported directly in the renderer
aaime so it's quite fair to say streaming renderer does not support se 1.1
aaime and won't unless somee udig folk updates it in that direction
aaime or GeoServer gets some sponsoring to work on SLD 1.1/SE 1.1
jgarnett well I will start slow by making use of the classification functions (which can be represented in SLD 1.0)
jgarnett still it is good to see this stuff moving; perhaps we can go shopping for a sponsor on this topic.
jgarnett shall we move on ... with the agenda and meeting?
jgarnett 1) what is up
aaime is fixing geoserver bugs for the 1.7.0-... rc1/beta2 (still haven't decided) release
Eclesia JSorel : working on GeoAPI SLD
jgarnett jgarnett - despairing over epsg-hsql and wondering how geoserver manages to render anything (perhaps someone can help me after the meeting?)
aaime is also mail drunk after reading 1100 mails in roughly one day
aaime jgarnett, GeoServer gave up using Hints because they don't work, we opened a jira issue and got back using System.setProperty
aaime ugly, but so far the only working solution
jgarnett thanks for the insight aaime; I am going to go freak out and break a lot of referencing in the process is my guess
jgarnett (sigh)
simboss simboss - jpeg2000, jpip and python
tar1 tara - lurking
aaime http://jira.codehaus.org/browse/GEOT-1704
aaime (for jgarnett information)
aaime jdeolive, we're in the "what's up" phase of the gt2 meeting
aaime want to join?
dwins having fun with wicket and fixing a gs bug or two
jgarnett moving on ...
jgarnett 2) 2.5.x branch
desruisseaux Andrea, could you remind me the JIRA issue please?
jgarnett dwins without gabriel here this one is mostly you ...
aaime desriusseaux, the jira issue it the one I pasted above
dwins okay
gdavis_ I wanted to get unsupported gt-wps and gt-process into this branch. dwins, how do I sort that out?
aaime it contains a small "main" that can be used to reproduce the issue
dwins as far as I know everything is in place
desruisseaux Oups! Thanls Andrea
aaime np
dwins gdavis_: good question. i'm not sure of the geotools policy for changing the 'unsupported' status of a module
dwins jgarnett: care to enlighten us?
jgarnett gdavis knows this one; it amounts to a page of docs and 40% test coverage.
aaime jgarnett, that is to get the module to supported land
jgarnett desruisseaux can point you towards a report of coverage; not sure if it covers unsupported modules however?
aaime he wants to keep it in 2.5.x as unsuported no?
jgarnett good question - gdavis what is your intention?
gdavis_ desruisseaux, how do I get test coverage of my unsupported modules?
aaime afaik the branching process will just keep it around, unless someone removes it manually
gdavis_ well are unsupported modules going to be in the 2.5 branch?
dwins aaime++
jgarnett well I want us to remove a lot of the unsupported modules; at the very least anything without a review.apt file...
jgarnett but stronger than that ... anything geoserver is not going to use.
gdavis_ review.txt file you mean?
aaime nope, apt
aaime (almost plain text)
gdavis_ well we have the wps geoserver module as well, which we'd like to get in 1.7
jgarnett gdavis_ they changed it in order to generate a "maven site"; no idea what apt stands for - looks similar to a wiki format.
gdavis_ i havent updated GT in a few days, was that a recent change? All mine still seem to say review.txt
desruisseaux About coverage: I do not yet have a coverage report for unsupported module. We had difficulty getting clover to run on GT trunk. We tried cobertura instead in a repository containing simplified pom.xml, but it doesn't cover unsupported modules yet.
gdavis_ so how does an unsupported module get test coverage in order to become supported then?
aaime so jgarnett, this is your idea, to remove unsupporetd modules from 2.5.x... it's the first time I hear about that
jgarnett aaime I have talked about this from the definition of the unsupported module idea / we are only hosting stuff to help get new developers. The actual library is defined by what meets our QA and Doc requirements.
jgarnett Every other time we talk about this you mention unsupported/oracle and assume I am losing my mind.
jgarnett (ie nobody supports oracle; but we need it; so jody must not be serious about removing unsupported modules from the release train)
aaime gdavis_, go to your module and type "mvn cobertura:cobertura"
aaime jgarnett, more or less correct, and how do we get out of that impasse?
jgarnett I think we start by removing everything geoserver is not using.
aaime I mean, we're talking about library procedures here
jgarnett and move the stuff we are using into the library.
jgarnett (by meeting the doc and testing requirements)
gdavis_ ok, what does this do?
aaime jgarnett, but oracle has no maintainer, so it cannot get into the library
aaime gdavis_, it generates a report, look into target/site
jgarnett well andrea we may be at a cross roads of either a) asking a sponsor to support a maintainer for oracle (refractions has at least one interested - but it will take dropping oracle from geoserver to show this is a serious requirement)
jgarnett b) recognizing that once something is in the library the community takes responsibility for keeping it going
jgarnett (at which point 40% test coverage and a page of docs looks like too small a bar to jump over)
jgarnett oracle is in limbo right now - no questions about that.
aaime we're going into a direction where I cannot talk about the issue intellligently. It involves providing resource, and I'm not the one controlling them
aaime cholmes can say if TOPP is going to maintain Oracle or not, and if it's ok to drop it completely, I cannot
jgarnett does the idea of removing unsupported modules that are not used by geoserver seem like a good compromise?
aaime sort of... I mean, what about modules used by udig but not geoserver?
jgarnett ie it has no effect on your release; and it provides insentive for people to finish their module.
jgarnett same deal
jgarnett if udig is keeping something in the build (like say the graph module)
jgarnett we can make sure it is passing tests on the branch.
jgarnett but udig is not following you on the 2.5.x branch (we could not get our feature event work done in time and referencing did not meet our requirements)
jgarnett so the 2.5.x branch is mostly about you
CIA-35 gdavis * r31086 /trunk/modules/unsupported/wps/src/test/java/org/geotools/data/wps/ (OnlineWPSFactoryTest.java OnlineWPSManualRequestTest.java): Turning online tests on for covertura
CIA-35 gdavis * r31087 /trunk/modules/unsupported/wps/src/test/java/org/geotools/data/wps/ (OnlineWPSFactoryTest.java OnlineWPSManualRequestTest.java): Turning online tests back off.
aaime well ok, I'm not exactly happy about this, but I don't see alternate routes
jgarnett thinking
jgarnett andrea what is there not to be happy about? You don't need widgets-swing-pending do you?
jgarnett (this is just a question - I am not sure if I understand your concern)
aaime I'm not exactly happy that modules do appear and disappear from the library depending on which project uses the branch
gdavis_ these reports all show 0% when I know that can't be true....
jgarnett you are correct; I am not happy that modules that projects depend on are not meeting our very low QA bar; I figure that is irresponsible ...
jgarnett but the same token I don't want to advertise modules that we know are in flux (ie the definition of an unsupported module)
jgarnett unsupported is only there to bootstrap quick development; the library slurps up the good ideas (and hopefully grows our developer community in the process)
aaime it still seems me we should advertise this on the users community before pulling the plug
jgarnett Perhaps we should return to the details of making a release this week ... I am sorry the handling of unsupported was a surprise Andrea.
aaime it's quite rushed for a branch that we should do this week
jgarnett okay I can do that; ask them what they think.
aaime like for example Camp2Camp is using MIF, we just pissed them off enough with the licensing questions that they stopped mailing us
aaime (questions -> requirements)
jgarnett andrea I would settle for deploying to maven but not making it part of the download. See the language on this page for my intension with unsupported modules: http://docs.codehaus.org/display/GEOTDOC/16+Unsupported
aaime I would like to make a separate zip instead
jgarnett aaime++ that would work.
gdavis_ so, can process and wps still reach supported status for this release?
aaime so that peopole can still use them, but would understand they should get they act togheter and support themselves
aaime gdavis_, dunno, I tried cobertura on various modules and the coverage I get is not 0
aaime you can also try out with the cobertura eclipse plugin, you might have better luck
gdavis_ [INFO] [surefire:test]
gdavis_ [INFO] Tests are skipped.
gdavis_ it says this
aaime gdavis_, can we talk about this later?
gdavis_ I guess so
aaime it's problem solving, not something we should do during a meeting
aaime especially since it's supposed to end in 7 minutes
aaime jgarnett, anything else that is holding up the 2.5.x branch?
gdavis_ alright
aaime (I was actually quite surprised by the rush of last minute api change proposals and actions, feature collection, feature id...this kind of stuff should be hanlded at the beginning on a development cycle, not at the end)
simboss aaime: I have something to say about the 2.5.x branch
jgarnett aaime I was surprised as well; a lot of this work was started and nto completed
jgarnett aaime I also did not do the deprecation cycle this release.
aaime feature collection and feature id are weren't started at all
jgarnett you know when we go through 2.4.x and remove deprecated methods.
jgarnett feature collection was started as part of the feature model change over; but it lost momentum.
jgarnett In trying to use this in a training environment I figured I could not stand to let it out the door with so many half finished ideas; I hope you don't mind.
aaime I've only seen proposal drafts for Justin, no coding was started
aaime I did not notice any significant change before your work of last week
aaime I do mind when these things are done last minute, since we're touching some fundamental class
aaime that would be better modified when a new trunk starts being worked on
jgarnett I kind of thought justin would get to it before release.
aaime how could you think that, we did not even vote the proposal??
jgarnett And I was hoping to do the featureid work with you but did not figure it out in time before you left on vacation.
aaime that one fell on me like a surprise as well, it's another major change that should not occur right before branching
jgarnett I could think that because we focused on the change over to simple feature during September; and we did the bare minimum to make the change. Other things that we knew were wrong (like featurecollection being a feature) were not attempted at that time.
jgarnett I have been talking to gabriel about the FeatureId handling as part of the feature event work for months; but perhaps because it was feature events it was not visible as a concern?
aaime jgarnett, I'm not questioning the goodness of the changes
aaime I'm questioning the timing
jgarnett But I agree too much was done last minuet; and too much was done by me at the last minuet.
jgarnett I don't know if I should of been more strict months ago or what.
jgarnett however I do like the result.
CIA-35 gdavis * r31088 /trunk/modules/unsupported/wps/src/main/java/org/geotools/data/ (4 files in 4 dirs): Adding package infos for these packages.
aaime ok...
aaime so, let's recap a bit
aaime how are we setup for the 2.5.x branching?
aaime what still needs to be done?
jgarnett we await a decision from dwins / gabriel
jgarnett then we tag
jgarnett we have to rollback referencing
jgarnett and I want to review the user guide and bundle it up for download.
jgarnett (we also need to tag a geoapi milestone but we can limit that to a maven deploy)
aaime ha great, we tested geoserver for months with the current referencing and now we roll back... this 1.7.x relelase will be a damned one I guess...
jgarnett well we can ask martin
jgarnett but he did not get to the work right now?
jgarnett I think all that happens aaime is we remove my classes (that are still not hooked up)
aaime ah, not hooked up you say... so we haven't been using them at all
simboss guys I have two minor fixes for imagemosaic, I have made tests run for both geoserver and geotools successfully; question is can I commit?
jgarnett correct
aaime simboss, sure you can
jgarnett the work I did for so long has not been hooked up yet because I cannot pass one test case about looking up an existing identifier.
jgarnett so rolling back (or deleting these classes) should not be too stressful.
aaime I guess it will just be deleting the classes, since desriusseaux has been making changes/fixes to referencing on trunk afaik
jgarnett agreed
jgarnett I think martin said he could help on that side; he feels bad about not getting time to work on referencing.
jgarnett and leaving me hanging.
CIA-35 simboss * r31089 /trunk/modules/plugin/ (4 files in 2 dirs):
CIA-35 - releaseing resource for ImageMoisacReader
CIA-35 - using some good old suppressWarnings tag
aaime ok, and we need to change the release scripts to create a separate zip for the unsupported modules... something I never managed to figure out how to do
Eclesia can wait 2 more weeks if it helps
jgarnett Eclesia I don't think it will help; only thing we should do that we are not is removing deprecated methods.
aaime jgarnett, that is going to be a big one, and not possible at all in various cases
aaime think filters
aaime you simply cannot remove the deprecated filters
jgarnett I know
aaime there is still code using them
jgarnett (it is one of the things listed on technical debt on the 2.5.x page)
jgarnett but I suspect there is some work we could do; but it was not as important as making our Java 5 transition and getting our Feature / FeatureCollection story straight.
aaime ok, who does what and when?
jgarnett dwins / gabriel was going to make the branch today
jgarnett I was going to review the user guide pages
jgarnett I think martin was going to rollback the referencing module?
jgarnett I was going to help gabriel by running deploy from here.
aaime I haven't seen groldan around today
dwins and I don't have write access to the repository
jgarnett dwins was mostly organizing; gabriel just had the ability to do the work.
jgarnett I was hoping for code freeze / branch / unfreeze and then starting up the release process from the branch; releasing when CITE tests pass?
aaime yep
aaime thought if the FeatureId change is still in the air, we cannot release gt2 2.5-rc
jgarnett can we wrap up the meeting; and leave the IRC log open for collaboration on the 2.5.x release ...
aaime is at the end of his working day almost right now
jgarnett if gdavis and simboss are happy we could branch 2.5.x fairly quickly. And worry about making the release from the branch tomorrow ...
simboss I just committed
simboss so yeah
simboss I just tested
aaime so we give up with FeatureId related changes?
simboss that the fix
simboss for the coverage bandselect problem
simboss worked
aaime (that's an API and GeoAPI change)
simboss and it worked indeed
dwins simboss: thanks a lot
aaime simboss, thanks
jgarnett FeatureID changes were done on the weekend Andrea; they went well.
jgarnett or actually late last week.
aaime Uh?
jgarnett I talked with gabriel after you left; and Justin.
aaime I did not even notice
aaime any page documenting how things are working vs pending ids?
jgarnett the FeatureEvent page
jgarnett but now you have the option of getting the FeatureIds from the features
jgarnett rather than only from events.
simboss dwins, aaime: If I were you I would double check anyway
aaime what about featureStore.add(..)?
jgarnett dwins made the change on the geoserver side.
jgarnett now returns a List<FeatureId>
jgarnett so you can build up your list ...
aaime and they do change after commit occurs?
jgarnett yes.
aaime I see
*--| tar1 has left #geotools
aaime any way to know the feature id is "transient"?
aaime (pending, whatever)
jgarnett but that is only as good as the datastore implementation as per usual.
jgarnett no there is not
aaime I see
aaime could have been useful
jgarnett you could add that to the FeatureIdImpl if you want; I would like to see some experimentation on that side.
jgarnett note versioned postgis was the only thing
jgarnett to want to set the feature id more than once.
jgarnett I wanted to ask you why that was ...
aaime I don't know
aaime I coded that datastore more than one year ago
aaime I simply do not remember why
jgarnett I suspect it is so you can include "feature id" and "version" as part of the Identifier?
jgarnett but dwins only found tests that failed in #geoserver so I could not verify.
aaime it probably has something to do with the intricacies of having a feature id mapping between an inner and an external view
aaime jgarnett, externally the id stays the same
dwins it looks like you generate a temporary id immediately after getting the feature from the writer
aaime version is not part of the feature id the users sees, but internally yes, it's part of the id
dwins and then I guess you do something with it to generate a final id for versioning
aaime I see.. don't know, I would need to check the code
jgarnett okay so perhaps a change of api class can do it .. generate the "fid"; use it to construct the FeatureId; and then you can still set it once when you have your final value...
jgarnett (I just had a check to freak out if a FeatureId was being changed multiple times; and we had to turn it off for your module)
aaime so now it's not part of the build?
jgarnett yes
aaime you should have sent me a mail saying so?
jgarnett I did?
aaime I did not see it
jgarnett reading
aaime (mind, 1100 mails dropped in my mail client yesterday)
jgarnett (gasp I may of been evil like dwins and just had a conversation on IRC and not sense an email... the horror)
aaime I've only seen this, but could not make any sense of it: http://jira.codehaus.org/browse/GEOT-1934
CIA-35 simboss * r31090 /trunk/modules/unsupported/coveragetools/src/main/java/org/geotools/utils/imagepyramid/PyramidLayerBuilder.java: -minor fix as directed by Thomas Lutz
aaime also the jira says it's fixed, if so, the module should be brought back into the build
jgarnett that is true; it was done after the change.
jgarnett it never left the build; it was always passing its geotools test cases.
jgarnett you are correct andrea; I sent email and closed bugs on the geoapi list.
jgarnett I will correct that now.
aaime k
aaime dwins, jgarnett, I have to go in a few minutes and I still have some pending commits
aaime can you send me a mail telling me if I should a) branch b) run the cite tests?
dwins sure

View Online

Groovy Eclipse plugin updated to Groovy 1.5.6 and Eclipse 3.4

Fri, 25 Jul 2008 04:44:19 -0700

News Item added by glaforge

The Groovy Eclipse team released an updated version of the Groovy Eclipse plugin.

In this new release, the main points of interest:

the plugin has been updated to use Groovy 1.5.6
and it is also working with the recent Eclipse 3.4

You can find the Groovy Eclipse plugin as a Zip file here and you can point your Eclipse update center at the following location:
http://dist.groovy.codehaus.org/distributions/update/

Upcoming version of the plugin will feature the first refactorings (extract method). You can discover more on the topic thanks to the students working on
this project as part of their Bachelor thesis at University of applied sciences, in Rapperswil, Switzerland.

Also, don't forget to read Groovy plugin developer James Ervin's words on the roadmap of the plugin.

Congratulations to everybody involved, and especially to James who pushed hard for this release!

View Online

Apache ActiveMQ -- Integrating Apache ActiveMQ with JBoss

Mon, 21 Jul 2008 14:49:11 -0700

IRC Logs July 21

Mon, 21 Jul 2008 11:43:53 -0700

News Item added by jgarnett

Agenda:
0) chat
1) what is up
2) follow up OSGeo
3) gridrange/gridenvelope

jgarnett I just remembered the new meeting time
jgarnett (hard to both deal with monday morning questions; and attend a meeting .. sorry for being late)
desruisseaux No worry, nothing started
jgarnett hrm
jgarnett okay sending email to the list now
desruisseaux I don't have any agenda topic for today...
jgarnett I noticed unsupported/go was removed?
jgarnett Is this a formal cancellation of the go-1 project?
jgarnett well we have some follow up to do from last week
desruisseaux No it is not a cancelation
graduation"
jgarnett Martin should I be doing something on this end? I feel like communication on has been poor recently?
desruisseaux I'm don't know if the issue is communication
desruisseaux This is true that we are not communicating as much as we could
desruisseaux And some of our comunication may be poor
desruisseaux When I have a strong opinion on a topic, I look like close minded
desruisseaux But while the community see the weakness as a communication issue from geomatys, on our side we are worried by the entropy of managing many project around the geotools code base.
jgarnett thinking
jgarnett the entropy?
simboss I would add a question about gridrange/gridenvelope to the topic list
jgarnett martin my thought is that we have these procedures and the PMC to account for the entropy.
jgarnett ie If a project wants to take part it can provide volunteers to geotools to handle the communication burden.
jgarnett martin I don't mind you appearing closed minded; indeed I value a good discussion with you - it results in high quality software (and we both learn from the discussion)
jgarnett I can think of a dozen examples
jgarnett My only concern is when people arrive "too late" to discuss stuff; ie when they actually have no time - and I think we try to be understanding about that.
jgarnett Is that what you meant by entropy?
desruisseaux I was thinking something a bit different
desruisseaux We started to cleanup metadata
desruisseaux fixing javadoc, splitting utilities methods in their own "utility" module
desruisseaux No design changes at this time
desruisseaux Then I have it Justin's converter classes in org.geotools.util
desruisseaux (typo: I have hit)
jgarnett ah
desruisseaux Those classes duplicates org.geotools.resources.ClassChanger, but Justin framework is more elaborated.
jgarnett I have not heard of class changer; I considered it a duplicate of the apache bean utils.
desruisseaux Nevertheless we have a duplication, so I wanted to retrofit the old ClassChanger functionality in Justin converters
jgarnett sounds great; I appologize if we knew about ClassChanger at the time we would of used it.
desruisseaux This kind of duplication is kind of the entropy I'm talking about
desruisseaux No it is not an issue - I do not expect peoples to known every bit that everyone write
jgarnett true
jgarnett thinking
jgarnett This was just before the change proposal process; do you think a change proposal (to introduce Converters) would of been enough
desruisseaux So it was part of entropy. Other part is that Justin converter were wrote in main module instead than metadata, but both defines classes in the same package (org.geotools.util)
jgarnett visibility
jgarnett that we could avoid the duplication?
desruisseaux No I don't think that a proposal would have helped much (more on it later)
jgarnett (thinking of this as a) technical thing to fix b) a process thing we could think about)
jgarnett okay keep going; I will shut up
desruisseaux So entropy = duplication, service duplicated in many module (in this case "utility" splitted between metadata and main; and furthermore "metadata" is probably a bad place for "utility")
desruisseaux Also implementation thats look like "brute force" (looping over every converter until one is found that doesn't returns null and doesn't throw exception)
desruisseaux I understand that a lot of things in GeoTools have been developped under time constraint.
desruisseaux This is where I think that the proposal process doesn't help a lot, because we often don't have the time to look at them carefully.
desruisseaux We end up trusting the guy who proposed it, and only later we realize that we could have fighted more against entropy.
jgarnett so far we average one proposal a month; and have two weeks to respond.
jgarnett I am trying to be "brutal" in getting people to document what they are doing in the proposal; so it takes less time for everyone to review.
jgarnett but I agree duplication is bad; proposal process may not catch everything.
jgarnett stronger measures (like code reviews) would take even more time.
jgarnett suggestions?
jgarnett Is having a two week chance to review a proposal "good enough" for you martin?
desruisseaux It is not only duplication; when I look at a code written by someone else, I often see stuff that I doesn't make me happy ("brute force" algorithms, eating exception in try .. catch ... log, bad usage of J2SE API...). It may be because I'm too maniac, but it make me worry
jgarnett martin: I agree - when out of time I tend to work on trust; I have stopped doing that in the last year and am "up front" when I am out of time and vote +0
jgarnett see this is why I like working with you; your worry is valuable to everyone
jgarnett is there any way we can address the kind of issues you mention above?
desruisseaux But this is where I came to an idea which I'm afraid would not be acceptable to the community
jgarnett I personally go in and fix stuff; and send email to the module maintainer as I go.
jgarnett but it is to little to be effective.
jgarnett I would rather set "find bugz" and use it to inpersonally catch mistakes like these. It works well for udig.
desruisseaux I got the feeling that GeoTools needs a "benevolant dictactor" in the way Linus is for Linux. I know that it is a radical point of view, but I have the feeling that the survival of the project as the "project of my dream" would need that.
desruisseaux But peoples can not be blocked because I dictator is too slow, or disagree, etc.
desruisseaux So this is clearly unacceptable on a centralized SVN.
desruisseaux But on a distributed system...?
dwins waves
jgarnett Hrm; I don't mind taking the roll.
jgarnett I am trying to work hard on geotools because it needs it.
desruisseaux If peoples are unhappy about a dictator on a given system, then can switch to an other distributed system managed in a different way.
jgarnett but I was going to take stock of what was needed for GeoTools 3; a dictator may be a good idea.
jgarnett not sure that works as a dictator; that is a democracy
jgarnett and personally I don't always trust the will of the masses on code decisions.
desruisseaux Thats my current though
jgarnett cool
jgarnett let us put it in the list for GeoTools 3
jgarnett now with OSGeo graduation out of the way
acuster dcvs solves the same problem in a more elegant way
jgarnett I promissed I would start taking action on those ideas.
acuster dvcs
jgarnett how so acuster
acuster everyone is dictoator over their repo
acuster they can decide what goes in
acuster the cost is everyone has to decide what goes it
acuster goes in
jgarnett (BTW acuster I had some usless naming questions for you - which would be very valuable for me; and prevent your annoyance in the future)
acuster which is why there are so many branches of linux
jgarnett I am not sure that this is an efficient approach; but yeah I get the idea.
acuster jgarnett, yes, on my todo list, you need answers today?
desruisseaux I'm done. I suggest to move on next IRC topic.
jgarnett acuster - if possible. I just want some words (we can chat on #udig)
jgarnett okay ... thanks for the chat guys
jgarnett 1) what is up
jgarnett jgarnett - trying to make sure the feature collection change did not break geoserver - dwins seems to have it all in hand. Working on bundling up a JRE+ImageIO-ext for udig development community. Juggling work responsibilities with open source commitments.
acuster acuster---iso19107 is messier than they would have you believe: I now have a working understanding of how geographic curves are expected to behave
acuster (well, that's a lie but a first approximation)
Eclesia hasck in puzzle-gis, and playing with JaxB
desruisseaux Martin: code review
simboss simone: ebrim
jgarnett acuster there was a good question on the JTS list as someone runs into some of the same questions (something about splitting a curve into a multi curve)
jgarnett oh; lucky simboss
jgarnett anyone else?
acuster yeah, that's in my inbox as a todo
jgarnett 2) follow up to OSGeo graduation
jgarnett It looks like we were successful; no official announcement yet.
jgarnett we have a couple blocker issues about license management to close up before the 2.5.x release.
jgarnett Firstly thanks so much for all the crazy hard work on this stuff.
jgarnett It has been long, brutal, and so on.
desruisseaux Thanks Jody, you worked hard on that too
jgarnett Hopefully over the next year we can benefit from this relationship on the "product" side of things; it sounds like we make do a few infrastructure things first (maven repository? etc...)
desruisseaux (the other one being Adrian)
jgarnett well thanks for keeping me sane. I know without acuster I would of slowed down on this stuff.
jgarnett Last week I was nominated as osgeo representative; as such I may get a few official questions
jgarnett I will punt each one of these to the geotools admin list; unless they are really really easy.
jgarnett And if you guys have questions about OSGeo; or if we have stuff we want to get done
jgarnett I can try and hunt down the right people.
jgarnett Does anyone have ideas for this week? Or can we relax for a bit and take this to email..
desruisseaux I have no additional item
jgarnett 3) gridrange/ gridenvelope
jgarnett simboss the floor is yours.
simboss thought/question for martin
simboss about the difference
simboss between what geotools does
simboss and what JAI does
simboss when cropping images
desruisseaux I saw email about cropping, but didn't investigated them.
simboss I have been sparing some time today to think about it
simboss even because I notice a while ago
simboss that you pushed the use of mosaic inside
simboss the resampler
simboss but that's another story....
simboss anyway
desruisseaux It is not a real mosaic
desruisseaux It doesn't take more than one image
simboss mosaic operator
desruisseaux Yes I know, but mosaic operator with a single image
desruisseaux (so it is not a real mosaic)
simboss I know
desruisseaux The mosaic operator handle the border outside the image in a special way
simboss if you ever looked at the crop operation
simboss I used it to crop rotated raster
desruisseaux This is the border handling that was interresting me, not the mosaic per se
simboss that is why I mention that
desruisseaux (sorry, lets continue on crop)
simboss but anyway if I crop an image
simboss with the JAI crop
simboss I always get the smallest rectangle that contains the requested area
simboss the behvaiour in geotools is slightly ifferent
simboss and can cause illegalargument exception
simboss if you try to cut a very small portion out of a coverage
simboss I think I managed to reproduce the same thing for resample as well
hudson geoserver-1.7.x build fixed (http://gridlock.openplans.org:8080/hudson/job/geoserver-1.7.x/54/)
simboss I think I could fix that for the Crop operation
simboss but I would like to have consistency with resample
simboss because probably sooner or later we could merge the two things into one, probably with a simplified interface for crop, reproject, resample, etc...
desruisseaux yes
simboss now the question is
simboss have you ever run into such a case?
simboss final annotation
simboss the sources of problems are 2
simboss generalgrid range roundings and usage of imagelayout
simboss done
desruisseaux I don't remember having seen that, but if you have a test case reproducing the issue that would be very appreciated.
simboss well, the idea is simple
simboss I get an envelope
simboss which is smaller than a unit in world coordinate
simboss I go back to raster coordinate
simboss w and h
simboss will be between 0 and 1
simboss exlusive
simboss if I ever use imagelayou
simboss or the gridrange constructor
simboss you'll get w and/or h as 0
simboss you might
simboss I think in this cases it would be better to have a behavior similar to the JAI behaviour
desruisseaux If the fix is just ensuring that width and height are always equals and greater than 1, I'm in favor of that.
jgarnett (back: was grabbed for a conversation)
desruisseaux Or do you think something more elaborated is needed?
simboss I still have to think a little bit about it, I'll try to capture thoughts in an email
simboss on a side
simboss I think we need to ensure
simboss that when we crop a coverage
simboss we always return something
simboss even if that something is bigger than the requested area
simboss e.g. 1X1 raster
simboss on the other side
simboss the generalgridrange constructor
simboss states the opposite
simboss if you recall it
simboss (hello? )
desruisseaux yes
desruisseaux (I need to look back what GeneralGridRange constructor said)
simboss so we might need to change that as well
simboss k
simboss anyway, i'll wrap that in an email
simboss since it might require some thinking
simboss I am done
desruisseaux Nothing more on my side...
jgarnett okay thanks guys
jgarnett I can post the logs.
simboss right on time
simboss :-9

View Online