From: Jody G. <jga...@re...> - 2004-03-26 18:36:48
|
Just setting up a new box and noticed that I had fallen behind the version train. New versions of Eclipse and Maven were available. - maven-1.0-rc2 - eclipse-2.1.3 The eclipse update is nice, it works with SF cvs again and is much faster then the Eclipse-3.0 M7. I am trying out the new version of Maven as we speak - it at least did not require a double start (once to get the repository going, and once to actually build). Cheers, Jody |
From: Jody G. <jga...@re...> - 2004-03-26 18:41:06
|
Just finished trying a build with maven 1.0 rc2 - most everything seems to work. Two modules did not install: arcgrid - ArcGridHandlerTest and ArcGridRenderTest both fail gui - StyledMapPane and StyledMapPane2 no longer knows about StyledRenderer But I am pleased - I figure any time pickel compiles on a windows box something must be going right. |
From: Andrea A. <and...@al...> - 2004-03-26 20:24:01
|
On Friday 26 March 2004 19:40, Jody Garnett wrote: > Just finished trying a build with maven 1.0 rc2 - most everything seems > to work. > > Two modules did not install: > arcgrid - ArcGridHandlerTest and ArcGridRenderTest both fail > gui - StyledMapPane and StyledMapPane2 no longer knows about StyledRenderer > My fault. They should be ok now (at least they are on my disk, can you confirm they build properly now?) Best regards Andrea Aime |
From: Jody G. <jga...@re...> - 2004-03-26 21:36:54
|
Andrea Aime wrote: >>gui - StyledMapPane and StyledMapPane2 no longer knows about StyledRenderer >> >> > >My fault. They should be ok now (at least they are on my disk, can you confirm >they build properly now?) > > The build now works, although geotools-demos/mapviewer/MapLegendViewer is broken. It would be nice to build the geotools-demos directories as part of our maven build process. Cheers, Jody |
From: William S. <wst...@wh...> - 2004-03-26 22:20:30
|
FYI, The legend module has a few files (e.g., FullStyleEditor.java) where the paths to some .gif files (that are used as icons in a gui) are hardwired for a local setup. The .gif files should probably be added to org.geotools.resources and the corresponding icon-loading code revised to access them via the getClass.getResource("/org/geotools/resources/xxx.gif") approach. BTW, Geotools2 came in handy lately when I had to deal with some shapefiles ArcGIS had mangled in some union/intersection-type operations! Best regards, Buck Stockhausen |
From: William S. <wst...@wh...> - 2004-03-30 19:30:58
|
All, Apologies to the Legend developers for my previous post! The "hardwired" gif files I referred to are located in the jlfgr-1_0.jar jar file (as you probably already knew). I hadn't mounted this jar file in NetBeans, so I kept getting null reference exceptions thrown when I tried double-clicking a legend in, say, the MapLegendViewer demo. Cheers, Buck William Stockhausen wrote: > FYI, > > The legend module has a few files (e.g., FullStyleEditor.java) where > the paths to some .gif files (that are used as icons in a gui) are > hardwired for a local setup. The .gif files should probably be added > to org.geotools.resources and the corresponding icon-loading code > revised to access them via the > getClass.getResource("/org/geotools/resources/xxx.gif") approach. > BTW, Geotools2 came in handy lately when I had to deal with some > shapefiles ArcGIS had mangled in some union/intersection-type operations! > > Best regards, > > Buck Stockhausen > |
From: Andrea A. <and...@al...> - 2004-03-27 08:22:01
|
On Friday 26 March 2004 22:36, Jody Garnett wrote: > Andrea Aime wrote: > >>gui - StyledMapPane and StyledMapPane2 no longer knows about > >> StyledRenderer > > > >My fault. They should be ok now (at least they are on my disk, can you > > confirm they build properly now?) > > The build now works, although geotools-demos/mapviewer/MapLegendViewer > is broken. ?? Here it compiles fine... are you sure you updated also the demo directories? > It would be nice to build the geotools-demos directories as part of our > maven build process. Yep Andrea |
From: Ian S. <Ian...@ar...> - 2004-03-26 19:20:42
|
On Friday 26 March 2004 11:40 am, Jody Garnett wrote: > Just finished trying a build with maven 1.0 rc2 - most everything seems > to work. Good news. > Two modules did not install: > arcgrid - ArcGridHandlerTest and ArcGridRenderTest both fail If the test fails, and you cannot determine a good reason for it - like ClassNotFound, etc. please post the details so that something can be done about it. It just built fine on my setup, so there is obviously something amiss... > But I am pleased - I figure any time pickel compiles on a windows box > something must be going right. Pickle nor many of the other platform problems (shapefile) are not due to maven, but differences in IO management on various platforms. What is going right is that thanks to feedback, the problems have been worked out. Regards, Ian |
From: Jody G. <jga...@re...> - 2004-03-26 20:26:51
|
Ian Schneider wrote: >If the test fails, and you cannot determine a good reason for it - like >ClassNotFound, etc. please post the details so that something can be done >about it. It just built fine on my setup, so there is obviously something >amiss... > > Here is the results of the tests that failed ... Both errors seem to be caused by the same problem encountered when parsing the Header (java.io.IOException: Expected new line, not null). I wonder if this is tripping up due to different nl characters on PC? Jody > C:\java\workspace\geotools2\geotools-src\arcgrid\target\test-reports>more > *.txt > Testsuite: org.geotools.data.arcgrid.test.ArcGridHeaderTest > Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.063 sec > > Testcase: > testHeaderSource(org.geotools.data.arcgrid.test.ArcGridHeaderTest): > Caused an ERROR > Expected new line, not null > java.io.IOException: Expected new line, not null > at > org.geotools.data.arcgrid.ArcGridRaster.parseHeader(ArcGridRaster.java:222) > at > org.geotools.data.arcgrid.ArcGridRaster.parseHeader(ArcGridRaster.java:180) > at > org.geotools.data.arcgrid.test.ArcGridHeaderTest.testHeaderSource(ArcGridHeaderTest.java:31) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > > > Testsuite: org.geotools.data.arcgrid.test.ArcGridRenderTest > Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.422 sec > > ------------- Standard Output --------------- > get a datasource org.geotools.data.arcgrid.ArcGridDataSource@116ab4e > ------------- ---------------- --------------- > Testcase: > testRenderImage(org.geotools.data.arcgrid.test.ArcGridRenderTest): > Caused an ERROR > IO error > org.geotools.data.DataSourceException: IO error > at > org.geotools.data.arcgrid.ArcGridDataSource.getFeatures(ArcGridDataSource.java:300) > at > org.geotools.data.AbstractDataSource.getFeatures(AbstractDataSource.java:91) > at > org.geotools.data.arcgrid.ArcGridDataSource.getFeatures(ArcGridDataSource.java:240) > at > org.geotools.data.arcgrid.test.ArcGridRenderTest.renderImage(ArcGridRenderTest.java:112) > at > org.geotools.data.arcgrid.test.ArcGridRenderTest.testRenderImage(ArcGridRenderTest.java:106) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > Caused by: java.io.IOException: Expected new line, not null > at > org.geotools.data.arcgrid.ArcGridRaster.parseHeader(ArcGridRaster.java:222) > at > org.geotools.data.arcgrid.ArcGridRaster.readRaster(ArcGridRaster.java:294) > at > org.geotools.data.arcgrid.ArcGridDataSource.createCoverage(ArcGridDataSource.java:164) > at > org.geotools.data.arcgrid.ArcGridDataSource.getGridCoverage(ArcGridDataSource.java:156) > at > org.geotools.data.arcgrid.ArcGridDataSource.getFeatures(ArcGridDataSource.java:297) > ... 18 more > > > Testsuite: org.geotools.data.arcgrid.test.ServiceTest > Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.281 sec |
From: Andrea A. <and...@al...> - 2004-03-26 20:30:32
|
On Friday 26 March 2004 21:25, Jody Garnett wrote: > Ian Schneider wrote: > >If the test fails, and you cannot determine a good reason for it - like > >ClassNotFound, etc. please post the details so that something can be done > >about it. It just built fine on my setup, so there is obviously something > >amiss... > > Here is the results of the tests that failed ... > > Both errors seem to be caused by the same problem encountered when > parsing the Header (java.io.IOException: Expected new line, not null). > > I wonder if this is tripping up due to different nl characters on PC? > Hm... in fact here on Linux it builds fine... Best regards Andrea Aime |
From: James M. <jma...@ps...> - 2004-03-26 20:58:29
|
At 09:34 PM 3/26/2004 +0100, you wrote: >On Friday 26 March 2004 21:25, Jody Garnett wrote: > > Ian Schneider wrote: > > >If the test fails, and you cannot determine a good reason for it - like > > >ClassNotFound, etc. please post the details so that something can be done > > >about it. It just built fine on my setup, so there is obviously something > > >amiss... > > > > Here is the results of the tests that failed ... > > > > Both errors seem to be caused by the same problem encountered when > > parsing the Header (java.io.IOException: Expected new line, not null). > > > > I wonder if this is tripping up due to different nl characters on PC? > > > >Hm... in fact here on Linux it builds fine... I;m getting that here on a windows box too. Important to note that the exact error is that the string tokenizer is getting a number instead of a String (rather than a null as the error suggests) i.e. the print line is something like: "exptected new line not " +st.sval); st.sval is indeed null, but st.nval is not! James |