Hi SS,
I think bug fixing should be done in the trunk so that you get feedback as
soon as possible.
Can you be more specific about utility code consolidation? Branching the
code isn't really going to help us evaluate your changes. If they aren't
too controversial, I'd rather they be done in the trunk too. I'm certainly
responsible for some duplicate utility code inherited from SkyJUMP.
What kind of unit tests - Junit? Which version? Sounds reasonable in
general, although it may be a case of "closing the stable door after the
horse has run away." "Tilting at windmills" and all that... :-)
You may know that there are some Junit tests from the original JUMP
already for:
AbstractPlugInTestCase.java
AffineTransformTestCase.java
AllTestCases.java
AngleTestCase.java
AttributeMappingTestCase.java
AttributeTypeTestCase.java
CollectionUtilTestCase.java
CoordinateArraysTestCase.java
EnvelopeIntersectorTestCase.java
FeatureCollectionMetaDataTestCase.java
FeatureTestCase.java
FlexibleDateParserTestCase.java
GMLWriterTestCase.java
GUIUtilTestCase.java
InteriorPointFinderTestCase.java
OverlayEngineTestCase.java
PanelTestCase.java
RangeTestCase.java
ShapeCollectionPathIteratorTestCase.java
SimpleGMLReaderTestCase.java
SplitLineStringToolTestCase.java
StringUtilTestCase.java
TestUtil.java
TriangulatorTestCase.java
ValidatorTestCase.java
VerticesInFencePlugInTestCase.java
regards,
Larry
2010/4/8 Michaël Michaud <michael.mich...@free.fr>
> Hi Sunburned Surveyor
>
> Fixing these bugs would be nice and starting unit tests would be nice too.
>
> I forgot bug (1) reported by Nacho as it has never been reported in the
> bug tracker.
> I can have a look this week end as I think I wrote the guilty plugin,
> and Nacho kindly supplied the data to reproduce the problem.
>
> There is another bug for which I spent some time without success :
> 2792806 Error while deleting heterogeneous item
> If you or someone else wants to have a look, it needs a good
> understanding of the item selection process (which is quite complex in
> OpenJUMP due to partial feature slection capability)
>
> Michaël
>
>
>
> Sunburned Surveyor a écrit :
> > I'd like to request permission to create a branch in the JPP SVN where
> > I can start work on two tasks:
> >
> > - A series of bug fixes and minor improvements. These fixes include
> > (1) reporting the FID in the Union By Attribute plug-in to address a
> > problem reported some time ago by Nacho; (2) making the cut polygon
> > tool obey the "editable" status of the layer that contains the polygon
> > being cut; and (3) consolidation of some utility code.
> >
> > - Creation of a set of units tests to start testing the OpenJUMP core.
> > I'll probably start with classes in the
> > com.vividsolutions.jump.workbench.model packages, since those are the
> > simplest.
> >
> > I would like to move these improvements to the trunk of the SVN, one
> > at a time, after getting approval from the other programmers on this
> > mailing list. I won't be proposing any major changes to the core, and
> > will make sure I get buy off from everyone before commiting to the
> > trunk.
> >
> > With Stefan's permission I'd like to start packaging monthly builds of
> > this branch in between his major OpenJUMP releases.
> >
> > Any comments or strong objections?
> >
> > The Sunburned Surveyor
> >
> >
> ------------------------------------------------------------------------------
> > Download Intel® Parallel Studio Eval
> > Try the new software tools for yourself. Speed compiling, find bugs
> > proactively, and fine-tune applications for parallel performance.
> > See why Intel Parallel Studio got high marks during beta.
> > http://p.sf.net/sfu/intel-sw-dev
> > _______________________________________________
> > Jump-pilot-devel mailing list
> > Jump-pilot-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
> >
> >
> >
>
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
