Thanks Adrian for your pom cleaning!

Adrian Custer a écrit :
> 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.

We already know that Maven use this info for web-site generation. Example:

http://maven.geotools.fr/reports/referencing/license.html

As you can see, Maven copied the content of the URL in the "Project License". 
Currently, I put the URL to the full license text on the GNU web site, which 
may 
more than necessary (our 2 usual paragrah may be enough). My proposal is to 
replace the current URL by the following one:

http://svn.geotools.org/geotools/trunk/gt/licenses/Geotools.html

And also add any other relevant licences from the 
http://svn.geotools.org/geotools/trunk/gt/licenses/ directory.

If Maven can put this the license text in the web site, we could probably get 
Maven to put the license text in the JAR as well if wanted (providing that we 
write the necessary Maven plugin I guess - I have not hear about a standard 
Maven plugin doing that).


>   * Licenses
>           What does <distribution>repo</distribution> do?

There is two possible value: "repo" or "manual". Meaning is there:

http://maven.apache.org/ref/current/maven-model/maven.html#class_license



>   * 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.

Small trick for removing all tabs with Netbeans, providing that your Netbeans 
IDE is configured for using spaces:

   * Select the lines that may contains tabs.
   * Press "Shift tabulation" once for removing one indentation level.
   * Press "tabulation" for reinserting the indentation level just removed.

The "tabulation" or "shift tabulation" actions in Netbeans replace tabulations 
by spaces as a side effect.


>   * 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?

It is probably a remanescence of older pom.xml. A while ago, we had <version> 
in 
every projects. I realized later that it was not necessary. I though that I 
removed <version> from every pom.xml files (keeping only the one related to the 
parent pom.xml), but I may have forget some (or they may have been commited 
after I did my cleaning).


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

I not sure to understand what you mean. One thing that I would like (not sure 
if 
it was your point) would be to avoid to repeat <organization>, <timezone> etc. 
informations for every developpers. It would be nice if we could list all 
developpers or contributors in a separated file, list only their Id in relevant 
modules, and get Maven to complete the informations automatically. But I don't 
think that we can do that ourself easily if Maven doesn't support that feature.


>   * Descriptions
>           Add these, you lazy bums!

I agree :)


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

In http://maven.apache.org/ref/current/maven-model/maven.html , I found 
<comment> only for the <licences> section. But maybe the schema has been 
updated 
and the documentation is still behind?


>   * 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.

A search and replace should do the trick. I will try to do that tomorrow, 
hoping 
that I will not forget.


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

There is "dependencies" and "dependencies management". This is not the same 
thing. "dependencies" are the real dependencies. "Dependencies managements" is 
just a place where we specify the version number that dependencies in 
sub-module 
should use. Was it your question, or do I'm misunderstanding?

        Martin

-------------------------------------------------------------------------
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