Hi,

I'm working on the branch named "gt-prefix-removal", to complete and try 
finishing the work begun by Martin two years ago. The goal is to have 
something working on this branch, and then merge on the trunk.
This work has already been discussed, and it has given birth to the JIRA 
task : http://jira.codehaus.org/browse/GEOT-995.

Now, I've a precise question about the xml module called "xsd" in the 
extension folder. It *only* concerns the jar name, not the maven module 
name.
XML is redundant with the XSD notion, that's why XML should disappear in 
the jar name.

Do you agree with the name of the jar proposed as below ?

Current                         Proposed
------------------         -----------
gt2-xml.jar                   gt-ext-xsd.jar
gt2-xml-core.jar           gt-ext-xsd-core.jar
gt2-xml-filter.jar           gt-ext-xsd-filter.jar

XSD is the parent folder of core, and a couple of others. That's why I 
propose to put it in the jar name.

Another proposition could be :
gt-ext-xsd.jar
gt-ext-core.jar
gt-ext-filter.jar

For all modules, the final name is obtain like that (in the 
gt-prefix-removal branch) for the library module :
<build>
    <finalName>gt-lib-${artifactId}-${version}</finalName>
</build>
For example, gt2-main-2.5-SNAPSHOT.jar will become 
gt-lib-main-2.5-SNAPSHOT.jar.

That's why if I apply the same procedure on these modules (children of 
xsd), nor xml or xsd will be present in the jar name. Maybe Justin or 
Jody could be interested to keep the XSD name in these jars, that's why 
I'm requesting specifically your opinions :)

Kind regards,
Cédric Briançon.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to