Hey All,

After hours of painless, mind numbing, boring cut-and-pasting, I have
committed the new poms to trunk and the 2.3.x branch.


Essentials:
  * valid xml
  * UTF-8 encoding
  * No tabs
  * Consistent unix eol style
  * Standard layout (for better or worse)
                Header
                Profiles
                Module Description
                Developers and Contributors
                Dependency Management             
                Build Configuration
                Modules included in the build
  * 80 col maximum (except for URLs, martin's inline comments, ...) 
                {no reason to be bigger}



Still to do:
  * Licenses
          All files are now simply LGPL. You (Jody?) have to add any
        other relevant licenses into the poms. Then we can see if maven
        can actually use the info.
        
  * Licenses
          Do we want to move these into the jar poms only? That is, the
        pom poms don't actually have any code so the license seems
        redundant.
        
  * Licenses
          What does <distribution>repo</distribution> do?

  * STOP USING TABS
          Maybe they are left over from earlier editing efforts and
        persist due to reuse. Nonetheless please check you aren't
        generating tabs.

  * Version numbering
          I only found the <version> tag used in two projects. For now,
        I have a commented out placement. Does anyone know how/why this
        is used?

  * Move developers/contributors out of pom POM files and into jar POMs
          This should be done, with top level holding only the pmc.

  * Descriptions
          Add these, you lazy bums!

  * coverage_development indentation
          I got discouraged by these. Simone, there are sections that
        need to be re-indented if and when you have the strength.

  * Try converting <!-- comments to <comment comments
          Apparently maven may handle such things and perhaps those
        comments would not disappear during releasing on a branch.

  * Regenerate all the accents which are now '?' (2.3.x only)
          Someone with a keyboard that can make these should do this. I
        cannot currently generate any accents, much to my embarrassment
        and chagrin.

  * Dependency Management blurb (e.g. top level pom.xml)
          The blurb is not quite English and I can't guess exactly what
        is intended.

now on to slay the javadoc mess; someday perhaps I'll get to code.

--adrian

*********** Start Adrian notes ********************* 


Check:
  * Validate all the pom.xml files
        wget -c http://maven.apache.org/maven-v4_0_0.xsd
        bash
        for file in `find . -name pom.xml`; do \
          xmllint --noout --schema maven-v4_0_0.xsd $file; done

  * Find tabs
        find . -name pom.xml | xargs grep -C 5 '{Type ctrl-V then tab
        here}'

  * check into trunk (see what the differences are first)
        bash
        for file in `find . -name pom.xml` ; \
        do svn diff http://svn.geotools.org/geotools/trunk/gt/$file  \
            http://svn.geotools.org/geotools/branches/2.3.x/[EMAIL PROTECTED]
        \
            >> diff.text ; \
        done
        
*********** End Adrian notes *********************





-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to