Hi folks (esp. Simone and colleagues) Today's source taglet updating on trunk revealed quite a few class files where the taglet line had been broken across multiple source lines. When that happens it doesn't get picked up properly during javadoc creation. Most of the occurrences were in the coverage module so I wonder if GeoSolutions folks are using particular settings with Eclipse that result in the breaks ? Or perhaps there are deeper source paths in the coverage module than in other modules (taglet line length is governed by the source file's path length)
I'm hoping that it's fairly easy to change the settings in Eclipse because I think trying to make the taglet code deal with broken lines reliably would be painful :( Michael ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
